On 12/15/2010 12:40 PM, Frank Weiss wrote:
Well, our perception of Eclipse is 180 degrees from mine. I'm curious, what did you meant by "beast"?
I guess it just seems really complex. I've never used and IDE, so there is a lot to learn. I did the android HelloWorld and Notepad in Eclipse and just decided to go back to the command line. I still push a button to compile install and run the app - it's just that the button is a scriipt. I'm comfortable on the command line, and I don't like to use the mouse. I also couldn't live without vim. I understand that there are plugins for that, but I googled around and gave up. Step debugging is the last thing that I need. Otherwise, I'm super happy with the SDK from the command line. I don't have Ctrl-Shift+O, but I'm new to Java, and new to android, so I don't mind that I'm forced to get familiar with the object heirarchy. I'm sure that the docs are more readily available from Eclipse, but the online android reference rocks.
In the OP you asked about setting breakpoints right in the code. In Eclipse debugger (and just about every GUI debugger, including Firebug) you just double click in the left margin of the source code line to set a breakpoint, which is indicated by a small dot in the left margin.
By "in the code" I mean that I want to be able to edit my source code with an editor and have that generate the breakpoint. With some other debuggers, there is a function call that can make this happen.
When the breakpoint fires, Eclipse highlights that line. From there you can inspect variables, the stack, etc. and step through the code. I've debugged with the command line before, but once I started debugging with Eclipse, Visual Studio, and Firebug, I would think that having to use a command line debugger is painful.
I get that it must be more streamlined, and I wanted to try it. I thought that I could just go to Eclipse for debugging and do everything else the same way I've been doing. I created a new android project from existing source, and pointed to my source tree. There were many errors listed, even though my app compiles and runs fine. I couldn't make sense of them. I tried to run the project and I got an error. I just gave up. I guess that made me think of the program as a beast. I will give it a try some other time. I can't make a valid choice until I have reached some level of familiarity with what Eclipse can do. I notice that there are two well represented camps on the net: those that love Eclipse and those that hate it. There's very little in between. I shy from GUI's in general. I always find myself doing repetitive mouse movements to get the same things done over and over. On the command line, anything repetitive is scripted. I guess I tried to further justify my original choice by thinking that I'd learn Java and the SDK in greater depth this way, and I might say that I believe that I was correct in that respect. Thanks, Toby -- 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
