maemo.org - Talk
Page 2 of 4 1 2 34
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Applications (https://talk.maemo.org/forumdisplay.php?f=41)
-   -   [Announce] QtComponents for Fremantle (https://talk.maemo.org/showthread.php?t=79134)

pelago 2011-10-25 15:40
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by inean (Post 1112317)
Unfortunately, there's no official support for QtQuick 1.1 from nokia, so every app that depends from features added by CSSU (like qt 4.7.4) will never reach extras repo.
I guess we need another repo for CSSU users.

ivgalvez 2011-11-02 19:19
Re: [Announce] QtComponents for Fremantle
 
Let's use the same repo than CSSU, what's the problem?

inean 2011-11-02 19:42
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by ivgalvez (Post 1117471)
Let's use the same repo than CSSU, what's the problem?
A) There's no clean way, for an app developer, to submit apps.
B) An app that depends of CSSU features will never reach extras repo

By the way, I'm thinking about extend qt-components-10 package with a components that make use of QtQuick 1.1, so package will end as:

QtQuick 1.0
----------------
org.maemo.fremantle
org.maemo.fremantle.extras

QtQuick 1.1
----------------
com.nokia.meego
com.nokia.meego.extras

The platform adaptation code should work fine with Qt 4.7.0 and Qt 4.7.4, so no problem at that point. That way, an app developer could build their app with code that works with BOTH namespaces and select the corrent QML frontend at runtime based on Qt library version.

With this approach, we make happy power users (CSSU ones) and app could reach extras.

MiK546 2011-11-02 20:14
Re: [Announce] QtComponents for Fremantle
 
Why dont you try and contact developers working with CSSU first and maybe they could work out how applications using CSSU's updated pakages could use the extras repositories. That might be earier for everyone.

inean 2011-11-02 22:10
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by MiK546 (Post 1117494)
Why dont you try and contact developers working with CSSU first and maybe they could work out how applications using CSSU's updated pakages could use the extras repositories. That might be earier for everyone.
It's easy. Get Qt 4.7.4 or (better) on extras and problem is solved... except that we could reach the following scenario:

Gtk Libraries loaded
Qt from PR1.3 or CSSU loaded
Qt (extras package) libraries loaded for QtComponents based apps
...
and an out of memory message ;)

Think about it

mikhas 2011-12-24 01:44
Re: [Announce] QtComponents for Fremantle
 
I added a new virtual keyboard to Maliit. It's written in C++ so performance should be good on the N900 even. It can load all MeeGo Keyboard layouts, including the N9 language layouts posted in this forum. For that, I could need some help with a settings application so that users can enable/disable language layouts without having to touch GConf directly: https://bugs.maliit.org/show_bug.cgi?id=60

The new VKB plugin is a buggy though when it comes to HWKB support (and as with any new software, it has other bugs, too), but I intend to fix that.

The theming might not fit Qt Components style on Fremantle, but it should be easy to fix for someone with basic photoshop/theming skills.

kent_autistic 2011-12-24 09:58
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by mikhas (Post 1141332)
I added a new virtual keyboard to Maliit. It's written in C++ so performance should be good on the N900 even. It can load all MeeGo Keyboard layouts, including the N9 language layouts posted in this forum. For that, I could need some help with a settings application so that users can enable/disable language layouts without having to touch GConf directly: https://bugs.maliit.org/show_bug.cgi?id=60

The new VKB plugin is a buggy though when it comes to HWKB support (and as with any new software, it has other bugs, too), but I intend to fix that.

The theming might not fit Qt Components style on Fremantle, but it should be easy to fix for someone with basic photoshop/theming skills.
um is this a system-wide vkb that can replace the stock fremantle vkb? or just for apps ported from harmattan?

inean 2011-12-26 17:42
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by kent_autistic (Post 1141398)
um is this a system-wide vkb that can replace the stock fremantle vkb? or just for apps ported from harmattan?
This is the best approach to get VKB on N900 (by far).

