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.
Thread beginning with comment 445050
To read all comments associated with this story, please click here.
...
by Hiev on Thu 14th Oct 2010 13:41 UTC
Hiev
Member since:
2005-09-27

Indeed, but the resources taken for that migration are gonna be needed in other interesting and imho parts that needs to be priority that already has been delayed to mutch.

I don't forget that QML is the "me too" answer to Adobe Air, Java FX and MS WPF, and all those three technologies stayed just on the hype, I don't think QML will be different, anyway, the best of luck.

Edited 2010-10-14 13:44 UTC

Reply Score: 1

RE: ...
by aseigo on Thu 14th Oct 2010 13:52 in reply to "..."
aseigo Member since:
2005-07-06

Indeed, but the resources taken for that migration are gonna be needed in other interesting and imho parts that needs to be priority that already has been delayed to mutch.


not everyone will be working on this (in fact, just a few will be, most likely). others will continue their work on things such as activities and what not.

what parts are you concerned about not getting the necessary attention?

I don't forget that QML is the "me too" answer to Adobe Air, Java FX and MS WPF, and all those three technologies stayed just on the hype, I don't think QML will be different, anyway, the best of luck.


it's really not so much an answer to Air, WPF, etc. as it is a similar kind of solution to an increasingly common problem. one very major difference with QML is that it isn't a platform that is being created with the hopes of luring app develpers to, it's a new tool being added to a framework app developers are already using.

as a result application developers are already using QML (Kontact Mobile and Plasma Mobile to name two from KDE; i'm aware of others, but will let them announce for themselves ;) . it's also being used by platform developers such as MeeGo. this essentially prevents it from becoming "hype only" since it already has an audience which is already starting to use it. it's a significant difference.

regardless of whether QML takes over the world or not, it is starting to give us already using Qt some much needed tools that we've been missing. and that's enough for me ;)

Reply Parent Score: 7

RE[2]: ...
by Bill Shooter of Bul on Thu 14th Oct 2010 15:11 in reply to "RE: ..."
Bill Shooter of Bul Member since:
2006-07-14

Java FX, Adobe Air and WPF are also used by people, just not most people who still work with the legacy methods offered by those companies: Java, Flash, and Win32/Winforms. it wouldn't be surprising if QML is similarly underused by QT developers.

Reply Parent Score: 3

RE[2]: ...
by tsuraan on Sun 17th Oct 2010 01:37 in reply to "RE: ..."
tsuraan Member since:
2006-01-16

what parts are you concerned about not getting the necessary attention?


This is a bit of a late post, and I'm not the person you were replying to, but the state of kdepim does concern me. I haven't heard any updates from them on planet kde, their website (pim.kde.org) hasn't been updated since February 2008, and Gentoo is still blocking KDE 4.5 until there is a 4.5 pim release. What's going on there, anyhow?

Reply Parent Score: 1

RE: ...
by miker on Thu 14th Oct 2010 14:13 in reply to "..."
miker Member since:
2009-07-08

I don't forget that QML is the "me too" answer to Adobe Air, Java FX and MS WPF, and all those three technologies stayed just on the hype, I don't think QML will be different, anyway, the best of luck.


Spoken like someone who hasn't had worked with any of those technologies.

I used to develop multimedia applications in WPF. I could build complex user interfaces in WPF in a fraction of the time it would take using a more traditional framework.

WPF, FLEX, and now QML truly allow designers to get more involved with the development process. On of the best developers I've worked with was a XAML (WPF xml) guru who couldn't write a line of code in any language.

If you want to develop ugly boring business apps, the go ahead and code in MFC or Winforms.

Edited 2010-10-14 14:14 UTC

Reply Parent Score: 2

RE[2]: ...
by Hiev on Thu 14th Oct 2010 14:18 in reply to "RE: ..."
Hiev Member since:
2005-09-27

I've also developed with WPF, is awesome but some how it did't take over how it should, why? I don't now.

But if you ask me I think it was opaqued by HTML5 and javascript.

If you want to develop ugly boring business apps, the go ahead and code in MFC or Winforms.

Depends, with WinForms you can do kick ass bussines apps. too, WPF lacks of some goodies WinForms has.

Edited 2010-10-14 14:20 UTC

Reply Parent Score: 1

RE: ...
by nt_jerkface on Thu 14th Oct 2010 20:30 in reply to "..."
nt_jerkface Member since:
2009-08-26


I don't forget that QML is the "me too" answer to Adobe Air, Java FX and MS WPF, and all those three technologies stayed just on the hype, I don't think QML will be different, anyway, the best of luck.


I can't speak for Air or FX but WPF is definitely not riding on hype. WPF vs Winforms is debated endlessly in .net forums but everyone agrees that WPF comes with discernible benefits. Very few would suggest using Winforms if the targeted audience is Windows7/Vista users.

You also can't expect an explosion of applications immediately after a new framework is released. Software takes time to develop and for a lot of applications it isn't cost effective for the company to switch over.

Some key benefits of WPF only work with Win7/Vista so WPF will become more appealing as the XP market starts to shrink. Give it some time, WPF applications are on the way.

Reply Parent Score: 2