KUAL: Kindle Unified Application Launcher (v2.7)

[twobob]

So I did a git pull and a build of the provisional 0.5? I get a timeout-load fail and no obvious developer/crashlog updates since the log adjustments.

Although I DO get the new log file, which is nice.

I am interested to know if I did it "right" since the stepk build I was testing didn't do this.

Will reboot my devices, strip out the extensions dir and try again.
Cheers

[stepk]

github's down ATM so I can't trace your steps. will try again later.

[stepk]

So I cloned a fresh copy, added the two required local files, and built a new awz2 file, which runs just fine on my KT. Can't test other platforms, sorry. Let me place this build on knetconnect for you...

edit: done

[twobob]

Thanks man... I'll do a diff see where I screwed up

EDIT: Nope... It's still annoyed. Good to know it wasn't something I did.

Will remove all extensions and see if I can find the culprit.

Question... Is the /mnt/us/extensions/system folder excluded from parsing?
I'll go code dive. It really should be if it isn't : )

[twobob]

hmm... Let me try that on the touch next then. It's the PW that doesn't like it.

EDIT: Nope. Crashes the touch too... Hmm... Oddness.

[stepk]

Originally Posted by twobob

Thanks man... I'll do a diff see where I screwed up

EDIT: Nope... It's still annoyed. Good to know it wasn't something I did.

Will remove all extensions and see if I can find the culprit.

Question... Is the /mnt/us/extensions/system folder excluded from parsing?
I'll go code dive. It really should be if it isn't : )

No subfolder in /mnt/us/extensions is excluded from searching for config.xml files. When a config.xml file is found to point to a xyz.json file that json file is then parsed.

[twobob]

Ah.. well.. yada/system could at some point get LARGE on some devices...

probably worth the exception

[stepk]

Searching could be optionally restricted in a couple of ways:
1. hard list of excluded folders
2. limit search to depth N
I favor #2. As a matter of fact I favor making N=1 the default behavior and adding an option to increase search depth beyond 1.
N=1 ensures faster start up time for all users - tough non-noticeable unless a user has a MEGA extensions folder. N=1 also drives menu developers to place their (possibly nested) menus at level 1 for maximum compatibility.
Any thoughts?

[twobob]

I agree with that completely. No recursive unless specified.

And maybe single exception for excluding the /extensions/system folder
(as that should probably never be parsed)

I think I may have found the other issue btw. The processes appear to still be running. (pictured) perhaps that is the cause...

[stepk]

Originally Posted by twobob

I agree with that completely. No recursive unless specified.

And maybe single exception for excluding the /extensions/system folder
(as that should probably never be parsed)

I'll see to it

I think I may have found the other issue btw. The processes appear to still be running. (pictured) perhaps that is the cause...

That would definitely be a problem. Does it happen both on the KT and PW? Looking at the PID spread I'm thinking that some of those processes were started before today.

EDIT: No, that is not the cause. It's the effect. It's started happening here too, for no apparent reason. It's actually good news, because now I have a chance to x-ray a kindle when the crash is happening.
BTW, I'm going to push a new version with the search options that we've discussed earlier today. You get both depth limit and path exclusion, with 'system' excluded by default. It does make quite a difference when /mnt/us/extensions/system exists. RSN on github, then I'll tackle this crash issue.

[twobob]

hmm could be. I will dig into it now I have noticed!

Thanks mate

EDIT: Although it makes me think of bit of "environment sanity" code would not go amiss in the future...

[stepk]

Just pushed to github "New options and default values speed up scanning /mnt/us/extensions"

[twobob]

Originally Posted by stepk

Just pushed to github "New options and default values speed up scanning /mnt/us/extensions"

nice one! still struggling to figure out if the new { runthing } >> blah/log format is failing to terminate gracefully..

Will grab a slice and test again

EDIT: Pulled. Great metrics btw!

[twobob]

I'm going to try hacking

// wrap cmd inside {} to support backgrounding multiple commands and redirecting stderr
bw.write("{ " + init + cmd + " ; } 2>>/var/tmp/KUAL.log"
	+ (background ? " &" : ""));

about and see where it gets me

EDIT: ah...

Thread group could not be destroyed - threads still alive:
Thread 1 => [Name=process reaper,ThreadGroup=Kindlet-Group-KUAL].

I was right...


I just literally "Laughed Out Loud" on the changelogs mate. 1 Septillion! HAHAHAHA. I love your changelogs, they really are fun reading. Thanks.

Gonna jump over and make a new build in 20 mins or so after I tidy up last nights manglings.

[twobob]

got the latest pull down now.

Gonna reboot, but this looks much better

EDIT: Yup. So much better.

Just that lower device navigation niggle.
I'll give my buddy a ring tomorrow see about getting the busted up kindle 3 a new screen for stepk so he can play too...

I think this one is good enough to be classed V1.0 (but don't wanna get too excited again so maybe 0.5 it is...)


TODO: set screen resolution larger than 1024 vertical so my screenshots fit on one page lol Done