inean 2011-12-26 17:57
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by mikhas (Post 1141332)
I added a new virtual keyboard to Maliit. For that, I could need some help with a settings application so that users can enable/disable language layouts without having to touch GConf directly: https://bugs.maliit.org/show_bug.cgi?id=60
.
Michel, I've been thinking about this, and IMO, the best/fastest approach for Fremantle/Nemo/Harmattan is to extend MesInput to be able to select different keyboards.
A different way could be create custom control center apps for Meego and Fremantle, but this implies more work...

sheng0729 2011-12-31 09:11
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by MiK546 (Post 1109442)
I'm having a problem with the latest QtComponents, it doesn't seem to be able to load the theme. When I open butaca for example I can't see the bottom menubar or the statusarea with clock and battery(like in the attached screenshot). When I open it from command line I get the following(it all doesn't fit the N900's command line application):
Code:
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:170:9: QML Image: Failed to get image from provider: image://theme/meegotouch-positionindicator-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/BusyIndicator.qml:68:5: QML QDeclarativeImage_QML_66: Failed to get image from provider: image://theme/spinner_96_1
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:226:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-indicator-horizontal
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:226:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-indicator-horizontal
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:220:9: QML Image: Failed to get image from provider: image://theme/meegotouch-positionindicator-background-horizontal
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:175:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-indicator
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:175:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-indicator
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:170:9: QML Image: Failed to get image from provider: image://theme/meegotouch-positionindicator-background
qrc:/qml/CustomListDelegate.qml:39:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-list-background-pressed-vertical-center
qrc:/qml/CustomListDelegate.qml:39:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-list-background-pressed-vertical-center
file:///usr/lib/qt4/imports/org/maemo/fremantle/StatusBar.qml:66:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-statusbar-landscape-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/StatusBar.qml:66:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-statusbar-landscape-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/ToolBar.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-toolbar-landscape-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/ToolBar.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-toolbar-landscape-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:220:9: QML Image: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-background-horizontal
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:226:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator-horizontal
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:226:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator-horizontal
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:170:9: QML Image: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:175:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:175:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator
file:///usr/lib/qt4/imports/org/maemo/fremantle/ToolIcon.qml:63:9: QML QDeclarativeImage_QML_51: Failed to get image from provider: image://theme/icon-m-toolbar-favorite-unmark-white
file:///usr/lib/qt4/imports/org/maemo/fremantle/ToolIcon.qml:63:9: QML QDeclarativeImage_QML_51: Failed to get image from provider: image://theme/icon-m-toolbar-share-white
file:///usr/lib/qt4/imports/org/maemo/fremantle/Button.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-button-inverted-background-disabled
file:///usr/lib/qt4/imports/org/maemo/fremantle/Button.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-button-inverted-background-disabled
file:///usr/lib/qt4/imports/org/maemo/fremantle/Button.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-button-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/Button.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-button-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/Button.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-button-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/Button.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-button-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/Button.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-button-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/Button.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-button-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/BusyIndicator.qml:68:5: QML QDeclarativeImage_QML_66: Failed to get image from provider: image://theme/spinnerinverted_96_1
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:220:9: QML Image: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-background-horizontal
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:226:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator-horizontal
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:226:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator-horizontal
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:170:9: QML Image: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:175:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:175:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:220:9: QML Image: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-background-horizontal
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:226:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator-horizontal
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:226:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator-horizontal
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:170:9: QML Image: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:175:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:175:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator
file:///usr/lib/qt4/imports/org/maemo/fremantle/BusyIndicator.qml:68:5: QML QDeclarativeImage_QML_66: Failed to get image from provider: image://theme/spinnerinverted_96_1
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:220:9: QML Image: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-background-horizontal
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:226:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator-horizontal
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:226:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator-horizontal
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:170:9: QML Image: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:175:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator
file:///usr/lib/qt4/imports/org/maemo/fremantle/ScrollDecorator.qml:175:9: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-positionindicator-inverted-indicator
qrc:/qml/CustomListDelegate.qml:39:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-list-inverted-background-pressed-vertical-center
qrc:/qml/CustomListDelegate.qml:39:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-list-inverted-background-pressed-vertical-center
file:///usr/lib/qt4/imports/org/maemo/fremantle/Button.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-button-inverted-background-selected
file:///usr/lib/qt4/imports/org/maemo/fremantle/Button.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-button-inverted-background-selected
file:///usr/lib/qt4/imports/org/maemo/fremantle/StatusBar.qml:66:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-statusbar-portrait-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/StatusBar.qml:66:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-statusbar-portrait-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/ToolBar.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-toolbar-portrait-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/ToolBar.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-toolbar-portrait-inverted-background
qrc:/qml/CustomListDelegate.qml:39:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-list-inverted-background-pressed-vertical-center
qrc:/qml/CustomListDelegate.qml:39:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-list-inverted-background-pressed-vertical-center
qrc:/qml/CustomListDelegate.qml:39:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-list-inverted-background-pressed-vertical-center
qrc:/qml/CustomListDelegate.qml:39:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-list-inverted-background-pressed-vertical-center
file:///usr/lib/qt4/imports/org/maemo/fremantle/StatusBar.qml:66:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-statusbar-landscape-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/StatusBar.qml:66:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-statusbar-landscape-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/ToolBar.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-toolbar-landscape-inverted-background
file:///usr/lib/qt4/imports/org/maemo/fremantle/ToolBar.qml:73:5: QML BorderImage: Failed to get image from provider: image://theme/meegotouch-toolbar-landscape-inverted-backgroundv
can i know how to solve this problem?

