Message: previous - next
Month: December 2011

Re: [trinity-devel] Qt3 legal issues?

From: Darrell Anderson <humanreadable@...>
Date: Mon, 19 Dec 2011 12:33:28 -0800 (PST)
> Let's hope so. Anyway I had an idea about whole Trinity, I
> already
> talked about this with Calvin and he liked this idea.
> I'd split whole trinity into 3 components: Trinity Libs,
> Trinity
> Desktop Enviroment and Trinity Apps. And call the whole
> thing Trinity
> Project
> Trinity libs: qt3, tdelibs and other libs we provide
> TDE: things only needed for desktop Enviroment. panels,
> menus,
> kcontrol, kwin ecc...
> Trinity apps: apps based on Trinity libs, but which do not
> require TDE
> to be run.
> What do you think about it?
> Besides, split current tde* monolithic groups into single
> apps. Do we
> have any reason to keep them as they are?

As I just mentioned in another response, I VERY MUCH like the idea of modularization. I think that would be a great R15 priority. (R14 sorely needs to focus on paper cuts. :) )

One of the appealing aspects about GTK desktops is the significant availability of apps. For GTK users, building TDE in a similar manner would help induce users to pick and choose non GTK apps from TDE.

Not to mention reducing build and debugging issues. :)