On 06/30/2011 09:17 AM, Reindl Harald wrote: >> >> right - and the default (I believe) for google-chrome is to use its >> own - which is DE independent :-) > > and the worst solution > > i wonder that there was no common used solution on unix-like systems > the past ten years to avoid such problems in the future > > A library of tools is a good solution - but YAD (yet another daemon)with inadequate service is not (e.g. seahorse). Its also not terribly hard to do - so the need to use a common one is pretty low - but would be convenient if they all used the same database store (and have choices what the store is - at least for the local storage - for remote store (which chrome also uses) - the issues are a little different). Perhaps a clear definition of the goals, needs and how UIs work - and how the common applications could use this API and benefit would be helpful to would be tool builders. gene/ _______________________________________________ kde mailing list kde@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
