If you're good with emacs, I would suggest using it for android development. I used eclipse for a bit and couldn't stand it.. it slowed me down enormously, and it hides a lot of lower level stuff that I think is very useful to know if you're serious about developing. You have to customize emacs a bit for it to be efficient enough for android programming, but I think it's worth it in the long run.
Sam On Jul 22, 12:17 am, Doug <[email protected]> wrote: > I use Eclipse daily, both professionally and personally. It's a fine > tool. > > If you don't like the logcat in Eclipse (I don't), run `adb logcat` > from a terminal. Run `adb logcat | grep 'yourtag'` if you want just > your apps' messages. > > The emulator is just fine. It can take a while to launch, but it is > not terribly that slow if you leave it running. If you have a compute- > intense app, then you may have a problem. > > If you have a compute-intense app, then modularize your code and write > JUnit unit tests that can run on your dev machine instead of the > emulator. > > Please explain to me "millions of c++ projects"! > > Doug -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