MiK546 2011-12-31 13:59
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by sheng0729 (Post 1143783)
can i know how to solve this problem?
Read trough the first page, the answer is right there in the last post.

rcolistete 2011-12-31 17:55
Re: [Announce] QtComponents for Fremantle
 
Thanks for releasing Qt Components 1.0-pre0 ! Fantastic to see :
- new status bar;
- new Nemo vkb;
- dialog buttons are fixed;
- infobanner working;
- many other bugs fixed.
Now I am sure to release some Qt Quick softwares for both Nokia N9 & N900 (instead of specific QWidget version to N900).

My bug-list that I have found :
- "Gallery->Sliders" closes when scrolling down;
- "Gallery->Miscellaneous" closes when 'Progress Bar' runs;
- tabs in TollBar are show with a 'noise' (something behing the text);
- "Extras Gallery->RatingIndicator" does not show starts, instead there are numbers in small font.

Keep the good working ! Happy New Year !

inean 2011-12-31 19:23
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by rcolistete (Post 1143970)
Thanks for releasing Qt Components 1.0-pre0 ! Fantastic to see :
- new status bar;
- new Nemo vkb;
- dialog buttons are fixed;
- infobanner working;
- many other bugs fixed.
Now I am sure to release some Qt Quick softwares for both Nokia N9 & N900 (instead of specific QWidget version to N900).
Thanks.

Take a look again to the first post. There are to links to examples on how you could develope for Fremantle (SSU) and Harmattan (of Fremantle CSSU)

Quote:
My bug-list that I have found :
- "Gallery->Sliders" closes when scrolling down;
- "Gallery->Miscellaneous" closes when 'Progress Bar' runs;
Seems like a regression. Please fill a bug against this at
https://bugs.maemo.org/enter_bug.cgi...=qt-components

Quote:
- tabs in TollBar are show with a 'noise' (something behing the text);
Known bug still pending :/

Quote:
- "Extras Gallery->RatingIndicator" does not show starts, instead there are numbers in small font.
That's becouse base theme is incompleted. Jakub is working on this for nemomobile. In the meantime, you could try to install blanco scaffold and move icons from QtSDK harmattan theme into your phone...

Same for Nokia pure font ;). All this stuff is propietary and we are not allowed to distribute freely.

Salu2

MartinK 2011-12-31 19:37
Re: [Announce] QtComponents for Fremantle
 
Nice to see such great progress ! :)
Looks like porting the new Qt Components based Mieru version back to Fremantle (and the QtC GUI for modRana) will be a breeze. :)

Also, happy new year and keep up all the good work ! :D

rcolistete 2011-12-31 19:57
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by inean (Post 1143992)
Thanks.

Take a look again to the first post. There are to links to examples on how you could develope for Fremantle (SSU) and Harmattan (of Fremantle CSSU)
Yes, I have seen them, thanks.

