Community
Participate
Working Groups
Created attachment 271752 [details] PDF with proposed design changes Andmore SDK Management covers package install and updates and virtual device configuration. The design appears to be unchanged from Android API 8. The pull request for Bug 526437 - Android SWT Libraries need to be forked - has been merged, and this contains features that can improve the user experience regarding SDK Management. Attached is a PDF which proposes the changes to be made.
Created attachment 272256 [details] User Guide for revised SDK Manager Design - Please review Development is now almost complete. I have attached a user guide to allow a design review before submitting the code. I would appreciate some prelimary feedback. At the start I tried to pay homage to the original design, but in the end I made some sweeping changes. The original Welcome Wizard has been all but replaced and the Android Preference Page has also undergone radical change. The SDK Manager has had a "facelift". The AVD Manager has some new features, but is the least touched by the design changes. I would like to have "Bug 526788 - Sequoyah project needs to be resurrected" resolved as ther are no startup errors as long as I use my Sequoyah rebuild. Sequoyah is also relevent to this bug report because when there is no AVD configured, a dialog pops up when Andmore starts or after an SDK installation prompting the user to configure an AVD. Strangely, if the user chooses to configure an AVD, they get take to a Sequoyah wizard for configuring an AVD. Given no Sequoyah devices this seems to be wrong and the regular AVD Manager should be presented to the user instead. If Sequoyah is only there as an alternative to AVD Manager, then maybe it can be jettisoned. Otherwise it looks like we will have to work out how to get Sequoyah devices to show up and update the alternative AVD Manager to work with the latest SDK API.
