Preparing terrain for kio_uiserver

[Robert Knight]

> That's why people shouldn't be changing their job icons. They should stick
> to the default, which is the application's name.
> Now, if the icon given could not be found (definitely a bug in the
> application),

Jobs may be launched by KDE daemons and other processes such as the
panel which do not have an associated icon however - at least, not an
icon that the user would recognise.  In such cases I think it would be
useful to allow the developer to specify a custom icon.

Another use case is where one application might launch various types
of jobs.  In which case the basic application icon could be
'decorated' to provide better visual cues as to which jobs are
currently in-progress.




On 24/12/06, Thiago Macieira <thiago at kde.org> wrote:
> Robert Knight wrote:
> >I understand.  Is it not possible to look up the icon via other means?
> > I am just concerned that someone could change the name of an
> >application and forget to change the KIO name.  Also in some cases
> >there won't be a proper icon for the application, and I think it would
> >not look good to show the generic blue gearwheel icon which is
> >currently displayed around KDE to indicate an application without a
> >custom icon.  Perhaps it would be better not to show an icon at all
> >unless one is explicitly set using setJobIcon().
>
> That's why people shouldn't be changing their job icons. They should stick
> to the default, which is the application's name.
>
> Now, if the icon given could not be found (definitely a bug in the
> application), an error message should be printed to stdout using kWarning
> and maybe no icon should be shown.
>
> --
>   Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
>     PGP/GPG: 0x6EF45358; fingerprint:
>     E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
>
>