On Saturday 10 December 2011 13:35:38 Timothy Pearson wrote:
> >> Does it drag in other KDE 4 dependencies?
> > Obviously it depends on kdelibs and kde-runtime like any KDE application.
> > The
> > dependencies will of course be better once frameworks 5 are released.
> > Considering the impact on a running environment I would say that all
> > depends
> > whether your users are using any KDE 4 applications or none. I would be
> > surprised if your users would use no KDE 4 applications. So I think it is
> > negligible.
> Right away AFAIK we would lose DCOP integration,
which should not be any issue for a window manager. Window managers use X for
IPC as well you get D-Bus integration. Given that in the long run you want to
migrate to Qt 4 and with that D-Bus anyway this sounds to me like a clear
> the window styles that come with TDE
you are aware that KWin 4 ships the same window decorations (some got moved to
kdeartworks) plus a theme engine? Do I have to point out that you broke all
3rd party decorations for kwin3 in such a way that kwin won't start if you
selected one of those?
> , and the kcontrol integration.
Which is no issue as KWin allows to access the complete configuration from
each window. You could even ship the old KCMs for KDE 3.5 as those have hardly
> Users can already run
> different window managers (compiz anyone?) so I would say this decision
> should be made on a per-user basis. A set of instructions on the Wiki for
> configuring a users' session to use kwin4 wouldn't hurt. ;-)
I can only recommend you to consider this offer from our side. Think about
what you actually want for your users. What is really important to you and if
you really want to develop a window manager.
> To unsubscribe, e-mail: trinity-devel-unsubscribe@...
> For additional commands, e-mail:
> trinity-devel-help@... 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