I agree, but let's not make of this redesign project too much a big deal. I think we're better to follow an evolutionary path, by evolving iteratively the current codebase. I'm afraid that if we want to include too many changes in a "new GTG", the project will stall again. We already made that mistake, let's not do it again.
You're right. I propose to do that as a standalone change to GTG before integrating a new design into GTG. It would result in less work and a nicer implementation. There is ongoing GTG web initiative, they will need it soon too.
So, in summary, I think we should consider a "client-daemon" as actually being independent of GTG redesign. It should figure on our roadmap, but not be a dependency of the UI redesign.
BTW: I've updated our Roadmap to the current state: https://live.gnome.org/gtg/Roadmap
Izidor _______________________________________________ Mailing list: https://launchpad.net/~gtg-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~gtg-contributors More help : https://help.launchpad.net/ListHelp
