just for your information - I'm in contact with Martin Gräßlin, the kwin maintainer. It looks like the work on reduce KDE dependencies for kwin. For now we discuss options to
- build kwin standalone; out of kde-workspace infrastructure
- build it with or without optional KDE dependencies.
The original idea (by Martin) is to allow another DE, like Razor-qt is, to use kwin without KDE deps. So in the future we can have 2 non-conflicting versions of kwin based on one source code:
- kwin, a full KDE build with deps to kdelibs, plasma, whatever
- razor-kwin, a reduced version with deps to Qt only probably. With less effects but with hooks to custom tools (alt+tab...)
The special branch for this project will be announced soon. I hope some of us can help with these tasks too.
Also I'd like to point that initiator of this activity is Martin, that's really, really cool!
cheers,
petr
> --
> You received this message because you are subscribed to the Google
> Groups "Razor-qt" group.
> For more options, visit this group at
> http://groups.google.com/group/razor-qt?hl=en
Regards.
--
Maciej Płaza.
On Tuesday 28 February 2012 16:48:44 Jerome Leclanche wrote:
> This is so great. I was looking into it a couple days ago, but this is
> great news.
>
> Kwin is a really good WM. It does have a couple of issues which openbox
> does not... will have to make a list some time.
>
> What does kwin depend on KDE for?
>
On my distro as with most IMO, it depends on kdeworkspace.
On Feb 10, 2012 (Friday), at 8:33 AM, Martin Gräßlin wrote:
On Feb 9, 2012 (Thursday), at 9:45 AM, Martin Gräßlin wrote:
I am the maintainer of KDE's compositor and window manager KWin, which
is
one of the window managers supported by Razor-Qt. I wanted to discuss
with you what we (KWin and Razor team) can do to increase the
integration. From my side I would be most interested in knowing what we
can do to make KWin the default window manager in Razor :-)
the basic thing for us would be to reduce required dependencies. I'm not
sure what's kwin linked to now (sitting in front of the mac). But also
distro dependencies. For example: I prepare virtual images for my company
customers with X11/Razor (it was KDE4 based before but now I can save
almost 40% of size what is quite important for download).
Yes that is in general a problem of all KDE applications and because of
that we are working on Frameworks 5 :-) After that I expect that KWin
will be almost Qt only. I investigated the efforts to get it Qt only some
weeks ago and the main problems currently are:
* kDebug statements
kDebug should be easyActually no as we have own hooks to pass internal classes to kDebug. Also it's
* KConfig
kConfig cold be a little bit harder. I did not examine it more but maybe
it's used only in one place (few places) so it can be conditionally
replaced with qsettings/whatever.Yes that was an idea I had as it should actually be just one class which reads
* KStandardDirs
The same as above.Yes, unfortunately also quite spread over the complete codebase and rather
* KWindowSystem (part of KWin is in kdelibs)
At least the last item will be solved by Frameworks and could even be
solved today by just compiling the files together with KWin.
if I understand it correctly - the "frameworks" will be something like split
kdelibs into smaller chunks?exactly and I hope that Razor can benefit from it as you can just depend on
Inside workspace KWin depends on Kephal, which is something on my kill
list
anyway and the activities which are optional anyway.
kephal can be replaced by QDesktopWidget if I undersatnd it correctlykephal is in fact just a wrapper around QDesktopWidget - that's why I want to
So - I think any big changes are not allowed in KDE 4.x lifecycle, correct?
So what's your roadmap? Branching?Yes, my current plan is to prepare a branch and as a first step allow to build
> I think it's too much work. Better to take something small,
> understandable and manageable and improve it. Something easy to merge
> in the git code.
>
> Currently QLWM code which quite simple, easy and manageable, allowing
> others to understand and make improvements, not so har for others its
> important due so then, many can contribute to the project RazorQT more
> easile, to advance more quickly ..
>
> So must take into account the time spent coding respect the every day
> life of each one of us, as well as the responsibilities...
>
> http://qlwm.get.to/
is QLWM compilable with later Qt4?
There is no problem to run QLWM with razor if it follows freedesktop standards.
So for me (personally) there is no free resource to hack a window manager. So if you or anybody else will prove that QLWM is usable and compilable I can create packages for rpm based distros to be used with razor...
QLWM have a qt4 version, of course, now its qt4 app..
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Cofundador de Venenux; debian based multimedia alike free only
zealots users (oh well, i try but..too many free guidelines buahhh)
http://shutendouji.net
creador de massenkoh linux; debian enhanchements for better up to date
support on stable brand, including non-free soft.
The idea its merge code and make a WM based on QLWM.. not implement a
WM over razorqt..