The alias build rules do not work and the flag wasn't even used
by ProjectCreator anyway. Will reintroduce later.
Original author: raphael
Merged from: //branches/cupcake/...
Automated import of CL 147027
The alias build rules do not work and the flag wasn't even used
by ProjectCreator anyway. Will reintroduce later.
BUG=1795718
Automated import of CL 147025
This also reorganizes some source so it's 90% refactoring.
There will be more filtering to do in another CL.
Original author: raphael
Merged from: //branches/cupcake/...
Automated import of CL 146744
This happens when you open the Windows > Prefs > Android panel
while an SDK is initially loading or when you change the
SDK in the pref panel. The target change listener was not
properly removed since the field was not properly disposed.
This also removed the multiple selection handling in the
SdkTargetSelector, which we never use. In the unlikely event
we want to use it later, it would be trivial to add it back.
Original author: raphael
Merged from: //branches/cupcake/...
Automated import of CL 146634
This happens when you open the Windows > Prefs > Android panel
while an SDK is initially loading or when you change the
SDK in the pref panel. The target change listener was not
properly removed since the field was not properly disposed.
This also removed the multiple selection handling in the
SdkTargetSelector, which we never use. In the unlikely event
we want to use it later, it would be trivial to add it back.
BUG=1793333
Automated import of CL 146631
For ADT #1603194, it is desirable to select the Instrumentation
Runner class from the android.jar. The class browser was filtering
it out. The class browser has been changed like this:
- include all source & jar package roots
- a checkbox let the user toggle between searching only sources
(of the project) or anything in the classpath (thus include jars.)
The default is to include everything for the instrumentation and only
the source for other browsers.
Also improved a bit the filter by not iterating over the hierarchy
and filtering out abstract classes (which was not needed before.)
Original author: raphael
Merged from: //branches/cupcake/...
Automated import of CL 146336
For ADT #1603194, it is desirable to select the Instrumentation
Runner class from the android.jar. The class browser was filtering
it out. The class browser has been changed like this:
- include all source & jar package roots
- a checkbox let the user toggle between searching only sources
(of the project) or anything in the classpath (thus include jars.)
The default is to include everything for the instrumentation and only
the source for other browsers.
Also improved a bit the filter by not iterating over the hierarchy
and filtering out abstract classes (which was not needed before.)
BUG=1603194
Automated import of CL 146335
The fix I did last week was just refreshing the UiRootNode
but it turns out we need to refresh the DescriptorFilters too
(since they are null when there's no SDK.) So the old fix was
wrong, what we need is to generate a new tree model when the
SDK is reloaded.
Original author: raphael
Merged from: //branches/cupcake/...
Automated import of CL 146250
Bug description is to add support for <uses-configuration>.
Currently the Manifest editor already supports <uses-sdk> (which is an
element node, not an attribute) by exposing it as a manifest attribute.
That doesn't scale. So instead just provide a tree for all <manifest>
child elements that are not handled in other pages. Currently that
contains uses-sdk and uses-configuration but the nice part of it is that
it will pick up automatically any new manfiest sub elements in the future.
Original author: raphael
Merged from: //branches/cupcake/...
Automated import of CL 146249
The fix I did last week was just refreshing the UiRootNode
but it turns out we need to refresh the DescriptorFilters too
(since they are null when there's no SDK.) So the old fix was
wrong, what we need is to generate a new tree model when the
SDK is reloaded.
BUG=1761064
Automated import of CL 146238
Bug description is to add support for <uses-configuration>.
Currently the Manifest editor already supports <uses-sdk> (which is an
element node, not an attribute) by exposing it as a manifest attribute.
That doesn't scale. So instead just provide a tree for all <manifest>
child elements that are not handled in other pages. Currently that
contains uses-sdk and uses-configuration but the nice part of it is that
it will pick up automatically any new manfiest sub elements in the future.
BUG=1789339
Automated import of CL 146237
