On 15-06-2010 at 19:28:48 Aaron J. Seigo <ase...@kde.org> wrote: > On June 15, 2010, Emdek wrote: >> Om 15-06-2010 at 09:58:21 Anton Kreuzkamp <akreuzk...@web.de> wrote: >> > I think I can have a look at it at the weekend. >> > But I'm a really unexperienced programmer so don't have too much hope >> (I >> > will >> > report if I'm able to do it) >> >> Well, I was working on launchers support for my applet Fancy Tasks that >> currently uses this library and I can say that I'm not sure if it's good >> idea to extend current library. > > as someone who has worked on libtaskmanager for a number of years now > (inhereted it from other kind and talented souls), all i can say is that > in my > humble opinion you are completely wrong. > > adding launchers to libtaskmanager would not be complex at all: they > would > simply be static entries read from a KConfigGroup passed in to > GroupManager. > this new class would probably be a subclass of AbstractGroupableItem and > would > group with windows of the app's type. > > the menus are provided by libtaskmanager, all window interaction is > provided > by libtaskmanager, all grouping is done by libtaskmanager ... which > means very > little would need to be done to the tasks widget to support these changes > (mostly just configuration stuff). > > it's not only doable, it shouldn't overly difficult.
Well, this was discussed already at least one time. In case of my project it's simply easier and better to write own library (but it will look more like data engine, or few engines combined) also because of other things that need to be done (like jobs progress visualization and other strange stuff) and for sure are not needed for default task manager applet. I hope to finish most important part before August and then everyone will have possibility to see if it's useful or only experiment to gain more experience. -- Best regards, Michal _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
