Style guide decision needed (was: [Kopete-devel] Bug#40938: behaviour change request)
Antonio Larrosa Jiménez
larrosa at kde.org
Sun Apr 28 13:31:42 BST 2002
El Sunday 28 April 2002 13:26, Martijn Klingens escribió:
> On Sunday 28 April 2002 00:34, Antonio Larrosa Jiménez wrote:
> > IMHO, I think that most people (in fact, I :-) ) use kopete just like
> > any irc client. I have never seen any irc client where Enter didn't
> > submit what you wrote, and I think that's what it should do in kopete.
>
> And use shift-enter for newlines? Remember that MSN, ICQ, and most other
No, no. Read below or in my other mails.
> protocols explicitly support multi-line messages. I actually use that
> ability quite a lot. In IRC that is (unfortunately, IMO) not even
> possible, which is why the enter key is available for whatever you want.
> Also, I think ctrl-enter should be a secondary key binding in single
> line edits, so that one just 'always' works, and normal enter being a
> convenience key in those cases where it doesn't conflict.
>
Yes, perhaps that would be nice, but IMVHO, not enough.
> > I've used kopete some times to talk with some MSN users friends and I
> > always found annoying that I had to move my hand to the mouse and
> > click submit to submit the text I wrote.
>
> Wow... That's a long time ago then :-) I hacked the ctrl-enter into the
> MSN dialog even before Kopete moved from SoruceForge to KDE CVS, so
> apparently you're a long-time user :P
I'm afraid I'm not, I just used it since it moved to kde cvs, but I never
found Ctrl-Enter until someone said it in this thread (again, imagine when
will the average user find it).
>
> > And no, nobody will find out that Ctrl-Enter submits it, at least not
> > "normal users".
>
> That's the single true argument against it for MSN users. ICQ users and
> KMail users are already used to the key, so they will find out. For MSN
I thought Ctrl-Enter was bound to "send mail now". I never thought
Ctrl-Enter was a way to submit what I wrote since a mail is much different
than a sentence (which is what I send to the people I talk to, as opposed
to people I write to, just sentences, in separate lines).
> (which uses enter in MS' own client) you're right.
>
It's not only about MS's client (which I never used so I don't know how it
works), but about intuition. In a shell, Enter executes (submits) the line
that you wrote while you have to do something different (writing \ at eol)
to execute (submit) multiple lines at once. Of course, we shouldn't force
the user to write \ to provide multi line edits, but I think providing an
option to use single line edits (by default) or multilineedits would be
nice.
> > Note that I'm not talking in general, but about kopete dialogs. I
> > don't care about multilineedits or lineedits, but I think Enter in
> > kopete should submit and if that means changing the multilineedit for
> > a lineedit just for consistency with Enter behaviour, I vote for that.
>
> You can't. You must be able to support multi-line messages!
>
IMHO kopete should always support them on "receive", but only to send them
when the appropiate option is set (_and_ show a message box when the user
checks the checkbox which says "In order to provide multi line messages,
you have to press Ctrl-Enter to submit your message while Enter just adds
a new line" ).
Greetings,
--
Antonio Larrosa Jimenez
KDE Core developer - larrosa at kde.org
http://devel-home.kde.org/~larrosa/
KDE - The development framework of the future, today.
More information about the kde-core-devel
mailing list