General => Feedback => Topic started by: EgonOlsen on December 10, 2014, 11:25:11 pm

Title: Android Studio...
Post by: EgonOlsen on December 10, 2014, 11:25:11 pm
...now that Android Studio (https://developer.android.com/sdk/index.html (https://developer.android.com/sdk/index.html)) is the new "official" IDE and the Eclipse-Plugin won't be developed any further, i tried to setup my RPG development environment in Android Studio. Here's the short version:


The long version is, that Android Studio is made for Android. It's not really made for developing and running desktop Java applications (and that includes, as sad as it is, libraries that are simple Java libraries and not for Android only). You can create and run Java applications, but it has it's limits. Android Studio forces you to use Gradle and adds an Android plugin to it, which doesn't seem to play well when mixed with normal Java apps.
I managed to setup everything in about 8h of trial and error except that i wasn't able to run the desktop version of the RPG. It compiled fine but when trying to run it, Gradle was suddenly unable to find the required libraries. 8h are enough...so i gave up on it and will continue to use Eclipse for the time being. Apart from that, it eats memory like crazy, is much slower than Eclipse and has various funny UI bugs.
I actually hate it...i think...
Title: Re: Android Studio...
Post by: Irony on December 10, 2014, 11:35:17 pm
That sounds really bad. Thank you for the warning.
Title: Re: Android Studio...
Post by: EgonOlsen on December 11, 2014, 07:45:55 am
I think it's ok (and maybe even has some advantages over Eclipse) if you are using it solely for Android development. But if you start combining Android and non-Android Java in one project, hell breaks loose. My RPG setup contains three normal java modules and 2 Android ones and these don't mix well (in fact, they don't mix at all and it required some additional Gradle configuration to make them work together at least a little bit).
A huge part of the problem is that you are forced by Android Sudio to use Gradle and that implies some restrictions. If you could setup it as "normal" IntelliJ modules, which i managed to do by accident a few times, things are a whole lot easier. But Android Studio won't let you, at least not reliable.
Using it to develop an Android app that includes jPCT-AE as a jar works actually fine (it still uses 2GB of memory for this though).
Title: Re: Android Studio...
Post by: Irony on December 11, 2014, 01:32:10 pm
Have you seen any advantages over Eclipse?
Title: Re: Android Studio...
Post by: EgonOlsen on December 11, 2014, 08:02:23 pm
It might be easier for beginners to get into and setup is simpler. I also liked the way in which it deals with changes to the files and directories of a module that happen behind its back. It instantly recognizes them (unlike Eclipse) and tries to do the "right thing", i.e. it tries to identify source and resource folders and is pretty successful with that.
Title: Re: Android Studio...
Post by: PaniX on March 22, 2015, 02:15:52 pm

Started Android programming again, tried Android Studio...
Gradle needs 3min to compile a simple Hello World - without upload to mobile phone. In Terminal.
5 seconds in Eclipse to compile and upload to Smartphone...

Eclipse FTW :)