KUAL: Kindle Unified Application Launcher (v2.7)

[knc1]

Originally Posted by DuckieTigger

Are you using 5.1.2 or lower? 5.3.1 is for PW only.

Maybe we need to draw a diagram for this member?

The interleaved version numbering Amazon is using for the two devices is causing a lot of confusion.

[April_7th]

Hey guys..
I'm on FW 5.3.2, I do have Jailbreak and the Kindlet Jailbreak..
I Put KindleLauncher-2.0.azw2 in documents folder and run it on my KT, with no problems.. But none of the listed extentions work.. when i press them, launcher just turns off..
Am I missing something? English is not my native language + I'm the new Kindle user and I might missunderstood something on the description..

[twobob]

Originally Posted by April_7th

Hey guys..
I'm on FW 5.3.2, I do have Jailbreak and the Kindlet Jailbreak..
I Put KindleLauncher-2.0.azw2 in documents folder and run it on my KT, with no problems.. But none of the listed extentions work.. when i press them, launcher just turns off..
Am I missing something? English is not my native language + I'm the new Kindle user and I might missunderstood something on the description..

Some logging would be helpful.

will look at this very soon now.

[April_7th]

Originally Posted by twobob

Some logging would be helpful.

will look at this very soon now.

I don't know how to do logging

[silver18]

I can confirm that Komic v2.1 doesn't work on 5.3.2 firmware.
This is not related to the unified launcher (it works really fine on 5.1.2 firmware with the same launcher)!

[twobob]

Originally Posted by April_7th

I don't know how to do logging

No. I mean like - WE need to provide better error output.

Notification of missing required elements etc.

[April_7th]

Originally Posted by twobob

No. I mean like - WE need to provide better error output.

Notification of missing required elements etc.

Got it

Forgot to say - Thank you for this great job..

[silver18]

Thanks a lot for v0.3!
Just a small thing: with the new parsing engine, extensions with more than one entry are scattered all over the list based on the first letter of the name.
This can be avoided adding the name of the extension before the name of the script.
I.E:

Komic run Komic
Komic Decompress CBZs and CBRs
Komic rename files

etc...

[stepk]

Originally Posted by silver18

Just a small thing: with the new parsing engine, extensions with more than one entry are scattered all over the list based on the first letter of the name.
This can be avoided adding the name of the extension before the name of the script.
I.E:

Komic run Komic
Komic Decompress CBZs and CBRs
Komic rename files

etc...

Thank you. The parsing engine can do that already, but it isn't currently enabled in the GUI. I think ixtab and twobob have a plan

[twobob]

[root@kindle root]# ./parse.sh
./parse.sh: line 67: syntax error: Bad substitution

on a kindle 3. Can we make this compliant on all devices?

[twobob]

[root@kindle root]# busybox sh ./parse.sh

BEGIN Run Grayed Installbin/start_update.sh
BEGIN USBNETWORKINGbin/usbnetwork.sh
PREVENT ScreenSaversbin/ssprevent.sh
ALLOW ScreenSaver bin/ssallow.sh
411 Page (Other Info)bin/411.sh 411

I "fixed" this by pointing to a more modern sh version that I had built for busybox...

but it would be nice to not have to bundle that just for the sh support.

if you REALLY felt it was worth it... possibly we should just go ahead and include BASH compiled for all kindles but I would prefer a native solution as this feels like overkill.



the current error is:

Line 67: if [[ \" = ${x:0:1} ]]; then

probably doesn't like x:y:z ?

Happy to test. the sh version on the older busybox is documented on the thread i linked. much obliged.

since [root@kindle root]# busybox sh ./parse.sh does no harm on devices that Dont have a multiple busybox installation and it Does allow for multiple busyboxes to bypass to horrid command line grabbing I may just shove that command in by default for now.

[DuckieTigger]

@twobob:
It might not like the [[ ]], that is something out of bash, barebone ash does not do that. You'd have to look at the busybox documentation to see which shell is implemented. Or you could try splitting the one liner up to expand to get rid of the inside of [[ ... ]].

[twobob]

http://landley.net/mantis/mantis-2924.html

The shell construct:

${varname:begin:end} does not produce the substring of $varname starting at begin and going to end.

example:

#!/bin/ash

mystr="This is a string"
echo $mystr
mysubstr=${mystr:0:4}
echo $mysubstr
#end of example

Expected output:
This is a string
This

Actual output:
This is a string
./testscript: line 5: syntax error: Bad substitution

thought it looked familiar

so

if [[ \" = ${x:0:1} ]]; then

is just trimming the first char for a test? perhaps I can bodge that another way

EDIT:

if [[ \" = $( `echo $x | awk '{print substr ($0, 0, 1)}'` ) ]]; then

maybe??

[knc1]

Or compare it using a case statement with a \"* case?
Might work. Might not.

[stepk]

Originally Posted by twobob

[root@kindle root]# ./parse.sh
./parse.sh: line 67: syntax error: Bad substitution

on a kindle 3. Can we make this compliant on all devices?

Please download update from #140 and let me know if that helps.
Is there any way my KT could run the K3 busybox binary, if you found a way to rip it from a K3? I don't have a K3 to test this script on.