Linked by David Adams on Wed 2nd Jul 2008 16:11 UTC, submitted by elsewhere
Permalink for comment 321042
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
Linked by Thom Holwerda on 06/14/13 11:39 UTC
Linked by Thom Holwerda on 06/14/13 11:32 UTC
Linked by Thom Holwerda on 06/13/13 19:39 UTC
Linked by Thom Holwerda on 06/13/13 14:45 UTC
Linked by Thom Holwerda on 06/13/13 11:43 UTC
More News »
Sponsored Links



Member since:
2007-08-03
"As long as there is no forking of the underlying core libraries I fail to see what the problem is."
The way I look at it, Plasma is *explicitly designed* to have a new "desktop" built on its technologies: the "desktop" background is designed to be replaceable; the panels are designed to be replaceable; core components like the taskbar, menu etc are designed to be replaceable; etc. As the scripting support and other core technologies mature, these items will eventually be able to be replaced simply by browsing with Hot New Stuff and seeing what pre-made desktops are available.
I'd look on a clone of OS X's dock - or indeed, of KDE3's kicker and kdesktop - written with libplasma as as much of a "fork" of Plasma as a new Firefox theme and an extension that grants it extra functionality is a "fork" of Firefox.
Edit:
Damnit, should've refreshed: Richard said everything I wanted to say already.
Edited 2008-07-02 18:48 UTC