Re: Plain Qt on Meego
 

It s not unfounded rant ! Just that it s not ready for every use case ! And many things still need to be debugged.

Libmeegotouch ? Are you kinding, it s worse than qml. So many things are missing. And explain me why desktop component aren't for mobile ? It s works well on Maemo. And are you saying that is better to kill the fact that Qt was multiplateforme. Now it s redo everything for each new plateform / device. It s a shame.

Of course it s have to do ! Without qt theme it s not just horrible, it s also horribly useless (auto rotation not working, no kinetic scrolling, scrollbar useless as too small ...)

Re: Plain Qt on Meego
 

FUD

http://labs.qt.nokia.com


But you can stick with you QtWidgets if you think thats the future for Tablets, touchscreens and handsets...

Re: Plain Qt on Meego
 

Finally someone that has tested Meego which I have not. So we don't know yet if plain Qt will look as good on Meego as on Maemo. I don't see the point with going through the fuzz of using QML if I don't have to so I rather not.

Re: Plain Qt on Meego
 

This is exactly how I feel. Why the heck should I be forced to use QML if I don't want to? Plain Qt should ALWAYS work and look good! As it work good on Maemo I don't think it can be that much work to get it to work good on Meego too. I say fix this asap Nokia!

Re: Plain Qt on Meego
 

Why shouldn't it be the future? The question is if it'll look ugly and be unsupported by Nokia? Well, much is uncertain today about Nokia so I guess we'll have to wait and see when Harmattan is properly released.

Re: Plain Qt on Meego
 

Finally one who has tested? O I forgot to say I has ALSO tested!

And personally I said above as half true and half FUD.

* First of QML doesnt mean we must write everything in Javascript that just ********!
* Second QML is progressing fast now to be more optimized for Handset/tablets and with QML 2 we have full OpenGL.

QML is here to stay QWidgets is on it way out and is not optimized for gestures and touchscreen.

But people can stay with QWidget if theyr so damn affraid for new stuff. But dont blame anyone if the bugs is not fixed in QtWidgets or if it doesnt work optimnal for touchscreens.

Re: Plain Qt on Meego
 

Also not all mobile apps require the wizbang of QML. Even on Nokia's site they encourage typical plain utility apps to use QWidget. Sadly the ideal of Qt being cross platform is not present.

QWidget for Desktop or Raw QML

Meego UX Components for Meego or Raw QML

QtComponents for Harmattan or Raw QML.

Notice a trend there? Either rewrite a UI that works perfectly well on each platform or write everything from scratch and not building on the shoulders of giants or even average height people.

At the Qt5 roadmap talk at Meego Conf there was talk of possibly rolling a QML widget set into Qt proper but sounds like that is a couple years off.

Yes, you can package one of those libraries for the other platforms but you have to build it directly into your app as you are not allowed to have deps outside of Meego to be Compliant.

Re: Plain Qt on Meego
 

QtWidget has been marked as *done*

I guess its upto the community to decide if they want to continue improve QtWidgets.

But personally I think in the long run even Desktop apps will use QML or more exact some kind of Widget set based on QML. The KDE team seems altready intrested to use QML in Plasma and also Ubuntu.

But i seems many is taking this as everything will be written in Javascript but that is not true! backends is still C++

http://labs.qt.nokia.com/2011/05/09/...ts-about-qt-5/

some of todays drawbacks using QML:

http://labs.qt.nokia.com/2011/05/26/...with-qt-quick/

Open GL in nextgen QML

http://labs.qt.nokia.com/2011/05/31/...aph-in-master/

QML widget on desktop

http://labs.qt.nokia.com/2011/03/10/...s-for-desktop/

Re: Plain Qt on Meego
 

This is exactly what I mean. You should be able to use all of Qt without QML. QML should be optional, use it if you want but it shouldn't be forced. It'll just add bloat and slow your app down. This just sounds like a crazy move from Nokia to not make QML optional.

Re: Plain Qt on Meego
 

The plan was that Qt-Componets for Harmattan AND Meego-ux-components should merge but its seems that Nokia neever get the damn sources out and also Intel seems to not be intrested to merge. Atleast when reading meego-dev mailinglist.

And btw qt-components exists for desktop too.

But again Handset UI/Tablet UI and Desktop UI are differenty beasts anyway.

Ofcourse as much of the QML "WidgetsAPI" should be compatible but try port QtWidgets from desktop to handset is often big fail. Just take a look at those desktop apps that have been ported to maemo 5. fonts wrong. cant see all button in some apps. menubar? how userfriendly is that on a handset!?

Devs has to tweek Desktop -> Handset anyway to make them look good on handset screen.