Quote:
Originally Posted by inean (Post 1143992)
Seems like a regression. Please fill a bug against this at
https://bugs.maemo.org/enter_bug.cgi...=qt-components
Done :
https://bugs.maemo.org/show_bug.cgi?id=12540

MartinK 2012-03-10 23:52
Re: [Announce] QtComponents for Fremantle
 
Any progress in the theme department ?

There has been some work on the "darko" theme in the meantime - might be useful to fill in some of the (many) missing icons.

inean 2012-03-11 20:16
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by MartinK (Post 1177636)
Any progress in the theme department ?

There has been some work on the "darko" theme in the meantime - might be useful to fill in some of the (many) missing icons.
I expect to update all stack (maliit 0.90) qtcomponents 1.1 and darko theme at the end of the month.

salu2

MartinK 2012-03-13 19:53
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by inean (Post 1178012)
I expect to update all stack (maliit 0.90) qtcomponents 1.1 and darko theme at the end of the month.

salu2
Nice! Looking forward to it ! :)

reinob 2012-03-14 08:19
Re: [Announce] QtComponents for Fremantle
 
Not sure, but "unable to create `./opt/share/.." doesn't seem right. Shouldn't the path be absolute (/opt/share/... and not ./opt/share/...).

It all depends on which directory apt-get is being run from. Try to do this without using fapman but directly using apt-get (and just in case, run it from the / directory so that /opt = ./opt in any case).

inean 2012-03-14 10:02
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by reinob (Post 1179230)
Not sure, but "unable to create `./opt/share/.." doesn't seem right. Shouldn't the path be absolute (/opt/share/... and not ./opt/share/...).

It all depends on which directory apt-get is being run from. Try to do this without using fapman but directly using apt-get (and just in case, run it from the / directory so that /opt = ./opt in any case).
Different thread ???

The Winter 2012-03-14 10:14
Re: [Announce] QtComponents for Fremantle
 
Qt components are nt going to get accepted as main stream components or are they ?

reinob 2012-03-14 10:24
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by inean (Post 1179248)
Different thread ???
Yup. Problem is no idea which. Something's seriously f**ked up with this forum.

EDIT: OK, I guess I didn't sleep well tonight. I was replying to http://talk.maemo.org/showpost.php?p...7&postcount=38, which is in this thread, but on the firts page.

inean 2012-03-14 16:55
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by reinob (Post 1179256)
Yup. Problem is no idea which. Something's seriously f**ked up with this forum.

EDIT: OK, I guess I didn't sleep well tonight. I was replying to http://talk.maemo.org/showpost.php?p...7&postcount=38, which is in this thread, but on the firts page.
I see, please, open a bug about this so I could take a look when update theme package; I'm bit busy right now :p

ivgalvez 2012-03-14 17:03
Re: [Announce] QtComponents for Fremantle
 
Is anyone else porting any Harmattan application to Fremantle?

AFAIK,right now there's only Meecast, Mallit, Butaca and Miniature using QtComponents and Mieru is waiting to be pushed to the repos. Apart from that, there are some QML applications but they implement their own components like CuteTube.

MartinK 2012-03-14 22:41
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by ivgalvez (Post 1179436)
Is anyone else porting any Harmattan application to Fremantle?

AFAIK,right now there's only Meecast, Mallit, Butaca and Miniature using QtComponents and Mieru is waiting to be pushed to the repos. Apart from that, there are some QML applications but they implement their own components like CuteTube.
For example, the schedule application for DevConf 2012 uses Qt Components and was available both from Ovi and as a deb package for N900. :)

We actually have a (Czech language) article about porting Harmattan applications to Fremantle in the pipeline. I plan to translate it to English once the Czech version is out. :)

reinob 2012-03-15 08:28
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by inean (Post 1179434)
I see, please, open a bug about this so I could take a look when update theme package; I'm bit busy right now :p
I don't have any such bug. I haven't even installed or wish to install qt-components-base-theme.

But I was replying to the guy having a problem. If my answer is correct it means that qt-components-base-theme_0.1.90-1+0m5.1_all.deb is broken, so I hereby declare this message to be a bug report :)

Cheers.

inean 2012-04-05 21:44
Re: [Announce] QtComponents for Fremantle
 
