KNotify-considerations for frameworks

[Eike Hein]

On 9/23/2011 2:36 AM, Albert Astals Cid wrote:
> I disagree, the fact that *all* KDE applications open the same dialog when you
> go to settings->configure notifications is a big plus. It adds consistency to
> the user experience and even if the dialog could be designed better (it works
> for me but things can always be improved) the user only has to learn it once,
> not per each and every application.

I'm with Albert here; retaining the default dialog is pretty
important imho.

In terms of my personal hopes for KNotify in Frameworks, it's
to finally deliver the extensibility that KNotify was origina-
lly planned to attain in KDE 4 already. What this means is to
improve the plugin support from compile time to runtime, allow
applications to ship plugins, and expose plugins in their
KNotify dialog. In other words, add new columns/checkboxes in
there. Then apps like Konversation which make use of KNotify
but also offer additional means of notification can unify in
the same dialog that the user already knows.

IOW the usability problem we have right now is not the KNotify
dialog, but rather that anything that goes beyond KNotify has
to be located elsewhere in the configuration UI. And no, this
isn't adequately solved by giving up on the KNotify dialog and
every app rolling its own notification config UI - that's
giving up on one of those important things that make KDE apps
feel so cohesive as you move from app to app. Rather, to re-
iterate, we need to make the standard UI extensible.



-- 
Best regards,
Eike Hein