search

MobileChromeApps / chrome-app-developer-tool

Mirror of Apache Cordova app harness
Other
202 stars 33 forks source link

Feature request: Support ARC (officially) #41

Closed kennystrawnmusic closed 9 years ago

kennystrawnmusic commented 9 years ago

The screenshot below says a whole lot. It's what happens when the Chrome App Developer Tool is sideloaded as an App Runtime for Chrome (ARC) app (used Vlad Filippov's Chrome APK Packager utility to convert it to a format that the chrome://extensions page can understand):

screenshot 2014-09-27 at 13 24 18

The only, I repeat ONLY, thing that doesn't work is the socket-binding... So, with that being said, it's probably a good idea to get the socket-binding working... and from there, put phone AND tablet versions of the ARC version of the Chrome App Developer Tool in the Web Store. Would be very useful as (an) emulator(s) for Android-targeted Chrome Apps... and once this app's integrated APK packager is finally implemented, it would provide a quick, convenient, and easy way to develop, test, export, and publish Android apps from a Chromebook without the need to use Crouton as a middleman.

mmocny commented 9 years ago

Hilarious and amazing. I was just waiting for someone to try this, but didn't expect it so soon. Did you try USB deploy?

mmocny commented 9 years ago

Wait usb doesn't make any sense :)

Too excited.

kennystrawnmusic commented 9 years ago

Also decided to package the ARC variant of App Developer Tool 0.9... just to make it easy for this project's developers to see what needs to be worked on, which is obviously the socket compatibility (or a bug that's causing the socket to not connect).

kennystrawnmusic commented 9 years ago

Mock-up describing how I personally see this feature implemented: when loaded in ARC, do not bind Port 2424 to an IP address (which likely isn't given to ARC), but to localhost instead... arcappdevtoolmock

mmocny commented 9 years ago

I still think this is hilarious and cool, but I don't see real value given that you can just run the chrome app natively on Chrome.

If you want to do android development on a chromebook, you are better off connecting a physical device, or finding a real android emulator for chromeos (not sure if one exists).

kennystrawnmusic commented 9 years ago

What the mobile CADT has that running the app natively on Chrome OS doesn't is the ability to export to an APK... and that's why I filed this request.

kennystrawnmusic commented 9 years ago

I don't know whether it's a fix that came with 0.12.0 or the use of Twerk on the Chrome OS side instead of the "ARChon Packager" app on an Android device, but the port binding issue has now been resolved.

Screenshot attached... screenshot 2015-03-24 at 21 40 46

agrieve commented 9 years ago

Very cool!