Android SDK workspace template

environment

#21

@jerteach my workspace is here: https://ide.c9.io/amanuel2/androidcheck#openfile-README.md . Im still not an android programmer, but plan on bieng later. So this plugin will help a lot :smiley: .


#22

I requested collaboration on that workspace. It is a fairly easy fix and I will put it on the github site.

basically you need ownership of the android sdk folder so that sudo is not needed. I will try to fix the github site.


#23

Ok i will allow Collab with pleasure @jerteach . Sorry but for now i dont know anything about android development. Im clueless :smiley: . I have one question though, when this is put officially on cloud9, would thier be like an emulator, as it is in Android Studio?


#24

I also put this on the issue here: https://github.com/hpssjellis/bash-android-cloud9/issues/1 . Its content is:

Alright so i set it up in cloud9ide. Then when i click on index.html to run it i get this page:

Then after when i click that link to set up android i get this:


#25

Yes. Thanks. That one I did not know about. It is simply a broken html link, which I have now fixed (HellowAnt was one folder abouve www, not inside www). Still working on the other issue.


#26

Yes but it is still not working… All the four links you provided gives 404.


#27

Yes. Strange. Things are now working for my Dockerfile, but are not working here. May take a while to fix it. I am starting with a fresh build from the github site at https://github.com/hpssjellis/bash-android-cloud9.git

P.S. I assume you know php and javascript, why not look into Phonegap instead of Android. With phonegap you can make iOS and Android Apps from webpages. Check out my video at

It is really amazing and I use cloud9 When your app works then just zip it hava a main index.html in the zipped folder and load it as your one private App to https://build.phonegap.com/ which makes your Android App for you.


#28

Yea but phonegap is slow… I already tried it. And Javascript is getting boring.


#29

funny :slight_smile:


#30

Looks like openjdk-7-jdk was not installing. I have included

sudo apt-get update

in the main setup.sh, which may improve things.

I have messed around so much with your workspace that I think it is broken.


#31

I shared a workspace with you called bash-android04 It fully works, the .apk files download to my phone an Android 4.4 and they run. Very boring hello world text only app.

The only issue I now have to work on is that both the Ant and Gradle .apk’s have the same App name, which makes it hard to install both at the same time. This should not be hard to fix, but will also be an issue on my dockerfile.

By the way it does not install an emulator. I really do not like them. I just want to know that the app works on my phone and it takes about 30 seconds and four clicks to install an App over the internet.


#32

Ok @jerteach can you give me the link you shared? And also im not quite sure about android development on Cloud9 as you dont have a view of the result(Or Emulator)… So ill probably wait but for those in my group who are having hard time installing android studio your solution should work!


#33

https://ide.c9.io/jerteach/bash-android04#openfile-README.md is the workspace, but I have already changed the github site so it is now old.

If you have an android phone, it is way better than an emulator, but if you don’t have the phone the emulator is your only bet. I do not think an emulator would work well using an online service, but maybe it can.

Anyway. Thanks for your help spotting some of the mistakes with my site.


#34

@bradydowling @justin8 @nikolai @fjakobs @mutahhir @harutyun

I have resumed working really hard on the Android-SDK Dockerfile. It is now fully working but I want to test it out with my students and tidy it up a bit, I have two questions. Could someone please take a stab at answering them.

  1. I have a very sweet method for testing the Dockerfile on a local install of Cloud9 using two bash files (One on the local machine and one in the workspace repository). Any suggestion’s for where to write about it. Should I put it here or make a new topic called: “How to Install Cloud9 Locally” or attach it to Nikolai’s post at https://c9.io/blog/cloud9-template-days/

  2. Does it make sense to have the workspace README.md file linked to a HELP repository on github such as https://github.com/hpssjellis/online-android-sdk-cloud9-help. The repository would allow a bit more of a dynamic way for the community to help with Android development issues about running Ant or Gradle and especially around porting Android Studio projects to Cloud9 (This can be done but as the projects get more complex, the process gets more complex!). Presently the help messages are hard-coded into the workspace and will be very difficult to change or update.


#35

I dont have a smartphone actually… But i do have a bluestacks android emulator… Maybe that can help! Anways, ima check if it works now!


#36

Never heard of it. Found this webpage about Bluestacks and Andy

with downloads at

Bluestacks http://www.bluestacks.com/

Andy http://andyroid.net/


#37

How have you been doing testing on Cloud9? I found this resource about Linux Android emulators but perhaps the standard emulator from Google will work if you use the desktop display plugin in Cloud9 (which I’ve heard good things about but I’ve never used it personally).

As for the PR you mentioned, I pinged Justin about that so let me see what he says about it.


#38

I believe both of those would require an X server to render on. I don’t think bluestacks has a linux release. Andyroid has a linux release in alpha but not publicly available yet.

I would also be wary of the licensing on a lot of the android emulators. Most of them are not free outside of personal use.

What are the details of your testing method with a script inside and outside of the container? We already have one we use for our deployments, which is where the check-environment script comes in; that’s our in-container one.

You would need at least the basics in the workspace readme so that users don’t have to click through to another page to actually get started; but you could link to it for more detailed documentation.

Possibly a better way might be to have the documentation separate that is pulled in at build time? But I would prefer it in the repository so it doesn’t have an external dependency just for documentation.


#39

@bradydowling

Thanks @justin8 I agree on all points.

  1. I am not really interested in the emulators, I just install the apps on my phone.

  2. My scripts are probably similar to the ones you use to deploy, just wondering if anyone else would like to see them to help with local testing of Dockerfiles?

  3. The repository for help information is a better idea than linking help at build time, since an old workspace could then still have new and relevant help information.

Which brings up a new question. Should Cloud9 host the Android-SDK help github repository and I make pull requests to it (bit of a pain for you guys) or should I host the Android-SDK help repository and people make pull requests to me? I guess a third option could be to link to a topic (or group of topics) on this community site.

P.S. I just used the Android-SDK workspace to grab a github Ant Android example https://github.com/sitepoint-editors/TodoList and got it fully working and onto my phone in under 2 minutes!


#40

The only issue then is if you update a tool or some requirement changes, you’re only giving people instructions for the latest version. If they open an old workspace and it says to run ‘foo’ but ‘foo’ only exists in the latest version it would be problematic. That’s why I would like to see a basic version that is version controlled with the image and links out to additional information.

I’m not sure on ownership of the repository for the help at this time. I believe it would be fine hosted on your account. Worst case if you delete it we can restore it to a fork on our repo and continue, so I wouldn’t worry too much about that.

2 minutes sounds awesome btw, it’ll be good to see it in action.