aboutsummaryrefslogtreecommitdiffstats
path: root/eclipse/plugins
Commit message (Collapse)AuthorAgeFilesLines
* SdkManager: Refactor name of UpdaterWindow.Raphael Moll2011-05-273-12/+12
| | | | | | | | | | | | | | Since the sdkmanager now contains separate windows for the "SDK Updater" versus the "AVD Manager", the various UpdaterWindow classes are renamed to SdkUpdateWindow. We already have now a standalone AvdManagerWindow that matches this pattern. This is a pure refactoring/renaming CL with no workflow change whatsoever. Change-Id: I18ecb6aa33b7e9bd2294a959b371b424d03b2060
* [EXTERNALIZATION] This commit externalizes the strings of the DDMS plugin.Pablo Leite2011-05-2715-262/+565
| | | | | | | | | | | | | | | | | | | | | | | | | | After applying it, please run the Eclipse's Externalize Wizard at “Source -> Externalize Strings…”. This ensure that hard-coded strings added between the time the patch was created and the time it was integrated will also be externalized. From the time this patch is integrated on, each new string created in the plugin should be added to the following files: eclipse/plugins/com.android.ide.eclipse.ddms/src/com/android/ide/eclipse/ddms/i18n/messages.properties Example: JavaClassName_MessageID=<string value> <string value> refers to the string itself. eclipse/plugins/com.android.ide.eclipse.ddms/src/com/android/ide/eclipse/ddms/i18n/Messages.java Example: public static String JavaClassName_MessageID; In the Java class, the new string should be referenced this way: Messages.JavaClassName_MessageID Related patches: All patches with the [EXTERNALIZATION] tag Changes after review: Code formatted according using android code formatter template Merged Strings DeviceView_Unable_Create_HPROF_For_Application and DeviceView_Unable_Create_HPROF_For_Application. Removed Motorola copyright notices. Change-Id: Id889db593ef313760515f28b5973d3a9a8ad80d0
* Default render target level should consider project targetTor Norbye2011-05-261-7/+45
| | | | | | | | | | | | | | | | | | When picking the default render target, we attempt to pick a render target that is at least version 5 of layoutlib (where rendering fidelity has improved significantly, where include support is improved, etc.) However, this sometimes picked a render target whose API level is lower than the project target. This CL fixes that problem, and also improves the detection of compatible layout libraries to not only consider API level 11 or higher, but also the new layoutlib API property which will identify qualified SDK versions when we release backported versions of layout lib. Change-Id: I4d4159389692d984a66856eeb80035a8e8b7d1cf
* Fix ADT-testXavier Ducrohet2011-05-251-0/+4
| | | | Change-Id: Iebc29d774747ba64f1f895cd36970330145fd6b4
* Add support for addon providing their own layoutlib and/or res.Xavier Ducrohet2011-05-254-6/+10
| | | | | | | | | | | | | | | | | | During addon parsing, the SDK Manager will detect whether the addon has: - data/layoutlib.jar - data/res/ - data/fonts/ if the first one is present, then it is used during rendering. if *both* the 2nd and 3rd ones are present, then addon resources are used during rendering. On the GLE side, all that's needed is adding addons to the list of rendering targets if they have either library or resources (or both). Change-Id: Id16925eea2c98b9fbaaa884ac6fd8c1c1c444db2
* Merge "Use sdklib.OsHelper in AddCompatibilityJarAction."Raphael Moll2011-05-241-106/+3
|\
| * Use sdklib.OsHelper in AddCompatibilityJarAction.Raphael Moll2011-05-241-106/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | ADT's AddCompatibilityJarAction defined 2 new generic useful methods, copyFile and isSameFile. SdkLib already had an OsHelper.copyFile, so I moved that class to a more generic sdklib.io package and added the new method isSameFile. Another suitable candidate would have been io.FileWrapper in the common project. Change-Id: If310e09af112c5f4d87a253b35e67e4f5adb34da
* | Merge "Don't apply default attributes in a move/copy"Tor Norbye2011-05-242-8/+22
|\ \
| * | Don't apply default attributes in a move/copyTor Norbye2011-05-242-8/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There is a method in the layout editor which fills in required default attributes like id, width and height, as well as some optional attributes like a default text attribute. This code was called unconditionally whenever a new child is added to a layout. However, this should only be done when a new widget is created, not during moves or copies from existing elements. Change-Id: Ic04dec746c70359eca38454bacfdcdb87891719f
* | | Merge "Disable palette preview for some widgets on some platforms"Tor Norbye2011-05-242-1/+44
|\ \ \ | |_|/ |/| |
| * | Disable palette preview for some widgets on some platformsTor Norbye2011-05-242-1/+44
| |/ | | | | | | | | | | | | | | | | | | ListView palette preview requires adapterview support in layoutlib, and DatePicker and TimePicker require Holo themes on Honeycomb. This changeset adds some conditional logic to the palette preview code to drop rendering of these widgets based on the current render target, layout library and theme. Change-Id: Ic42a40faf817e60525485e0a46b7ad967ed1c363
* | Merge "List project themes, if any, before framework themes"Tor Norbye2011-05-231-39/+39
|\ \
| * | List project themes, if any, before framework themesTor Norbye2011-05-201-39/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changeset moves the project-themes in the combobox up above the framework themes, since (a) it's likely that the user wants to frequently choose these, and (b) the list of project themes is usually much smaller than the framework list, so it brings these items up to the visible part of the combo Change-Id: Idb989d388f5cb1f5cc6a302a6c5796db69e78c8e
* | | Detect and add special warning for wrong themesTor Norbye2011-05-232-4/+13
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If you open a layout designed for a particular theme in another theme, you can get many confusing error messages. Instead of "attribute missing" it may tell you that it failed to convert a resource to a color or drawable, and so on. To help guide users to the root problem (wrong theme chosen) this changeset detects the scenario where theme attributes can't be resolved, and when these are found the top of the error log will start with a bold message stating that theme resources were not found and to check whether the correct theme is chosen. To do this, the resource resolver emits a new sub-type of the resource missing tag into the error log, which is used in the IDE to prefix the errors with the special error message. Change-Id: Ic29c9af37da4b5cc2c9fb1ca5670c8b8f79bf852
* | Merge "NPE safeguard"Tor Norbye2011-05-231-0/+4
|\ \
| * | NPE safeguardTor Norbye2011-05-201-0/+4
| |/ | | | | | | Change-Id: I3f55c21f79ad66bed1329a2f5882deb94e93be62
* | Merge "Mechanism to disable SwtMenuBar in SdkMan2"Raphael Moll2011-05-201-3/+4
|\ \
| * | Mechanism to disable SwtMenuBar in SdkMan2Raphael Moll2011-05-201-3/+4
| |/ | | | | | | | | | | | | | | | | | | | | | | | | The SDK Manager 2 should not try to change the menu bar when invoked from Eclipse. Actually it can't because the SwtMenuBar lib isn't even present to it crashes with a NoClassDef exception. This CL adds the notion of "invocation context" so that we know what is invoking the manager and we can change the UI accordingly. Change-Id: I606850a20fbc5f9d2d1d4fd0e16aa0bd71ef41c7
* | Offer to install fragment compatibility libraryTor Norbye2011-05-205-36/+156
|/ | | | | | | | | | | | | | | This changeset changes the popup displayed when you drop a fragment tag in a pre-API-11 project. Instead of just displaying an error message, you now get a dialog which asks if you want to install the project, and if you click the "Install" button it invokes the SDK manager to install the right package, and then copies it into the project. In addition, the fragment selector now has a "Create New" action which invokes the New Class wizard pre-configured with the right fragment class. Change-Id: I4ce1b51fbfe939a21e91379eb6b77ff722c13f0f
* Merge "SDK Manager dialog to perform specific updates from ADT."Raphael Moll2011-05-203-7/+354
|\
| * SDK Manager dialog to perform specific updates from ADT.Raphael Moll2011-05-203-7/+354
| | | | | | | | | | | | | | | | As a working case example, this adds an ADT project context menu to add the Android Compatibility JAR to an android project. Change-Id: Icd86930b72558240dc9f5a6f732478253b8cb0fb
* | Fix potential stackoverflow in theme detection.Xavier Ducrohet2011-05-191-3/+6
|/ | | | Change-Id: I19d2a3c9c6802b3e1c065ca36828d2b672130630
* Add preview support for GridViewsTor Norbye2011-05-196-27/+101
| | | | | | | | GridViews are another AdapterView subclass. This changeset adds preview support for GridViews by modifying the ListView preview support to also accommodate GridViews. Change-Id: I5af0a4c7e270cfa23c609be316d01dfb188a051b
* Fix auto-mergeTor Norbye2011-05-191-27/+0
| | | | | | | | | A change that was cherrypicked from the external master into the tools-r11 branch was automerged back into the external master in such a way that a method and a field got duplicated. This CL fixes the merge. Change-Id: I5b05c8a9477b4afb669efd1904c1415925d25307
* merge from tools-adt_r11The Android Open Source Project2011-05-181-0/+27
|\ | | | | | | Change-Id: Ic374b2d4185f1c3c4dbad2ea81b901fe9b07666a
| * Add Request Focus to textfieldsTor Norbye2011-05-186-3/+164
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changeset adds a couple of focus related changes: 1) When the first text field is added into a layout, it is automatically requesting focus 2) There is a new context menu item available on textfields to request focus. When invoked on a text field, it will both add <requestFocus> to itself and remove it from any other text fields that have set it in the layout. When invoked on a text field which already has focus, it will offer to clear the focus. 3) The Advanced section of the palette also contains the <requestFocus> tag. Change-Id: Ie9e1ab07c4f7ea701e9fac17f6c82e52656bc755
| * Merge "Binary XML editor" into tools-adt_r11Tor Norbye2011-05-181-3/+13
| |\
| | * Binary XML editorHaris Peco2011-05-171-3/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | This change contains the workaround for http://code.google.com/p/android/issues/detail?id=15003 For details, see http://code.google.com/p/android/issues/detail?id=15003#c50 Change-Id: I6485d32620a23c17879922155a8cfb6e4290f05e
| * | Merge "Fix bug in editor open utility" into tools-adt_r11Tor Norbye2011-05-182-47/+55
| |\ \
| | * | Fix bug in editor open utilityTor Norbye2011-05-172-47/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The code to open a file (called by Go To Declaration, Show Include etc) handles two scenarios: (1) The file is in the workspace - open using Eclipse IFile mechanism (2) The file is outside the workspace - open using the fallback external storage (which means you get a plain XML editor) There's a third scenario: the file is not in the workspace, but is part of a project in the workspace so it does have a valid IFile. (This can happen if you import a project but choose not to copy the contents into the workspace). This changeset adjusts the code to open up an editor such that it handles this third scenario and we get our own XML editors for these types of files. Change-Id: I040e1b899cd38bbda3fcf3475cc4dfb541d10016
| * | | Merge "Fragment Rendering Support" into tools-adt_r11Tor Norbye2011-05-188-27/+382
| |\ \ \ | | |/ /
| | * | Fragment Rendering SupportTor Norbye2011-05-178-27/+382
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changeset adds designtime-previewing of fragments, where a layout which contains fragments will show the contents of the fragments inline. Initially, the fragments are empty, but you can right click on them to bring up a context menu where you can choose which layout to show at designtime. This is persisted across IDE sessions, just like the ListView render preview. In addition to the generic layout chooser, all layout references found in the associated Fragment class (usually what you want) are listed directly in the menu. Change-Id: Iff3e6e5cbf87a19bdb61e677a63f663ca6e4848b
| * | | Merge "Basic fragment support" into tools-adt_r11Tor Norbye2011-05-1812-18/+325
| |\ \ \ | | |/ /
| | * | Basic fragment supportTor Norbye2011-05-1712-18/+325
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changeset adds preliminary support for fragments: * Add <fragment> to the palette, along with a drop handler which pops up a class chooser to pick the Fragment class; all project implementations of android.app.Fragment and android.support.v4.app.Fragment are listed. * Adds a fragment descriptor such that code completion works for <fragment> elements * Fix project callback such that it does not complain about a missing class "fragment". * Fix outline to display the name of the fragment rather than the fragment tag name. * This changeset also centers the label in MockViews since those are still used to render fragments Conflicts: eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/layout/descriptors/LayoutDescriptors.java Change-Id: I6f39f0c29a0cf21799fa8a55406eeae1e3beb57f
| * | | Merge "Make Go To Declaration work for <fragment> names." into tools-adt_r11Tor Norbye2011-05-188-5/+102
| |\ \ \ | | |/ /
| | * | Make Go To Declaration work for <fragment> names.Tor Norbye2011-05-178-5/+102
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/common/layout/LayoutConstants.java Change-Id: I5260aacb7d7a14141f43d9a65bb4bb87627d17c2
| * | | Merge "Custom View handling improvements" into tools-adt_r11Tor Norbye2011-05-188-9/+65
| |\ \ \ | | |/ /
| | * | Custom View handling improvementsTor Norbye2011-05-178-9/+65
| | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | First and foremost, allow custom views to accept children such that you can drag & drop children into the custom view in the outline. Second, prevent an NPE which can occur if you drag into a layout where the root element is a custom view. Third, handle <view> (not <View>) better: provide a custom icon, and inline the view class name in the outline label. Fourth, allow double clicks (in addition to ctrl-click which is already supported) on the custom views in the palette to allow jumping to the custom view code. Change-Id: I13c2bf2f4169185c9fcc893ce487f2abdac46802 Conflicts: eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/layout/descriptors/LayoutDescriptors.java
| * | Escape Strings extracted with the Extract String refactoringTor Norbye2011-05-171-0/+31
| |/ | | | | | | | | | | | | | | | | Escape any single or double quotes inside the string value definition in strings.xml: This'll work => "This'll work" Escape '" => Escape \'\" Change-Id: I21cb506e10e837feb0e435a21cb50aaa5342f0fa
| * Merge 580ecb7a from master. do not merge.Xavier Ducrohet2011-05-171-0/+1
| | | | | | | | | | | | | | | | | | Add baseline/margins to ViewInfo. Also make it so that older layoutlib that are using API5 return the value through reflection (done in LayoutLibrary.) Change-Id: Ied102625430b53f9b5e62aa738c8c598054cc266
| * Merge 'Remove "Android Tools > Convert to Android Project"' into tools-adt_r11Raphael Moll2011-05-162-189/+0
| | | | | | | | | | | | | | | | | | | | | | | | The feature to convert a Java Project into an Android Project is broken. It's also quite irrelevant now since project are better created using the NPW. SDK Bug: 3259855 (cherry picked from commit 7f8f80cfe2a29b7ebaf139fb4228ad31192fb8a9) Change-Id: Ifb5e93d2dcf6853136cd4add5e4af6b14fafec35
| * Merge "Add code completion support for drawables, animations and colors"Tor Norbye2011-05-0457-57/+2328
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changeset adds in descriptor metadata and XML editors for: - Drawables (res/drawable/) - Animations (res/anim/) - Animators (res/animator/) - Colors (res/color) These types have also been added to the New XML File wizard. There is some specialized completion support for animators: - Completing on the propertyName property of <objectAnimator> will offer the various integer and float properties in views - Completion for the interpolator property shows the framework interpolators immediately and on top (instead of having to complete the individual resource paths @android: and anim/ first There is also a new quickfix and marker resolution for the AAPT error which complains about an unbound prefix. This will insert a xmlns:android="http://schemas.android.com/apk/res/android" attribute declaration on the root element. This CL also includes a fix to make the New XML File Wizard preselect the current project in more scenarios. NOTE: This changeset adds new XML editors for these resource types. It does not attempt to update previous editor bindings for files of the given type, so to test this you may need to use "Open With" in the package explorer to pick the right file type. A subsequent CL will try to migrate settings over to these editors, but that work will tie into another effort: merging all these different editors into a single editor class that does its own content type switching and different viewparts for the other tabs. (cherry picked from commit aaa917c9c5e6f974ca20b94adfd53d1bf01bb54e) Change-Id: Iddc2405c4802d43126d9b2172f86869de80bef10
| * Merge "Misc fixes"Tor Norbye2011-05-043-6/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changeset fixes a couple of misc problems I ran into: (1) Save the current file when double clicking on an included view. When double clicking on an included view, the included view is opened in a "Show Included" context where the including file is surrounding the include. This will read the surrounding file from disk, and if we don't save the file when opening the file then it's possible to see a stale view (best case) or it won't work at all if the include tag itself isn't in the saved version of the file. (2) Fix a bug in the "Select Same Type" context menu action where the list was cleared before reading out the item to be selected. (3) Filter out a few more properties from the Extract Style refactoring dialog, and include margin attributes (cherry picked from commit 2047b3b061e179faf6d613540a34cc7e6d492176) Change-Id: I3c1c9d3094b7488ddf45abe6df4d686949eb8fd0
| * Merge "Improve custom view search and filtering"Tor Norbye2011-05-043-15/+75
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change improves the code which identifies custom views in the project. It will now filter out a number of "false" matches: - Classes that were only defined in a javadoc (these are included in Eclipse type hierarchy search results) - Anonymous classes - Classes that extend View, but do not define one of the 3 base View constructors: View(Context context) View(Context context, AttributeSet attrs) View(Context context, AttributeSet attrs, int defStyle) We can only instantiate custom views with one or more of these constructor signatures at designtime. It also fixes two additional bugs: - It changes the search flags passed to the search engine which makes it now find custom views that are static innerclasses. - It fixes a bug in handling view descriptors which made the custom view palette not work at all in some projects (in some case the descriptor would be null, which caused an NPE which caused the whole palette initialization to bail.) This is the bug which made me dig through the custom view code and discover the above problems too. (cherry picked from commit 916b78d9e78cb446d72de6cba30f2f395728f612) Change-Id: I5a80e86dccb8b7fd339919e79e7ed59cd6357819
* | Migrate render target settings to released versionsTor Norbye2011-05-181-0/+18
| | | | | | | | | | | | | | | | | | | | | | When loading the project's render target setting (which as of ADT 11 is per project rather than per layout), check to see if it has a code name, and if so, see if the user has the final version of the platform installed as well. If so, migrate the render target to the final version instead since the user probably did not intentionally want to stay with the pre-release version after installing the final version. Change-Id: Ic45232b5dc691b770045c3281f2c36b580347784
* | Improve the choice of default configurationTor Norbye2011-05-181-3/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When you open a new layout, the layout editor needs to pick an initial configuration for the layout. Currently, the choice of layout is based on the project API level (such that it picks tablet screen and landscape orientation for API 11, and phone and portrait for lower APIs). This changeset adds another factor: the currently used configuration. If you have another layout visible and you open a new layout, then the configuration for the current layout will be used for the new layout (if it is a compatible match). Change-Id: I601b4373514cb30d6051e9de1bfa2ad91ff1b5f4
* | Fix bug in editor open utilityTor Norbye2011-05-172-47/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The code to open a file (called by Go To Declaration, Show Include etc) handles two scenarios: (1) The file is in the workspace - open using Eclipse IFile mechanism (2) The file is outside the workspace - open using the fallback external storage (which means you get a plain XML editor) There's a third scenario: the file is not in the workspace, but is part of a project in the workspace so it does have a valid IFile. (This can happen if you import a project but choose not to copy the contents into the workspace). This changeset adjusts the code to open up an editor such that it handles this third scenario and we get our own XML editors for these types of files. Change-Id: I0fc89316e4625fcf66dd61060cd9b00054bc5464
* | Fragment Rendering SupportTor Norbye2011-05-178-27/+382
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changeset adds designtime-previewing of fragments, where a layout which contains fragments will show the contents of the fragments inline. Initially, the fragments are empty, but you can right click on them to bring up a context menu where you can choose which layout to show at designtime. This is persisted across IDE sessions, just like the ListView render preview. In addition to the generic layout chooser, all layout references found in the associated Fragment class (usually what you want) are listed directly in the menu. Change-Id: Ib7f8caae568eff94a57fd50b8e054f5fa52f3da6
* | Merge "Basic fragment support"Tor Norbye2011-05-1712-18/+325
|\ \
| * | Basic fragment supportTor Norbye2011-05-1612-18/+325
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changeset adds preliminary support for fragments: * Add <fragment> to the palette, along with a drop handler which pops up a class chooser to pick the Fragment class; all project implementations of android.app.Fragment and android.support.v4.app.Fragment are listed. * Adds a fragment descriptor such that code completion works for <fragment> elements * Fix project callback such that it does not complain about a missing class "fragment". * Fix outline to display the name of the fragment rather than the fragment tag name. * This changeset also centers the label in MockViews since those are still used to render fragments Change-Id: I6e062970b335d9c95870f181ed408960978c423e
generated by cgit v1.1 at 2025-04-03 01:17:04 +0000