Qt Creator 2.2 released
The latest version of Qt's IDE, Qt Creator, has been released. According to the announcement on the Qt Labs blog: Even if this release is following the previous release after not even ten weeks it contains a whole lot of new features as well as bug fixes and enhancements making an update worthwhile. The key point of interest is in its ability to now target MeeGo and maemo.org's open source autobuilder. Available as a download, it will be rolled into the Qt SDK as an update "in a few weeks".
Branches for MeeGo 1.2 finalisation created
Rolla Selbak has announced that the code freeze in effect whilst the MeeGo 1.2 branches were created has now been lifted: The MeeGo 1.2 Branch has been created successfully. Trunk and 1.2 are now re-open for development. Please carefully read the following short, informative wiki on the branching phase which covers: Branching phase; Trunk frozen during branching process; Which changes are accepted into Branch; How to submit a bug-fix into the Branch; Setting your home: and devel: OBS projects to build against Branch
Security architecture for MeeGo won't be Harmattan's, but what will it be?
Alberto Mardegan took the opportunity of a thread on meego-dev to raise an architectural question about MeeGo's security framework: I think we all agree that a security framework is needed. What will it be, then? In your mail from March 7th, you announced that the long term focus for the MeeGo security would be end-user privacy. To me, that also means having the means for a process which "owns" some of the user data to establish the identity of another process which requests access to the said data. IMHO, this is something that MSSF is doing very well in Harmattan, so I hope that this possibility will also come to MeeGo. The response suggested that one of the many existing Linux security frameworks would be used (future tense). None of these have been used in mainstream mobile devices though, and often require complex administration. It may well be that Nokia's MSSF (originally called Aegis when part of Maemo 6) will be the most robust and tested solution by the time MeeGo selects one.
Working around Qt 4.7.2 bugs in the CSSU
Alberto Mardegan has found a workaround for the issues he was having with Oculo, his webpage content widget, written in Qt: Your hint was extremely precious! Indeed, adding this just at the beginning of main() does the trick: [...] Benoît HERVIER has also raised the issue of needing developers familiar with Qt to tackle the rendering issue present in the 4.7 upgrade contained in the Community SSU.
Which SDK for MeeGo 1.2 tablet & handset?
Cornelius Hald has asked a question which is very appropriate for those of us coming from a Maemo background: I've got a Qt/QML app that is working fine on Maemo5 and Symbian. Now I'd like to compile it for MeeGo 1.2. I need MeeGo 1.2 because of the Qt Mobility version included. Also I realize that MeeGo 1.2 is not final yet. What's the best/easiest way to install that SDK? So far he's had success with the May 3rd preview release for Linux. It would be interesting to document the leanest and most consistent SDK experience for targetting Maemo 5, Symbian and MeeGo; hopefully something made easier by the Qt Creator 2.2 release.
Locking screen orientation in MeeGo
Cornelius Hald has asked how to lock an application's screen orientation in MeeGo: in my C++/QML application I want to lock the screen orientation to portrait mode. How I can I do that? There was a thread about this a month ago but without clear answer. I've got working solutions for Maemo5 and Symbian and now I'm testing on MeeGo/Tablet 1.2 on ExoPC. The only current way of doing this is within MeeGo Touch Framework (MTF) applications, a toolkit which is deprecated in MeeGo 1.2 and may not even ship as part of MeeGo 1.3. More work needed here.
Blocker bug process for MeeGo 1.2
Rolla Selbak has reminded people of the process required to raise and triage bugs which might block the MeeGo 1.2 release: Only approved blockers targeting the Branch will be accepted into the Branch. The 'blocker' flag in bugs.meego.com exists a few weeks before branching. Anyone can set a feature or bug as a 'proposed' blocker through bugs.meego.com. Within the bug, state your case as to why you believe this bug should be a blocker for 1.2. Release Engineering gathers feedback from Program Management and Development teams as to which bugs should be accepted or rejected.
Qt Commercial licence and MeeGo Compliance
A question on meego-dev was simple: My apologies if this has been discussed in the past already but I'm struggling to get a definite answer to this question: - Can someone switch to the Qt Commercial license, and yet pass the MeeGo compliance test? The answer is "no": the main system Qt must be MeeGo's, which is obviously the open source one, with minor patches. An application or the system can provide a Qt alongside, which must only be used for specific applications, which would then possibly not be MeeGo Compliant.