I don't know if anyone else has come across this using Eclipse for Android development, but;
- You have to update the Manifest manually; I would have expected this to be managed by the tool.
- You have to define a base package in the Manifest; which means all class references in the Manifest must be partial / relative; as a result you don't seem to be able to pass fully qualified classes to methods that take classes as args (ie. startService()).
- The Log functionality seems a bit flaky in Eclipse. I had it working briefly at one point (with an older SDK) now I have to quit Eclipse and run DDMS from the command line.
- The R.java does not appear to get auto-updated.
- If you do a 'Clean' and build of an Android project in Eclipse things can get easily screwed-up.
- If you kill the emulator in Eclipse, DDMS can then have problems re-connecting to the adb process when you try and restart the emulator.

0 comments:
Post a Comment