[sclug] Pi and Android app

[Graham Swallow]

((I replied to a digest - so email threading will not perfect ))

Android Tutorials can be found on YouTube
They are all irritating, but some get more done.
http://www.youtube.com/watch?v=boj0f_O3i88&list=PLGLfVvz_LVvQUjiCc8lUT9aO0GsWA4uNe

Qt5.1 promises Android, and the non-bleed release, is R.S.N.
http://blog.qt.digia.com/blog/2013/05/14/qt-5-1-beta-released/?utm_source=rss&utm_medium=rss&utm_campaign=qt-5-1-beta-released
But Android is really a JAVA+NON-X11-GUI+LIBS+RESOURCES platform

Pi uses X11 ? Which allows pretty much any development env (except
Android, .NET, W32), If you use Python, (a good choice if you never go
down an unused code path), you will have to pick a GUI: gtk or Tcl/Tk
or FL or FOX or Qt (X11 direct is possible, but only just). These have
their own XML RAD tools, like glade or (...) where you draw a screen,
built from components, add on_event() control function, and write less
code, with options of moving to C, with the RAD layout file much the
same.

All scripting languages suffer the unexpected error on unused code
path problem. Python is a very fine late-binding scripting language,
with MODULE / CLASS / FUNCTION ideas at its core.

Python's biggest disadvantages, are (1) every attribute needs a
dictionary lookup, every time, and (2) that it has allowed
feature-creep in, to its core, libraries and syntax. Lots of caveats
mean that it is no longer as simple to read, as it used to be.

Python is popular with hardware module writers,
seeking a scripting platform to write a C-module for.

Graham