JetBrains Company Blog gives details on Android Studio:
http://blog.jetbrains.com/blog/2013/05/15/intellij-idea-is-t...
Introducing Android Studio
111–120 of 189 posts
Re: Introducing Android Studio
#112The great thing about Android Studio based on IntelliJ is that Kotlin plugin should work with no or minimal change to work there.
Re: Introducing Android Studio
#113Android Studio, at present, embeds Eclipse...
./sdk/tools/lib/monitor-x86_64/
This seems to be the DDMS view of the Eclipse ADT.
Re: Introducing Android Studio
#114Earlier quoted context omitted.
That makes me angry. I really like Jetbrains as a company and you would think Google could spare some money and pay Jetbrains something.
CTO of Jetbrains is talking about this at the moment at Google IO. It could have been a collaboration.
Hell, imagine all the PR at the moment. They don't just do Java, they have IDEs for PHP, iOS, etc. I wouldn't be surprised if their sales took off as a result of this keynote.
Re: Introducing Android Studio
#115Early access preview available now: http://developer.android.com/sdk/installing/studio.html
Just a head up: you will need to edit the configuration to run on device (the default only launches on AVD). Took me a while to figure that out.
Re: Introducing Android Studio
#116Earlier quoted context omitted.
The feature set is fine, and when it came out it was basically revolutionary. But over the years the architecture has developed real instability. Frequent crashes, terrible and fundamentally broken package/dependency management. Difficult to find features, inconsistent UX and a vast amount of very low-quality plugins in the ecosystem. Then there's the extremely varied and confusing set of packages. There's even a mat…
Everything you wrote was true several years ago, but today it's no longer true. Eclipse is pretty stable now since it has OSGI under the hood. UX wise though it's still pretty crappy. I wouldn't be surprised if the new Android IDE is still Eclipse.
Actually from the screenshots at The Verge it looks like it's ... IntelliJ rebranded!
Re: Introducing Android Studio
#117Earlier 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.
You're right, it isn't.
This post[1] from JetBrains helped clear the situation up for me.
[1]: http://blog.jetbrains.com/blog/2013/05/15/intellij-idea-is-t...
Re: Introducing Android Studio
#118Earlier quoted context omitted.
I use Eclipse extensively personally, but the one thing that drives me nuts about it is it's general speed. Conversely I'm so well versed it in I don't have a strong desire to replace it at the center of my work flow. Just been getting better/faster machines over the years.
They took a step back with the CSS theming disaster which seemed to slow down the UI dramatically. Other than I have never hated Eclipse. It's very productive for Java development. That said I use SublimeText for every other language...
For quick edits I will turn to jEdit or vim. I've also been giving LightTable a try and enjoying the early stages.
Re: Introducing Android Studio
#119The early access preview ( http://developer.android.com/sdk/installing/studio.html ) is definitely prettier than Eclipse. Not that that's a high bar to clear. It also seems to be less stable, which is a high bar to clear. ;) Yeah, I know, pre-release software. The windows seem to take a long time to load, too. That strikes me as odd -- it's one thing when you're starting up some sort of interpreter, but several secon…
The long loading time might be unoptimized-yet parsing of various XML files of ones app. In general, it's mostly an evolutionary work on existing IntelliJ Android plugin.
The View editor afaik has some support for custom views, but only some - it's rather iffy (IntelliJ Android view renderer simply used Android libs to render them, but of course that doesn't work for everything, and anything fully programmatic is dead anyway). Fwiw, IntelliJ's XML editor was always much better at not freaking out at the fact that you haven't finished writing that new tag so of course your view doesn't validate (something that was a constant for me back when I used Eclipse).
The editors in general are standard for IntelliJ, with some nifty transformations added - the XML string example reminds me of how IntelliJ dynamically renders certain idioms into Java 8 forms while still keeping the code in 1.6 (well, that's how I have it configured, that is).
In general, it's nice, I hope it will be available as plugin into plain old IntelliJ as well.
Re: Introducing Android Studio
#120Earlier quoted context omitted.
I have neither used Eclipse or IntelliJ much. So from a new user point of view - I dislike Eclipse primarily because of really bad UI. Big toolbars, tabs, everything takes up considerable amount of screen leaving very limited space for code. Looks ugly. Speed sucks too. On other hand, IntelliJ not only has cleaner UI, but also better shortcuts and even show hints to remember them. Speed not great, but feels better th…
Traditional Style Tabs are quite a bit less ugly.
Indeed, my first move after every install is to change to classic appearance. I really don't know what they were thinking.