For Developers: Live On The Edge - Upgrade To The Latest Eclipse ADT (Currently v9.0.0) Before It Is Released [How-To]

Changes since release 8.0.0:

• Many bug fixes.
  • Of particular note, the launch feature in Eclipse will now properly work when the target device is running a production build. It will not complain that debuggable=true is missing from the Android Manifest anymore, since the build system inserts it automatically.
• Go To Declaration hyperlink support: You can jump directly from code references such as "R.id.main" in Java code right into the corresponding XML declaration, as well as from XML attributes (like @string/name) to the corresponding resource definition, and from manifest XML registrations to activities and services, etc.
• Improved support for empty and nested layouts. Dragging over nested and invisible layouts automatically enlarges and highlights these layouts such that they can receive drops.
• Support for rendering targets. You can now choose an arbitrary Android platform to have the current page rendered with, regardless of the minimum platform chosen by the project. This makes it easy to check pages visually for different platforms.
• XML formatting improvements: The XML edited by the tool should be much cleaner, and you can enable auto-formatting in the options.
• Automatic configuration for various view types. As an example, you now automatically get match_parent width filling when you drop say an EditText into a vertical LinearLayout, you get a default image added to ImageButtons, etc.
• Dragging from the palette, and dragging within the layout editor, now shows live previews of the dragged item rather than just a simple drag & drop cursor.
• Improvements to the support for rename refactoring.
• In the layout editor, double click views to warp to the corresponding XML element, and in the outline view, a double click will open the properties view.

• In your Java code, if you see a symbol like R.id.button1, you can click on this to jump right to the layout definition of the view which defines id button1 (@+id/button1).
• In the R file, you can jump right from "public static final int Button01=0x7f050000" to the corresponding button definition
• In your Manifest file, you can jump from an activity definition (or service definition), such as <activity android:name=".TestActivity", right into the corresponding Java class
• You can jump to any value definition (e.g. @string:foo), regardless of which XML file "foo" is defined in
• In addition to values you can also jump to all the file-based declarations (e.g. @layout/bar)
• You can jump to non-XML resources as well, such as @drawable/icon. This will launch whatever Eclipse opening mechanism exists for the given file type, in this case an image.
• You can jump into @android namespace resources. This will open the resources found in the SDK install area.
• From XML layouts, you can jump to custom view classes (e.g. <foo.bar.MyView></foo.bar.MyView> ), or  <view class="foo.bar.MyView")