Message from discussion Necessitas alpha 4, a New Hope!
Received: by 10.58.91.100 with SMTP id cd4mr4062766veb.8.1346019616000;
Sun, 26 Aug 2012 15:20:16 -0700 (PDT)
Received: by 10.220.49.131 with SMTP id v3ls2584769vcf.1.gmail; Sun, 26 Aug
2012 15:20:14 -0700 (PDT)
Received: by 10.58.91.165 with SMTP id cf5mr4153449veb.34.1346019614868;
Sun, 26 Aug 2012 15:20:14 -0700 (PDT)
Received: by 10.58.91.165 with SMTP id cf5mr4153448veb.34.1346019614856;
Sun, 26 Aug 2012 15:20:14 -0700 (PDT)
Received: from mail-vb0-f49.google.com (mail-vb0-f49.google.com [126.96.36.199])
by gmr-mx.google.com with ESMTPS id y4si3135620vds.2.2012.08.26.15.20.14
Sun, 26 Aug 2012 15:20:14 -0700 (PDT)
Received-SPF: pass (google.com: domain of taipanroma...@gmail.com designates 188.8.131.52 as permitted sender) client-ip=184.108.40.206;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of taipanroma...@gmail.com designates 220.127.116.11 as permitted sender) smtp.mail=taipanroma...@gmail.com; dkim=pass header...@gmail.com
Received: by vbbfo1 with SMTP id fo1so4055762vbb.36
for <email@example.com>; Sun, 26 Aug 2012 15:20:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
Received: by 10.58.189.73 with SMTP id gg9mr10995343vec.26.1346019614481; Sun,
26 Aug 2012 15:20:14 -0700 (PDT)
Received: by 10.220.71.73 with HTTP; Sun, 26 Aug 2012 15:20:14 -0700 (PDT)
Date: Mon, 27 Aug 2012 01:20:14 +0300
Subject: Necessitas alpha 4, a New Hope!
From: BogDan Vatra <taipanroma...@gmail.com>
To: android-qt <firstname.lastname@example.org>, Necessitas <necessitas-de...@kde.org>
Content-Type: text/plain; charset=windows-1252
Today I have the great honor to announce the alpha 4 release of
Necessitas. Since Nokia=92s radical change of direction, Qt has had a
very hard time and many asked themselves whether it was worth
investing their time and money in it anymore. I=92m not going to comment
further on Nokia=92s recent stupid decisions because I value too highly
the contributions Nokia has made to Qt.
Instead, I want to comment on the future of Qt and how to make sure
it will survive no matter what. I didn't comment on this matter until
now because I was too busy getting this release out, and how better to
prove to you folks that we are committed to Qt than to continue our
work with this new release? First and foremost Qt is free software,
according to the KDE Free Qt Foundation Nokia (and most probably
also Digia) must release it under both the LGPL 2.1 and the GPL 3.
Otherwise *"the Foundation has the right to release Qt under a
BSD-style license or under other open source licenses. The agreement
stays valid in case of a buy-out, a merger or bankruptcy."* So from
this point of view you don't have anything to worry about! What about
Qt's future development, who will continue to work on it now that
Nokia have dropped it? While we all share great hopes that Digia will
manage the Qt Project well, the beauty of free software if that it
doesn't need any single company behind it, it also needs a committed
community; KDE, Necessitas, ICS, KDAB etc, and most importantly *YOU*!
Now more than ever it is very important for all of us to join together
and for you to show your support and appreciation. You have to ask
yourself which option is better for you:
- to be selfless and to spend some of your time (or your money) to
make the things you love better and to keep them free for everybody...
- or to be selfish, forget about Qt and start learning some crappy
closed source C# or iFramework instead which, some day (sooner or
later), will die with the *ONLY* company behind it?
We choose the first option. The Necessitas developers will do their
best to succeed where Nokia has failed: to make Qt available on a huge
number of (Android-powered) devices. Yes baby, the next billion is
This alpha 4 release is one of the final steps that we needed to do.
It *should* be our last alpha release! If there are no show-stopping
regressions reported, in one and a half months we'll ship the first
beta release. Why one and a half months? From now on, to be sure that
there are no regressions introduced, releases will be made in two
- The first step is to release the SDK, and to push the new Android
libs to Ministro's testing repository. The new Android libs will stay
in the testing repository for at least one month to give developers
enough time to test their apps using them. They should use the
Ministro configuration tool to switch to the testing repository.
Additional updates will be released in the testing repository and this
period may be extended if any regressions are reported. A new update
must stay for at least two weeks in the testing repository; known
issues are not considered regressions!
- Once the new libs in the testing repository are determined to be
regression-free, they will land in the stable repository and they will
be available to all Android users.
In other words developers should perform the following two steps:
- Update the SDK, use the Ministro configuration tool to switch to
the testing repository, update your apps, and report any regressions.
*DO NOT* publish any apps on Google Play until the version from the
testing repository reaches the stable repository, otherwise they will
- *WAIT* for the alpha 4 release to land in the stable repository,
then you can publish the updated apps on Google Play!
Go back and carefully read these two statements one more time!
The alpha 4 release will stay in the stable repository for another
two weeks, then *if no regressions* are reported, it will be
re-released as beta 1. Basically we'll simply re-label it as beta 1!
From that moment we'll guarantee that the ABI/API will remain stable
and therefore you can safely deploy any apps you like on Google Play!
The most important changes:
Necessitas has a new home page: http://necessitas.kde.org
Here you can find latest news and information on how to get involved
(http://necessitas.kde.org/getinvolved.php), how to help and to get
help (http://necessitas.kde.org/gethelp.php) and much more.
We've also moved the wiki and the bugs from sf.net to KDE's infrastructure.
- Update to Qt 4.8.2
- Native Android look&feel for classic widgets.
- Native Android menus - known limitation: Android menus support only
one submenu. We'll try to find a solutions for this problem in a
future release (follow https://bugs.kde.org/show_bug.cgi?id=3D304240 to
check its progress).
- Fixed user Java/C++ interaction.
- New assets access scheme. Please add "assets:" prefix, check
http://techbase.kde.org/Development/Tutorials/Necessitas for more
- SMP safe atomics.
- Many bug fixes.
- As stated above, native Android menus support only one submenu.
- While some demos and examples work fine, many will not, particularly
- No other new issues.
- Extracts Android native look&feel.
- Secure config files downloading.
- Bug fixes.
- Android Bluetooth implementation.
- A few bug fixes.
- No new issues.
- Updated to 2.6 (alpha).
- Fixed bug in ma-make.exe where all rule commands were run through a
batch file leading to each 8192nd character being dropped. Now
CreateProcess is used for nearly all commands, and a work around for
the (MS) batch file bug was also implemented.
- A few other bug fixes.
- This release is based on an un-released QtCreator version, so some
unexpected issues may occur.
- When you install the qt src package, the source paths mapping is not
set automatically anymore so to debug the qt libraries at the source
level, you need to set it manually: put
=93/tmp/necessitas/unstable/Android/Qt/482=94 in the source path and
=93YOUR_INSTALLATION_FOLDER/Android/Qt/482=94 in the target path.
- On Windows, adb loses track of the connected devices a lot and
otherwise misbehaves (worse with emulators), causing QtCreator to
hang. When this happens, to get it to respond again you can execute:
android-sdk\platform-tools\adb.exe kill-server &
android-sdk\platform-tools\adb start-server &
android-sdk\platform-tools\adb devices (from cmd.exe in
taskkill /F /IM adb.exe /T (from cmd.exe in any directory)
SDK Installer framework has been updated with upstream=92s latest
changes. One of the biggest improvements is the ability to add
3rd-party repositories, so:
- If you are a developer who has something interesting to share for
Android (e.g. plugins, custom widgets, QML controls, etc.) please add
your repository to
- If you are a developer looking for something which is not shipped
with the Necessitas SDK, you can check the same page:
- Due to some bugs, the old installer can=92t be used update the SDK, so
you need to reinstall the SDK using the new installers.
Updated the Android NDK and Android SDK to latest versions. Please do
not use the Official Google Android NDK, instead use our Necessitas
The following people have made large contributions to this release
- Marco Bernasocchi <ma...@bernawebdesign.ch> Moved all the bugs from
sf.net to kde.org. He is also one of the Necessitas website & wiki
- Ray Donnelly <mingw.andr...@gmail.com> as usual he had a decisive
contribution to this project. He created a custom Android NDK (the
official NDK-r8b was not able to build Necessitas), gdb with Python
support, and most importantly, the Windows and Mac OS X SDKs.
- Willy Gardiol <wi...@gardiol.org> reworked most of Necessitas
website and wiki pages. He is also one of the Necessitas website &
- Marijn Kruisselbrink <mkruisselbr...@kde.org> and Chris Browet
<c...@semperpax.com> did most of the native Android menu integration.
- Lauri Laanmets <lauri.laanm...@proekspert.ee> Android Bluetooth
- Tyler Mandry <tman...@gmail.com> reworked Java/C++ interaction,
added support for Android QML debugging in QtCreator.
- BogDan Vatra <bog_dan...@yahoo.com> Most of the QtCreator Android
Plugin, Ministro updates, SDK Installer updates, Android native
look&feel (Qt and Ministro implementation), cleanup of native Android
menus integration, new assets implementation, SMP safe atomics, most
of the bug fixes.
As usual, special thanks goes to KDE for their hosting and support!
I'll also like to personally thank everyone who has summited bugs (and
even better, patches for some of them!)
You can check out Necessita's glory wall
(http://necessitas.kde.org/people.php) for a complete list of all
contributors (who agreed to be listed).
You can grab the new SDK installer for the following platforms:
-Mac OS X: http://files.kde.org/necessitas/installer/release/mac_osx-online=