--===============1141133873== Content-Type: multipart/alternative; boundary=bcaec53af292ec82e204a75a7e9d --bcaec53af292ec82e204a75a7e9d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Artem, I've made mock http://bit.ly/nrvZdP. It should let make anyone to edit, do not hesitate to try it out :) Its made in 2 column layout, similarly as Network manager or upcoming Telepathy plugin. All services are separated into 2 groups : services, that are usefull for > user. E.g. "Strigi" or "Backup" and services, that are not usefull for us= er > ( Nepomuk system services ) > I would let user to decide himself. See star in top corner on mock. Every plugin has 2 operation modes: 'user' and 'advanced'. These 2 models > _only_ differ in exporting extra actions to the menus. > Wasn't regular and advanced modes abandoned within KDE some time ago? if i recall right, the consensus was, either options should be made useful for every users, or it shouldn=E2=80=99t be at all? And of course, the name and description of the service is available to the > GUI. > > That is currently all info, that plugin export to GUI. But I am open for > implementing methods if there will be necessity in extra information. > > Currently, applet creates one standard widget for every service. It is > shown on the first picture. If 'Show all services' is checked, then all > widgets are shown, if unchecked - only widges from first group. > In network manager + More / -Less button looks cleaner option than check bo= x with "show all" Tooltip prints one of: > "All services running" > "Not running X Running Y", X,Y - numbers > "No service running" > (This is unlocalized strings of course. No idea what they will be after > translation ) > is it possible to distinguish b/w services who does not run, because they failed and services that was disabled/stopped be esplicit user action?. If so, names of failed services could be showed in the the tooltip. 1. The systray tooltip provides information about the > number of running services. This is of no interest to the user. The curre= nt > systray shows the indexing state. While this is rather random it puts use= rs > at ease when nepomuk uses resources. It might make more sense to allow th= e > plugins to provide useful information in some way (that is if you are fix= ed > on the whole plugin design which IMHO is a bit over-engineered). > Colors could be used to provide useful info: Green - all ok; Red - somethin= g failed; Yellow - either resource hungy procces or some user attention is required. 2. The main widget is not very pretty. It shows non-localized service names > and uses a list with buttons that do not fit the rest of KDE. That's why i labeled Nepomuk as Search indexing - more understandable strin= g for the user. Full service name could go under description, if logo is not enough to identify it > It would be much more helpful to have generic information in there like t= he > current systray widget does. Seeing the state of services is not interest= ing > to the user. It is an implementation detail! Only color indicates state. 24*24 icon takes little space, while the rest o= f the line could be used for human friendly information. For the right side of plasmoid. Try to avoid intermediate dialogs as much as possible. E.g. to let user create new backup instructions, have big button for that i= n the UI, instead of having big button to configure global backup settings, and then hide it somewhere under menus in new window. Imho global configuration could be placed next to start/stop/... service buttons below service title. Also when action buttons makes UI look cluttered, it is allways possible to display/fadein only on hover. Cheers, Lukas --bcaec53af292ec82e204a75a7e9d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Artem,

I've made mock http:/= /bit.ly/nrvZdP. It should let make anyone to edit, do not hesitate to t= ry it out :)

Its made in 2 column layout, similarly as Network manag= er or upcoming Telepathy plugin.


All ser= vices are separated into 2 groups : services, that are=20 usefull for user. E.g. "Strigi" or "Backup" and service= s, that are not=20 usefull for user ( Nepomuk system services )
=C2=A0
I would let user to decide himself. See star in top corner on mock.=


And of course, the name and description of the service is available to t= he GUI.

That is currently all info, that plugin export to GUI. But I am open for implementing methods if there will be necessity in extra=20 information.

Currently, applet creates one standard widget for=20 every service. It is shown on the first picture. If 'Show all services&= #39;=20 is checked, then all widgets are shown, if unchecked - only widges from=20 first group.
=C2=A0
In network manager + Mor= e / -Less button looks cleaner option than check box with "show all&qu= ot;


Tooltip prints one of:
"All services running"
"Not ru= nning X Running Y", X,Y - numbers
"No service running"(This is unlocalized strings of course. No idea what they will be after tr= anslation )
=C2=A0
is it possible to distinguish b/w servic= es who does not run, because they failed and services that was disabled/sto= pped be esplicit user action?. If so, names of failed services could be sho= wed in the the tooltip.


1. The systray tooltip provides information about the
number of running services. This is of no interest to the user. The current=20 systray shows the indexing state. While this is rather random it puts=20 users at ease when nepomuk uses resources. It might make more sense to=20 allow the plugins to provide useful information in some way (that is if=20 you are fixed on the whole plugin design which IMHO is a bit=20 over-engineered).

Colors could be used to provide = useful info: Green - all ok; Red - something failed; Yellow - either resour= ce hungy procces or some user attention is required.
=C2=A0

2. The main widge= t is not very pretty. It shows non-localized=20 service names and uses a list with buttons that do not fit the rest of=20 KDE.
=C2=A0
That's why i labeled Nepomuk as = Search indexing - more understandable=20 string for the user. Full service name could go under description, if=20 logo is not enough to identify it
=C2=A0
It would be much more helpful to have = generic information in there=20 like the current systray widget does. Seeing the state of services is=20 not interesting to the user. It is an implementation detail!
=C2=A0
Only color indicates state. 24*24 icon takes little spa= ce, while the rest of the line could be used for human friendly information= .

For the right side of plasmoid.

Try to avoid intermediate dialo= gs as much as possible.
E.g. to let user create new backup instructions= , have big button for that in the UI, instead of having big button to confi= gure global=C2=A0 backup settings, and then hide it somewhere under menus i= n new window. Imho global configuration could be placed next to start/stop/= ... service buttons below service title.

Also when action buttons makes UI look cluttered, it is allways possibl= e to display/fadein only on hover.

Cheers,
Lukas
--bcaec53af292ec82e204a75a7e9d-- --===============1141133873== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kde-usability mailing list kde-usability@kde.org https://mail.kde.org/mailman/listinfo/kde-usability --===============1141133873==--