PRS+: Enhanced firmware for Sony Reader, Folders, Games & more

[Analogus]

Thank you quisvir. Working flawless!
Additionally removed the 'x' from the popup - lucky now ;-)

Next part is the 'Application'-page. There would be room for a third application (addit. to dic and notes). I did not find the responsible file for the layout. Any hints?

I regard the calendar as a good application to move.

A.

Edit: found the XML-files. Now it's to find out how to assign a new button with a function...

[quisvir]

That would require a bit of coding, I'm afraid. There is a function 'updateApplicationRoot' responsible for assigning the content to the page, similar to the 'updateDeviceRoot' function used in the common_x50 js.

[Lukk]

I have one annoying problem. Every time I reset the reader or its hung in all the books I've already read the page number goes back to time when PRS-plus was instaled. How to fix it?

[kartu]

Originally Posted by Lukk

I have one annoying problem. Every time I reset the reader or its hung in all the books I've already read the page number goes back to time when PRS-plus was instaled. How to fix it?

Cache is persisted when you connect reader to PC or switch it off.

PS
Why is it hanging, are you playing games?

[Lukk]

Originally Posted by kartu

Cache is persisted when you connect reader to PC or switch it off.

Shoutdown device helped. Thank you

Originally Posted by kartu

Why is it hanging, are you playing games?

Yes, I used to play games. After this cache problem I'm not playing any more

[quisvir]

Analogus:
I forgot to mention that it's relatively easy to add code to enable close-by-tap in other overlays. Just take the 'id' of the overlay from main.xml, and change '128' to the height of the inner group (the group within the overlay's group). Here are a few more examples, from which I'm sure you can build any others you want

Spoiler:

kbook.model.container.sandbox.OPTION_OVERLAY_PAGE_JUMPBAR.sandbox.canTap = function () {
   return true;
}
kbook.model.container.sandbox.OPTION_OVERLAY_PAGE_JUMPBAR.sandbox.doTap = function (x, y) {
   if (y < this.height - 128) this.getModel().closeCurrentOverlay();
}
kbook.model.container.sandbox.SEARCH_OVERLAY.sandbox.canTap = function () {
   return true;
}
kbook.model.container.sandbox.SEARCH_OVERLAY.sandbox.doTap = function (x, y) {
   if (y < this.height - 369) this.getModel().closeCurrentOverlay();
}

/edit: the tone curve overlay was a bad example... it doesn't seem to work.

[Analogus]

quisvir:

Thanks very much. I'm playing around with your code and it works. And yes, tone-curve doesn't work. Bad, cause this would be a 'very nice to have'. But I don't give up ;-)

I have to admit I do not understand your code... but implementing on the right place seems to be possible. Besides: altering the application-page did not work (as to expect...).

Annother thing:
Do you regard it to be simple to do following?
For closing full-page-overlays (e.g. authors-list-overlay) you have to hit the small button in the left upper corner. It would be nice to be able to close it by touching somewhere on the broad black upper border, not just the small area of the button.

A.

[quisvir]

Originally Posted by Analogus

For closing full-page-overlays (e.g. authors-list-overlay) you have to hit the small button in the left upper corner. It would be nice to be able to close it by touching somewhere on the broad black upper border, not just the small area of the button.

Yes, that's possible. In main.xml, look for id="MENU_DETAILS_GROUP". In that group, about 120 lines down, there's this line:

Spoiler:

<button2 skin="button_back" left="5" top="5" width="61" height="61" can="canBack" do="doMenuClose"/>

Now, right before that line, insert the following line of code:

Spoiler:

<kbookHotspot do="doMenuClose" left="0" right="0" top="0" height="70" visible="false"/>

That should take care of most 'regular' views. If you do a search for skin="button_back" though, you'll see that there are more definitions for specific views. Of those, I'd say that SETTING_GROUP and maybe SCROLL_SETTING_GROUP are the most used, so you could consider adding the code there too. Note that in the latter case, the back button refers to doMenuClose2, so you'll have to change the inserted line accordingly.

[Analogus]

Thank you!
Working perfect!

A.

[Analogus]

Success. More or less ALL overlays and dialogues closeable with single tap or tapping onto the upper black bar of the screen:


A couple of 'x' aren't longer necessary:


Contrast-dialogue has been altered that way. Closeable with single tap:


A.

Download possible for the 350/650 (see link below; look for 'Zork'-Edition)

[ilovejedd]

My older PRS-350's are still on 2.0.12 Beta and I've just been too lazy to update. Bought a refurb PRS-350 for backup and just installed the latest version of PRS+. The single tap for next page option is plain awesome. It's just so convenient. I have it set to "Anywhere for Next Page". PRS+ has really made my PRS-350 much nicer and easier to use (folders, custom fonts, custom gestures, etc). A big thanks to all the developers!

[Analogus]

@ quisvir (?):

I want to make a new point in PRS+-setting. Could you give me a hint on how-to?

I want:
Saving the complete setting of PRS+ with one push on a button.
Restoring this setting with one push on a button
Nice to have: 2 different versions to store/restore

what I know:
I have done this (storing, restoring) with a simple CP-line in prsp.sh. Reason: from time to time I copy the settings from one of my two readers to the other one.
So I know the LINUX-commands and place where the settings are stored.

What I don't know:
How to produce a button/menu-point which does this simple script.

Any help/pushing to the right direction appreciated

A.

[quisvir]

ilovejedd:
I think I speak for all developers when I say, you're quite welcome

Analogus:
Take a look at the 'Mark all Books' option in BM. This is also really an action rather than an option, and it has three parts:
- a regular option definition in optionDefs
- a few lines in onSettingsChanged, which calls the markAllBooks function and resets the option value
- the markAllBooks function itself, which actually does the work.

You could skip the 3rd part and just put the code in onSettingsChanged itself, but it's probably neater with a separate function.

Since you know the linux commands, it's probably easiest to call those from the function, using Core.shell.exec('command').

[Analogus]

Thanks, I'll try bring myself on.

Annother thing:
Could it be that in the newest nightly build the option for the reading-progress is damaged?
I want to change the reading-progress shown for the current book under ... --> format for Current Book:
There are 8 menu points. But no point for ... (pages to next chapter), no... (time to end of next chapter), etc. Just '5 of 100', '5%', '5 / 100 (5%)' and similiar.

A.

Edit: maybe I destroyed something. Where can I find the code for the menue-points? The functions itself I can find in StatusBar_PageIndex.js

[Mark Nord]

Analogus,

if you can manage to add a "clear/reset" all PRS+ Settings, too. This would also fullfill a FR from the-ebook.org

Option A) shell-script to delete /opt0/prsp
Option B) use Core.io.deleteDirectory to achieve the same goal