Three days from the launch and I'm already working on QT - quick and all the new SDK suite...
Very good representation, with compliments! Not later than tonight (local time ;) ) I setup open-source projects for the community.
Well, so a little question, not really technical I think. When I start QT-Creator I can decide to create a QT-Quick project (that can later put as mobile project for symbian etc.) or a QT-Mobile project directly. What does it happens between the simulator and all other tools for mobile development / debug working on a QT-Quick project ?
(I have not read all the documentation on the new version)
[quote author="atrasatti" date="1295884054"][quote author="xsacha" date="1295706806"]Just decided it isn't worth the effort. Forum Nokia is quite large and there's only 3 (possible more, I know) winners. Better off selling the app.[/quote]
The competition rules DO NOT say that you are not allowed to also sell your application, so why not build the hottest application, make the source available for others to learn from the best, get the E7 and sell it on Ovi store and make money?
yeah. And I am really hoping the best for Symbian^3. Right now I am using a Nokia N8 as my default phone, I see the Symbian^3 has some issues. But we are a bit out of topic here. Let's start a new discussion :)
Hmm this article is really interesting but as far as IDE is concerned if we exclude cross platform thing then VS is the best IDE i can think of on the planet as of now, Qt creator is still behind though not too far.
Does anyone know if it's possible (or will be possible) to download them? The flash player works quite bad on Linux, and all this embedded players are quite inconvenient to seek the video when it's about an hour long. :(
[quote author="xsacha" date="1291477086"]
But, if anyone is following this, when will this SDK come out of beta? Presumably they will wait until they have the shipping version of Qt that the first Meego devices will use.
I can't find a roadmap for it. [/quote]
If somebody were to ask me last year, I would say that by December holidays I would be using the N900's successor. However, right now I think that the first MeeGo phone from Nokia, or other big vendor, still needs several months from now.
Why? Well, Qt 4.7 and Qt Quick is great, but the MeeGo Touch Framework is deprecated for new development, and everyone should use Qt Quick. But... the Qt Components project is still very very young.
Also, the SDK has some problems, IMHO. Without an Intel graphics chip, or hardware virtualization, some stuff doesn't even run, which is a problem. I have a modern PC, and I found it was surprisingly difficult to try MeeGo (compared to other stuff).
I am using this release candidate right now and it seems pretty good. I really hope the merge with Nokia Qt SDK to happen when the final 2.1 is released. I want to be able to create both Desktop and Mobile applications using one SDK :D
I've posted this on other forums, but the common misunderstanding is that static linking is prohibited under the terms of the LGPL, it is not.
Section 6a provides a provision which allows static linking provided that the developer provides (binary) object code, or an offer to do so for a period of 3 years, which may be re-linked with the LGPL components.
Regarding app bundle signing restrictions, these are prohibited by the GPL, but the LGPL allows you to distribute under "...terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications."
If those terms comply with 6a, i.e. that you provide access to unsigned object code in a form which may be relinked, modified for the users own use etc., then there doesn't seem to be a conflict.
6b specifies dynamic linking, but it is only one option in section 6.
Whether 'permitting modification' refers to the actual app bundle, or the components provided under 6a is to my mind an open question. If it were so, then 6a would be invalid regardless. The prerequisites for doing so would be an apple developer account and apple's tools / hardware etc, but under the terms of the LGPL and GPL, the developer is not required to provide these.