I don't think we want any 3rd party to bundle the SDK in an Eclipse
based product.
Instead, I would prefer them to have the ability to download the SDK
from the repository on first launch (with the ability to skip the
install).
This will guarantee that the SDK that gets installed is always the
latest one. Also, we are starting to have a lot of platforms and it
makes no sense to bundle all of them. The UI should force the
developers to install the required packages (such as the tools), but
then choose which component they want (basically almost the same as
the SDK Updater).
Xav
--
Xavier Ducrohet
Android SDK Tech Lead
Google Inc.
Please do not send me questions directly. Thanks!
I didn't mind that 3rd part bundle any platforms than just SDK
(http://dl.google.com/android/android-sdk_r07-windows.zip, for
instance).
Actually, it is possible that you (Google) include this SDK as Eclipse
bundle in ADT update site (it is simple). ADT would configure SDK on
first startup and the user can download some platforms in standard way
or plugin can offer him to download them. In this way, setting Eclipse
environment for the development Android application would be much
simpler.
If SDK bundle contains any platform, it is possible to execute plugin
tests easy with valid target (my second reason for this feature is
also important; maybe more important).
Do you agree with the following scenario :
- if ADT doesn't found system variable, it is old behavior; we can
offer dialog for download and install SDK and some platform(s)
- if ADT find system variable, then it check and set SDK
Additional, ADT would set any default device if there is SDK and there
is no one device.
Regards,
Peco
I don't know anything about Motodev Studio for Android. I am
independent developer and I have tried to implement this feature in
my Android development application. You can take a look at
http://www.snpe.rs/sad/overview.html
Is there this feature in Motodev Studio ?
Best regards,
Haris Peco
At this time, I think the only thing we would look into is downloading
the SDK components on first start from our own repository.
Since we already maintain our repository, there's little point in
maintaining an Eclipse repository for the SDK as well.
I think it should work this way:
On first launch only, detect there is no preferences set for the
Android SDK and display a UI to either
- point to an SDK
- download one to a specified location. This in turn open the SDK
Updater UI (or a simplified version of it) to select which platform to
download.
Alternatively, for the 2nd option, we can automatically choose a
location for the SDK so that all the user has to do really is choose
which platform he/she wants from a very simplified and easy UI.
Xav
I saw your other message and just replied.
Note that ADT 8.0.0 is complete and in tools_r8.
Master now builds ADT 9.0.0
Both of them indeed only work with an SDK build from AOSP.
We are looking at providing daily builds as binary archive, but I
think a test repository will be tough. We'll look into it though.
Xav