Style guide decision needed (was: [Kopete-devel] Bug#40938: behaviour change request)

[Rob Kaper]

Dear kde-core-devel, this is a rather hot GUI issue currently discussed for
Kopete, lacking any style guide coverage. Please read and discuss, it would
be fruitful to address the issue and improve the style guide and have a
decision to fall back on.

On Fri, Apr 26, 2002 at 12:54:08PM -0500, Nick Betcher wrote:
> We've all given examples and counter examples as to which applications use 
> Enter as their line feed or sending/executing and that proved to be useless.

I don't care what Licq, Windows ICQ version *, GAIM, Trillian or whatever
do. I care about consistency within KDE.

> I'm just quite sick of hearing about how Enter should and shouldn't send a 
> message, we have better things to be doing.

I will accept *any* solution as long as it adheres to the style guide. Too
bad there is nothing in the style guide about this behaviour.

http://developer.kde.org/documentation/standards/kde/style/keys/cursorKeys.html

seems most qualified to be updated, though.

I think we need to decide this on core-devel now and implement it
consistently within all of KDE.

With KHTML and other KDE applications in mind, I really think it is most
consistent to use Enter as newline and Ctrl-Enter as "submit" shortcut (I'd
love that in KHTML in lineedits and textedits).

Simplifying Kopete to make Enter submit the data might be a handy *option*
for those who only send one-liners, but the default should be to not do so
because 1) it is more consistent with the whole of KDE and 2) you cannot
assume other people use a text edit for one-liners as well while it is
reasonable to expect users to use a multiline text edit for multiple lines.

Rob
-- 
Rob Kaper     | "This [party] is your idea of hell?"
cap at capsi.com | "Actually, in hell you tend to know a lot of the people"
www.capsi.com | -- Cordelia and Angel, "She"