Provide UI to start existing emulators

[vogella]

I don't think we need the option to create emulators in Dartboard but it would be nice to be able to start existing ones.

May Andmore has an UI which we could adapt? I go and ask on their mailing list.

[cybersearch2]

Would you like my assistance? Just over a year ago I published a proof-of-concept of the successor to Andmore, which I called Andworx. The project at that stage was capable of importing an example project at the most recent stable API level, building it, launching it on any available connected device and, as a bonus, also able to debug the application.

That means I can confidently provide UI to start the Android SDK emulator. This can provide a good starting point for including other emulators.

By the way, I am still progressing with Andworx, but it is now running as a pure RCP application. The concept is Andworx as build server + the most useful tools of the original ADT.
The best thing is that it is all done with OSGI bundles - no Gradle!

[jonas-jonas]

Yes! This sounds amazing.

We will be speaking about the general structure of the project tomorrow (28.01.) and I'll update you on the progress/let you know when the refactoring efforts of the wip-flutter branch have been merged (should also be tomorrow). After that we would be happy about any assistance on the project, especially in these parts of the architecture (emulators, android specific stuff).

[jonas-jonas]

I just merged the wip-flutter branch. We have done a lot of refactoring and some cleaning up.

If you @cybersearch2 would still like to work on this, or anything else (#169 or #164) feel free to open a PR.

[vogella]

Andrew, would be great to have you on board.

The project lead @cybersearch2 of Andmore is very welcome.

With Flutter we actually have a real change to bring back mobile development to Eclipse. Flutter SDK supports the LSP protocol and therefore we may be able to leverage a lot of existing functionality. Also the Dartcode project seems to support this effort.

[cybersearch2]

Jonas and Lars

Thanks for your welcome into the Dartboard project. This is a great opportunity for me to catch up on what is happening on the Eclipse IDE. For example, yesterday I got up to speed on Declarative Services, which gets a big tick from me. I envisage a service will be required for each supported SDK to handle the check for intall status, and in the case of Android, start the ADB to monitor devices.

Regarding LSP protocol, I have high expectations that we can move towards modular IDE components just like we now have modular code components = OSGI bundles.

[cybersearch2]

I have 2 concerns about including the Android Emulator in the Dartboard project. The first concern is the potential impact of adding Android dependencies to the project? I have just done some research and found the damage comes in at 37 jars at 9.3 Mb. However, the jar count is likely be reduced to some extent by substituting third-party libraries available as plugins.

My other concern is how easy is it to get a large number of third-party libraries through the CQ process? When I was working on Andmore, David Carver was always anxious to start early with CQs when preparing a release as getting through the CQ process was likely to delay it.

Should I proceed with Android Emulator project, and if so, can I get assistance to get a large number of third-party libraries through the CQ process?

[vogella]

I think we should only call the flutter API to create the emulator. We should not include the Android UI into Flutter. Let's stay as light-weight as possible Andrew Bowley <notifications@github.com> schrieb am Sa., 8. Feb. 2020, 07:39:

…

I have 2 concerns about including the Android Emulator in the Dartboard project. The first concern is the potential impact of adding Android dependencies to the project? I have just done some research and found the damage comes in at 37 jars at 9.3 Mb. However, the jar count is likely be reduced to some extent by substituting third-party libraries available as plugins. My other concern is how easy is it to get a large number of third-party libraries through the CQ process? When I was working on Andmore, David Carver was always anxious to start early with CQs when preparing a release as getting through the CQ process was likely to delay it. Should I proceed with Android Emulator project, and if so, can I get assistance to get a large number of third-party libraries through the CQ process? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#151>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABCFBTL2LWSSSU76MIVSLLRBZHTVANCNFSM4JMXZWFQ> .