Re: Fragmentation

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: Fragmentation
by Anon on Wednesday 30/May/2007, @23:56

"I can't imagine adding the same fixes that were in kwin's code base to theirs for whatever application we've still not heard of that fails would be that hard. I REALLY doubt it would be anywhere near as hard as duplicating that much of Beryl's functionality was."

[~]>cd kdebase/workspace/kwin
[~/kdebase/workspace/kwin]>(find . -iname "*.cpp"; find -iname "*.h") | xargs cat | wc -l
65271
[~/kdebase/workspace/kwin]>cd effects
[~/kdebase/workspace/kwin/effects](find . -iname "*.cpp"; find -iname "*.h") | xargs cat | wc -l
7277

So the sum of "that much of Beryl's functionality" is about 11% of the codebase of kwin. You seem to think that adding an expose clone is some kind of momentous achievement that must have taken masses of hard code to duplicate. In fact, all it took is this:

http://websvn.kde.org/trunk/KDE/kdebase/workspace/kwin/effects/presentwindows.cpp?view=markup

A mere 700 or so lines of code, a lot of which is boilerplate. That neat grid?

http://websvn.kde.org/trunk/KDE/kdebase/workspace/kwin/effects/desktopgrid.cpp?revision=669033&view=markup

A mere 500 or so lines of code. That spiffy "live thumbnails on the taskbar" effect?

http://websvn.kde.org/trunk/KDE/kdebase/workspace/kwin/effects/demo_taskbarthumbnail.cpp?view=markup

About 100 lines.

I'd also remind you that kwin has been under development since KDE2.0, whereas the entirety of the effects you see here - whose development was most definitely not the sole focus of Lubos, Rivo and Phillip - has occurred since October of last year.

I really don't don't know how Free Software developers do it - being constantly criticised based on the thoroughly misinformed guesses of random strangers all day long would probably make me quit in disgust. The fact that they don't makes me respect them all the more. Keep it up, ladies and gentlemen - your work is much appreciated :)

Related Links

·   Articles on KDE Public Relations and Marketing
·   Also by Anon
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Fragmentation
by b on Thursday 31/May/2007, @00:24

> I really don't don't know how Free Software developers do it - being
> constantly criticised based on the thoroughly misinformed guesses of random
> strangers all day long would probably make me quit in disgust. The fact that
> they don't makes me respect them all the more. Keep it up, ladies and
> gentlemen - your work is much appreciated :)

I agree. I guess you really have to have a "thick skin" to endure all this false claims...
So, a big thank you to all devs!

[ Reply To This | View ]

Re: Fragmentation
by Brotherred on Thursday 31/May/2007, @01:02

"I really don't don't know how Free Software developers do it - being constantly criticised based on the thoroughly misinformed guesses of random strangers all day long would probably make me quit in disgust. The fact that they don't makes me respect them all the more. Keep it up, ladies and gentlemen - your work is much appreciated"

Okey on that you got me. Clearly I am coming at it from a end user and New user perspective. As I said I was glad I was very glad to see Compas and Beryl join forces again, for reasons I have made clear.

Gnome and KDE have came from different areas and methods and that is all cool. Now however they have been agreeing on common APIs and that to me is a win for all and that with in their own idea of how each is wanting to do things.

I still can not get passed how commercial developers will not know what to do with now not only two different sets of window manager APIs that are not completely merged but now three (two??) different 3D compastating options.

All very confusing and I watch this stuff constantly just like the rest of you.

[ Reply To This | View ]

Re: Fragmentation
by John Tapsell on Thursday 31/May/2007, @05:41

I'm not sure how likely it is that commercial developers would want to write a plugin for beryl/kwin.

If you mean general composite stuff that an app would use, then that is totally standard, and is done by the x server.

Any gnome app using composite will work in kwin and vice versa. Everything is standard except the plugins, and that's a tiny amount of the code.

[ Reply To This | View ]

Re: Fragmentation
by Andrew on Thursday 31/May/2007, @13:30

Thank you for giving specific information. As much as I might tend to agree with the original author, it is sad that I had to dig this far into the comments to find specific information about what was implemented. From an initial reading of the article, it DOES sound like an ego issue. Thank you, Anon.
--Drew

[ Reply To This | View ]

Re: Fragmentation
by Nobbe on Friday 01/Jun/2007, @03:38

*clap* *clap* *clap*

I enjoy being a bystander, well said sir!

"I really don't don't know how Free Software developers do it - being constantly criticised based on the thoroughly misinformed guesses of random strangers all day long would probably make me quit in disgust. The fact that they don't makes me respect them all the more. Keep it up, ladies and gentlemen - your work is much appreciated :)"

Yeah as far as I can tell, Free Software people take a lot of shit all day long. Just from reading the planet and peeking in on some blogs you can see what some KDE devs have to put up with! I suppose KDE really is a labor of love.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"KDE: Get Over It!" -- Ivan E. Moore II
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.