Re: [ide-dev] News about Android Studio

[Lars Vogel <lars.vogel@xxxxxxxxxxx>]

Hi Mickael,

I use Android Studio on a regular basis and it seems to me that they
moving more and more functionality to Gradle. AFAIK the target is
still to stay as much independent as possible from the IDE and
delegate as much as possible to the build system.

Once the Gradle tooling has been extended to support Android, we
(Eclipse) should be a good alternative again for Android development.
Android Studio feel to us and our customers relatively buggy and slow.

Unfortunately the Eclipse Gradle project seems currently slow
(https://github.com/eclipse/buildship/commits/master), not sure if
they planning to work on Android support in the near future.

Best regards, Lars

On Mon, Nov 30, 2015 at 3:29 PM, Mickael Istria <mistria@xxxxxxxxxx> wrote:
> Android Studio recently released a new version. This good video covers some
> nice features https://www.youtube.com/watch?v=Y2GC6P5hPeA#t=770 . Nothing
> very new, no big uber-powerful feature changing the game. This video is also
> a good opportunity to see the completion, quick-fixes and templates of IDEA
> in action. The features I find the most interesting are all already logged
> in Bugzilla and were already discussed there, so I won't get into details.
> There performance tools seem very good. It's IMO something we're missing in
> Eclipse IDE since TPTP was abandonned. As far as I remember, none of the
> main Eclipse IDE packages provide a way to profile or monitor applications
> under development easily. That's a major missing feature compared to Android
> Studio. However, it simply seems like it's not one our community wishes to
> invest into, probably because it's still not a top-priority in most
> end-users projects.
> However, my lack of general experience with Gradle nor C++ make me unable to
> evaluate what's good/bad in Android Studio compared to Eclipse BuildShip or
> CDT.
>
> For Android, it's interesting how they answer to the 1st question, ie most
> of the tools about Android development will move only to the IDE. It seems
> to mean that the SDK and IDE are going to be merged at some point, and that
> the IDE will be the single entry-point for development. That means that it's
> a lot of thing to duplicate in Eclipse IDE if most other tools are going to
> be dropped.
> Another interesting one is about sharing project settings, for the project
> specific configuration such as the "structural replace". It's actually an
> important question when you add into the IDE some checks that are not
> possible to "externalize" in the build or in independent tools. They do
> encourage to share the project specific files, like we usually do for
> Eclipse IDE:
> http://www.slideshare.net/AurelienPupier/committing-ide-meta-files-misconceptions-misunderstandings-and-solutions
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat
> My blog - My Tweets
>
> _______________________________________________
> ide-dev mailing list
> ide-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/ide-dev



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (032) 221739404, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com