-3

This Idea is about an Abstraction Layer (I'm going to call it Workspace) for realizing a complete separation between the logic of a program and the GUI.


As you can see an Application that wants to show a window goes to Workspace and sais "Hey I want a window, with a menu bar, and here a Button and here an Editor"
Workspace now goes to an library, which provides the needed Elements (in the example Plasma) and for the wanted Editor it goes to Kate, Workspace joins this parts together and gives the result to KWin.

This concept has two big advantages:

• An Application which uses that Concept doesn't have to care about which GUI-Library the user uses (so an Application can use GTK for Gnome and Qt(or maybe Plasma) for KDE, of course just if KDE AND Gnome would use this concept)
  
• With this Concept an Application could without any problems say "Hey I want a Plasmoid" or sth. like that.
  

KDE depends on Qt. I mean everything about KDE. Doing this would require completely re-doing almost all of KDE from the ground up. This is the sort of thing we might have a slight chance of seeing in KDE 6.x at the earliest. If you want this it would probably be just as easy to make an entirely new desktop environment from scratch.

I don't want to say that everything is made over this AL, It don't want that a KDE-program won't have Qt as dependency.
It just thought to organize the GUI over "Workspace".
Maybe I have to change the sentence
"An Application which uses that concept doesn't have to care about which GUI-Library the user uses"
to
"All Applications, using this concept would have an unified look, independent from whether they use Qt, GTK or whatever"

Currently all applications do care, so changing that requires a rewrite. So...

Besides all KDE programs will use this feature for nothing since Qt can pretty much display itself using GTK anyway. And GTK programs... remain GTK programs and will not be affected in any way.

This probably should be some freedesktop standard or something to have any chance of success.

Actually I worked on similar framework. Application can deliver custom GUI definition in minimal set of common element. It's like connection of XUL with XSLT - application have definition of many windows and tells: create rip window, I handle thats buttons, etc. If user have defined another GUI for rip window, libraries would use system wide definitions.

Also, there's can exists different GUI definitions for each system, libraries(QT/GTK+).

If somebody are interested in cooperation, please contact.

I'm moving this to wontfix. This is simply not going to happen any time in the next decade or so.