KUAL "listing bump" proof of concept

[j.p.s]

The list view listing for the KUAL booklet drifts down the screen and eventually off the first page as other books are opened even if KUAL has been used in the meantime. That is, the access time for the booklet KUAL does not get updated, unlike the kindlet KUAL.

The good news is that updating p_lastAccess for the KUAL record in cc.db raises KUAL to the second entry of the list view listing with the Recent filter after another book is opened and closed. The bad news is that the sqlite3 on board the kindle can not update cc.db (See post #1862 in https://www.mobileread.com/forums/sh...03326&page=125 )

Proof that there is hope:

mkdir local
sshfs root@oasis:/var/local local
NOW=`ssh root@oasis date '+%s'`
sqlite3.26 local/cc.db "SELECT icu_load_collation('en_US.utf8', 'icu');  update Entries set p_lastAccess = $NOW where p_titles_0_nominal = 'KUAL';"
fusermount -u local

Open a book on the kindle, then close it. KUAL will be the second entry in list view.

So, with a kindle sqlite3 binary that speaks icu, it would be straightforward to make a KUAL extention that bumps KUAL's listing.

This has been implemented as a KUAL extension. See https://www.mobileread.com/forums/sh...63#post3803463

[knc1]

Originally Posted by j.p.s

The list view listing for the KUAL booklet drifts down the screen and eventually off the first page as other books are opened even if KUAL has been used in the meantime. That is, the access time for the booklet KUAL does not get updated, unlike the kindlet KUAL.

The good news is that updating p_lastAccess for the KUAL record in cc.db raises KUAL to the second entry of the list view listing with the Recent filter after another book is opened and closed. The bad news is that the sqlite3 on board the kindle can not update cc.db (See post #1862 in https://www.mobileread.com/forums/sh...03326&page=125 )

Proof that there is hope:

mkdir local
sshfs root@oasis:/var/local local
NOW=`ssh root@oasis date '+%s'`
sqlite3.26 local/cc.db "SELECT icu_load_collation('en_US.utf8', 'icu');  update Entries set p_lastAccess = $NOW where p_titles_0_nominal = 'KUAL';"
fusermount -u local

Open a book on the kindle, then close it. KUAL will be the second entry in list view.

So, with a kindle sqlite3 binary that speaks icu, it would be straightforward to make a KUAL extention that bumps KUAL's listing.

Try the one NiLuJe packages with SS(??) - one of his catch-all packages.
If not, then I have a build linked to the entire Uncode data library - as in: everything.
If NiLuJe's does not do the trick, post in this thread and I will attach my build.


PS: There is another db there, with one entry, which holds the collation value setting to execute in sqlite3 to modify and delete of cc.db. (maybe: locale.db ??)

[j.p.s]

Originally Posted by knc1

Try the one NiLuJe packages with SS(??) - one of his catch-all packages.
If not, then I have a build linked to the entire Uncode data library - as in: everything.
If NiLuJe's does not do the trick, post in this thread and I will attach my build.

Thanks.

I dumped the SS tar.xz but didn't think to dump the update.bin

I'll have to grab kindletool and have a look.

Originally Posted by knc1

PS: There is another db there, with one entry, which holds the collation value setting to execute in sqlite3 to modify and delete of cc.db. (maybe: locale.db ??)

Can't find anything like that.

I guess there will need to be two versions. One for those (including me) who don't like case insensitive order anyway and another for those that don't mind using space on another copy of sqlite3. (I prefer not to make it dependent on SS, but I guess that those with SS can have the best of both.)

[knc1]

Originally Posted by j.p.s

Thanks.

I dumped the SS tar.xz but didn't think to dump the update.bin

I'll have to grab kindletool and have a look.



Can't find anything like that.

I guess there will need to be two versions. One for those (including me) who don't like case insensitive order anyway and another for those that don't mind using space on another copy of sqlite3. (I prefer not to make it dependent on SS, but I guess that those with SS can have the best of both.)

I do not know how "space" fits into this.
The content collections data base is set to the collation determined by the language question's answer when powering up the Kindle for the first time.


Your choice of English UTF8 just happens to be what yours is set for.
Other countries, probably not.
But I think the various UTF8 'space' types appear in the same position in all collation orders.

[PoP]

My (very simple) trick to access KUAL without scrolling.

Since the KUAL Doc does indeed drift down, I placed it in a collection "Jeux & Applications" with very few items showing on a single page. I also choose the collection name to sort hi on page one of my Kindle list view.

Two taps and I can launch KUAL.

[j.p.s]

Originally Posted by knc1

I do not know how "space" fits into this.

Sorry. I meant the storage space required for yet another sqlite3 binary.

BTW, I'm not having any luck finding an sqlite binary in the SS package.

[j.p.s]

Originally Posted by PoP

My (very simple) trick to access KUAL without scrolling.

Since the KUAL Doc does indeed drift down, I placed it in a collection "Jeux & Applications" with very few items showing on a single page. I also choose the collection name to sort hi on page one of my Kindle list view.

Two taps and I can launch KUAL.

Thanks.

That sounds like the way to go for anyone using collections. I gave up trying to use collection years ago in frustration.

[NiLuJe]

@j.p.s: It's in the Python package (which is a recommended dependency of the SS package ).

FWIW, that's also how I used to handle Kindlets back in the day: put 'em in a dedicated collection .

[ilovejedd]

Originally Posted by PoP

My (very simple) trick to access KUAL without scrolling.

Since the KUAL Doc does indeed drift down, I placed it in a collection "Jeux & Applications" with very few items showing on a single page. I also choose the collection name to sort hi on page one of my Kindle list view.

Two taps and I can launch KUAL.

Lol, I just use search. "kual" is pretty much permanently on my recent search history (either as first or second item). Takes more taps but I've got too many collections and change sort/filter often so search is most efficient for me.

[j.p.s]

Originally Posted by NiLuJe

@j.p.s: It's in the Python package (which is a recommended dependency of the SS package ).

FWIW, that's also how I used to handle Kindlets back in the day: put 'em in a dedicated collection .

The sqlite3 in the python package worked great.

I'll probably put together a KUAL package next weekend.

I'm open to suggestions for name, including capitalization. If I don't hear anything better, I'll probably use bump-kual

If that violates some naming convention, please let me know.

[NiLuJe]

I like Title Case for stuff like that, but that's just me .

[knc1]

Why not use a stored procedure to update last used time of KUAL, triggered on open, close, or 'home' button press?


Hint: dump the schema of the various tables to see how stored procedures are being used now (expect firmware version variations but we don't really need to support anything older than 5.2).

[j.p.s]

Originally Posted by knc1

Why not use a stored procedure to update last used time of KUAL, triggered on open, close, or 'home' button press?


Hint: dump the schema of the various tables to see how stored procedures are being used now (expect firmware version variations but we don't really need to support anything older than 5.2).

Thanks, that's a good suggestion and I will consider giving it a try.

Shouldn't exiting KUAL generate a close event and shouldn't that already trigger an access time update? Is this a kindlet vs booklet thing, an amazon bug, or a missing piece in KUAL?

[knc1]

Originally Posted by j.p.s

Thanks, that's a good suggestion and I will consider giving it a try.

Shouldn't exiting KUAL generate a close event and shouldn't that already trigger an access time update? Is this a kindlet vs booklet thing, an amazon bug, or a missing piece in KUAL?

Perhaps I mis-understood what you wanted to achive.
Closing KUAL **should** make it the most recently used already.

I thought you wanted to prevent the opening/closing of anything else from moving KUAL from "most recent" position.

So where ever the system records how recent something is used, the stored procedure should modify that field for KUAL, for anything opened/closed OTHER THAN KUAL.
(Don't want to loop when changing KUAL use time (whatever it is named) by letting it trigger the procedure again.)

I admit, I am not looking at a Kindle db at the moment and not even I trust my memory (which is why I no longer answer questions).
In fact, I am going through my stack of Kindles, looking for the one with the sql stuff on it.
It is here, somewhere. ....

[ilovejedd]

Originally Posted by knc1

Perhaps I mis-understood what you wanted to achive.
Closing KUAL **should** make it the most recently used already.

That works with KUAL Kindlet (azw2) but not with KUAL Booklet.