Today I've pushed a new release of qt-components and qt-components-base-theme.

QtComponents is still based on meego-1.1.1 components. ToolbaLayout.js has been updated to mimic Meego behaviour so it shouldn't be a problem anymore (now tabs render properly)

For deverlopers: Please, take a look to https://qt.gitorious.org/~inean/qt-c...tle/HelloWorld to check how you can maintain both, SSU and CSSU/Harmattan versions of your project.

For designers: Base theme needs a lot of love. The list o missing images could be reached at https://gitorious.org/fremantle-qt-c.../generated.txt.

Happy coding ;)

inean 2012-04-06 09:35
Re: [Announce] QtComponents for Fremantle
 
I've pushed a minor revision of yesterdays's package on which I introduce a last minute regression on example's code.

I'm also pushing a new qt-components-base-theme package. Theme coverage is complete and only icons are still missing. Seems like blanco theme was open sourced two months ago. More details here

http://lists.qt.nokia.com/pipermail/...il/000660.html

ivgalvez 2012-04-07 12:06
Re: [Announce] QtComponents for Fremantle
 
Tested and working fine with Meecast except for forced Autorotation with CSSU.

MartinK 2012-04-07 12:54
Re: [Announce] QtComponents for Fremantle
 
Working fine with Mieru and the new modRana GUI.

BTW, if I understand the situation with the theme correctly, all the icons in:
http://meego.gitorious.org/meegotouc...s/master/icons
Have been generated to PNGs and are inside the new base theme package ?
There seems to be quite a few issues though:
  • many icons that should be black are white
    examples: icon-s-common-previous, icon-s-common-next, icon-m-toolbar-list, ...
    This results is white icons on white-gray buttons on Fremantle. :)
  • most *-inverse icons have just the red placeholders
    I guess just generating the non-inverse versions and then applying an inverse filter with imagemagic should fix this ?

imo 2012-04-07 14:31
Re: [Announce] QtComponents for Fremantle
 
thanks for wonderful work mate .Just wanted to know if new Qt-components affect any of already installed packages from repos ?Since they replace the built in nokia Qt components , so will it be ok to have them ?
secondly after installation of these Qt-components ,will it be possible for us to install ported meego apps for fremantle ? & will it affect any package which is already there in repos (as if deb - installation requires old Qt-components ) ?
thanks .

qwazix 2012-04-07 14:36
Re: [Announce] QtComponents for Fremantle
 
please clarify where should we depend on, qt-components or qt-components10 and why

imo 2012-04-07 14:53
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by qwazix (Post 1189305)
please clarify where should we depend on, qt-components or qt-components10 and why
to run meego apps .
to get blanco theme working perfect .
to get a feel of N9 on N900
:)

imo 2012-04-07 14:54
Re: [Announce] QtComponents for Fremantle
 
about when do we expect anything for CSSU users to test new qt-components and experience meego apps ?

inean 2012-04-07 14:56
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by ivgalvez (Post 1189250)
Tested and working fine with Meecast except for forced Autorotation with CSSU.
Thanks, remember that all qtcomponent based apps must be on Autorotation blacklist. That's something that developers should take into consideration when packing their apps (triggers should help in this case)

inean 2012-04-07 15:11
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by MartinK (Post 1189263)
BTW, if I understand the situation with the theme correctly, all the icons in:
http://meego.gitorious.org/meegotouc...s/master/icons
Have been generated to PNGs and are inside the new base theme package ?
No, only the icons whose name match 1:1 with the ones presented at blanco theme.
Icons are fetched from this sources (in preference order): Darko theme > qt-components-base-icons package > meegotouch-graphics-theme

Quote:
There seems to be quite a few issues though:
  • many icons that should be black are white
    examples: icon-s-common-previous, icon-s-common-next, icon-m-toolbar-list, ...
Those icons probably comes from meegotouch-graphics-theme. remember Meego UI? It was quite dark... ;).

Quote:
[*]most *-inverse icons have just the red placeholders
I guess just generating the non-inverse versions and then applying an inverse filter with imagemagic should fix this ?[/LIST]
IMO, the best approach is to provide good icons to darko-theme. That way, I could merge it into qt-components-base-theme. Go ahead If you feel that the imagemagic approach could do the trick. It will benefit not only us, but also nemomobile.

