On Sunday 11 December 2011 20:19:31 Julius Schwartzenberg wrote:

> The offer of a special branch seems nice. I suppose that the kwin

> dependencies on libraries like kdelibs and Qt may not be that

> sophisticated that it would be possible to have a KWin version that

> compiles against the Trinity equivalents of these libraries. Maybe with

> trivial improvements on both sides, for example making certain Trinity

> APIs more KDE4-like or disabling certain advanced features on the KWin

> side (when compiling with Trinity), I could imagine the current KWin

> versions could be made source compatibile with Trinity.

Disabling parts of KWin is certainly the way to go. That's what we already do for Plasma Active (our mobile offerings). So this is certainly possible.

 

Now here the list of libraries KWin links against (from CMakeLists)

* ${KDE4_KDEUI_LIBS}

* ${KDE4_PLASMA_LIBS}

* ${KACTIVITIES_LIBRARY}

* ${QT_QTDECLARATIVE_LIBRARY} and kdeclarative

* kephal

* kworkspace

* kdecorations

* kwineffects

* ${X11_LIBRARIES}

* ${X11_Xrandr_LIB}

* ${X11_Xcomposite_LIB}

* ${X11_Xdamage_LIB}

* ${X11_Xrender_LIB}

* ${X11_Xfixes_LIB}

* ${QT_QTSCRIPT_LIBRARY}

* ${QT_QTXML_LIBRARY}

* ${OPENGL_gl_LIBRARY} or ${OPENGLES_LIBRARIES}

 

Some remarks for the specific imports:

= KDE4_KDEUI_LIBS =

Required for KWindowSystems. It is possible to split this out as done for WMIface[1]. So that it is a Qt only dependend library. For Frameworks 5 it will become an own library.

 

= KDE4_PLASMA_LIBS =

Required for integration parts in the effects and some other parts. Most likely we will be able to drop this dependency in 4.9 as we migrate these parts to QML and Plasma would only be a runtime requirement. This could be replaced by Trinity with QML files not using Plasma

 

= KACTIVITIES_LIBRARY =

Integration with Activities. Can be patched out.

 

= QT_QTDECLARATIVE_LIBRARY and kdeclarative =

In fact could be patched out, but not without losing large parts (e.g. Alt+Tab).

 

= kephal =

Small library for screen handling. Depends itself only on Qt and KDE_UI.

 

= kworkspace =

Some small libraries. Not sure at the moment why we need them (I think it was just for KActivities and they got moved out).

 

= kdecorations and kwineffects =

KWin internal

 

= Xlib stuff =

Yes we want that ;-)

 

= QT_QTSCRIPT_LIBRARY =

Already optional for scripting support.

 

= QT_QTXML_LIBRARY =

Will be dropped in 4.9

 

= OpenGL or ES =

both optional

 

Overall the dependencies to kdelibs will become better once Frameworks 5 is out. We currently have no plan to add more dependencies except Wayland ;-)

 

So I think from a Trinity perspective only the "Plasma" part is probably something not liked and that is probably going away or easily to patch out. It is only used for Plasma styled graphics view and I want to get rid of graphics view in the next cycle.

 

Cheers

Martin

 

[1] http://blogs.kde.org/node/4016

>

> In the end, the main question is whether it will be easier to maintain

> Trinity's TKWin or enabling source compatibility with KDE4's KWin. If

> you consider all the Freedesktop specs and how subtle WM bugs can be

> with different applications, I can imagine the second option is indeed

> the most attractive long term.

>

> ---------------------------------------------------------------------

> To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net

> For additional commands, e-mail:

> trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the

> Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not

> to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting