Necessitas alpha 4, a New Hope! - android-qt

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Necessitas alpha 4, a New Hope!
Received-SPF: pass (google.com: domain of qtn...@gmail.com designates 209.85.210.182 as permitted sender) client-ip=209.85.210.182;
MIME-Version: 1.0
In-Reply-To: <CABY81mZdarozXKGp3EVbJh87trjj=rwMsHbsYq6XMuJ1uu0...@mail.gmail.com>
References: <CAG9QW4HbD=BQeRa7q5GXDVpLp-s4FzbgcZ-UgozkBOr-EZP...@mail.gmail.com>
	<CABY81masZUtjU3hCNEMH617XSqBu9avqVJhaapffX+8RSM6...@mail.gmail.com>
	<CANeVCouKbivJORi4fDCBxBbiMYpaqC536PAN72CF4Qu9efW...@mail.gmail.com>
	<CABY81mZdarozXKGp3EVbJh87trjj=rwMsHbsYq6XMuJ1uu0...@mail.gmail.com>
Date: Tue, 28 Aug 2012 10:15:57 +0200
Message-ID: <CANeVCov4TBFaM8QBY3wve=w5cZRG-+HzbrzsUmqHKtZhn9W...@mail.gmail.com>
Subject: Re: Necessitas alpha 4, a New Hope!
From: qtnext <qtn...@gmail.com>
To: android-qt@googlegroups.com
Content-Type: multipart/alternative; boundary=90e6ba6e8c5a4b224404c84f0d5f

--90e6ba6e8c5a4b224404c84f0d5f
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

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 ap=
k
> 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 enabl=
e
>> 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 al=
l
> 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


> Hope this helps...
>
> Regards,
>
> Nalin
>
>
>>
>>
>> 2012/8/27 Nalin Savara <nsn...@gmail.com>
>>
>>>
>>>
>>> On Mon, Aug 27, 2012 at 3:50 AM, BogDan Vatra <taipanroma...@gmail.com>=
wrote:
>>>
>>>> Hello folks,
>>>>
>>>>  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 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
>>>
>>>
>>>> very hard time and many asked themselves whether it was worth
>>>> investing their time and money in it anymore. I=92m not going to comme=
nt
>>>> further on Nokia=92s recent stupid decisions because I value too highl=
y
>>>> 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=3D304240 t=
o
>>>> 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
>>>> =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
>>>> YOUR_INSTALLATION_FOLDER) or:
>>>> 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
>>>> 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=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
>>>> 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.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 &
>>>> wiki maintainers.
>>>>  - 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
>>>> implementation.
>>>>  - 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:
>>>> -GNU/Linux:
>>>> http://files.kde.org/necessitas/installer/release/linux-online-necessi=
tas-alpha4-sdk-installer
>>>>
>>>> -Windows:
>>>> http://files.kde.org/necessitas/installer/release/windows-online-neces=
sitas-alpha4-sdk-installer.exe
>>>>
>>>> -Mac OS X:
>>>> http://files.kde.org/necessitas/installer/release/mac_osx-online-neces=
sitas-alpha4-sdk-installer.7z
>>>>
>>>> Yours sincerely,
>>>> BogDan.
>>>>
>>>> [1] http://kde.org/community/whatiskde/kdefreeqtfoundation.php
>>>>
>>>
>>>
>>
>

--90e6ba6e8c5a4b224404c84f0d5f
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">2012/8/27 Nalin Savara <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:nsn...@gmail.com" target=3D"_blank">nsn...@gmail.com=
</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><br><div class=3D"gmail_quote"><div class=3D"im">On Tue, Aug 28, 2012 a=
t 2:46 AM, qtnext <span dir=3D"ltr">&lt;<a href=3D"mailto:qtn...@gmail.com"=
 target=3D"_blank">qtn...@gmail.com</a>&gt;</span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">

Congratulation :) yeee !<div><br></div><div>I have tested the alpha 4 :</di=
v><div><br></div><div>1)- the release apk is always named &quot;debug&quot;=
 : is it normal ? does it means that the apk contains debug information (I =
don&#39;t wants to provide apk with debug info inside) ?</div>

</blockquote><div><br></div></div><div>yes; the release apk is always named=
 &quot;debug&quot;.</div><div><br></div><div>Not sure abt normal... but mys=
elf, to be double-sure =A0create a release apk by:</div><div>a. cd to andro=
id folder in project dir</div>

<div>b. use command: ant clean release</div><div class=3D"im"><div><br></di=
v><div>-</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
<div>2)- my application is fully qml : if I don&#39;t enable opengl lib in =
qt creator, all images are awvfull (gradiant not good looking) : If I enabl=
e opengl, my application is more fluid and the images looks good : good gra=
diant .. Perhaps it&#39;s good to have opengl enable by default when the ap=
plication is qml based ? or at least add this information in documentation =
?</div>

</blockquote><div><br></div></div><div>This is expected behavior:-</div><di=
v>a) =A0not including opengl will use the software renderer-- available on =
all phones... but worse looks, performance.</div><div><br></div><div>b) ena=
bling opengl will use hardware renderer-- may not be available in all-- but=
 faster=A0</div>

<div><br></div></div></blockquote><div><br></div><div>It&#39;s not evident =
for common dev that when opengl is enable in a qml apps, it automaticaly sw=
itch to an opengl backend with good gradiant ...=A0</div><div>it&#39;s good=
 to indicate this in wiki for example=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div class=3D"gmail_quote"><di=
v></div><div>Hope this helps...</div><div><br></div><div>Regards,</div><div=
><br>
</div><div>Nalin</div><div><div class=3D"h5"><div><br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">
<div><div>
<div><br></div><div><br></div><div><br><div class=3D"gmail_quote">2012/8/27=
 Nalin Savara <span dir=3D"ltr">&lt;<a href=3D"mailto:nsn...@gmail.com" tar=
get=3D"_blank">nsn...@gmail.com</a>&gt;</span><br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">


<br><br><div class=3D"gmail_quote"><div>On Mon, Aug 27, 2012 at 3:50 AM, Bo=
gDan Vatra <span dir=3D"ltr">&lt;<a href=3D"mailto:taipanroma...@gmail.com"=
 target=3D"_blank">taipanroma...@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hello folks,<br>
<br>
=A0Today I have the great honor to announce the alpha 4 release of<br>
Necessitas. Since Nokia=92s radical change of direction, Qt has had a<br></=
blockquote><div><br></div></div><div>Very awesome to BogDan, Ray and entire=
 team!!!</div><div><br></div><div>Congrats...=A0</div><div><br></div><div>


and thank you for your sweat and blood invested-- to all contributors... we=
 are all indebted to you guys...</div><span><font color=3D"#888888">
<div><br></div><div>-Nalin</div></font></span><div><div><div>=A0</div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">
very hard time and many asked themselves whether it was worth<br>
investing their time and money in it anymore. I=92m not going to comment<br=
>
further on Nokia=92s recent stupid decisions because I value too highly<br>
the contributions Nokia has made to Qt.<br>
=A0Instead, I want to comment on the future of Qt and how to make sure<br>
it will survive no matter what. I didn&#39;t comment on this matter until<b=
r>
now because I was too busy getting this release out, and how better to<br>
prove to you folks that we are committed to Qt than to continue our<br>
work with this new release? First and foremost Qt is free software,<br>
according to the KDE Free Qt Foundation[1] Nokia (and most probably<br>
also Digia) must release it under both the LGPL 2.1 and the GPL 3.<br>
Otherwise *&quot;the Foundation has the right to release Qt under a<br>
BSD-style license or under other open source licenses. The agreement<br>
stays valid in case of a buy-out, a merger or bankruptcy.&quot;* So from<br=
>
this point of view you don&#39;t have anything to worry about! What about<b=
r>
Qt&#39;s future development, who will continue to work on it now that<br>
Nokia have dropped it? While we all share great hopes that Digia will<br>
manage the Qt Project well, the beauty of free software if that it<br>
doesn&#39;t need any single company behind it, it also needs a committed<br=
>
community; KDE, Necessitas, ICS, KDAB etc, and most importantly *YOU*!<br>
Now more than ever it is very important for all of us to join together<br>
and for you to show your support and appreciation. You have to ask<br>
yourself which option is better for you:<br>
=A0 - to be selfless and to spend some of your time (or your money) to<br>
make the things you love better and to keep them free for everybody...<br>
=A0 - or to be selfish, forget about Qt and start learning some crappy<br>
closed source C# or iFramework instead which, some day (sooner or<br>
later), will die with the *ONLY* company behind it?<br>
<br>
=A0We choose the first option. The Necessitas developers will do their<br>
best to succeed where Nokia has failed: to make Qt available on a huge<br>
number of (Android-powered) devices. Yes baby, the next billion is<br>
coming!<br>
=A0This alpha 4 release is one of the final steps that we needed to do.<br>
It *should* be our last alpha release! If there are no show-stopping<br>
regressions reported, in one and a half months we&#39;ll ship the first<br>
beta release. Why one and a half months? From now on, to be sure that<br>
there are no regressions introduced, releases will be made in two<br>
steps:<br>
=A0 - The first step is to release the SDK, and to push the new Android<br>
libs to Ministro&#39;s testing repository. The new Android libs will stay<b=
r>
in the testing repository for at least one month to give developers<br>
enough time to test their apps using them. They should use the<br>
Ministro configuration tool to switch to the testing repository.<br>
Additional updates will be released in the testing repository and this<br>
period may be extended if any regressions are reported. A new update<br>
must stay for at least two weeks in the testing repository; known<br>
issues are not considered regressions!<br>
=A0 - Once the new libs in the testing repository are determined to be<br>
regression-free, they will land in the stable repository and they will<br>
be available to all Android users.<br>
<br>
=A0In other words developers should perform the following two steps:<br>
=A0 - Update the SDK, use the Ministro configuration tool to switch to<br>
the testing repository, update your apps, and report any regressions.<br>
*DO NOT* publish any apps on Google Play until the version from the<br>
testing repository reaches the stable repository, otherwise they will<br>
stop working!!!<br>
=A0 - *WAIT* for the alpha 4 release to land in the stable repository,<br>
then you can publish the updated apps on Google Play!<br>
Go back and carefully read these two statements one more time!<br>
<br>
=A0The alpha 4 release will stay in the stable repository for another<br>
two weeks, then *if no regressions* are reported, it will be<br>
re-released as beta 1. Basically we&#39;ll simply re-label it as beta 1!<br=
>
From that moment we&#39;ll guarantee that the ABI/API will remain stable<br=
>
and therefore you can safely deploy any apps you like on Google Play!<br>
<br>
The most important changes:<br>
Necessitas has a new home page: <a href=3D"http://necessitas.kde.org" targe=
t=3D"_blank">http://necessitas.kde.org</a><br>
Here you can find latest news and information on how to get involved<br>
(<a href=3D"http://necessitas.kde.org/getinvolved.php" target=3D"_blank">ht=
tp://necessitas.kde.org/getinvolved.php</a>), how to help and to get<br>
help (<a href=3D"http://necessitas.kde.org/gethelp.php" target=3D"_blank">h=
ttp://necessitas.kde.org/gethelp.php</a>) and much more.<br>
We&#39;ve also moved the wiki and the bugs from <a href=3D"http://sf.net" t=
arget=3D"_blank">sf.net</a> to KDE&#39;s infrastructure.<br>
<br>
Qt framework:<br>
- Update to Qt 4.8.2<br>
- Native Android look&amp;feel for classic widgets.<br>
- Native Android menus - known limitation: Android menus support only<br>
one submenu. We&#39;ll try to find a solutions for this problem in a<br>
future release (follow <a href=3D"https://bugs.kde.org/show_bug.cgi?id=3D30=
4240" target=3D"_blank">https://bugs.kde.org/show_bug.cgi?id=3D304240</a> t=
o<br>
check its progress).<br>
- Fixed user Java/C++ interaction.<br>
- New assets access scheme. Please add &quot;assets:&quot; prefix, check<br=
>
<a href=3D"http://techbase.kde.org/Development/Tutorials/Necessitas" target=
=3D"_blank">http://techbase.kde.org/Development/Tutorials/Necessitas</a> fo=
r more<br>
information.<br>
- SMP safe atomics.<br>
- Many bug fixes.<br>
Known issues/limitations:<br>
- As stated above, native Android menus support only one submenu.<br>
- While some demos and examples work fine, many will not, particularly<br>
on Windows.<br>
- No other new issues.<br>
<br>
Ministro:<br>
- Extracts Android native look&amp;feel.<br>
- Secure config files downloading.<br>
- Bug fixes.<br>
Known issues/limitations:<br>
- None.<br>
<br>
Qt mobility:<br>
- Android Bluetooth implementation.<br>
- A few bug fixes.<br>
Known issues/limitations:<br>
- No new issues.<br>
<br>
QtCreator:<br>
- Updated to 2.6 (alpha).<br>
- Fixed bug in ma-make.exe where all rule commands were run through a<br>
batch file leading to each 8192nd character being dropped. Now<br>
CreateProcess is used for nearly all commands, and a work around for<br>
the (MS) batch file bug was also implemented.<br>
- A few other bug fixes.<br>
Known issues/limitations:<br>
- This release is based on an un-released QtCreator version, so some<br>
unexpected issues may occur.<br>
- When you install the qt src package, the source paths mapping is not<br>
set automatically anymore so to debug the qt libraries at the source<br>
level, you need to set it manually: put<br>
=93/tmp/necessitas/unstable/Android/Qt/482=94 in the source path and<br>
=93YOUR_INSTALLATION_FOLDER/Android/Qt/482=94 in the target path.<br>
- On Windows, adb loses track of the connected devices a lot and<br>
otherwise misbehaves (worse with emulators), causing QtCreator to<br>
hang. When this happens, to get it to respond again you can execute:<br>
android-sdk\platform-tools\adb.exe kill-server &amp;<br>
android-sdk\platform-tools\adb start-server &amp;<br>
android-sdk\platform-tools\adb devices (from cmd.exe in<br>
YOUR_INSTALLATION_FOLDER) or:<br>
taskkill /F /IM adb.exe /T =A0(from cmd.exe in any directory)<br>
<br>
SDK Installer framework has been updated with upstream=92s latest<br>
changes. One of the biggest improvements is the ability to add<br>
3rd-party repositories, so:<br>
- If you are a developer who has something interesting to share for<br>
Android (e.g. plugins, custom widgets, QML controls, etc.) please add<br>
your repository to<br>
<a href=3D"http://community.kde.org/Necessitas/3rd_party_SDK_repositories" =
target=3D"_blank">http://community.kde.org/Necessitas/3rd_party_SDK_reposit=
ories</a><br>
- If you are a developer looking for something which is not shipped<br>
with the Necessitas SDK, you can check the same page:<br>
<a href=3D"http://community.kde.org/Necessitas/3rd_party_SDK_repositories" =
target=3D"_blank">http://community.kde.org/Necessitas/3rd_party_SDK_reposit=
ories</a>.<br>
Known issues/limitations:<br>
- Due to some bugs, the old installer can=92t be used update the SDK, so<br=
>
you need to reinstall the SDK using the new installers.<br>
<br>
Updated the Android NDK and Android SDK to latest versions. Please do<br>
not use the Official Google Android NDK, instead use our Necessitas<br>
Special version.<br>
The following people have made large contributions to this release<br>
(alphabetic ordering):<br>
=A0- Marco Bernasocchi &lt;<a href=3D"mailto:ma...@bernawebdesign.ch" targe=
t=3D"_blank">ma...@bernawebdesign.ch</a>&gt; Moved all the bugs from<br>
<a href=3D"http://sf.net" target=3D"_blank">sf.net</a> to <a href=3D"http:/=
/kde.org" target=3D"_blank">kde.org</a>. He is also one of the Necessitas w=
ebsite &amp; wiki<br>
maintainers.<br>
=A0- Ray Donnelly &lt;<a href=3D"mailto:mingw.andr...@gmail.com" target=3D"=
_blank">mingw.andr...@gmail.com</a>&gt; as usual he had a decisive<br>
contribution to this project. He created a custom Android NDK (the<br>
official NDK-r8b was not able to build Necessitas), gdb with Python<br>
support, and most importantly, the Windows and Mac OS X SDKs.<br>
=A0- Willy Gardiol &lt;<a href=3D"mailto:wi...@gardiol.org" target=3D"_blan=
k">wi...@gardiol.org</a>&gt; reworked most of Necessitas<br>
website and wiki pages. He is also one of the Necessitas website &amp;<br>
wiki maintainers.<br>
=A0- Marijn Kruisselbrink &lt;<a href=3D"mailto:mkruisselbr...@kde.org" tar=
get=3D"_blank">mkruisselbr...@kde.org</a>&gt; and Chris Browet<br>
&lt;<a href=3D"mailto:c...@semperpax.com" target=3D"_blank">cbro@semperpax.=
com</a>&gt; did most of the native Android menu integration.<br>
=A0- Lauri Laanmets &lt;<a href=3D"mailto:lauri.laanm...@proekspert.ee" tar=
get=3D"_blank">lauri.laanm...@proekspert.ee</a>&gt; Android Bluetooth<br>
implementation.<br>
=A0- Tyler Mandry &lt;<a href=3D"mailto:tman...@gmail.com" target=3D"_blank=
">tman...@gmail.com</a>&gt; reworked Java/C++ interaction,<br>
added support for Android QML debugging in QtCreator.<br>
=A0- BogDan Vatra &lt;<a href=3D"mailto:bog_dan...@yahoo.com" target=3D"_bl=
ank">bog_dan...@yahoo.com</a>&gt; Most of the QtCreator Android<br>
Plugin, Ministro updates, SDK Installer updates, Android native<br>
look&amp;feel (Qt and Ministro implementation), cleanup of native Android<b=
r>
menus integration, new assets implementation, SMP safe atomics, most<br>
of the bug fixes.<br>
<br>
As usual, special thanks goes to KDE for their hosting and support!<br>
<br>
I&#39;ll also like to personally thank everyone who has summited bugs (and<=
br>
even better, patches for some of them!)<br>
<br>
You can check out Necessita&#39;s glory wall<br>
(<a href=3D"http://necessitas.kde.org/people.php" target=3D"_blank">http://=
necessitas.kde.org/people.php</a>) for a complete list of all<br>
contributors (who agreed to be listed).<br>
<br>
You can grab the new SDK installer for the following platforms:<br>
-GNU/Linux: <a href=3D"http://files.kde.org/necessitas/installer/release/li=
nux-online-necessitas-alpha4-sdk-installer" target=3D"_blank">http://files.=
kde.org/necessitas/installer/release/linux-online-necessitas-alpha4-sdk-ins=
taller</a><br>




<br>
-Windows: <a href=3D"http://files.kde.org/necessitas/installer/release/wind=
ows-online-necessitas-alpha4-sdk-installer.exe" target=3D"_blank">http://fi=
les.kde.org/necessitas/installer/release/windows-online-necessitas-alpha4-s=
dk-installer.exe</a><br>




<br>
-Mac OS X: <a href=3D"http://files.kde.org/necessitas/installer/release/mac=
_osx-online-necessitas-alpha4-sdk-installer.7z" target=3D"_blank">http://fi=
les.kde.org/necessitas/installer/release/mac_osx-online-necessitas-alpha4-s=
dk-installer.7z</a><br>




<br>
Yours sincerely,<br>
BogDan.<br>
<br>
[1] <a href=3D"http://kde.org/community/whatiskde/kdefreeqtfoundation.php" =
target=3D"_blank">http://kde.org/community/whatiskde/kdefreeqtfoundation.ph=
p</a><br>
</blockquote></div></div></div><br>
</blockquote></div><br></div>
</div></div></blockquote></div></div></div><br>
</blockquote></div><br>

--90e6ba6e8c5a4b224404c84f0d5f--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
