Is it possible at the moment to add the Android Studio extensions to a current IntelliJ IDEA installation?
Xavier Ducrohet and Tor Norbye mentioned in their talk, that Android Studio is an extension to the Community Edition of IntelliJ IDEA and that it's not a fork. So it should be possible to add the extension.
Is there an easy way to do so and probably to revert?
They also mentioned in their talk, that Android Studio uses Gradle as default build system. This should break the builds of current modules. Is this correct?
Thanks for the answers, but I finally found the corresponding statement by JetBrains: http://blog.jetbrains.com/blog/2013/05/15/intellij-idea-is-the-base-for-android-studio-the-new-ide-for-android-developers/
You can upgrade by hitting help -> Checking for updates and then choose Early Access Program as channel in the Update settings. You should receive a notification, that version 13 is available.
This EAP version contains almost all Android Studio features except the new Project Wizard and the App Engine Cloud Endpoints, but they will come soon. The reason for the delay is the Google IO, in the future new Android Studio and IntelliJ versions will be synced (mentioned in the comments of the blog post).
I guess it will be at androidstudio but the project is currently empty.
The installation page is here: Android Studio.
From what I understand in the download page & from what they said in the conference, it's a stand alone IDE based on the intelliJ, but i'm skeptical to whether one can get it as an extension to an already installed intelliJ IDEA.
About the build - in Migrating from Eclipse page they explain how to generate Gradle build files for your projects in Eclipse and then import those projects to Android Studio. It's pretty simple and straight forward.
Related
using Android Studio for development. Last week I discovered really neat feature in IntelliJ IDEA IDE, which when debugging Java app shows listing of variables next to the line of code. It is really helpful.
I have been wondering if the same option can be enabled in AS, since it uses the same core? Anybody knows? I would really love to use it in AS as well.
Here is screenshot what I am talking about.:
Android Studio 1.2 Preview 1 has been released just this week, and is the first version of Android Studio based on IntelliJ 14.
Since the feature you're describing was introduced in IntelliJ 14, Android Studio 1.2 will contain this feature as well:
Please note that this is an alpha release, so expect to encounter bugs.
That's a new feature of IntelliJ IDEA 14, as you can see here.
Android Studio is based on IntelliJ IDEA 13, so currently it is not possible to have such feature. Anyway if you want to have it you can always download IntelliJ IDEA 14 and use the Android plugin, which covers the same funcionality that Android Studio does:
From Jetbrains FAQ:
When can I get the Android Studio features in IntelliJ IDEA?
The EAP of IntelliJ IDEA 13, which includes all of the Android Studio
features except for the redesigned new project wizard and the App
Engine cloud endpoints integration, is available now. The remaining
features are going to be integrated in the coming weeks.
See more at: http://blog.jetbrains.com/idea/2013/05/intellij-idea-and-android-studio-faq/#sthash.OPJSeIA2.dpuf
To Download this plugin in IDEA 14, go to Settings, Plugins and then Search for Android Support:
Android Studio Preview has recently been updated to use IntelliJ IDEA 14. If you want to get the new updated make sure you are set to receive updates from the Cannery channel.
To do this go to Android Studio > Check for updates...
Then Click the Updates text and select the channel you wish to receive updates from.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I used to be an Android developer for 2 years, but over 2 years ago. I believe that things changed - we have Android Studio, Gradle and probably more tools that I'm not aware of right now.
What is the current development stack for creating Android applications? What tools should we used right now?
I used to use eclipse with ant, but as far as I can see, a lot of people are using AS with Gradle, which is, for my first experience, extremely slow.
How to jump back into Android development after some time of not being up to date with development stack?
Eclipse vs Android Studio is a matter of choice. You can get used to it within hours, or you can continue with Eclipse. I am using both tools for different projects.
Android Studio seemed to be more stabile at some points.
Update on Android SDK and third party libraries are more easily handled with Android Studio.
Android Studio has not NDK support yet. You have to compile native codes outside of Android Studio. Edit:(Well, actually it has support but claimed to be deprecated, probably developers are working on a better solution)
Edit2:(It will be soon officially supported with C/C++ debugger)
With Android Studio you can use java7 syntax, but you have to stick with java6 syntax on Eclipse. Edit:(you can now force java8 with a plugin on A.S and I guess java7 is usable on eclipse too) Edit2:(java7 is a must now for both parties, but still java8 syntax can only be used in A.S with a help of plugin)
Google releases example codes compatible with Android Studio saying eclipse versions will be available soon.
Android Studio has better GUI designer.
Android Studio has better refactoring capabilities.
The most important change is SDK itself, actually. Just check if Android Studio is good enough for you and study on SDK.
It depends on your project. For non critical or hobby projects you should definitely start with AS and Gradle right away because this the the future of Android development. Although it is still in 'beta' and it can break some stuff after a new upgrade, it has many new features which make you more productive and happier in development.
If you have a critical project and you don't want to spend your time with checking and fixing things your are not supposed to fix, you should stick back to Eclipse, at least until AS is released.
Independently on whether you use AS or Eclipse, you should already start learning and using Gradle. It works perfectly for both options. If you hesitate you can even keep Ant and Gradle building your project in parallel. They work together and don't overlap.
I have been using Android Studio the last year and I can say that it is a very powerful tool, that I believe, in the next year, will overcome Eclipse.
When AS was still in version 4.+ Alpha, there were some issues (mostly with external libraries .jar) but since beta was released and up until now almost every bug was fixed.
Moreover, AS is better when it comes to indexing and suggestions. You will be surprised by its suggestion system, which helps you save a lot of time when coding.
I still use eclipse for other projects, but I believe for Android Development AS is the tool you should invest in, if not for now, definitely for the future.
We are using both, Android Studio and the good old Eclipse IDE. We noticed, that it basically depends on what you're doing. Android Studio is good enough for developing from now and it will replace Eclipse soon. However, it has some drawbacks where Eclipse is your choice. A small comparison was made by Google themselves: https://developer.android.com/sdk/installing/studio.html
Eclipse: Eclipse is very stable and works perfectly with ant driven builds. However, if you want to use gradle, there's some work to do to get the build process working with eclipse. We tried to use Eclipse with Gradle but the Gradle Plugin was quite buggy at this time. If you want to use native C code, you must use Eclipse, as Android Studio does not support that, yet.
Android Studio: Looks great and does also a very good job. The gradle integration works much better there. This is a big advantage over Eclipse when you have to deal with many dependencies. This is probably not an issue for small projects. But, if you're developing projects with additional libraries or frameworks you should definitely give Gradle a try. I hope, that the NDK support is coming soon, so that we can switch to AS completely. Ant builds are someway out-dated.
First of all, I will not debate about Android Studio vs Eclipse as it's an opinion based discussion and a kind of a troll...
The Android development basically the same : the base tools still ADB, Android SDK, Java language... So you can continue to use a "notepad" and compile, build and deploy by the SDK tools.
However, like in every development project, you could choose your upper level tools. Your question is about IDE and building system. This is only a matter of choice.
Android Studio and Gradle are still in beta phase for Android developments and you could use them only if you keep this in mind. You could continue to use Eclipse and Maven or switch to Android Studio and Gradle or keep using Eclipse but moving from Maven to Gradle... just make what you prefer.
The Android development stack evolved this way :
Basics tools : Text editor, SDK tools
First IDE : Eclipse with ADT plugin (can run your program from an IDE)
Industrialisation phase : Eclipse ADT + Maven (dependencies management, building process management...)
Coming phase : Android Studio (IntelliJ based) + Gradle (you can compare Gradle to Maven, but this is another discussion)
I think that other answers will give you personnal points of view about Eclipse vs Android Studio, Maven vs Gradle, etc... which is a really personnal choice ;)
My development stack for Android :
IntelliJ 14
Maven
Android SDK
plus my own OSS Framework to ease the pain of Android for a Java EE developer
Reasons:
IntelliJ is the best available IDE imo
Maven is pretty mature
The plugin has become useable
The workspace integration Maven -> IntelliJ is working great (both, using maven builds and deriving IDE builds from maven)
If Android Studio (which is in great parts IntelliJ) has become slow, it come due to the gradle stuff. I had a large scale project based on gradle and made these experiences :
Slow, Slower, gradle (up to 2GB memor consumption for building an app)
Xml is horrible, but gradle dsl is imo even worse
Switching to gradle 2.1 broke the predicate logic (e.g. formerly working project.hasProperty("foo") && property.ext.foo.equals("bar") does not work any more, this must not happen during a MINOR release
Compared with maven's xml hell, gradle leaves a callow, unmature impression on me, especially building with gradle is hell of a slow job compared with maven.
But - and this is my true oppionion - if gradle is pushed by google and gradleware, it definitely has the potential to become the next generation building tool, although I doubt that the flexibility in gradle will ever lead to a proper IDE workspace build derivation. From my point of view, the choice for gradle over maven done by google happened in a too early state.
just my two cents.
PS: Try tuning the memory settings. Give more memory to IDEA (e.g. 2GB in a 64bit enviroment). My experience with IntelliJ is, that the default mem settings are too small. You can find it in $InstallDir/bin/idea.exe.vmoptions resp. $InstallDir/bin/idea64.exe.vmoptions
EDIT: This is not intended to be gradle bashing. Gradle has large potentials indeed. This post reflects my experiences during my last project basing on gradle (non-Android). For beginners gradle might be the better choice since it is a lot easier than maven.
Im looking for a way to migrate my project from Eclipse+ADT plugin to Android Studio.
Is there any tutorial for this ? or i can just open the project normally in Android Studio?
plus i want to add my project to gradle in andorid studio.
also there is Caution in google site for using "early access preview" product.
is there any cons or pros for this migration ?
or should i stick to eclipse?
the project im building is getting bigger and bigger and its kinda hard to open it in eclipse(slow loading). even the clean process takes about 10-15 second.
Is it Worse or worst to do this procedure?
1 - Android for .NET Developers: 1 Getting Started
2 - Android for .NET Developers: 2 Building Apps With Android Studio
3 - Android for .NET Developers: 3 Adopting The Android Mindset
4 - Android for .NET Developers: 4 Understanding The Android Platform
At Pluralsight above 4 is a series of tutorials. All these four tutorials use Android Studio. And during these tutorials instructor explains about many features of Android Studio.
If you're using Android Studio 0.4.2 or later, the best way to import an Eclipse project is to import it into Android Studio; it will make a copy of the project, rearrange its directory structure to something more suitable for Gradle-based projects, and set up the Gradle build files for you.
There is documentation that recommends that you export your project from Eclipse to a Gradle-based export. That documentation is based on older versions of Android Studio not having direct import, and the documentation is out of date. What's more, that export specifies old versions of the Android Gradle plugin in its export, which you'd need to fix up manually. For those reasons it's better to use the new method of direct import.
I wonder if there is any difference between using the Android Studio, Google offer to use, and use the IntelliJ Base IDE, and install the Android plugin?
Would it effect the project and module handling?
Would it effect facets?
I've been using IntelliJ IDEA 12 for Android projects for a long time. Android studio has a lot of beneficial additional Android integration, such as:
Inline Lint API checks
Drawable and string previews
Better layout editor
Built in Gradle support
Better DDMS integration
But you can certainly just use the community edition of IntelliJ 12 for Android projects, and for production projects, I would say it's preferable at this time until Android Studio stabilizes. Also, I believe IntelliJ 13 will essentially include all of the Android functionality that Android Studio does, from what I've heard.
This is useful FAQs about Android Studio vs Android Plugin in IntelliJ IDEA.
It is clear to me that
The EAP (Early Access Preview) of IntelliJ IDEA 13, which includes all of the Android Studio features except for the redesigned new project wizard and the App Engine cloud endpoints integration, is available now.
http://blog.jetbrains.com/idea/2013/05/intellij-idea-and-android-studio-faq/
As of today, Android studio actually functions, so I guess this would be my immediate solution. plus I'm not even sure the Android plugin would support all the features as Android studio will, and that there would not be any conflicts... better safe then sorry.
I am building a project under netbeans with a lot of preprocessing instructions. Netbeans handle that pretty well but unfortunately it is not very well supported as an IDE for blackberry and android.
So the idea behind this question is to import the project into eclipse in order to get the new features of every plugin and ease the development. I already found a pretty nice solution for handling preprocessing instructions with Antenna, but I would like to know how to handle the multiple facets of the project : an android project with ADT, a blackberry project with its plugin and finally a J2ME project as well. My goal is to taking advantage of the best plugins eclipse has to offer.
(And the project compiles with ant, so no real problem on this side).
Regards,
Stéphane
Well, you would have to create a separate project for each Android, Blackberry etc in the same workspace, then you would have to define the logical dependency between those projects. So if Project A is dependent on Project B, right-click on Project A in the project tree then Properties > Java Build Path > Projects and add the Project B to the list of projects Project A depends on.
This will allow you to work on Project B as if it was a stand alone project and you and work on Project A as if Project B was a part of it.
You can do this with any number of projects.
Regards,
get BB eclipse plugin from Blackberry site
install Android ADT manager from developer.android
install j2me wireless toolkit
create all project separately into same work space
use relative sdk for build path
after creating project you can also copy your source files to your project n file system, you can defile project dependency as Ali said
i reccomend to disable pre-processing, if you are using ant to build, just disabele it from windows > preference
My Suggestion to you is build your project in HTML5.If you are targeting the android as well as Blackberry .I do not Know How you will do it but It will be really easy to transform the the application of Blackberry to Android.
You have to install the BlackBerry plugin from the RIM site and it is a huge download that includes Eclipse itself. Then you can add the Android plugin via the Eclipse "Install New Software" menu.
I personally did it on my home machine and here is how How I had done
First install the the Eclipse plugin provided on blackberry developer site
Next install the android in same eclipse from Android developer site.
And voilla you are ready for android and blackberry development on single eclipse. I dont know about J2ME bcoz I no longer works on it but I think the plugin for Eclipse will do the work
This may not be quite what you're looking for but perhaps use Ant to do the builds, packaging etc. That makes it easier to support multiple platforms, set preprocessor macros etc. So the IDE would be used for mostly editing. Note that on BB you can have the IDE refer to the .jar thus resolving dependencies.
I had faced a similar issue. I installed Android first and was working on Google maps project .Since I shifted to Blackberry for a while, when i tried installing that plug-in,it did not accept it. Later after much research I found out that the Emulator for android was supporting Maps which inturn does not support installation of BlackBerry. Pretty weird. Like ber444 mentioned, BB plugin is a huge download file of 402 MB which consists of eclipse 3.5 support.
I was working on Ganneymede for android and installed indigo for BB but its not supported