Necessitas alpha 4, a New Hope!

Showing 1-61 of 61 messages
Necessitas alpha 4, a New Hope! BogDan 8/26/12 3:20 PM
Hello folks,

 Today I have the great honor to announce the alpha 4 release of
Necessitas. Since Nokia’s 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’m not going to comment
further on Nokia’s 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[1] 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
coming!
 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
steps:
  - 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
stop working!!!
  - *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.

Qt framework:
- 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=304240 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
information.
- SMP safe atomics.
- Many bug fixes.
Known issues/limitations:
- As stated above, native Android menus support only one submenu.
- While some demos and examples work fine, many will not, particularly
on Windows.
- No other new issues.

Ministro:
- Extracts Android native look&feel.
- Secure config files downloading.
- Bug fixes.
Known issues/limitations:
- None.

Qt mobility:
- Android Bluetooth implementation.
- A few bug fixes.
Known issues/limitations:
- No new issues.

QtCreator:
- 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.
Known issues/limitations:
- 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
“/tmp/necessitas/unstable/Android/Qt/482” in the source path and
“YOUR_INSTALLATION_FOLDER/Android/Qt/482” 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
YOUR_INSTALLATION_FOLDER) or:
taskkill /F /IM adb.exe /T  (from cmd.exe in any directory)

SDK Installer framework has been updated with upstream’s 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
http://community.kde.org/Necessitas/3rd_party_SDK_repositories
- If you are a developer looking for something which is not shipped
with the Necessitas SDK, you can check the same page:
http://community.kde.org/Necessitas/3rd_party_SDK_repositories.
Known issues/limitations:
- Due to some bugs, the old installer can’t 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
Special version.
The following people have made large contributions to this release
(alphabetic ordering):
 - Marco Bernasocchi <ma...@bernawebdesign.ch> Moved all the bugs from
sf.net to kde.org. He is also one of the Necessitas website & wiki
maintainers.
 - Ray Donnelly <mingw....@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 &
wiki maintainers.
 - Marijn Kruisselbrink <mkruiss...@kde.org> and Chris Browet
<cb...@semperpax.com> did most of the native Android menu integration.
 - Lauri Laanmets <lauri.l...@proekspert.ee> Android Bluetooth
implementation.
 - Tyler Mandry <tma...@gmail.com> reworked Java/C++ interaction,
added support for Android QML debugging in QtCreator.
 - BogDan Vatra <bog_d...@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:
-GNU/Linux: http://files.kde.org/necessitas/installer/release/linux-online-necessitas-alpha4-sdk-installer

-Windows: http://files.kde.org/necessitas/installer/release/windows-online-necessitas-alpha4-sdk-installer.exe

-Mac OS X: http://files.kde.org/necessitas/installer/release/mac_osx-online-necessitas-alpha4-sdk-installer.7z

Yours sincerely,
BogDan.

[1] http://kde.org/community/whatiskde/kdefreeqtfoundation.php
Re: Necessitas alpha 4, a New Hope! mingw.android 8/26/12 3:21 PM
Fantastic!
Re: Necessitas alpha 4, a New Hope! Andrei Zuse 8/26/12 7:30 PM
Amazing Job!

Thanks Necessitas Developers!
Re: Necessitas alpha 4, a New Hope! Ruslan Vorobei 8/27/12 12:54 AM
Good Job!
Re: Necessitas alpha 4, a New Hope! Peter Bočan 8/27/12 12:07 PM
Great work, BogDan, well done :).

Dňa pondelok, 27. augusta 2012 0:20:14 UTC+2 BogDan napísal(-a):
Re: Necessitas alpha 4, a New Hope! Nal Sav 8/27/12 12:14 PM


On Mon, Aug 27, 2012 at 3:50 AM, BogDan Vatra <taipan...@gmail.com> wrote:
Hello folks,

 Today I have the great honor to announce the alpha 4 release of
Necessitas. Since Nokia’s radical change of direction, Qt has had a

Very awesome to BogDan, Ray and entire team!!!

Congrats... 

and thank you for your sweat and blood invested-- to all contributors... we are all indebted to you guys...

-Nalin

Re: Necessitas alpha 4, a New Hope! qt next 8/27/12 2:16 PM
Congratulation :) yeee !

I have tested the alpha 4 :

1)- the release apk is always named "debug" : is it normal ? does it means that the apk contains debug information (I don't wants to provide apk with debug info inside) ?
2)- my application is fully qml : if I don't enable opengl lib in qt creator, all images are awvfull (gradiant not good looking) : If I enable opengl, my application is more fluid and the images looks good : good gradiant .. Perhaps it's good to have opengl enable by default when the application is qml based ? or at least add this information in documentation ?



2012/8/27 Nalin Savara <nsn...@gmail.com>

Re: Necessitas alpha 4, a New Hope! Nal Sav 8/27/12 2:33 PM


On Tue, Aug 28, 2012 at 2:46 AM, qtnext <qtn...@gmail.com> wrote:
Congratulation :) yeee !

I have tested the alpha 4 :

1)- the release apk is always named "debug" : is it normal ? does it means that the apk contains debug information (I don't wants to provide apk with debug info inside) ?

yes; the release apk is always named "debug".

Not sure abt normal... but myself, to be double-sure  create a release apk by:
a. cd to android folder in project dir
b. use command: ant clean release

-
2)- my application is fully qml : if I don't enable opengl lib in qt creator, all images are awvfull (gradiant not good looking) : If I enable opengl, my application is more fluid and the images looks good : good gradiant .. Perhaps it's good to have opengl enable by default when the application is qml based ? or at least add this information in documentation ?

This is expected behavior:-
a)  not including opengl will use the software renderer-- available on all phones... but worse looks, performance.

b) enabling opengl will use hardware renderer-- may not be available in all-- but faster 

Hope this helps...

Regards,

Nalin

Re: Necessitas alpha 4, a New Hope! qt next 8/28/12 1:16 AM


2012/8/27 Nalin Savara <nsn...@gmail.com>


On Tue, Aug 28, 2012 at 2:46 AM, qtnext <qtn...@gmail.com> wrote:
Congratulation :) yeee !

I have tested the alpha 4 :

1)- the release apk is always named "debug" : is it normal ? does it means that the apk contains debug information (I don't wants to provide apk with debug info inside) ?

yes; the release apk is always named "debug".

Not sure abt normal... but myself, to be double-sure  create a release apk by:
a. cd to android folder in project dir
b. use command: ant clean release

-
2)- my application is fully qml : if I don't enable opengl lib in qt creator, all images are awvfull (gradiant not good looking) : If I enable opengl, my application is more fluid and the images looks good : good gradiant .. Perhaps it's good to have opengl enable by default when the application is qml based ? or at least add this information in documentation ?

This is expected behavior:-
a)  not including opengl will use the software renderer-- available on all phones... but worse looks, performance.

b) enabling opengl will use hardware renderer-- may not be available in all-- but faster 


It's not evident for common dev that when opengl is enable in a qml apps, it automaticaly switch to an opengl backend with good gradiant ... 
it's good to indicate this in wiki for example 

Re: Necessitas alpha 4, a New Hope! Marco Bernasocchi 8/28/12 1:20 AM

wiki contributions are always welcome.

Marco Bernasocchi (mobile)
http://opengis.ch

Re: Necessitas alpha 4, a New Hope! mingw.android 8/28/12 1:27 AM
Yeah, the OpenGL stuff is almost too easy!

It's a really nice implementation I think but definitely worth a mention.
Re: Necessitas alpha 4, a New Hope! deion 8/28/12 3:05 AM
What about the announced Digia Qt port to Android? Will Necessitas merge with whatever official Android port will come from Digia, or there will be 2 different Qt for Android projects (the official Digia one and Necessitas)?

Thanks a lot for all your hard work and wish you all the best,
Ionut
Re: Necessitas alpha 4, a New Hope! Walid Ziouche 8/28/12 12:49 PM
+1 For this question
Re: Necessitas alpha 4, a New Hope! abdallah 9/4/12 8:55 AM
 I have on question to ask you??
did Necessitas beta release in these year
Re: Necessitas alpha 4, a New Hope! Ruslan Vorobei 9/4/12 9:46 AM
maybe :D

вторник, 4 сентября 2012 г., 18:55:31 UTC+3 пользователь abdallah написал:
Re: Necessitas alpha 4, a New Hope! BogDan 9/4/12 12:01 PM
As I said in the announce, *IF* everything goes right and nobody
reports any show stopper, will ship beta on mid Oct.

This week or early next one we plan to release an update which fixes
all regressions reported until now.

Cheers,
BogDan.
Re: Necessitas alpha 4, a New Hope! Marco Bernasocchi 9/4/12 5:34 PM

hi bogdan any news on the sub menu front?
ciao

Marco Bernasocchi (mobile)
http://opengis.ch

Re: Necessitas alpha 4, a New Hope! BogDan 9/4/12 10:43 PM
Just a few bad news, I need to rewrite most of the current
implementation and it will take a while.

Cheers,
BogDan.


On 5 sep., 03:34, Marco Bernasocchi <ma...@bernawebdesign.ch> wrote:
> hi bogdan any news on the sub menu front?
> ciao
>
> Marco Bernasocchi (mobile)http://opengis.ch
Re: Necessitas alpha 4, a New Hope! Marco Bernasocchi 9/5/12 9:57 AM
On 09/05/2012 12:42 PM, BogDan wrote:
> Just a few bad news, I need to rewrite most of the current
> implementation and it will take a while.
:( pity, I'd love to help but my java is waaaay bad... discussing today
in IRC: will setting 'QT_USE_ANDROID_NATIVE_STYLE=0' in 'QtActivity.java
completely disable the new menu thing?

ciao Marco
>
> Cheers,
> BogDan.
>
>
> On 5 sep., 03:34, Marco Bernasocchi <ma...@bernawebdesign.ch> wrote:
>> hi bogdan any news on the sub menu front?
>> ciao
>>
>> Marco Bernasocchi (mobile)http://opengis.ch
>> On Sep 5, 2012 2:01 AM, "BogDan" <taipanroma...@gmail.com> wrote:
>>
>>
>>
>>
>>
>>
>>
>>> As I said in the announce, *IF* everything goes right and nobody
>>> reports any show stopper, will ship beta on mid Oct.
>>
>>> This week or early next one we plan to release an update which fixes
>>> all regressions reported until now.
>>
>>> Cheers,
>>> BogDan.
>>
>>> On 4 sep., 18:55, abdallah <abdallah.14...@gmail.com> wrote:
>>>>  I have on question to ask you??
>>>> did Necessitas beta release in these year


--
Marco Bernasocchi
http://opengis.ch
Re: Necessitas alpha 4, a New Hope! kate 9/10/12 3:26 AM
On Mon, Aug 27, 2012 at 1:20 AM, BogDan Vatra <taipan...@gmail.com> wrote:

Thank you about this new great release.

> -Mac OS X: http://files.kde.org/necessitas/installer/release/mac_osx-online-necessitas-alpha4-sdk-installer.7z

Why Mac OSX version is using .7z format ? .7z is not supported by OSX
as default configuration and it looks that
finding one is not one click away, trying to find one i get dead
domains, suspicious download pages etc. I admit
that using work and courage one could find one but it would be much
user friendly way to use some format
supported by mac as default.


Kate
Re: Necessitas alpha 4, a New Hope! mingw.android 9/10/12 3:40 AM
Hi Kate,

Unfortunately I couldn't find a compression scheme that I liked and
was native to Mac OS X so I ended up compiling 7z (so no need to visit
those dodgy sites):

https://mingw-and-ndk.googlecode.com/files/p7zip-macosx.tar.bz2

...but to be honest, for the installer I should have just used xar or
tar.bz2. We will change it.

Cheers,

Ray.
Re: Necessitas alpha 4, a New Hope! Alaa Hossam 9/16/12 1:51 AM
BogDan you are awesome !!,please keep up the good work,and congratulations on the release.
Re: Necessitas alpha 4, a New Hope! Joris Mak 9/17/12 5:01 AM
Is there news on how to proceed? Are there much regressions? Is it time to (re)release apps written with Alpha4 yet, or switch from testing to stable?

Is there any ETA or at least confirmation about Alpha4 not working on Android 2.3 _at all_ while working fine on Anroid 4.0, like has been posted in some threads on this group?


Op maandag 27 augustus 2012 00:20:14 UTC+2 schreef BogDan het volgende:
Hello folks,

 Today I have the great honor to announce the alpha 4 release of
Necessitas....
Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/17/12 6:44 AM

Hello Group.

When I try to deploy application on andriod tablet, initallly I got Can’t find Ministro service, the application can’t start . But after solving this problem(by installing ministro || apk), I am encountering with Invalid Qt version error on android tablet.

FYI: I have used linux-online-necessitas-alpha4.1-sdk-installer

Someone please help me.

Re: Necessitas alpha 4, a New Hope! BogDan 9/17/12 7:54 AM
We've found a few regressions and update will be available soon.
BogDan.

2012/9/17 dipje <jori...@gmail.com>:
Re: Necessitas alpha 4, a New Hope! BogDan 9/17/12 7:55 AM
Pleas read my initial post one more time, this time please have the
patience to read it entirely.

BogDan.

2012/9/17 BogDan Vatra <taipan...@gmail.com>:
> We've found a few regressions and update will be available soon.
> BogDan.
>
> 2012/9/17 dipje <jori...@gmail.com>:
>> Is there news on how to proceed? Are there much regressions? Is it time to
>> (re)release apps written with Alpha4 yet, or switch from testing to stable?
>>
>> Is there any ETA or at least confirmation about Alpha4 not working on
>> Android 2.3 _at all_ while working fine on Anroid 4.0, like has been posted
>> in some threads on this group?
>>
>>
>> Op maandag 27 augustus 2012 00:20:14 UTC+2 schreef BogDan het volgende:
>>>
>>> Hello folks,
>>>
>>>  Today I have the great honor to announce the alpha 4 release of
>>> Necessitas....
Re: Necessitas alpha 4, a New Hope! Vijay shan 9/17/12 8:15 AM
Great work and a big thanks to everyone involved. Any news about the QtMultimedia stuff? Will that be a part of the Beta? QML video is what I am looking for specifically.

thanks,
Vijay
Re: Necessitas alpha 4, a New Hope! christian.vrl 9/17/12 9:09 AM

You have to change repo as stated on initial e-mail

Em 17/09/2012 10:44, "Mohan_qt_developer" <mohan....@gmail.com> escreveu:

Hello Group.

When I try to deploy application on andriod tablet, initallly I got Can’t find Ministro service, the application can’t start . But after solving this problem(by installing ministro || apk), I am encountering with Invalid Qt version error on android tablet.

FYI: I have used linux-online-necessitas-alpha4.1-sdk-installer

Someone please help me.



On Monday, August 27, 2012 3:50:14 AM UTC+5:30, BogDan wrote:
Hello folks,

 Today I have the great honor to announce the alpha 4 release of
Necessitas. Since Nokia’s 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’m not going to comment
further on Nokia’s 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[1] 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
coming!
 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
steps:
  - 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
stop working!!!
  - *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.

Qt framework:
- 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=304240 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
information.
- SMP safe atomics.
- Many bug fixes.
Known issues/limitations:
- As stated above, native Android menus support only one submenu.
- While some demos and examples work fine, many will not, particularly
on Windows.
- No other new issues.

Ministro:
- Extracts Android native look&feel.
- Secure config files downloading.
- Bug fixes.
Known issues/limitations:
- None.

Qt mobility:
- Android Bluetooth implementation.
- A few bug fixes.
Known issues/limitations:
- No new issues.

QtCreator:
- 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.
Known issues/limitations:
- 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
“/tmp/necessitas/unstable/Android/Qt/482” in the source path and
“YOUR_INSTALLATION_FOLDER/Android/Qt/482” 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
YOUR_INSTALLATION_FOLDER) or:
taskkill /F /IM adb.exe /T  (from cmd.exe in any directory)