I encomend you to push your apps into extras-devel, even with the red incons problem. Maybe a a designer is interested in your app and provide the missing icons your app need. ;)

inean 2012-04-07 15:47
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by imo (Post 1189303)
thanks for wonderful work mate .Just wanted to know if new Qt-components affect any of already installed packages from repos ?Since they replace the built in nokia Qt components , so will it be ok to have them ?
Those that already depends on qt-components-10. Because this is a lib package, they should update their package dependences to match latest qt-components-10 package.

Said that, according to packages.maemo.org there isn't any program which depends on original qt-components.

Quote:
secondly after installation of these Qt-components ,will it be possible for us to install ported meego apps for fremantle ? & will it affect any package which is already there in repos (as if deb - installation requires old Qt-components ) ?
thanks .
The first version of qt-components-10 could be paralell installable with qt-components, because the different name space (org.maemo.fremantle vs com.nokia.meego). That is no longer the case. To add support to CSSU, I'm deploying to sets of QtComponents inside qt-components-10 packages, one that works with both, SSU and CSSU (org.maemo.fremantle) and another one (com.nokia.meego) which only works with Qt >= 4.7.4 (and don't require any tricks on QML code, only platform adaption)

Theoretically, a lazy developer could backport their app just removing unsupported Harmattan features, if any, and packing for fremantle. Problem is that he/she will be targetting CSSU users only.

IMO, the approach following in the HelloWorld example doesn't require much more effords but you gain the possiblity to reach extras repo (like meecast)

inean 2012-04-07 15:55
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by qwazix (Post 1189305)
please clarify where should we depend on, qt-components or qt-components10 and why
Your are luckily if your app works properly with qt-components package. A simple hello world app (The one that is generated by qt-creator) lacks of:
  • VKB integration (yes a a VKB in portrait mode thanks to Maliit guys)
  • Switch or close buttons
  • Autorotation
  • Window state notifications (inactive, visible thumbnail, visible fullscreen)
  • Status indicators (batery, time, cell state, wifi state, etc)

inean 2012-04-07 16:04
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by imo (Post 1189310)
about when do we expect anything for CSSU users to test new qt-components and experience meego apps ?
The main difference between org.maemo.fremantle vs com.nokia.meego is related to workarounds against bugs is qt 4.7.0.
org.maemo.fremantle MUST run with reaster qt graphics engine, while com.nokia.meego SHOULD be run with opengl graphics engine. (and only by CSSU users, remember)
  • fremantle components use Qt 4.7 namespace (they don't depend on qtquickcompat package)
  • fremantle components don't have magnifier (opengl segfault)
  • fremantle users can't use 'action key' (with SipAttributes component) on Maliit VKB (qt segfault)
  • fremantle users can't use opengl with progressbar (qt segfault)

I still wonder why Nokia didn't push a Qt 4.7.3 or 4.7.4 on oficial firmware...

MartinK 2012-04-07 18:16
Re: [Announce] QtComponents for Fremantle
 
Quote:
Originally Posted by inean (Post 1189320)

Those icons probably comes from meegotouch-graphics-theme. remember Meego UI? It was quite dark... ;).
Well, the end result is still the same - you get get buttons with icons that can't be seen. :) Would a list of icons having this problem help ? :)

Quote:
Originally Posted by inean (Post 1189320)
IMO, the best approach is to provide good icons to darko-theme. That way, I could merge it into qt-components-base-theme. Go ahead If you feel that the imagemagic approach could do the trick. It will benefit not only us, but also nemomobile.
Well, I'm unfortunately already quite overcommited. There seems to be no shortage of Fremantle theme designers - maybe some of them could step forward for such an important project ?

Quote:
Originally Posted by inean (Post 1189320)
Said that, according to packages.maemo.org there isn't any program which depends on original qt-components.
So if it's not used & badly broken it might be safe to remove it ? Not sure if there is some easy way of doing that or if you need to tell the super-testers or repo admins.


All times are GMT. The time now is 17:32.
Page 2 of 4 1 2 34
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8