KUAL: Kindle Unified Application Launcher (v2.7)

[stepk]

PM'd you the link to an interim push.

[stepk]

Originally Posted by ixtab

I just committed Unicode support for KualButton. Tested and working on K3 and K4 (K5 isn't affected anyway).

But the second screenie looks odd. There should be just one right-arrow pointer at the end of just the sub-menu entries.

[ixtab]

Originally Posted by stepk

But the second screenie looks odd. There should be just one right-arrow pointer at the end of just the sub-menu entries.

Yeah, I was unsure about whether I should state this or not: The second one was just a test to see if Unicode characters "inside" plain text are properly rendered. I simply had it insert that triangle every 4 characters. Of course, this was only for testing purposes, and is not there in the real code.

[knc1]

Originally Posted by stepk

twobob, I'm going to upload this build to knetconnect RSN so you can take screenies on K3...

done: PM'd you the link

Could you be a bit more specific please?
OR
At least give a hint, like which sub-domain of knetconnect.com or which WebDAV directory.

Just because I run it, doesn't mean I can find your upload without at least some hints. It is getting to be a big place for only 3 people.

[ixtab]

Originally Posted by knc1

Could you be a bit more specific please?
OR
At least give a hint, like which sub-domain of knetconnect.com or which WebDAV directory.

Just because I run it, doesn't mean I can find your upload without at least some hints. It is getting to be a big place for only 3 people.

My suggestion is to simply push everything (once it's working) to the main repository... That's what it's there for.

@twobob: unless I'm terribly wrong, there still is no link to the source code in the first post. I suggest to add it there - right now, it's buried somewhere later in the thread.

[twobob]

@knc1 http://kual.knetconnect.com/forums/t...2-test-builds/

[twobob]

Originally Posted by ixtab

My suggestion is to simply push everything (once it's working) to the main repository... That's what it's there for.

@twobob: unless I'm terribly wrong, there still is no link to the source code in the first post. I suggest to add it there - right now, it's buried somewhere later in the thread.

In support Section now.

[knc1]

Originally Posted by ixtab

My suggestion is to simply push everything (once it's working) to the main repository... That's what it's there for.

@twobob: unless I'm terribly wrong, there still is no link to the source code in the first post. I suggest to add it there - right now, it's buried somewhere later in the thread.

I don't think they are using "branches" yet to keep the different version developments in parallel.

Although your suggestion is the best one, if using branches.

PS: You could become the 4th member of the KUAL support forums if you choose too - that sites registration is working, only the new registrations on the KUAL wiki is temporarily
disabled.
http://kual.knetconnect.com/forums/forum/kual/

And IT IS a "Support Forum" not just a "Discussion Forum" (although we currently only have one 'Resolved' thread).

The other 300,000 members here are also welcome to join if interested in the KUAL project.
See if any of you can beat ixtab to being the #4 member.

[stepk]

Originally Posted by ixtab

My suggestion is to simply push everything (once it's working) to the main repository... That's what it's there for.

@twobob: unless I'm terribly wrong, there still is no link to the source code in the first post. I suggest to add it there - right now, it's buried somewhere later in the thread.

Originally Posted by knc1

Could you be a bit more specific please?
OR
At least give a hint, like which sub-domain of knetconnect.com or which WebDAV directory.

Now the source code is in the main repo on github. As soon as I have time I will push the commented script source, now it's just the uncommented (stripped) script.
https://bitbucket.org/ixtab/kindlelauncher/

[twobob]

\\o//
_| |_

WOOT.

[stepk]

The screenies in #639 and #660 got me thinking a bit more about how to make the best use of the side Left/Right buttons, especially for the 4-way controller.

So what do people think of this? I suspect that in real use cases the L/R buttons will be disabled in most dive-in menus because it's unlikely for a sub-menu to include but a handful of entries, which only need a single page to fit(*). So I propose that when KUAL is showing a dive-in menu (second-level and deeper) the side buttons change their function from Left/Right to Up/Down. Of course in the top level menu L/R work only to scroll pages horizontally as they do now.

The benefit on KT/PW is that there's a larger area to hit with fat fingers to go up a level. The benefit on older platforms is that there's less tedious scrolling to do to navigate the menu hierarchy.

(*) Currently 5 items fit in a K3/K4/DX page. That's probably not enough to support this proposal. In KUAL2 dev builds it is actually easy to change the number of items per page by setting KUAL_page_size="8" or another suitable number.

[twobob]

I keep thinking of something logical to say about this excellent proposal.
So I read it over many times.

Probably the only thing I can say is that whatever minimises clicking on the lower devices is the best win. That was always the design goal previously.

Thus assuming that goal is met I am 110% behind this. Possibly 120%.

[twobob]

Okay so I took the plunge and emptied the coffers. With just a small amount of pocket searching I have purchased a kindle PW to help in the support effort. It has arrived.

Next funding will go toward fixing up stepks k3 (I managed to get an almost working one - cracked screen - for no cost, thanks to my debricking efforts), some serial cables and the other outlined top post goals.

Thanks to everyone for their support for this project so far.

Regards,

I will begin testing those things marked as PW supported in the KUAL versioning thread as time allows.

[ixtab]

[twobob]

Originally Posted by ixtab

:ROCK HANDS: : )

Thanks to everyone.