diff options
| author | Tor Norbye <tnorbye@google.com> | 2011-02-17 16:53:34 -0800 |
|---|---|---|
| committer | Tor Norbye <tnorbye@google.com> | 2011-02-28 17:19:31 -0800 |
| commit | 0757ce4af2764e4dd564acc0b1a013e910abc8da (patch) | |
| tree | 630e43803cdc7d63aa05dafec73fd164f2616958 /eclipse/dictionary.txt | |
| parent | 2695266bdddb8d827ea682a7e310e19919a73826 (diff) | |
| download | sdk-0757ce4af2764e4dd564acc0b1a013e910abc8da.zip sdk-0757ce4af2764e4dd564acc0b1a013e910abc8da.tar.gz sdk-0757ce4af2764e4dd564acc0b1a013e910abc8da.tar.bz2 | |
More refactoring work: Convert hierarchy, and change type
A lot of work on the "Change Layout" refactoring to improve conversion
to a Relative Layout. First, add a "Flatten Hierarchy" option which
can take an entire hierarchy of layout widgets and flatten it down to
a single top level RelativeLayout where the constraints attempt to
reflect the original layout. (This isn't always possible, since some
layout managers offer features not possible to express in
RelativeLayout, such as a LinearLayout with multiple different
weights) but it often works or is at least a good start. (This work
is ongoing, but since my changeset is getting large I want to check in
this snapshot since the functionality is better than what is in the
trunk.)
This changeset also adds a new refactoring: Change Widget Type. This
can be applied to a selection of elements, and it will convert the
widget type to the new target widget type. It will also remove any
attributes that are not valid for the new layout.
It also improves the wizards which display the possible target types.
For Change Widget Type, it will first offer "related" widgets, so for
an AnalogClock it will first offer Digital Clock, for a checkbox it
will offer a checked text view and a radio button, etc.
In addition, it will list Views and Layouts that it finds in any
library jars (except for the builtin Android ones), and any custom
view classes in the project.
There is also now some preliminary support for refactoring unit
tests. These tests must be run as Eclipse plugin tests, since they
utilize the XML model (and the XML model cannot be mocked). The test
infrastructure reads source XML files, applies the refactoring change
list to them, and diffs the output with the known expected output
(also stored as result XML files in the test project).
Finally, there are a number of fixes and improvements to the shared
refactoring code.
Change-Id: I0974653e530dfb4feb625e0eef8257c29d50614b
Diffstat (limited to 'eclipse/dictionary.txt')
| -rw-r--r-- | eclipse/dictionary.txt | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/eclipse/dictionary.txt b/eclipse/dictionary.txt index 8246992..5e364be 100644 --- a/eclipse/dictionary.txt +++ b/eclipse/dictionary.txt @@ -16,6 +16,7 @@ apk app apps arg +async attrs avd avds @@ -122,6 +123,7 @@ marquee metadata min monte +ms multi multimap multimaps |