SDK Installer framework has been updated with upstream’s 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
http://community.kde.org/Necessitas/3rd_party_SDK_repositories
- If you are a developer looking for something which is not shipped
with the Necessitas SDK, you can check the same page:
http://community.kde.org/Necessitas/3rd_party_SDK_repositories.
Known issues/limitations:
- Due to some bugs, the old installer can’t 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
Special version.
The following people have made large contributions to this release
(alphabetic ordering):
 - Marco Bernasocchi <ma...@bernawebdesign.ch> Moved all the bugs from
sf.net to kde.org. He is also one of the Necessitas website & wiki
maintainers.
 - Ray Donnelly <mingw....@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 &
wiki maintainers.
 - Marijn Kruisselbrink <mkruiss...@kde.org> and Chris Browet
<cb...@semperpax.com> did most of the native Android menu integration.
 - Lauri Laanmets <lauri.l...@proekspert.ee> Android Bluetooth
implementation.
 - Tyler Mandry <tma...@gmail.com> reworked Java/C++ interaction,
added support for Android QML debugging in QtCreator.
 - BogDan Vatra <bog_d...@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:
-GNU/Linux: http://files.kde.org/necessitas/installer/release/linux-online-necessitas-alpha4-sdk-installer

-Windows: http://files.kde.org/necessitas/installer/release/windows-online-necessitas-alpha4-sdk-installer.exe

-Mac OS X: http://files.kde.org/necessitas/installer/release/mac_osx-online-necessitas-alpha4-sdk-installer.7z

Yours sincerely,
BogDan.

[1] http://kde.org/community/whatiskde/kdefreeqtfoundation.php
Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/17/12 9:33 AM

What does below statement mean. Please give me little more information.

"You have to change repo as stated on initial e-mail"

Re: Necessitas alpha 4, a New Hope! CHEN Xing 9/17/12 11:51 AM
On Mon, Sep 17, 2012 at 9:33 AM, Mohan_qt_developer
<mohan....@gmail.com> wrote:
>
> What does below statement mean. Please give me little more information.
>
> "You have to change repo as stated on initial e-mail"

It means that please read Bogdan's original e-mail carefully, the
answer is right there:)

CHEN Xing / 陈醒
Re: Necessitas alpha 4, a New Hope! jenna 9/17/12 1:27 PM

@ dipje
I think you are misinformed about alpha4 not working with android 2.3.  I'm using it daily in my phone with android 2.3.
unk...@googlegroups.com 9/18/12 12:45 AM <This message has been deleted.>
Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/18/12 12:47 AM

I am really sorry, I have gone through Bogdan's original e-mail but still not able to get through the problem.

Please see below two instances I encountered after following the intial mail.

Instance 1 : When I install only ministro configuration tool || on android tablet, after deploying the qt application, Tablet is prompting me to install latest ministro from ...
Instance 2: When I stall only minitro || on android tablet, after deploying the qt application, Tablet does some configuration by referring ministro ||(already installed on tablet). But after configuration process, it throws warning like QT version not valid.

Whether manually building QT libraries using tool chain and giving the path of QT library while deploying shall work????

I am really desperated for some help.

FYI: My android tablet has android 2.3.5 version.

Thanks
Mohan
Re: Necessitas alpha 4, a New Hope! Joris Mak 9/18/12 2:01 AM
Curious how you managed that. I'm not the only one who reported problems getting it to work.

First I thought it was just the emulator image from the SDK 2.3.3, but then someone reported the exact same problem on a real 2.3.3 device (still, while real android 4.0 device _and_ android 4.0 emulator works fine).
What kind of device you use it on? It it android 2.3.3 but with a recent processor? It might be that arm5 architecture has problems with the new Qt libs  in testing.

I do a new install of Alpa4 SDK. I make sure to use the SDK and NDK supplied with alpha4. I make a new Qt gui project, and just put a label on the form to have something.
I take a new android 2.3 image from the SDK. I use adb to install the latest MinistroII from the KDE site, and do the same with ministroconfigurationtool.
I start the config tool, set it to testing, then build the just created project in Qtcreator and let it run. It pushes everything, starts the app.
The app says it needs to download qt libraries (like it should, new image) and happily goes downloading stuff. After that, it just disappears and you're back at the launcher or homescreen of the emulator.
If you start the app again, you see the ministro splash image, and then a second a black screen, and then back to launcher/homescreen.

It does this with emulator image 2.3.3, google-image 2.3.3, my old Htc Hero with cyanogenmod7 (android 2.3.3) and a chinese cheap tablet with android 2.3.3.
If I do the exact same thing with any emulator 4.0 image, or my Htc Sensation (android 4.0), or cyanogenmod10 (Android 4.1) or my Transformer TF101 (android 4.1).. it just works and I see the app.

