Linked by vivainio on Thu 14th Oct 2010 11:31 UTC
KDE In his lengthy and interesting blog post covering the future of Plasma, KDE's Aaron Seigo proposes Qt Quick and QML (a declarative language that embeds JavaScript) as replacement of the Graphics View architecture currently used by Plasma. This holds a promise of massive speedups and cheap effects as all paint operations become candidates for OpenGL acceleration, contrary to the aging Graphics View architecture that is still stuck with various inefficiencies caused by the underlying QPainter approach. Expressiveness and easy programmability of QML is a nice bonus, of course.
Permalink for comment 445053
To read all comments associated with this story, please click here.
RE[4]: ...
by Hiev on Thu 14th Oct 2010 13:53 UTC in reply to "RE[3]: ..."
Member since:

The fact that all plasma widgets will have to be migrated to QML eventually or not is a lot of change, a lot of work, alot of testing, a new start over, is like admiting that the things were wrong in the beginning and now have to be corrected, tha impact is not only on the visual side, but also in the python and ruby bindings and if you say is doable it may be, but not w/o a lot of work and testing before. So it feels so frustrating that now may be mandatory to write plasma widgets in QML, and throw away many invested time.

I think it sucks when you don't control the toolkit and the one who controls it makes these low moves that makes you change lots of stuff.

Time will tell, In a couple of years will see how it goes and how mutch was won or lost in that period.

Edited 2010-10-14 14:04 UTC

Reply Parent Score: 1