KUAL: Kindle Unified Application Launcher (v2.7)

[NiLuJe]

@twobob: That works fine for a script, or a command, but, like ixtab said, for an application, it's not really applicable or recommended (eating ALL THE RAM!), especially if the target application is a Kindlet.

Depending on what the target application does, one could potentially try to watch the logs/listen for a specific event to catch its exit and restore the previous state, but that's hackish, potentially unreliable, and out of scope for KUAL.

@nasser: Yeah, I use it extensively in my stuff, but that's because I only launch a quick command, or a very short-term script (a couple of seconds at most) with it.

[twobob]

no worries.

Note that it is wrapped in ""

[twobob]

Originally Posted by NiLuJe

@twobob: That works fine for a script, or a command, but, like ixtab said, for an application, it's not really applicable, especially if the target application is a Kindlet.

Depending on what the target application does, one could potentially try to watch the logs/listen to a specific event to catch it's exit and restore the previous state, but that's hackish, potentially unreliable, and out of scope for KUAL.

Agreed.

I used it on a gtk application "9 mens morris"

what niljue said "YMMV"

[nasser]

Originally Posted by nasser

...
Will try out adding it to the other buttons..

Works ok for:
1. Frotz
2. Leafpad
3. kterm
4. KindleExplorer
5. gtkmines
6. Draw

Kual is now really Kool(er)..

thanks again.. twobob..

[twobob]

Originally Posted by nasser

Works ok for:
1. Frotz
2. Leafpad
3. kterm
4. KindleExplorer
5. gtkmines
6. Draw

Kual is now really Kool(er)..

thanks again.. twobob..

Yeah pretty much the gtk stuff.

What the boys said is spot on though. Just so you know.

[nasser]

Originally Posted by twobob

Yeah pretty much the gtk stuff.

What the boys said is spot on though. Just so you know.

Yes.. noted..

As long as the app run by the button doesn't run out of RAM..

[nasser]

Originally Posted by nasser

.....
As long as the app run by the button doesn't run out of RAM..

Tried running "free" command in kterm with and without return to kual entry in kterm's menu.json file.. but no clear result.. the difference in memory is not much..

[twobob]

yeah.

not a great deal I wouldn't imagine.

It's just such a small RAM every little helps.

[ixtab]

Originally Posted by nasser

Yes.. noted..

As long as the app run by the button doesn't run out of RAM..

No... it's that, but not only that. If the command that is run is itself, or transitively results in the execution of, a Kindlet, KUAL will inevitably get killed along the way.

KUAL is a replacement for yifanlu's GUI Launcher, which closely matches the semantics of the well-known Windows "Start Menu": Once your desired action was started, the launcher disappears. That is by design (and given the limitations of the Kindle, it is the only feasible least common denominator).

You may be able to work around the original purpose of it by modifying the extension definitions to your liking -- but don't expect KUAL to be persistent. Ever.

[twobob]

I pulled down all the latest tweakings Ixtab.

~/GIT/kindlelauncher $ git pull
remote: Counting objects: 568, done.
remote: Compressing objects: 100% (308/308), done.
remote: Total 523 (delta 220), reused 0 (delta 0)
Receiving objects: 100% (523/523), 77.16 KiB, done.
Resolving deltas: 100% (220/220), completed with 18 local objects.
From https://bitbucket.org/ixtab/kindlelauncher
980c560..2a41fed master -> origin/master
9ee6ba1..8b1aec5 commented -> origin/commented
* [new branch] niluje-sucks-at-java -> origin/niluje-sucks-at-java
Updating 980c560..2a41fed
Fast-forward
.../ixtab/kindlelauncher/LauncherKindlet.java | 290 +--
.../ixtab/kindlelauncher/resources/KualEntry.java | 63 +-
.../ixtab/kindlelauncher/resources/KualLog.java | 14 +-
.../kindlelauncher/resources/MailboxProcessor.java | 2 +-
.../kindlelauncher/resources/aloop/CHANGELOG.txt | 35 +
.../ixtab/kindlelauncher/resources/aloop/KUAL.cfg | 27 +-
.../resources/aloop/extensions-kindle-list.txt | 10 +-
.../resources/aloop/test-tree-kindle.tgz | Bin 4069 -> 8836 bytes
.../kindlelauncher/resources/aloop/tool/strip.awk | 79 +-
.../ixtab/kindlelauncher/resources/parse.awk | 1890 ++++++++++++--------
.../ixtab/kindlelauncher/ui/v1/KUIAdapter.java | 2 +-
.../ixtab/kindlelauncher/ui/v1/KualLabel.java | 109 ++
12 files changed, 1499 insertions(+), 1022 deletions(-)
create mode 100755 src/com/mobileread/ixtab/kindlelauncher/ui/v1/KualLabel.java

Seems like a lot has happened.

Will attempt to get up to speed

[ixtab]

Originally Posted by twobob

I pulled down all the latest tweakings Ixtab.


Seems like a lot has happened.

Will attempt to get up to speed

Hehe... yeah. That's what you get from giving random strangers commit access

Just kidding, of course. What NiLuJe did is absolutely awesome, fixes a bunch of issues, and should be committed to trunk right away (nope, not kidding this time).

@NiLuJe: do you mind merging your branch back in?

[twobob]

okay.

Will do.

And then test.

And then release.

Yeah?

Much obliged you guys. Super heroism.

[NiLuJe]

@ixtab & @twobob: stepk mentioned in the issue tracker he planned to review the changes a bit before merging to master, and that he would be back sometime in August.

That said, I'm all for a merge & release, of course, but I don't want to step on anyone's toes... .

Technically, the part that worries me the most is the ugly way I handled counting the extra quit/toRoot button at the end of a page, but the rest should be trivial/sane enough .

When you do release, don't hesitate to ping me so that I can sum up my changes for the changelog [EDIT: done]

[stepk]

@NiLuJe, please go ahead and merge in your changes. I don't have 'nough time to review them and you certainly don't need my blessing whatsoever. I'm certain KUAL will shine with your fixes and extensions merged in. I'm looking forward to the next official build
Oh, https://wiki.mobileread.com/wiki/KUAL_What's_New might need updating...

[NiLuJe]

@stepk: Okidoki . Done & done .