On Tue, Oct 11, 2011 at 9:54 AM, Till Oliver Knoll <[email protected]> wrote: > 2011/10/11 Adriano Rezende <[email protected]>: >> > ... >> I'm working in a QML project for desktop that has more than 500 QML >> files (~ 43 K LOCs). Unfortunately it's under NDA so I cannot say much >> about it, but it proves that QML can scale if you know how to use your >> resources. > > "If you know how to use your resources" - "Manage your boundaries" - > "Plan your development" - "Industrialise the work to be done" etc. > > Yep, I'll try to remember these ;) I don't think I'll hear them enough > every week or so ;)
The meaning is really technical, it's not a management bullshit. You need to take care about performance penalties and memory consumption, since the kind of applications QML are designed to uses heavily anchor-layouts and rely on huge image datasets. > Seriously, I didn't say it was not *possible* doing desktop > development using QML! I just think the whole idea of "outsourcing" > your GUI logic to JavaScript is... well... just not optimal for large > GUI projects, for points that I already hinted at in another post > here, but which I prefer to post into more detail into a separate > thread for discussion) later on this week, when I'll have time to do > some more research. To be fair I tend to use Javascript as minimal as possible, I don't like it either. I don't know why most of the discussions ends up in Javascript. The most important feature is the language itself, JS is just a helper. You will need to use in most of the cases just for property bindings, which basically ends up being optimized in the QML side, most of them are not even interpreted by the JS engine. > So what was your experience? QML needs some improvements and optimizations, but currently it's the best way to address native look&feel and custom applications IMO. > Does your UI look unusually different than if you had used the QWidget > approach? Yes, it's totally different. Full of animations and effects and a lot of fancy widgets. Basically it's a game oriented design applied to a custom application. > What is the performance memory consumption like? It uses more memory than a custom QWidget based application just by the fact that it has a heavy image data set. > Why did you go for QML in the first place? The client just wanted a beautiful application, full of animations and effects, which basically is almost a pre-requisite today. Implementing this kind of application using QWidget is out of question. > Do you think you saved development time (substracting your learning effort, > off course)? I work with QML before it was officially released, when its syntax was XML based. So I may be biased to say that its learning curve tends to zero. Regarding, the boost in development time, it's something already noticed by several developers. You need to experiment it in a real application to see the real benefits. > Why do you think you could not have achieved the same results with QWidgets? Basically because QWidget is not up for the task and it was not designed for this kind of application. > And most importantly: does your UI conform to the relevant OS look and feel? No it doesn't. I believe, this would be the common case for future applications. Most of the clients wants a customized application, even for desktop. >> Try to get some real information, or study more about it, before >> spreading fear and dispair. > > I already have most of the information I need to show my point and why > I still think QWidgets should not only remain intact (yes, I know, > they will remain), but even be actively be developed further (by > whoever). Further why I think being able to integrate QML (sic!) with > QWidgets would help both worlds and why I am not totally against the > idea to design some "custom widgets" with QML (in the best case > without any dependency on JavaScript). I'm not against integrating QML on top of QWidget, I'm against integrating QWidget on top of QML. I agree that the first approach would probably easy this transition from a bottom-up perspective. Also, even applications with native look&feel uses fancy widgets sometimes. Br, Adriano _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
