http://www.developer.com/http://www.developer.com/ws/android/development-tools/mastering-eclipse-content-assist-for-android.html
When you're just beginning to develop Android apps in Eclipse, your immediate concern will be coming to grips with the ins-and-outs of a new platform, but once you've mastered the essentials you'll want to focus on making development easier, less error-prone and ultimately faster. This is where some extra Eclipse know-how comes in handy. As essential way to speed up your day-to-day development work is to harness Eclipse's powerful and time-saving 'content assist' feature. Content assist provides context-sensitive code completion via a pop up window, saving you from typing out every line of code in full, while also reducing the chances of spelling mistakes and typos. To access content assist for Android, press Ctrl and the space bar. This will open a pop up containing potential endings for whatever code you're currently typing. If you're not a fan of keyboard shortcuts, the content assist option can also be found in Eclipse's Edit menu. In this example, I'll use the simple scenario of specifying the width parameter for TextView to demonstrate how you might use content assist for Android in your project. Tip:You can press Ctrl+space without typing anything first if you wish to view all the constants and methods of a class. Despite being such a useful and intuitive tool, Eclipse's content assist for Android functionality can sometimes be a source of pain for Android developers, as it may stop working when you update your Eclipse installation -- or seemingly stop working at random! In this section, we'll address some common complaints and share some techniques for getting content assist for Android back on track. If your code completion window is displaying a 'No Default Proposals' message, your default options might be at fault. To address this: If content assist is constantly bringing up non-usable suggestions (for example "default namespace - Default namespace attribute" or "xsinsp - XML schema namespace"), the problem may be that your XML file has been assigned to the XML editor, rather than the customized Android XML editor. To check whether this has occurred in your installation: If you've just upgraded to the latest, 'Juno' release of Eclipse, you may suddenly start seeing the dreaded "No Default Proposals" when you call content assist, despite it working perfectly before. In this situation, there are several possible fixes that can get content assist running smoothly again. Restore Defaults Java Proposals If this doesn't solve the problem, re-open the above dialog and ensure the Java Proposals checkbox is selected in the Default Proposal Kinds box. And If All Else Fails ... Closing and restarting Eclipse in 'clean' mode will remove cached data stored by the Eclipse runtime and force cache reinitialization. This should rectify any outstanding issues with content assist for Android. Add Restart Eclipse. Note, Eclipse will typically take much longer to load with the Tip: After you've run the Alternatively, you can open a clean installation using your Eclipse shortcut. Again, remember to remove the Having content assist for Android handy can greatly increase your productivity. Not only will it save you typing out every character of your code, but its context-sensitive nature means you are less likely to insert the incorrect code or make typos/spelling mistakes, which aren't always easy to spot. In this article, we covered the essentials of coming to grips with content assist for Android, and shared some tips for keeping this useful functionality running smoothly. Eclipse has plenty more ways to accelerate your day to day development work - if you're interested in learning more, then the Juno documentation is a great source of up to date information.
Mastering Eclipse Content Assist for Android
September 26, 2012
Accessing Eclipse Content Assist for Android
Troubleshooting with Content Assist for Android
Content Assist Is Displaying 'No Default Proposals'
Content Assist Is Always Displaying the Same Non-Usable Suggestions
Upgrading to Eclipse 'Juno' Has Broken My Content Assist
-cleanas the first argument on the first line.-cleanargument in place, so be patient!-clean argument once, you should remove it. Leaving the -clean argument in the eclipse.ini file means you will keep encountering these increased startup times.
-cleanargument after the current Target.
-clean argument once you've finished with it, as it greatly increases Eclipse's load time.Conclusion