Quote:
Originally Posted by stepk
Thanks, food for thought. However, I think this would be difficult to do with the current code base, due to the way the kindlet invokes the parser - one shot, control doesn't go back and forth, data is passed back in a single stream
Thread history: I learned the hard way that KUAL development likes a simple incremental path.
Q for all: is a two-level nested menu, that is no sub-sub-... menus, just sub-menu, not enough for the vast majority of kindle use cases? |
Ahhhh, I see. Is it really necessary to parse each time KUAL starts? Leave the output in temp, this way it only needs to actually parse once per reboot - or until that file gets deleted per request. The java does need more flexible handling if switching from shell script to java is undesired. If one sub-menu is easier to implement, then one should work. I can see a problem when one wishes to have sub-menus for system-tools, games, editors, ... - that uses up the one level, everything underneath would be flat.