Linked by Thom Holwerda on Wed 2nd Jan 2013 19:05 UTC
Permalink for comment 547327
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 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2005-11-29
No, I'm not. Its a lot more clumsy when compared to something like the XAML platform.
Its like they lifted things from XAML that they liked, and implemented them weirdly.
Of course its ugly. You're forced to litter your data model with Qt-isms. Who the hell wants to pull in a dependency to Qt on their data model?
In XAML my Models don't know anything about the XAML platform, and in fact move freely between XAML (including multiple XAML platforms), Cocoa, and Android's UI layer.
There are a lot of little issues, and admittedly I have not used Qt in a little while, but if I'm wrong I'd be interested in solutions.
So far it seems just about everything is more convoluted to do in Qt.