faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Thanks for resisting peer pressure and waiting
by T. J. Brumfield on Saturday 01/Dec/2007, @20:20
|
Yes, but we're not at the future yet. With the bugs and speed issues of Kwin at the moment, I think many will be using compiz-fusion at launch.
I still think they should have worked to incorporate existing compiz-fusion core into Kwin, and allowed Kwin to just use compiz-fusion plugins.
|
[
Reply To This | View ]
|
Re: Thanks for resisting peer pressure and waiting
by Paul Eggleton on Saturday 01/Dec/2007, @20:47
|
If you watch the talks given the last two years at Akademy by Lubos Lunak, he explains why this was not done.
|
[
Reply To This | View ]
|
Re: Thanks for resisting peer pressure and waiting
by T. J. Brumfield on Saturday 01/Dec/2007, @22:47
|
Could someone please sum up these statements?
Living in the US, I can't make it out to Akademy.
|
[
Reply To This | View ]
|
Re: Thanks for resisting peer pressure and waiting
by Paul Eggleton on Saturday 01/Dec/2007, @23:57
|
Neither can I, but you can do what I do, which is to watch the videos recorded at the conferences:
http://home.kde.org/~akademy06/videos/
http://conference2007.kde.org/conference/programme.php
(some of them have some encoding problems, you just have to put up with the frame freezing)
|
[
Reply To This | View ]
|
Re: Thanks for resisting peer pressure and waiting
by Luca Beltrame on Sunday 02/Dec/2007, @00:06
|
Basically Beryl/Compiz Fusion just exposes its internals for plugin writers (instead of having a good API), therefore re-using its plugins it's not possible.
|
[
Reply To This | View ]
|
Re: Thanks for resisting peer pressure and waiting
by Diederik van der Boor on Monday 03/Dec/2007, @00:12
|
Some reasons not to use Beryl/Compiz:
* The "API" for plugins was using internals directly. So it's not usable outside Beryl.
* Effects happen to be a small portion of the window manager code. (like 10% for the total code)
* Window management is quite a black art. It was better to add effects then to throw all good code away.,
|
[
Reply To This | View ]
|
Re: Thanks for resisting peer pressure and waiting
by T. J. Brumfield on Monday 03/Dec/2007, @12:23
|
I didn't suggest that you throw out Kwin. I suggested you include the 10% of effects code from Compiz-fusion into Kwin, and try to stabilize a plugin API that both Compiz-fusion and KDE can use.
|
[
Reply To This | View ]
|
Re: Thanks for resisting peer pressure and waiting
by Anon on Monday 03/Dec/2007, @12:28
|
Frankly, re-implementing the effects would be far easier than a) persuading the Compiz Fusion guys to re-architect everything so that they have a neutral API and port all their plug-ins to it just so KDE can use them and b) actually doing the changes once you've somehow managed to persuade them and c) porting KWin and all its effects to the new API.
|
[
Reply To This | View ]
|
|
Re: Thanks for resisting peer pressure and waiting
by Nobbe on Sunday 02/Dec/2007, @18:19
|
I read here on the dot (I believe) some time ago that kwin implemented compiz like functionality in a trivial amount of code. Compiz is something like research and kwin is something like realistic implementation of said research. Compiz is huge and buggy whereas kwin has all the kinks worked out, is lean, and is fast. This is mainly because it has been around for over a decade (right?). Last I checked the devs did make sure it works with 4.0 anyway ;) Guess that goes along with the whole "future proofing" idea as well.
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
