Alright, I was really excited to get the HTC Hero. REALLY. I had extremely high hopes for the Hero (those are long gone) and Android (which I still do - I even began developing for it) but the Hero has so many ridiculous bugs that I am *this* close to bringing it down to the Pre level (I'm not going to dare though - Pre still leads in the "I Want To Smash This Phone Into A Wall" category).
In this article I will describe the problem I've had with Eclipse's handling of XML file formatting as well as the best way to fix it.
I use Eclipse to do my Android development for a few reasons:
- it's the only IDE fully supported by the Android dev team
- it has a visual Layout/Resources builder that transforms XML files into corresponding visual representations
- it's free and open source
- I've been using Eclipse for many years and am very familiar with it
The Problem
However, one thing about Eclipse Android development has bothered me for a while - and that is XML formatting by the visual tools.
Today is my first day looking at Android development. My first encounter with the Android plugin for Eclipse has not been very smooth, to say the least. I am not sure if it's Android's or Eclipse's fault but I just wasted 2 hours on errors during the plugin installation and would like to pass on the time savings to you.
The plugin install page provides initial instructions and the location of the plugin to give Eclipse (https://dl-ssl.google.com/android/eclipse/).
I think this is going to be really neat: you walk around the streets of San Francisco, for example, with your Android powered phone, en route to your destination 20 blocks away.
You whip out your phone, go to Google Maps, pull up the StreetView (remember this?), which zeroes in on your location using a built-in GPS, and then changes as you move the phone around using the built-in compass.




116,034
64,495
0
8,274