I tried turning off 'native look & feel', and I've been searching crazy if I see an indication for 'sdk target' anywhere, because maybe it's set to high. But nothing. The only api-target I see is already set to 7, while 10 or higher is required for android2.3.3.

So I'm at a loss.
unk...@googlegroups.com 9/20/12 6:07 AM <This message has been deleted.>
Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/20/12 6:12 AM
Dear Elites,

I am still struggling to see qt application running on android tablet/emulator.
 
In order get cross compiled qt libraries, I tried to compile android-qt downloaded from but no luck(compilation errors)==> git://anongit.kde.org/android-qt-creator.git

Is there any way to link cross compiled qt libraries((Deploy local qt libraries) during deployment.

Please help me Elites..

Thanks
Re: Necessitas alpha 4, a New Hope! Anjin 9/20/12 6:27 AM
Try
 
1)  Download and install the latest Ministro II.apk
 
 
2)  Run Ministro Configuration Tool to switch to "testing" repository.
 
3)  Run your application
     You will be asked to download the QT libs.
 
Lood luck.
 
Anjin

Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/20/12 7:47 AM
I have already tried this.


When I install only ministro configuration tool || on android tablet, after deploying the qt application, Tablet is prompting me to install latest ministro from ...

When I install only minitro || on android tablet, after deploying the qt application, Tablet does some configuration by referring ministro ||(already installed on tablet). But after configuration process, it throws warning like QT version not valid
Re: Necessitas alpha 4, a New Hope! jenna 9/20/12 9:56 AM
I had a similar issue today using the MinistroII.apk.  I installed the MinistroII 8.9 apk and made sure it was still set to use the testing repository and it started working as expected.
http://files.kde.org/necessitas/installer/release/
Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/20/12 10:01 AM
hello,
Can you please let me know how to set to testing repository ??, I think I am going wrong some where in this part.
Thanks for help.
Re: Necessitas alpha 4, a New Hope! mingw.android 9/20/12 10:14 AM
It's on the android device or emulator, run the App called "ministro
configuration tool" and select it from the drop down, then press back.
Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/21/12 3:42 AM

Hello Mr. mingw.android,

