Introducing Android Studio
141–150 of 189 posts
Re: Introducing Android Studio
#142Unfortunately, switching to Android Studio presents a different set of issues, like lack of Perforce integration (using Perforce is out of my control here, unfortunately).
I'd assume some sort of hybrid Android Studio/IDEA setup is possible, but even still the Pro version of IDEA that I would seemingly need to get any Perforce integration working is priced at a point ($499 and up) where I'm not sure I could make a justification for the purchase. Eclipse kinda sucks, but it also mostly works and the perforce integration on it is free (and also quite good, I have no idea if IDEA's is any good).
I could, of course, just eschew IDE/VCS integration, but editor integration is, in my experience, kind of a big deal with Perforce because of the rather old-school model it uses of checkouts. It becomes really annoying to merge code in if you don't preemptively check things out before you change them, and having the IDE manage this by just checking things out when you first start editing them is a huge win. Pseudo-ironically, if the VCS I used were any of the ones Android Studio/IDEA gives you for free having support for it in the IDE would be less of a big deal for me, I'd just do all the VCS stuff at the command line.
Re: Introducing Android Studio
#143Eclipse is a constant source of small annoyances for me, none of which by itself is a huge deal but when taken together color my view of the editor negatively. Unfortunately, switching to Android Studio presents a different set of issues, like lack of Perforce integration (using Perforce is out of my control here, unfortunately). I'd assume some sort of hybrid Android Studio/IDEA setup is possible, but even still the…
Re: Introducing Android Studio
#144This is huge. I've held out on Android development for many reasons, but my visceral hate for Eclipse is one of them. I know I've been able to use IntelliJ before now, but Eclipse was Google's example in tutorials, etc. Now I'm very excited to make an Android app.
Why does everyone seem to hate Eclipse? I've been using for a while and I can't find reasons to dislike it.
Re: Introducing Android Studio
#145Earlier quoted context omitted.
Even the community edition[1] supports android development. Just point IntelliJ at your android sdk installation folder, and you're off to the races! [1]: http://www.jetbrains.com/idea/features/android.html
But I think this version is not the same as Android Studio community edition.
[1] http://blogs.jetbrains.com/idea/2013/05/intellij-idea-13-ear...
Re: Introducing Android Studio
#146Looks great, too bad it won't even launch for me on Windows 7. Anybody else running into problems running it?
Re: Introducing Android Studio
#147Eclipse is a constant source of small annoyances for me, none of which by itself is a huge deal but when taken together color my view of the editor negatively. Unfortunately, switching to Android Studio presents a different set of issues, like lack of Perforce integration (using Perforce is out of my control here, unfortunately). I'd assume some sort of hybrid Android Studio/IDEA setup is possible, but even still the…
I don't get it. Perforce is ~$200/seat/year. IDEA at $500 seems like a no-brainer compared to limping on with Eclipse.
I suppose I will try the 30 day demo of IDEA and see if it is worth fighting for, but probably not until Android Studio is more baked because I've played around with it enough to know that the 0.1 designation is warranted at this time.
Re: Introducing Android Studio
#148Preview or not, you don't expect such dribble from Google.
Mac error was:
Can't register given path of type 'SOURCE' because it's out of content root.
Windows error was:
(After env var fix) "There must not already be a project at this location" and would not let a new one be created.
If they can't test enough to guarantee basic project creation on stock standard OS's they shouldn't release it.
Re: Introducing Android Studio
#149Many of us game devs use C++ for performance and especially cross-platform support, so I am very interested in seeing how NDK support turns out in this. Debugging native code in particular has always been a pain point even for people who don't hate Eclipse.
[1] http://blog.jetbrains.com/objc/2013/04/c-ide-an-april-fools-...
Re: Introducing Android Studio
#150Earlier quoted context omitted.
I don't get it. Perforce is ~$200/seat/year. IDEA at $500 seems like a no-brainer compared to limping on with Eclipse.
I work at a company that mandates Perforce for political reasons and getting budget for a $500 purchase when I can't reasonably articulate the benefits over the free thing we've been using all this time would be an uphill battle that I'm honestly not sure is worth it, because while I find Eclipse annoying I don't have enough experience with IDEA to know that it is not annoying in a different set of ways. I suppose I…
It's hours and days wasted, and that's before I consider any difference in productivity while actually using each IDE. If any of this sounds familiar, do spend a couple of weeks in the free version of IDEA. It was night-and-day for me. The worst part will be your muscle memory (e.g. stepping through the debugger).