Active Topics
-
Maemo repository (5)
to Community by dredlok706 - 1 day, 18 hrs ago -
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 1 day, 21 hrs ago -
Porting apps to Leste (41)
to Maemo 7 / Leste by Arno_11 - 2 days, 15 hrs ago -
List of well performing apps on Leste (33)
to Maemo 7 / Leste by teroyk - 2 days, 23 hrs ago -
N900 is not recognizable on any of my devices (windows 10,7, xp) What can I do? (1)
to Nokia N900 by nieldk - 4 days, 3 hrs ago - more...
 |
|
2011-06-06
, 19:01
|
|
Posts: 1,012 |
Thanked: 817 times |
Joined on Jul 2007
@ France
|
#22
|
Originally Posted by mikecomputing
FUD Yourself !
Originally Posted by mikecomputing
Nice we can talk seriously
Finally one who has tested? O I forgot to say I has ALSO tested!
Originally Posted by mikecomputing
Never said that ... just that currently it s not possible to do everything in qml than we can do with qwidget, maybe i didn't explain it.
* 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.
[/QUOTE]
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.
So what, i m just angry... because it s mean again, trash everything and rewrite ... gtk ... qt ... qml ... and yes it s a rewrite. I'm loosing more time changing framework than doing interesting things. So now ... i ll not add anything new ... disconnect for a moment a stop thing to take the time to think what doing next...
Regards,
__________________
Benoît HERVIER, Khertan
KhtEditor - Sdist_Maemo - Khweeteur - PyPackager - KhtSimpleText - KhtNotes - KhtBMA - Wleux - and more ...
Benoît HERVIER, Khertan
KhtEditor - Sdist_Maemo - Khweeteur - PyPackager - KhtSimpleText - KhtNotes - KhtBMA - Wleux - and more ...
| The Following User Says Thank You to Khertan For This Useful Post: | ||
 |
|
2011-06-06
, 19:03
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#23
|
Originally Posted by mikecomputing
My understanding is QtComponents was open from the beginning. Intel evaluated it and found it too slow and rather than working with Nokia they reimplemented it and kept it quiet until they did the big reveal of the Tablet UX. I missed the Meego UX Components presentation at Meego Conf but this was the word I got from those who attended.
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.
Yes, take a look at those apps that use QWidget, that can run on both desktop, Maemo 4.1, and Maemo 5. In particular look at my apps. I took the time to port 3 from GTK to QWidget in prep for Meego under the false pretense that QWidget would work well (including theming). See DialCentral, Gonvert, and ejpi. They look consistent with the system, don't have half-working widgets, and work well within the limited space.
Testing on the desktop and directly deploying to the phone without any change of code has been a big time saver for me and is one of the things that I have enjoyed about developing for Maemo. Meego seems to be sucking the joy out of things by increasing the friction in doing development.
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
| The Following 3 Users Say Thank You to epage For This Useful Post: | ||
|
|
2011-06-06
, 19:03
|
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#24
|
Originally Posted by xerxes2
I am not sure QML is slower than QtWidgets on handset. Why do you think that?
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.
Maybe if you use alot of Javascript but again we can still use C++ for most stuff if we prefer that.
 |
|
2011-06-06
, 19:05
|
|
Posts: 513 |
Thanked: 651 times |
Joined on Feb 2011
@ Sweden
|
#25
|
Originally Posted by mikecomputing
Yes but for Qt the "tweeks" were VERY small. Qt desktop apps will work with very few changes on Maemo, and I hoped (and still do) on Meego too.
Devs has to tweek Desktop -> Handset anyway to make them look good on handset screen.
__________________
But the WM7 "horse" has a blood lineage tracing back to donkeys such as WM6.5, 6.1, 6.0, 5.1 that was fully neglected for too many years and Microsoft did sweet F all to maintain it (still running on Pocket IE4/6!!).
But the WM7 "horse" has a blood lineage tracing back to donkeys such as WM6.5, 6.1, 6.0, 5.1 that was fully neglected for too many years and Microsoft did sweet F all to maintain it (still running on Pocket IE4/6!!).
|
|
2011-06-06
, 19:06
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#26
|
I'd also like to add the note that I am fine with using QML with a proper widget library if it delivers on the cross-platform out-of-the-box promise, especially if it works on older systems like Maemo 4.1 and Maemo 5.
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
|
|
2011-06-06
, 19:10
|
|
Posts: 235 |
Thanked: 339 times |
Joined on Nov 2010
|
#27
|
Originally Posted by epage
That's already out of the question then: according to Google, QML was introduced in 4.6/4.7 but Maemo 4 only has Qt 4.5.2. Admittedly, all the other components on Maemo 4 are ancient too...
I'd also like to add the note that I am fine with using QML with a proper widget library if it delivers on the cross-platform out-of-the-box promise, especially if it works on older systems like Maemo 4.1[...]
|
|
2011-06-06
, 19:22
|
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#28
|
Originally Posted by Khertan
Well The libQtGui is still there, but no bugfixes will be done to qtWidgets, so you dont have to trash your code, but in the long run i think its a good way go QML it seems? Maybe next application you do ;-)
So what, i m just angry... because it s mean again, trash everything and rewrite ... gtk ... qt ... qml ... and yes it s a rewrite. I'm loosing more time changing framework than doing interesting things. So now ... i ll not add anything new ... disconnect for a moment a stop thing to take the time to think what doing next...
Regards,
If I understand it correcly from the discussions at labs.qt.nokia.com they "dished" QtWidget because it have to be heavily rewritten to integrate OpenGL?
But yes I agree there should be a stable "QML Widgets" and stuff need to be optimized in the "javaengine".
|
|
2011-06-06
, 19:24
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#29
|
Originally Posted by jstokes
Yes, I was aware of this. I was just bringing up the ideal and will compromise from there.
That's already out of the question then: according to Google, QML was introduced in 4.6/4.7 but Maemo 4 only has Qt 4.5.2. Admittedly, all the other components on Maemo 4 are ancient too...
At some point I will have to drop Maemo 4 support or fork Qt/GTK support (like I'm starting to go back to do with my transition from GTK->Qt). I would like to still support n900 users for a while longer though.
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
|
|
2011-06-06
, 19:29
|
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#30
|
Originally Posted by Khertan
Well I think complex listview should not be used on handset anyway.
We can clearly hope, as currently it s slower to display complex list view display than with qwidget, it s slower to do something correct for the developper, and it s CURRENTLY do everything yourself, even feedback on simple ui element.
Or maybe I misundestand "complex" when thinking very big lists with 1000 of items? I mean its bad design if I have to scroll that long lists anyway imho?
The rest I agree.
Last edited by mikecomputing; 2011-06-06 at 19:33.
But the WM7 "horse" has a blood lineage tracing back to donkeys such as WM6.5, 6.1, 6.0, 5.1 that was fully neglected for too many years and Microsoft did sweet F all to maintain it (still running on Pocket IE4/6!!).