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

[Antonio Larrosa Jiménez]

El Monday 29 April 2002 10:49, Neil Stevens escribió:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Monday April 29, 2002 01:11, Antonio Larrosa Jiménez wrote:
> > Perhaps others interpret my words in the same sense than you and what
> > happens is that really my arguments aren't understood.
>
> OK, here's how I read it:
>

You missed my "clear and explicit question", but I'm going to answer you 
anyway just to keep things clear.

> Martijn described a way to highlight the behavior that users may never
> guess on their own, and further showed a way to make the behavior
> configurable.  He pointed out that it's the way things have been done
> all over KDE.

Wrong. _I_ am the one that pointed out that people won't guess by their own 
that Ctrl-Enter submits (which is what Martijn wants to use by keeping a 
multilineedit). _I_ am the one that wants to make the behaviour 
configurable (by using QLineEdits by default and so, Enter submits and 
allow to set a checkbox that makes kopete use multilineedits, and so 
Ctrl-Enter submits, being completely standard comformant). And Martijn 
_and_ _me_ have always talked about making things standard comformant, 
noone said _never_ to make a multilineedit send on Enter, or use 
non-standard key bindings.

>
> Your reply dismissed it, implying that "IM clients" are special in some
> way.

They are special because _every_ application is special somehow and needs 
specific work to make it usable. Relying in a tooltip or ktip to tell the 
user how to use an application is bad design, and that's what I wanted to 
say. Of course, you can always tell people how to use an application in a 
tip of the day, but isn't it better if they don't have to read it and the 
application just "works as expected" ?

>
> And I replied, challenging that assumption.  Especially in the case of
> using KActions to get configurable key bindings, that's just how things
> seem to be done in KDE.

I don't have anything against using KAction (where did you read that?), I 
am against making bad default decisions that force people to use 
mega-cool-kaction key binding configuration dialogs to make things usable. 
Don't you really see anything wrong with that ?

>
> What didn't I understand in this sequence?
>

It's all above (and was in other mails in the thread if you would have read 
them)

And now _this_ is my last mail in this matter, please answer in private if 
you want to continue arguing.

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.