Now I am able to set to testing repository from drop down menu. But still I am not able to run qt application on android :(

Now I am seriously thinking to compile QT framework source code. Yesterday I downloaded qt-android from

git://anongit.kde.org/android-qt.git but I was encountering with lot of compilation issues.

Someone please share the archive for git://anongit.kde.org/android-qt.git

If I  am at least able to build it, then I shall be having cross compiled library which I can link to qt application while deploying to android tablet.

Thanks a lot
Mohan

Re: Necessitas alpha 4, a New Hope! mingw.android 9/21/12 4:01 AM
I'm not meaning to be rude here, but if you're having trouble getting
Necessitas to work (where we try hard to make things easy for the
users) the I don't think you'll get *anywhere* with trying to build it
from source. Dealing with the source code makes things a lot more
complicated, not any easier.

Can you set up a simple test project (Qt Quick hello world for
example) then try to use the local Qt libraries (as it seems that you
can't get Ministro to work correctly).

1. Go to Projects on the side-bar at the left
2. Select Run from <Build/Run>
3. Press <Details> on Deploy Configurations.
4. Tick "Deploy local Qt libraries"
5. Tick "Use local Qt libraries"

Once you've got this working you can again re-try with Ministro using
the help that people have given you already.

Cheers,

Ray Donnelly (not mingw.android; that's a project name and an email address)
Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/21/12 5:10 AM

Hello Donnelly,

Sorry for calling you as mingw.android

FYI: I have already tried with the steps suggested by you.

But still after following your steps, I am ending with process died.

Below is log for your reference.

Starting remote process...D/dalvikvm(17716): GC freed 821 objects / 60200 bytes in 317ms
D/dalvikvm(17716): GC freed 80 objects / 3288 bytes in 161ms
I/System.out(17716): My path is: /data/local/qt/jar/QtIndustrius-7.jar
D/dalvikvm(17716): DexOpt: --- BEGIN 'QtIndustrius-7.jar' (bootstrap=0) ---
D/dalvikvm(17716): DexOpt: --- END 'QtIndustrius-7.jar' (success) ---
D/dalvikvm(17716): DEX prep '/data/local/qt/jar/QtIndustrius-7.jar': unzip in 41ms, rewrite 1154ms
D/dalvikvm(17716): Trying to load lib /data/local/qt/lib/libQtCore.so 0x44e8efe8
D/dalvikvm(17716): Added shared lib /data/local/qt/lib/libQtCore.so 0x44e8efe8
D/dalvikvm(17716): No JNI_OnLoad found in /data/local/qt/lib/libQtCore.so 0x44e8efe8
D/dalvikvm(17716): Trying to load lib /data/local/qt/lib/libQtGui.so 0x44e8efe8
D/dalvikvm(17716): Added shared lib /data/local/qt/lib/libQtGui.so 0x44e8efe8
D/dalvikvm(17716): No JNI_OnLoad found in /data/local/qt/lib/libQtGui.so 0x44e8efe8
D/dalvikvm(17716): Trying to load lib /data/local/qt/plugins/platforms/android/libandroid-5.so 0x44e8efe8
D/dalvikvm(17716): Added shared lib /data/local/qt/plugins/platforms/android/libandroid-5.so 0x44e8efe8
I/Qt      (17716): qt start
D/dalvikvm(17716): Trying to load lib /data/data/org.kde.necessitas.example.mohan_sample/lib/libmohan_sample.so 0x44e8d3f0
D/dalvikvm(17716): Added shared lib /data/data/org.kde.necessitas.example.mohan_sample/lib/libmohan_sample.so 0x44e8d3f0
D/dalvikvm(17716): No JNI_OnLoad found in /data/data/org.kde.necessitas.example.mohan_sample/lib/libmohan_sample.so 0x44e8d3f0
D/Qt      (17716): QAndroidPlatformIntegrationPlugin::create "android"
D/Qt      (17716): QAndroidPlatformIntegration::QAndroidPlatformIntegration():  creating QAndroidPlatformScreen => Using Raster (Software) for painting
I/Qt JAVA (17716): surfaceChanged: 480,762,480,762


'org.kde.necessitas.example.mohan_sample' died


Thanks,
Mohan
Re: Necessitas alpha 4, a New Hope! mingw.android 9/21/12 5:16 AM
Ok so you've got a crash happening or your app exits. Debug it? Can
you try the most basic QtQuick app ("Hello World") and see if it
works?

Cheers,

Ray.
Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/21/12 5:52 AM

Basic Hello world program is also encountering with same problem.

Regards
Mohan
Re: Necessitas alpha 4, a New Hope! mingw.android 9/21/12 6:24 AM
Zip up your source and build folders and put them somewhere where we
can investigate please.
Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/22/12 4:37 AM

Hello Ray,

Please find the attachments you asked for.

Attached application has form(ui) that has push button widget with 'Hello World' name.

After selecting local qt libraries and build, I am seeing FATAL CRASH in emulator.

During project selection, I have selected 'arm5'. Emulator is the default one that comes with Necessitas alpha 4.

Thanks
Mohan
Re: Necessitas alpha 4, a New Hope! mingw.android 9/22/12 4:48 AM

Ok thanks. I can't look at this for the next for days as I'm on holiday.

Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/24/12 3:28 AM
Hello,

Since Ray is on vacation, Could someone give me solution for this question.

Thanks,
Mohan
Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/24/12 3:46 AM
Hello Group,

I have a question.

To support deploying of Qt application on Android, Bogdan and his team has developed Necessitas and ministro.

Whether is there a similar approach to deploy Qt application on Apple's IPAD ??

Thanks
Mohan
Re: Necessitas alpha 4, a New Hope! Marco Bernasocchi 9/24/12 4:34 AM
On 09/24/2012 05:46 PM, Mohan_qt_developer wrote:
> Hello Group,
>
> I have a question.
>
> To support deploying of Qt application on Android, Bogdan and his team has
> developed Necessitas and ministro.
>
> Whether is there a similar approach to deploy Qt application on *Apple's
> IPAD* ??
Did it ever occur to you to ask google? :)

>
> Thanks
> Mohan
>
> On Monday, September 24, 2012 3:58:14 PM UTC+5:30, Mohan_qt_developer wrote:
>>
>> Hello,
>>
>> Since Ray is on vacation, Could someone give me solution for this question.
>>
>> Thanks,
>> Mohan
>>
>> On Saturday, September 22, 2012 5:18:12 PM UTC+5:30, mingw.android wrote:
>>>
>>> Ok thanks. I can't look at this for the next for days as I'm on holiday.
>>> On Sep 22, 2012 1:37 PM, "Mohan_qt_developer" <mohan....@gmail.com>
>>> wrote:
>>>
>>>>
>>>> Hello Ray,
>>>>
>>>> Please find the attachments you asked for.
>>>>
>>>> Attached application has form(ui) that has push button widget with
>>>> 'Hello World' name.
>>>>
>>>> After selecting local qt libraries and build, I am seeing FATAL CRASH in
>>>> emulator.
>>>>
>>>> During project selection, I have selected *'arm5'*. Emulator is the
>>>>>>>> I/System.out(17716): My path is: /data/local/qt/jar/**QtIndustrius-7.jar
>>>>>
>>>>>>>> D/dalvikvm(17716): DexOpt: --- BEGIN 'QtIndustrius-7.jar'
>>>>> (bootstrap=0)
>>>>>>>> ---
>>>>>>>> D/dalvikvm(17716): DexOpt: --- END 'QtIndustrius-7.jar' (success)
>>>>> ---
>>>>>>>> D/dalvikvm(17716): DEX prep '/data/local/qt/jar/**QtIndustrius-7.jar':
>>>>>
>>>>>>>> unzip
>>>>>>>> in 41ms, rewrite 1154ms
>>>>>>>> D/dalvikvm(17716): Trying to load lib /data/local/qt/lib/libQtCore.
>>>>> **so
>>>>>>>> 0x44e8efe8
>>>>>>>> D/dalvikvm(17716): Added shared lib /data/local/qt/lib/libQtCore.*
>>>>> *so
>>>>>>>> 0x44e8efe8
>>>>>>>> D/dalvikvm(17716): No JNI_OnLoad found in
>>>>>>>> /data/local/qt/lib/libQtCore.**so
>>>>>>>> 0x44e8efe8
>>>>>>>> D/dalvikvm(17716): Trying to load lib
>>>>> /data/local/qt/lib/libQtGui.so
>>>>>>>> 0x44e8efe8
>>>>>>>> D/dalvikvm(17716): Added shared lib /data/local/qt/lib/libQtGui.so
>>>>>>>> 0x44e8efe8
>>>>>>>> D/dalvikvm(17716): No JNI_OnLoad found in
>>>>> /data/local/qt/lib/libQtGui.so
>>>>>>>> 0x44e8efe8
>>>>>>>> D/dalvikvm(17716): Trying to load lib
>>>>>>>> /data/local/qt/plugins/**platforms/android/libandroid-**5.so
>>>>> 0x44e8efe8
>>>>>>>> D/dalvikvm(17716): Added shared lib
>>>>>>>> /data/local/qt/plugins/**platforms/android/libandroid-**5.so
>>>>> 0x44e8efe8
>>>>>>>> I/Qt      (17716): qt start
>>>>>>>> D/dalvikvm(17716): Trying to load lib
>>>>>>>>
>>>>>>>> /data/data/org.kde.necessitas.**example.mohan_sample/lib/**libmohan_sample.so
>>>>>
>>>>>>>> 0x44e8d3f0
>>>>>>>> D/dalvikvm(17716): Added shared lib
>>>>>>>>
>>>>>>>> /data/data/org.kde.necessitas.**example.mohan_sample/lib/**libmohan_sample.so
>>>>>
>>>>>>>> 0x44e8d3f0
>>>>>>>> D/dalvikvm(17716): No JNI_OnLoad found in
>>>>>>>>
>>>>>>>> /data/data/org.kde.necessitas.**example.mohan_sample/lib/**libmohan_sample.so
>>>>>
>>>>>>>> 0x44e8d3f0
>>>>>>>> D/Qt      (17716): QAndroidPlatformIntegrationPlu**gin::create
>>>>> "android"
>>>>>>>> D/Qt      (17716):
>>>>>>>> QAndroidPlatformIntegration::**QAndroidPlatformIntegration():
>>>>>  creating
>>>>>>>> QAndroidPlatformScreen => Using Raster (Software) for painting
>>>>>>>> I/Qt JAVA (17716): surfaceChanged: 480,762,480,762
>>>>>>>>
>>>>>>>>
>>>>>>>> 'org.kde.necessitas.example.**mohan_sample' died
>>>>>>>>>> git://anongit.kde.org/android-**qt.git<http://anongit.kde.org/android-qt.git>but I was encountering with lot
>>>>>>>>>> of
>>>>>>>>>> compilation issues.
>>>>>>>>>>
>>>>>>>>>> Someone please share the archive for
>>>>>>>>>> git://anongit.kde.org/android-**qt.git<http://anongit.kde.org/android-qt.git>
>>>>>>>>>>>>> http://files.kde.org/**necessitas/installer/release/<http://files.kde.org/necessitas/installer/release/>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>
>>>>


--
Marco Bernasocchi
http://opengis.ch
Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/24/12 10:45 PM

Hello Elites,

When I browsed the internet, I got to know there is a development going on for qt-iphone support. I would like to know whether the tool is available for the users.

Since Ray is on vacation, Could some one please look in to my problem and help me.

Vinayak has given solution like:

I downloaded the hello_world_test.tar.gz. Deleted the android folder and ran it on my Samsung Galaxy 10" tablet. It shows the Hello World text as expected.


But above solution didn't work for me, since without android folder, deployment process is not starting up.

For your information: I tried deploying on android SDK that comes as default with Necessitas alpha 4. I even tried on android tablet with android 2.5 version but still it is not working.

Someone's help would be highly respected.

There is a latest version of Necessitas released in last week. Whether using that version shall solve my problem.

Thanks
Mohan
Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/25/12 2:04 AM
Hello Elites,

When I browsed the internet, I got to know there is a development going on for qt-iphone support. I would like to know whether the tool is available for the users.

Since Ray is on vacation, Could some one please look in to my problem and help me.

Vinayak has given solution like:

I downloaded the hello_world_test.tar.gz. Deleted the android folder and ran it on my Samsung Galaxy 10" tablet. It shows the Hello World text as expected.


But above solution didn't work for me, since without android folder, deployment process is not starting up.

For your information: I tried deploying on android SDK that comes as default with Necessitas alpha 4. I even tried on android tablet with android 2.5 version but still it is not working.

Someone's help would be highly respected.

There is a latest version of Necessitas released in last week. Whether using that version shall solve my problem.

Thanks
Mohan

On Monday, September 24, 2012 5:04:29 PM UTC+5:30, Marco Bernasocchi wrote:
Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/25/12 9:24 PM
Hello Ray,
Are you back from vacation ?
Regards
Mohan
Re: Necessitas alpha 4, a New Hope! Mohan_qt_developer 9/26/12 9:05 AM
Hello Ray,

I downloaded Necessitas again today(26 september) for linux. Now it is absolutely working fine. My qt application has qtwebkit requirement. My qt application is perfectly running on android emulator.

Thanks for your help.

Hello Bogdan,

Kudos to your work. God bless you.

Thanks
Mohan
Re: Necessitas alpha 4, a New Hope! 毛林 10/21/12 7:32 PM
i made a VOIP app,so i had to capture/play audio stream. by alpha 3,i can modify qtmain_android.cpp to load java class AudioRecord and AudioTrack to do that because there was no implemention in necessitas yet. now alpha 4 released, qtmain_android.cpp is missing,i see that you said "user java/c++ interaction is support",but i have no idea how to do it,could you post some simple example? thx very much! 

在 2012年8月27日星期一UTC+8上午6时20分14秒,BogDan写道:
Hello folks,

 Today I have the great honor to announce the alpha 4 release of
Necessitas. Since Nokia’s 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’m not going to comment
further on Nokia’s 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[1] 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
coming!
 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
steps:
  - 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
stop working!!!
  - *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.

Qt framework:
- 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=304240 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
information.
- SMP safe atomics.
- Many bug fixes.
Known issues/limitations:
- As stated above, native Android menus support only one submenu.
- While some demos and examples work fine, many will not, particularly
on Windows.
- No other new issues.

Ministro:
- Extracts Android native look&feel.
- Secure config files downloading.
- Bug fixes.
Known issues/limitations:
- None.

Qt mobility:
- Android Bluetooth implementation.
- A few bug fixes.
Known issues/limitations:
- No new issues.

QtCreator:
- 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.
Known issues/limitations:
- 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
“/tmp/necessitas/unstable/Android/Qt/482” in the source path and
“YOUR_INSTALLATION_FOLDER/Android/Qt/482” 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
YOUR_INSTALLATION_FOLDER) or:
taskkill /F /IM adb.exe /T  (from cmd.exe in any directory)

SDK Installer framework has been updated with upstream’s 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
http://community.kde.org/Necessitas/3rd_party_SDK_repositories
- If you are a developer looking for something which is not shipped
with the Necessitas SDK, you can check the same page:
http://community.kde.org/Necessitas/3rd_party_SDK_repositories.
Known issues/limitations:
- Due to some bugs, the old installer can’t 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
Special version.
The following people have made large contributions to this release
(alphabetic ordering):
 - Marco Bernasocchi <ma...@bernawebdesign.ch> Moved all the bugs from
sf.net to kde.org. He is also one of the Necessitas website & wiki
maintainers.
 - Ray Donnelly <mingw....@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 &
wiki maintainers.
 - Marijn Kruisselbrink <mkruiss...@kde.org> and Chris Browet
<cb...@semperpax.com> did most of the native Android menu integration.
 - Lauri Laanmets <lauri.l...@proekspert.ee> Android Bluetooth
implementation.
 - Tyler Mandry <tma...@gmail.com> reworked Java/C++ interaction,
added support for Android QML debugging in QtCreator.
 - BogDan Vatra <bog_d...@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:
-GNU/Linux: http://files.kde.org/necessitas/installer/release/linux-online-necessitas-alpha4-sdk-installer

-Windows: http://files.kde.org/necessitas/installer/release/windows-online-necessitas-alpha4-sdk-installer.exe

-Mac OS X: http://files.kde.org/necessitas/installer/release/mac_osx-online-necessitas-alpha4-sdk-installer.7z

Yours sincerely,
BogDan.

[1] http://kde.org/community/whatiskde/kdefreeqtfoundation.php
Re: Necessitas alpha 4, a New Hope! Anjin 10/22/12 6:56 AM
With Alpha4, you can have your own JNI_OnLoad in your module ( shared lib), it will be called when your lib is loaded.
 
You can add this function in main.cpp.
 
Q_DECL_EXPORT jint JNICALL JNI_OnLoad(JavaVM* vm, void* /*reserved*/)
{
    // Do what you need to here.
    return JNI_VERSION_1_4;
}
 
Anjin
Re: Necessitas alpha 4, a New Hope! Tomas Raf 3/3/13 8:39 AM
I found one issue when launching emulator from Necessitas on win7. I always get error "LoadLibrary failed with error 998: Invalid access to memory location" I found that it's related with android-sdk/Tools/ emulator.exe. When I launch it from command line emulator-arm.exe -avd Android_QVGA_AVD it starts emulator with android OS.
Re: Necessitas alpha 4, a New Hope! SeDi 3/3/13 9:49 AM
Am 03.03.2013 17:39, schrieb Tomas Raf:
I found one issue when launching emulator from Necessitas on win7. I always get error "LoadLibrary failed with error 998: Invalid access to memory location" I found that it's related with android-sdk/Tools/ emulator.exe. When I launch it from command line emulator-arm.exe -avd Android_QVGA_AVD it starts emulator with android OS.
Just a quick shot: are all involved directory names free of spaces and special characters?


Re: Necessitas alpha 4, a New Hope! Rajesh 5/17/14 9:12 AM
I would like to build an app to access postgresql server from qt necessitas. but i was failed to build psql driver.i tried all the ways, i did the following

1.download and installed qt necessitas
2.clone QGIS, QGIS-Android and Quantum-GIS
3.build libs with build_libs.sh with postgresql-dev and i got libpq.so
4.and i placed libpq in qt-src directory but still im getting driver not loaded

i build another gui-apps working smoothly, Tell me how to build the psql driver

Thanks in advance.
More topics »