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

[Waldo Bastian]

On Friday 26 April 2002 04:34 pm, Rob Kaper wrote:
> 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).

Sounds fine with me. Something like

"Enter" Will ok/submit/send in situations where only 1 line-edit is available, 
but not in case of multi-line-edits or multiple line-edits.

"Ctrl-Enter" Will always ok/submit/send.

Cheers,
Waldo