Quote:
Originally Posted by nasser
Will think of a suitable alternative!
And a KUAL button too may be handy. Will add that too.
|
That: "Will solve a chess problem in a text file ...." feature -
Only KUAL does not accept user input fields ....
Two choices that I can think of :
Have a button that uses a fixed filename in visible USB storage (seen as /mnt/us from KUAL scripts); or
Use our 'extended' search bar command - that can take arguments.
or single purpose the
;log runme
;log custom
extensions of the search bar.
See a copy of the extension script in:
*/mkk/dispatch.sh
Hmm...
dispatch.sh does not, currently, pass arguments or handle anything other than the fixed filename 'RUNME.sh' but those things could be fixed.
(Its distribution home is part of the 'hotfix' package, and it was done in a hurry, late at night, so it is about as simple as a dispatcher can get).
But the only part of it in public use is the:
;log mrpi
so as long as that continues to work as the current users expect, that dispatcher is open to change.
Note: the copy */mkk/dispatch.sh is just that, a backup copy, not the one actually executed, that one is installed by the 'hotfix' bridge code into /var/local (or somewhere, I would have to read the hotfix install script).
Edit:
Hmm...
The searchbar extension is only for touch screen devices....
All touch screen devices have Lua and the Lua-Json library pre-installed....
It would not be too much trouble to make that dispatcher read a directory of extensions, similar to how KUAL reads */extensions/name/menu.json files.
That way we would not have to re-build the 'hotfix' package everytime someone wanted to extend the ;log command. The
;log mrpi
command extension could remain hardcoded in the new dispatcher so we do not have an unexpected behavior change.
Note: The extension of the ;log search bar command is one of those things that are bridged across Amazon updates.