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

[Terisa de morgan]

I'll look at it, and I'll tell you... because I made a new menu for some particular settings I have

[Mark Nord]

Originally Posted by Terisa de morgan

...
BTW: Beta version doesn't load now in my reader, core to big

Yes this is becoming a problem, my workaround is to remove core_zabout.js from the /Beta/Core folder to get Beta-builds back to work.

We'll have to think about a more general approach.

[Terisa de morgan]

Thank you by the hint, I was building a normal install and using a Beta directory with config for log, but it's slower.

[Terisa de morgan]

Originally Posted by Analogus

Terisa:

If you just include my code from my file some functions may not work. My idea was to use my own language-section in the lang.ods. Most of my simple functions point to this part of the lang.ods. Look at the beginning of the file - there you will find a line:

LA = Core.lang.getLocalizer("ANALOGUS");

which points to the lang.ods. LA() is used instead of L() for localisation.

That I know. I got your lang.ods, translated it and mixed it with mine (some changes, too).

Originally Posted by Analogus

A couple of functions require certain files and/or folders on the reader. Without the right folder some of the functions will not work but just quit without message.

I'll check it now. I've been reproducing some changes I wanted to add and, after looking the options appear translated, and seeing it doesn't look like it works one I tested, I haven't investigated more.

Originally Posted by Analogus

If you find a way to make a new menu in prs-settings with the functions let me know. I was not able to do that...

Are we talking about a new menu entry (that I have done it for my options) or a new group for actions? I would have to check if I find where the groups are defined.

[Analogus]

Terisa:

What I want:

1) Best would be to have a complete new entry in menu beside 'actions', 'CLI', 'Frotz' ... Say 'Analogus Tools' which contents all the options and functions I add to PRS+. So I could assign the whole group to a button calling the new menu.

2) Second best would be a complete menu-point say 'Analogus Options' with all functions and options I add in PRS-options side by side with 'Status Bar', 'Dictionary-Options', ...

3) Third best would be to have one ore more new groups of actions with my functions in 'Actions'. That's what I already have. 'Actions' are renamed (as you can see) in 'Swiss Knife' and my new groups are called 'Save&Restore', 'System Fonts' and 'Developer Tools'.

4) In any case it would be fine to put one of the 3 points above in a complete new *.JS file (say 'analogus_options.js') to keep the rest of the PRS-code as clean as possible and not mixing my contributions into existing PRS-code.

A.

[Terisa de morgan]

I hadn't checked the first point (I don't use that menu so.... ). I can try. The second one is done, not completely, it's a boring task because it means to change actions into menu options and it's tedious, but I've tested it with a couple of options and it works). I think the first one can be easier.

Anyway, it's done into a new file, out of StandardActions, because it was hard for me to work with the other one

If you want I can send you my test now or after trying your first option.

[Analogus]

Terisa:

If I may be impudent :
Both would be fine. So I could see how to do those things...

Maybe you have already such 'thing':
One or the other function needs a 'do you really want to..'-question. Any ideas how to implement it in my existing functions?

A.

[JSWolf]

So currently, what's the best version of PRS+ to install on a 650?

[Terisa de morgan]

No problem, here I attach you the second option (not complete but you can see the idea). I'll try to do the other version and attach it. About dialog, do you know any other function with a similar behavior? To look all the code is a bit boring

BTW, that's the method I use: Find something similar to what I want to do.

[Terisa de morgan]

Originally Posted by JSWolf

So currently, what's the best version of PRS+ to install on a 650?

What do you understand as "best"? Not a rhetoric question. It depends on what you want to have in your ereader.

[JSWolf]

Originally Posted by Terisa de morgan

What do you understand as "best"? Not a rhetoric question. It depends on what you want to have in your ereader.

What options are there?

[Terisa de morgan]

Well, the main difference would be 2.0 or 2.1, where you have subcollections and a lot of more "shortcuts", touch settings, options to change standby time and things like that (not a detailed info, sorry). So, your decision.

[quisvir]

JSWolf:
For the differences between 2.1 and 2.0, see the WhatsNewIn2_1_x wiki page.

Analogus:
To create a dialog on x50 models, you can use this code in a function:

var dialog = kbook.model.getConfirmationDialog();
dialog.onOk = function () {
	// what to do if Ok/Yes is pressed
}
dialog.onNo = function () {
	// what to do if No/Cancel is pressed
}
dialog.openDialog('Dialog text', 'As many lines as you want', 'three...', 'maybe four?', 0);

The last parameter given to openDialog determines the buttons (basically):

0 = Yes/No
1 = Ok
2 = no buttons, keys locked
3 = no buttons, keys working
4 = Cancel

There are more possibilities (see main.xml, search for CONFIRMATION_DIALOG_AREA), but these are the most useful. Dialogs have a few more properties and methods such as 'target' and 'closeDialog', but the above should cover most cases.

[Analogus]

Terisa:

Thank you very much - your file is very helpful. I'll use it as template.

Quisvir:
Thanks. Will use your code for my functions, especially for restoring and clearing systemcache.

A.

[ilovejedd]

Originally Posted by JSWolf

What options are there?

As mentioned by quisvir, you can go with 2.0.18 stable or 2.1.01 alpha. Quite frankly, 2.1.x releases appear to be quite stable despite being in alpha. There are tons of new features and options available (particularly love sub-collections) and it really makes a noticeable upgrade over 2.0.x.

@quisvir:
Special request, can you add the backslash (\) as a possible separator for sub-collections? Thank you so much!