Hello, After cleaning up the tasks dataengine (i know it is not really used in the applet..), I'd also like to help out. I looked at the tasks applet code a while back and indeed it is a bit scary.
However, school is busy and I can't really promise anything. If there are some "simpler" things to do, I may find the time to pitch in a little. Alain. Aaron J. Seigo wrote: > hi... > > i'd like to have a tasks widget hacking day. > > the reason for this i that the code is something of a mess internally and > imho > it's unmaintainable in its current state. i say this because changing little > things in one place often create rather unexpected results; there's a good > amount of unreachable code; there's what looks to be some pretty obvious > memory leaks (e.g. Tasks::m_groupTaskItems never seems to have items removed > from it!); Tasks does bookkeeping, but for only some things, and this > bookkeeping is controlled from Tasks, LayoutWidget *and* TaskGroupItem! > > there are bugs that sometimes results in "holes" showing up in the layout, > grouping not working reliably on start up and more. > > if we ship with it like this, we will hate ourselves later. > > unfortunately, i'm not particularly sure what all the reasons and rationals > are for some of the code decisions. > > so if you have been working on the tasks widget in the last month or two, > please respond in this thread with when would be a good time and day for you > so we can get together on irc and sort this thing out. =) > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
