------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=76583
------- Additional Comments From handsclark gmail com 2007-11-14 15:43 -------
Configuration "bloat"....
It kills me when I see terms used so much that they lose all meaning. Just
because you don't want to spend a couple minutes thinking of a way to implement
this does not mean that there isn't a clean way to implement the feature.
I would think that many people only use Kopete with one protocol, and for those
who do use it with multiple protocols there isn't a problem presenting them
with a very clean interface similar to the one that is used now. Allow users
to choose a default emoticon set in the same way that it is done now. Then,
just add a button or tab that would only be accessed for deviations from the
default. A user could then choose to only change the emoticon set with one
protocol or all of them depending on preference and use.
I imagine that for stability and consistency reasons it would be best to use
some kind of default emoticon set anyway. So, an exception list is both
practical and clean from a configuration standpoint.
Oh, and the standardization across protocols...
I realize that development time and effort being expended here isn't free. So,
it does make sense that the program itself have a certain amount of
consistency, but with the protocols themselves behaving in so many different
ways and having inherent differences in capability, I don't entirely understand
that argument. In fact, it doesn't make much sense in an area where even one
protocol behaves in a distinct manner from the rest. I see emoticons being
such an area of concern.
_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel
