[DuckieTigger]

Random thought that just struck me about standardization: Provide a ways for dependencies. Like most package tools do, only not completely automatic. KUAL extensions say what they need, and what they provide. If you start an extension, that cannot find what it needs, a popup comes up and says: MEEEP, cannot run, depend on having a keyboard, but none found. On DX and KK nothing needs installed extra, since they kind of have a keyboard build in. On other Kindles you only need to have ANY extension that says: I provide keyboard - and lets KUAL know what to execute to embed and link it to the other extension that needs keyboard.

Example, shell script again. Imagine a shell script that goes through some files, gathers information, processes it, outputs something meaningful - think something like 411, 711 for example. For all this you will need:

- a shell that will output the result
- a keyboard to get out of there
- the extension that creates the data to be displayed

(you need all 3 to make it work, but you don't have to create all 3 parts yourself, you just have to have them all - possibly from 3 different developers / projects)

The shell provides, well, a shell that can be displayed on the Kindle. It depends on a keyboard to be able to run stand-alone. Install keyboard depending on which extension provides keyboard for your Kindle. And so on and so on. Keyboard maybe not enough, now another extension requires a custom layout for defining their own keys - now a customizable keyboard needs to be installed. On the KK or DX that could be as simple as a little display on screen that says: Play [p], Stop [s], Rewind [r] .... to know which buttons on the physicaly keyboard to push. On Touch models it could be a Touch keyboard, that sends p, s, or r key-events, but display [Play] [Stop] [Rewind] as the buttons.

Now you can start developing for any Kindle - and it does not need to be a complete application all at once. Does not need to be the program that gathers the information either, it could be a port from one Kindle to next. gtkSudoku comes to mind. That does not work on Paperwhite, but it might as well work "easily" if you only run it in part of the screen, and put a keyboard on the bottom.