Pages

Tuesday, 25 October 2011

My Android-on-Android workflow so far

With the release of the first of my SL4A scripts, I thought it beneficial to document how I got here and what I'm using.
I'm using a lot of existing Android applications and gluing them all together, which is Android's biggest strength.
Firstly, the core applications are the programming environment.
SL4A is the scripting environment and text editor.
Py4A is the Python interpreter.
I'm using Github which likes Markdown documentation, so for this I use Epistle as a simple WYSIWYG editor.
I'm using IconReader2 in my layouts to use built-in Android icons in my scripts.
I'm using Hacker's Keyboard for typing. It gives a full keyboard including the Python-critical Tab key. And it fits okay on my 7-inch Samsung Galaxy Tab.
And of course I'm using the Blogger app to make these announcements on my blog.
I use the ASTRO file manager for those duties, including its ability to create and modify zip files that I use for distribution and to enable the Android browser to upload any file (though seemingly except for zip files).
I tried using the (Google) Docs app for uploading but I found its multiple versions support lacking and a little unreliable.
In stark contrast the Box.net app supports both of these including in-app sharing. (At this point I cheated and used my iPhone to sign up for Box because you'll get 50GB this way right now.)
I then use the Urly app to make short URLs from the Box.net ones.
And my Samsung Galaxy Tab is powered by Overcome 7 Series Gingerbread.
Then I use my Gitter script just released to update my Git repository, a script I designed with the help of the UI Builder I've made, which is soon-to-be-released.
All of the above have my recommendation.