When HN users recommended it
1 HN user recommended this in 2014, in one comment.
20072026
Each tall tick is one HN user's first recommendation. A short tick is the same user again. Click a tick to jump to the comment.
1 HN user recommended this in 2014, in one comment.
Each tall tick is one HN user's first recommendation. A short tick is the same user again. Click a tick to jump to the comment.
Similar to "bergie", I have used Terminal IDE on my 2nd gen Nexus 7 to do some exploratory work programming Android.
It's doable, and battery life is quite good, but having an IDE on a PC to work on the screen layout XML file helps. Also, the Android API documentation layout sucks, which makes it harder to look things up. Auto-complete in a real IDE also helps compensate for how bad the online documentation for the API is.
If it was up to me, the Android documentation would be better, and an API to programmatically set up the screen layout would be readily accessible.
For all of Java's faults, I like how compact the online javadoc is for the runtime library, compared to the crap layout with mandatory frames that Android API uses (or MS .NET, for that matter).
I used "Terminal IDE" for the environment: https://play.google.com/store/apps/details?id=com.spartacusr...
An example Android program to make a "D Pad" to move a circle around on the screen (written using above): https://github.com/roboprog/dpad
I use a bluetooth mouse and keyboard. The keyboard has exactly the same layout as my Mac Pro: http://www.amazon.com/gp/product/B00E1MRYK2/ref=oh_aui_detai...