Re: Does Fremantle support any Qt Quick Components?
On Jul 15, 2011, at 2:33 PM, ext ti...@sch.bme.humailto:ti...@sch.bme.hu wrote: Hello Kate, Your timing couldn't b better as I was just starting to port my apps to QML and I began with Harmattan's Qt Components. So basically you are saying that the same QML code that runs on Harmattan will run on Fremante too? Do I need to take any special steps to allow this for my app? Yes and no, 99.9% yes, but when you read my blog http://www.developer.nokia.com/Community/Blogs/blog/kate-alholas-forum-nokia-blog/2011/07/08/porting-meego-1.2-harmattan-qt-quick-components There are some UX differences like toolbar position, close and home buttons etc. This Maemo5 port is still experimental and there may be bugs. Kate Cheers, Timur On Fri Jul 15 13:11:28 2011 kate.alh...@nokia.commailto:kate.alh...@nokia.com wrote: On Jul 14, 2011, at 11:48 PM, ext Attila Csipa wrote: On Thursday 14 July 2011 23:15:46 you wrote: My question is very simple: are any of the Qt Quick Components packaged and working on Maemo 5? Not the latest greatest, but ... http://maemo.org/packages/view/qt- components/ That package is acually the latest and greatest qt-components 1.0~git20110620-7-1fnhttp://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/qt-components/1.0%7Egit20110620-7-1fn/ same version than in MeeGo 1.2 and Harmattan. I submitted it to autobuilder couple of days ago. I noticed that there is still some bugs and possible core dumps on Maemo5 Qt version. I have not yet have time to analyze it deeper but the problems are related im Maemo5 Qt or OpenGl version because sam code works in MeeGo 1. N900 CE and Ubuntu Natty. Also, the custom branch should be usable directly (i.e. just get the stuff from https://qt.gitorious.org/qt-components/qt-components/commits/custom and shove it in your qml dir), with the caveat that in the case of Maemo5, you will have to use a version from before they switched to QtQuick 1.1. This qt-components 1.0~git20110620-7-1fnhttp://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/qt-components/1.0%7Egit20110620-7-1fn/ is actually latest version that has Qt Quick 1.1 support and then my backport patch to Qt Quick 1.0 compatibility. Kate Personally, I wouldn't mind if some packaging support came from the community side, there are only so many packages and projects I can support myself. Best regards, Attila Csipa ___ maemo-developers mailing list maemo-developers@maemo.orgmailto:maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers On Fri Jul 15 13:11:28 2011 kate.alh...@nokia.commailto:kate.alh...@nokia.com wrote: On Jul 14, 2011, at 11:48 PM, ext Attila Csipa wrote: On Thursday 14 July 2011 23:15:46 you wrote: My question is very simple: are any of the Qt Quick Components packaged and working on Maemo 5? Not the latest greatest, but ... http://maemo.org/packages/view/qt- components/ That package is acually the latest and greatest qt-components 1.0~git20110620-7-1fnhttp://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/qt-components/1.0%7Egit20110620-7-1fn/ same version than in MeeGo 1.2 and Harmattan. I submitted it to autobuilder couple of days ago. I noticed that there is still some bugs and possible core dumps on Maemo5 Qt version. I have not yet have time to analyze it deeper but the problems are related im Maemo5 Qt or OpenGl version because sam code works in MeeGo 1. N900 CE and Ubuntu Natty. Also, the custom branch should be usable directly (i.e. just get the stuff from https://qt.gitorious.org/qt-components/qt-components/commits/custom and shove it in your qml dir), with the caveat that in the case of Maemo5, you will have to use a version from before they switched to QtQuick 1.1. This qt-components 1.0~git20110620-7-1fnhttp://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/qt-components/1.0%7Egit20110620-7-1fn/ is actually latest version that has Qt Quick 1.1 support and then my backport patch to Qt Quick 1.0 compatibility. Kate Personally, I wouldn't mind if some packaging support came from the community side, there are only so many packages and projects I can support myself. Best regards, Attila Csipa ___ maemo-developers mailing list maemo-developers@maemo.orgmailto:maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.orgmailto:maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Qt with OpenGL ES 1.1 on Maemo / N900
On Sep 2, 2010, at 4:13 PM, ext Thomas Perl wrote: Hello! According to the OpenGL ES Wiki page[1], Qt on Maemo only supports OpenGL ES 2.x. Is this really true? I've added the following two lines to my .pro file, and my application compiles, links and runs happily. However, the window (a QGLWidget) will stay black - nothing is drawn on the screen. DEFINES += QT_NO_OPENGL_ES_2 QT_OPENGL_ES_1 LIBS += -lGLES_CM Now my questions: 1.) Is it possible to use QGLWidget with OpenGL ES 1.1 on the N900? 2.) Is there a minimal example using QGLWidget + OpenGL ES 1.1? By default in device there is only OpenGL2 libraries, there are extra packages libgles1-sgx-img and libgles-sgx-dev containing OpenGL-ES1 . The implementation is based emulating OpenGL-ES1 fixed function pipeline by special shader code loaded. That may cause problems, because Qt uses by default GLES2. It may happen that if you try run GLES1 functions under QGlwidget, ir tuns happily but does not draw anything if GLES1 emulation is not initialized and shader codes loaded. I don't know is it possible to load emulation ( initialize GLES1) without doing some harm for other Qt GL stuff. Kate The same code works fine when compiled with Qt under Ubuntu on a laptop, so the code works and does draw something ;) I'm using the experimental Qt 4.7.x packages from Extras-Devel in Scratchbox and on the device. Any help appreciated :) Thanks! Thomas [1] http://wiki.maemo.org/OpenGL-ES ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QT map widget
- Original message - kate.alh...@nokia.commailto:kate.alh...@nokia.com wrote: I don't know hat mappero (ex maemo mapper) does internaly but least, it can eat all cpu power when doing processing maps so that only way out is remove battery from device. I've been told that this happens when downloading large amounts of map tiles, so it has nothing to do with the map widget itself. That one is based on clutter, and seems to be quite efficient. Situation is when lot of map tiles are loaded. I dont't know what internaly happens. Some memory leak ? For application performance and cpu usage also time needed for tile pre-processing need to be counted. Does it some scaling for tiles after loading them ? Finally time used for scaling tiles is one key issues. Do we scale them or download every size. How much cpu power is used for scaling or do we leave it all for GPU ? For mappero case i don't know how much cpu is used for actual scaling and how much by exhausting virtual memory ? (off topic: if you can find some way to reproduce it reliably, please file a bug -- although if you really need to take out the battery, that cannot be a bug in the application itself) I think, without any actual debug or analysis that it consumes all virtual memory and there won't be any memory for system UI even kill application when everything is swapped out. Kate Ciao, Alberto -- http://blog.mardy.it -- geek in un lingua international! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Routing SMS to another app.
From: ext Cláudio Sampaio [pat...@gmail.com] Sent: Monday, April 05, 2010 11:39 AM To: Alhola Kate (Nokia-FNDC/Helsinki) Cc: singheinst...@gmail.com; maemo-developers@maemo.org Subject: Re: Routing SMS to another app. On Sat, Apr 3, 2010 at 9:51 AM, kate.alh...@nokia.commailto:kate.alh...@nokia.com wrote: Kate, can we use this to hijack voice calls also? Like the SMS thing you mentioned, that before the message comes we can trap the signal. Does the same hold for voice calls too? There is not yet voice call support in QtMobility but you can get signal of incoming voice call using libtpsession. It then depends what do you mean hijack. You can Catch SMS or Voice call singal but with these methods you can't prevent other applications like Messaging Ui or Phone UI getting also notification of incoming SMS or Call. Case in point, would it be possible to make an application for custom ringtones for contacts? This is a request made very often by users of the N900. When you can catch indication of incoming call with number on it, you can play your custom ring tone but i am not sure, how you can easily prevent system ringtone playing. As you response readily implies a 'no', the 'not yet' means how long? I mean, PR1.2 has something for it? Is it planned for some release, or what? Wouldn't that be very very simple to code in the phone call library? Sorry for being too inquisitive and I know Nokia does not give dates. But I just want to know if it's worth spending my time on this issue. WIth these methods does not mean impossible but it needs more complicated methods. The call and SMS system is based on Telepathy framework. You can check rough diagram from http://tpsession.garage.maemo.org/ . With tpsession or qtmobility you can receive events that Telepathy is sending via dbus but you can't prevent other stake holdsers receiving these events. Technically Telepathy framework allows implementing filters in message path that does exactly what you are asking and there is TelepathyQt4 library. I am using TelepathyQt4 for TpSesison. I have not tried to implement filters with Telepathy and Telepathy is not simplest API at all. There has been discussion having simplifies filter API for TpSession but i have not had even Time to check it now. At the moment only way to do filtes is to use Telepathy API's. Kate ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Routing SMS to another app.
From: maemo-developers-boun...@maemo.org [maemo-developers-boun...@maemo.org] On Behalf Of ext Sukhbir Singh [singheinst...@gmail.com] Sent: Saturday, April 03, 2010 2:32 PM To: maemo-developers@maemo.org Subject: Routing SMS to another app. Hi developers, I was wondering whether there is any way I can divert SMS messages from the Inbox to another app that I would be designing for this purpose. Like when a SMS comes, I just need to delete it from the Inbox, extract the sender's name and the message body and store it inside my app. Is there any way to do this? I am potential GSoC student. Easiest way is to do this with QtMobility messaging API. There QMEssagestore, you can get signal of arriving SMS and then delete it. QTmobility Messagign with Messge Store support will be there in next couple of weeks. Kate ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: How to include glib-object.h
From: maemo-developers-boun...@maemo.org [maemo-developers-boun...@maemo.org] On Behalf Of ext Christoph Eckert [...@christeck.de] Sent: Monday, March 29, 2010 1:14 AM To: maemo-developers@maemo.org Subject: How to include glib-object.h Hi, I try to port a Maemo 4.1 pygtk application to Qt4 on Maemo 5. The application is running, but now it requires location data. Since the location API has changed in Maemo 5, I try to understand the example given at http://bit.ly/a3HTFD May be better solution is to use directly qt-mobility libqtm-location . Qt mobility will be foture proof cross platfrom solution. For marmatan native location API will anyhow change. For fremantle libqtmlocation is wrapper over liblocation0 . For Harmatan its is direct connection to dbus but API remains same. Kate As soon as I put #include location/location-gps-device.h #include location/location-gpsd-control.h in one of my files, the compiler complains: http://pastebin.com/c45NU0FB glib-object.h: No such file or directory This file includes further files, as listed here: http://bit.ly/dprcX6 I'm obviously missing some include path or similar. Appearently I'm a bloody hobbyist, so please bear with me :) . Any hint, even RTFM is much appreciated. Best regards, ce ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: GSoC project - aGLESory
From: maemo-developers-boun...@maemo.org [maemo-developers-boun...@maemo.org] On Behalf Of ext Thomas Perl [th.p...@gmail.com] Sent: Friday, March 19, 2010 12:02 PM To: Carolina Simões Gomes Cc: maemo-developers@maemo.org Subject: Re: GSoC project - aGLESory Hello! 2010/3/19 Carolina Simões Gomes carolina.sgo...@gmail.com: If possible, I'd like to know more about the aGLESory project, in order to begin forming my ideas about the project proposal. (I'm not the one who proposed the project, so I might be wrong about the motivations and ideas behind aGLESory.) I *think* the idea behind aGLESory is to make it easier to start creating projects utilizing OpenGL ES for Maemo/MeeGo. Right now, if one was to use Xlib to create a Hello World-ish GL ES app, it would look like this: http://wiki.maemo.org/SimpleGL_example There's too much boilerplate code (setting up the X window, etc..) which makes it hard (or a copy'n'paste job) to start a new project utilitzing OpenGL ES. I guess most of this is covered by using Qt and its QGLWidget, which can be subclassed to implement the rendering/setup: http://doc.trolltech.com/4.6/qglwidget.html - This also provides texture loading using QImage. Still, maybe a more lightweight solution with Xlib and DevIL, packed into a nice, little C++ framework is what aGLESory is about (maybe with some additional helper classes to make it easier to get started). There is also Qt3d that is much one you are looking for. It is utility class to making easier to create OpenGl apps with using OpenGL API when graphicswiew and graphics iten is more heavy and hign level. It is least worth of checking up http://labs.trolltech.com/blogs/2009/11/10/qt3d-features-in-qt-46/ It would be nice if Flandry (the reporter on the GSoC ideas page) could elaborate a bit on what the idea is exactly. I've added myself as a possible mentor for this project, as it does interest me personally :) Kate HTH. Thomas ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Developing for Maemo 5 using Qt
Qt Mobility Phone API is not yet defined. You can get indication on icoming call using libtpsession. Libtpsession is not stantard one but you can find in from extras. I am currently working eventlogger interface to Qt Mobility, let's see could I find way to access Call hirsory with it. Kate From: ext Jose Maria Garcia-Valdecasas [jgvaldeca...@gmail.com] Sent: Thursday, February 25, 2010 1:05 AM To: Alhola Kate (Nokia-FNDC/Helsinki) Cc: maemo-developers@maemo.org Subject: Re: Developing for Maemo 5 using Qt Thanks for the update Kate. One question regarding QMobility, just in case you know the answer. Will QMobility API allow access to phone info? For example, check lost calls, last call, time of each call and so on. There seems to be an API for messages, but have not seen anything about specific phone features. Cheers, Jose 2010/2/24 kate.alh...@nokia.commailto:kate.alh...@nokia.com From: maemo-developers-boun...@maemo.orgmailto:maemo-developers-boun...@maemo.org [maemo-developers-boun...@maemo.orgmailto:maemo-developers-boun...@maemo.org] On Behalf Of ext Jose Maria Garcia-Valdecasas [jgvaldeca...@gmail.commailto:jgvaldeca...@gmail.com] Sent: Wednesday, February 24, 2010 11:15 PM To: Daniil Ivanov Cc: maemo-developers@maemo.orgmailto:maemo-developers@maemo.org Subject: Re: Developing for Maemo 5 using Qt Thanks for the links. Seems that platform compatibility chart is a bit out of date, as AFAIK Maemo 6 will never appear with that name. It is also out of the date for Maemo 5 features. Messaging, Contacts and Multimedia is going in pipeline and should appear with most features in external repo very soon. Bearer managementhas some dependency problem but they should be resolved also soon. Kate Anyway, i will check the APIs. 2010/2/24 Daniil Ivanov daniil.iva...@gmail.commailto:daniil.iva...@gmail.commailto:daniil.iva...@gmail.commailto:daniil.iva...@gmail.com Hi Jose! QtMobility is already available. API should be quite stable at the moment. http://qt.nokia.com/developer/new-qt-apis The only problem with Maemo 5 backend: http://qt.nokia.com/doc/qtmobility-1.0-beta/index.html#platform-compatability Thanks, Daniil. On Wed, Feb 24, 2010 at 10:06 PM, Jose Maria Garcia-Valdecasas jgvaldeca...@gmail.commailto:jgvaldeca...@gmail.commailto:jgvaldeca...@gmail.commailto:jgvaldeca...@gmail.com wrote: Ville, now it's official :) http://labs.trolltech.com/blogs/2010/02/24/qt-for-maemo-5-home-screen-widgets/ Thanks for your help. Now... i just need to check QMobility and it's use in Maemo 5. Cheers 2010/2/23 Ville M. Vainio vivai...@gmail.commailto:vivai...@gmail.commailto:vivai...@gmail.commailto:vivai...@gmail.com On Tue, Feb 23, 2010 at 11:53 AM, Sun Yalong yalong@digia.commailto:yalong@digia.commailto:yalong@digia.commailto:yalong@digia.com wrote: No, hybrid application is more like an application composed of web view + javascript that talks to C++ through QObjects exposed to it. Got a question that: is it possible to add hybrid application on Home screen like Widget does. Yes, there is nothing special about them. -- Ville M. Vainio http://tinyurl.com/vainio ___ maemo-developers mailing list maemo-developers@maemo.orgmailto:maemo-developers@maemo.orgmailto:maemo-developers@maemo.orgmailto:maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Developing for Maemo 5 using Qt
From: maemo-developers-boun...@maemo.org [maemo-developers-boun...@maemo.org] On Behalf Of ext Jose Maria Garcia-Valdecasas [jgvaldeca...@gmail.com] Sent: Wednesday, February 24, 2010 11:15 PM To: Daniil Ivanov Cc: maemo-developers@maemo.org Subject: Re: Developing for Maemo 5 using Qt Thanks for the links. Seems that platform compatibility chart is a bit out of date, as AFAIK Maemo 6 will never appear with that name. It is also out of the date for Maemo 5 features. Messaging, Contacts and Multimedia is going in pipeline and should appear with most features in external repo very soon. Bearer managementhas some dependency problem but they should be resolved also soon. Kate Anyway, i will check the APIs. 2010/2/24 Daniil Ivanov daniil.iva...@gmail.commailto:daniil.iva...@gmail.com Hi Jose! QtMobility is already available. API should be quite stable at the moment. http://qt.nokia.com/developer/new-qt-apis The only problem with Maemo 5 backend: http://qt.nokia.com/doc/qtmobility-1.0-beta/index.html#platform-compatability Thanks, Daniil. On Wed, Feb 24, 2010 at 10:06 PM, Jose Maria Garcia-Valdecasas jgvaldeca...@gmail.commailto:jgvaldeca...@gmail.com wrote: Ville, now it's official :) http://labs.trolltech.com/blogs/2010/02/24/qt-for-maemo-5-home-screen-widgets/ Thanks for your help. Now... i just need to check QMobility and it's use in Maemo 5. Cheers 2010/2/23 Ville M. Vainio vivai...@gmail.commailto:vivai...@gmail.com On Tue, Feb 23, 2010 at 11:53 AM, Sun Yalong yalong@digia.commailto:yalong@digia.com wrote: No, hybrid application is more like an application composed of web view + javascript that talks to C++ through QObjects exposed to it. Got a question that: is it possible to add hybrid application on Home screen like Widget does. Yes, there is nothing special about them. -- Ville M. Vainio http://tinyurl.com/vainio ___ maemo-developers mailing list maemo-developers@maemo.orgmailto:maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Graphical Interface designer for Qt
I hope you know that Maemo UI is quite differente from the desktop Qt version. It must be because it must be finger usable and most of desktop UI paradigm is based on mouse use. There aren't only QtButton, QtDialog, QtLabel ecc... in a user interface. Maemo has its own widget and there's no way (at the moment) to have a real preview of them. If you have seen the recently published video on youtube, showing Maemo 6 widgets, you surely have noticed that Qt developers are showing Maemo support in QtCreator, but it's not ready/published at the moment. We should not mix two things. Maemo 6 widgets are based on new QGraphiscview based widget set and that's different than Maemo 5 widget set that is based on enhaged Qt desktop widget set. You can see video of Maemo 5 widgets here. Only bad thing in this video is that they are using stylus, i have not used mine with N900 in many months because it is not needed with finger optimized widgets. http://labs.trolltech.com/blogs/2010/02/15/qt-462-for-maemo-5-released/ Kate ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: MeeGo
From: maemo-developers-boun...@maemo.org [maemo-developers-boun...@maemo.org] On Behalf Of ext Max [petersonm...@googlemail.com] Sent: Monday, February 15, 2010 8:30 PM To: Johan Helsingius Cc: maemo-developers@maemo.org Subject: Re: MeeGo Nokia was the leader with the communicator phone, everyone wanted since the smartphone age, nokia knows, selling hardware has gone and acquired Qt. the N 900 is a relaunch of the communicator. but no phone house gets it. In the meantime we have - Motorola Milstone and - sony ericson x-peria 10 http://www.heise.de/newsticker/meldung/MWC-Was-Kleines-von-Sony-Ericsson-930178.html?view=zoom;zoom=1 Nokia knows, that the linux app store is sooo small and buggy, not comparable with Iphone, OVI Store for Maemo has just opened, it will grow. Think how big was Apple appstore half of year after iPhone was published ? I think that it was not existing at all. Furthermore maemo5 is not allowing to install Qt, the overslept to bring mamemo 06 on the nokai N 900. There has been Qt for Maemo 5 lot before even N900 was released. Qt for Maemo5 was releaste together with SDK beta about one year ago. Qt has been instalable from repositories and now in MWC, we also annouced that final Qt4.6 port for Maemo 5 is there http://qt.nokia.com/products/qt-news-from-mwc Then Symbian was made open source, so no meamo is needed anymore. Maemo is Open Source but it is also targeted to diferent device category than Symbian. The rest is to merge maemo and pull off the ground for the N900, as app developers can make apps open for symbian. The result is a delay again and again no selling of phones, esp., the N900 The mass market buys phone in a phonehouse, not because linux is on it. that would be a side effect to bring linux to the masses. It depends a lot of market area how end users buy their device. In some markets, like in North America most ones buy subsidized phone from Operators. In many others markets, they buy device from shop and then SIM from operator. We need good selling phones, then this list makes sense. Which consumer wil buy a N900 , while Qt is not installed on maemo 5, they wait for a upgrade to mamemo 06 and now they wait 2 years for N900 with meego. End user does not even know what is Qt or GTK. When end user installs applications, they does not even know is it Qt or GTK application. many of OVI store applivations for Maemo 5 are already Qt apps. Kate ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Qt on N900 (+ video)
N900 is Maemo 5 . The current device has Qt4.5.3 core libraries in flash, Qt4.5.3-gui etc from app repository. Qt4.6 for Maemo-5 final release is scheduled 1Q2010 Kate From: maemo-developers-boun...@maemo.org [maemo-developers-boun...@maemo.org] On Behalf Of ext Max [petersonm...@googlemail.com] Sent: Friday, October 09, 2009 12:49 PM To: Ville M. Vainio Cc: maemo-developers@maemo.org Subject: Re: Qt on N900 (+ video) thanks, Nokia n900 should be delivered with mameo Qt default ! isn´t it then maemo 6? On Fri, Oct 9, 2009 at 11:45 AM, Ville M. Vainio vivai...@gmail.com wrote: http://labs.trolltech.com/blogs/2009/10/09/qt-on-the-n900/ -- Ville M. Vainio http://tinyurl.com/vainio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: New apps for fremantle with Qt?
From: maemo-developers-boun...@maemo.org [maemo-developers-boun...@maemo.org] On Behalf Of ext Andrew Flegg [and...@bleb.org] Sent: Saturday, September 05, 2009 11:47 AM To: Soini Mox (EXT-Movial/Helsinki) Cc: maemo-developers@maemo.org Subject: Re: New apps for fremantle with Qt? On Sat, Sep 5, 2009 at 08:01, ext-mox.so...@nokia.com wrote: However, if you want to have the exact same user experience as the preinstalled Maemo 5 applications have (as seen in all youtube videos and the SDK), then you have much easier time and faster development with the gtk-based hildon widgets in Maemo 5. This doesn't give much of a transition plan for developers, or the chance to fix things in the Qt API whilst it's in community support mode. Let's once again get back to the roots. There is no one-to-one parity between Qt and Hildon widgets but same functionality can be done with both of them. Mox sees a big problem that there are some composite widgets missing and you need to build them from several Qt basic widgets. I don't see it as much problem at all because Qt does make much more compact code and things are easily doable. We in qt4.garage.maemo.org have been concentrating more to fundamental issues that were not easily doable with plain Qt like input method, maemo-style integration, finger kinetic scroll or some hildon dependent window manager properties etc. Because there are several persons that see missing of some ready made composite widgets as big problem, we should also do some solution to this even it is not complicated at all. It's unclear who, exactly, the Qt community who are doing the support are. Is it people like David Greaves (lbt) and others at http://qt4.garage.maemo.org/ or is it Kate and other people at Nokia? Maemo qt port has been done from beginning in full open source fashion anyone can participate open project and anyone can offer support as free or for charge an for any open source software. We have several persons that are Nokia employees, who are doing work with this Qt, we just do it as open. About this supported status, we have plan to to clarify situation in maemo summit. Presumably, with Fremantle (almost) out, people at Nokia are now working on Harmattan and the transition to Nokia supported for Qt. Is this being done in the open? Is the Harmattan UI going to be similar enough that the concepts (app menus etc.) are translatable? We are telling more about Harmatan UI much advance before releasing actual device. There will be also presentations about Harmatan subject in maemo summit. If so, presumably Nokia are going to need an app menu API; and it seems perfectly reasonable that we should be seeing it sooner rather than later. There's a lot of confusion in this thread, and it risks fueling FUD about the stability and viability of Fremantle as a platform if - when developers are starting writing Fremantle apps - they can't see where the platform is going in 1-2 years. We have tried to release key information much advance. First story about Harmatan and Qt was told in LinuxTag 2008, that more than one year from this date. Maemo Qt project were also published as garabe project around same time. We did first Fremantle releases of Qt together with alpha SDK . The equivalent of Hildon (i.e. mobile, finger optimized widgets) is roughly the QT mobility http://labs.trolltech.com/page/Projects/QtMobility, which is not available yet. We have finger optimized widgets already. We did not like to make something different than Hildon but rather we took Hildon style and adapted it to widgets. Then we added missing features listed above. So that raises some obvious questions: * When _is_ it going to be available? * Will it be available for Fremantle? * Will it provide a seamless experience with Hildon on Fremantle? You should rather think Qt Mobility as parallel track. Once again, we have finger friendly basic widgets. About some composite widgets mentioned earlier to get exactly same look and feel layout should be same than Hildon and that's not a problem. You don't need Qt mobility to make Qt apps with Hildon look and feel. Most of that page is talking about high-level services APIs (multimedia, contacts, location etc.). What if I just want to write a simple calculator app? If you would like to write simple calculator app, you just need basic widgets like buttons, labels, text entries, containers etc. We have all of them and they are using Hildon style. You will have exactly same look and feel as you have with GTK The discussion about missing widgets has been has been about some composite widgets like picker button that you can compose from dialog, scrollabele list and buttons. Kate ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: New apps for fremantle with Qt?
From: maemo-developers-boun...@maemo.org [maemo-developers-boun...@maemo.org] On Behalf Of ext Alberto Garcia [agar...@igalia.com] Sent: Friday, September 04, 2009 7:38 PM To: maemo-developers@maemo.org Subject: Re: New apps for fremantle with Qt? On Fri, Sep 04, 2009 at 06:18:37PM +0300, Kate Alhola wrote: I have used Maemo 5 and N900 since early prototypes and i don't see lot of important frequently used functionality missing from Qt. I admit that some rarely used widgets like earlier mentioned date and time picker are missing etc. Rarely used widgets? Come on, these are used all throughout the platform. Moreover, even if the time and date pickers were not so commonly used, their style, user experience, and base API (through HildonPickerButton, HildonPickerDialog and HildonTouchSelector[Entry]) are central to the Fremantle UI, and certainly the most recommended starting point for anyone writing an application for Fremantle. As I said before, we are doing examples how to do many of these things with Qt . The question is not whether similar widgets can be created using Qt. Of course they can. What people are asking here (among other things) is whether there are Qt widgets similar to HildonAppMenu or HildonPickerButton -which are absolutely essential for creating Fremantle applications- or developers are supposed to write them themselves. To avoid re-inventing the wheel again we are providing examples how you can do things with Qt. If some thing can be done with dozen lines of Qt code, it just matter of taste, should we provide widget or just example that you can cut-and-paste. The most important thing is that we have all basic widgets like finger scrollable lists etc so that only action needed is to collect them together. If some of these composite widgets are so big problem, we can collect these examples as widget library. Kate ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Maemo will switch (completely?) to Qt?
On Mon, 2009-07-06 at 16:23 +0100, Aniello Del Sorbo wrote: 2009/7/6 Andrea Grandi a.gra...@gmail.com: What always stopped me from writing Qt application was that I had to learn a new language to use it. Of course the same reason applies the other way around. As much as I would love to learn Qt, I really hate C++. And I don't want to rely too much on Python. If you plan to stay in the business as career software developer, then the ability and willingness to retool yourself with new language/OS is a must. Otherwise, you have a slim chance to make a living for yourself and your family. Let me see, Algol/IBM360, Fortran/IBM360, PL/1/IBM360, Pascal/PC, C/Win,UNIX, C++/Win,UNIX,Embedded, Java/* - you get the picture. And this barely covers first 15 years of paid experience. The army of software developers is expotentially growing in east europe, asia, china, india, and here is US and writing new languages has become extremely easy compare to the old days. You must also see the thing from Nokia's view. To stay in leading position in cellular busines, then ability to renew and respond to challanges is mandatory. You now who are challangers with fancy animated UI and touch screen, to respond this, Nokia need to take next generation toolkit in use. I rather see this as choice between Clutter and Qt. GTK+ is previous generation toolkit. Now Maemo and Symbian developers both are in same situation, they need to learn new toolkit that has required feateres to compete in market. Kate ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Fremantle OpenGL wrapper?
From: maemo-developers-boun...@maemo.org [maemo-developers-boun...@maemo.org] On Behalf Of ext Qole [qole.tab...@gmail.com] Sent: Thursday, June 04, 2009 9:47 PM To: maemo-dev Subject: Re: Fremantle OpenGL wrapper? I hoped to start a discussion about making an OpenGL - GL ES 2 translation library for porting games to Maemo 5, in the manner that is being done in the Pandora community. I have been having several presentations to maemo community how to use OpenGL-ES in maemo You can find them from my blog http://blogs.forum.nokia.com/blog/kate-alholas-forum-nokia-blog It is ot so much question of transition libraries but understanding what is OpenGL-ES and how it relates to desktop OpenGL I checked openpandora wiki http://pandorawiki.org/Development_tutorials . It looks a like they are having very similar approach, no silver bullet OpenGL to OpenGL-ES translation library but just OpenGL-ES1.1 tutorial and example how to use OpenGL-ES with SDL. I have had my tutorials about how to use OpenGL-ES2.0 and how to use it with Qt . If you read http://pandorawiki.org/OpenGL_ES_1.1_Tutorial . It tells a lot what is the qestion. There is just no single OpenGL but desktop OpenGL has many, many legacy layers of API's . Mobile OpenGL implements only the most efficient subset of them. Because there is hundreds of ways to use OpenGL, there is no simple way to convert. The Openpandora OpenGL-ES1.1 wiki tries to explain ( as i had in my presentations/blog and maemo wiki page ) that as example OpenGL has legacy API glBegin/glVertex/gEnd that are obsoleted in OpenGL-ES and OpenGL-ES only supports way to pass vertexes as array. Of course passing them as array is much more efficient, just one API call with big number of vertexes as opposed one call for one coordinate point. That just an example what is the difference. For game developer it is much more sense port the application to use vertex arrays because it is more efficient also in desktop. When we go to OpenGL-ES2.0 or Desktop OpenGL-2.0, we have thing called programmable shaders. OpenGL1.x or OpenGL-ES1.x has fixed function non programmable pipeline doing transformations and lighting. In OpenGL-(ES)2.0 it is all programmable and it offers much more features to make much better looking games. I strongly recommend to take it in use. If you still would like use fixed function pipeline to port old not so advanced games, you can still use OpenGL-ES1.x emulation libraries in maemo. I hope that we can get them in to next SDK release. Kate ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Fremantle OpenGL wrapper?
From: maemo-developers-boun...@maemo.org [maemo-developers-boun...@maemo.org] On Behalf Of ext Qole [qole.tab...@gmail.com] Sent: Tuesday, June 02, 2009 9:05 PM To: maemo-developers Subject: Fremantle OpenGL wrapper? Hi all, I'm not much of a developer, but I really think it would be a good idea to get a couple OpenGL wrappers ready for Fremantle. What do you like the wrapper do ? If you like to get easiest way to run OpenGL you can take example skeleton from Imagination OpenGL-ES2.0 examples. They run in Fremantle, you just need to compile them or then you can take Qt GLWidget as it is done in hellogl_es2 that is part of Qt4.5 source. I also runs nicely in Fremantle. Good thing using Qt as a wrapper is that you can use full GL but you can mix it with Qt UI widgets or QGraphicsWiew higer level drawing primitives. Kate I have a thread on talk.maemo.orghttp://talk.maemo.org[1], but maybe I should be posting here too. [1] http://talk.maemo.org/showthread.php?t=29085 I think there should be a wrapper for applications that use OpenGL directly, and maybe an SDL library for games that use OpenGL via SDL. There's work in this area for the Pandora, but I haven't seen much yet for Maemo devices. I propose starting with a simple test game like Armagetron Advanced [2], which actually runs on an N800 at 3 fps with software OpenGL rendering. This game uses SDL and the mesa GL libraries, which suggests that an SDL library like the one developed for the Pandora [3] might work here. [2] http://packages.debian.org/lenny/armagetronad [3] http://www.gp32x.com/board/index.php?showtopic=48023 Like I said, I'm not really a developer, and I can't really take these ideas and make them happen. But I'm paying close enough attention to these things to see that this seems to be an important gap in the available software right now. I would prefer comments on my talk.maemo.orghttp://talk.maemo.org thread, but you can discuss here, too. -- enthusiast, n. One whose mind is wholly possessed and heated by what engages it; one who is influenced by a peculiar fervor of mind; an ardent and imaginative person. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
