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

[Terisa de morgan]

Originally Posted by Analogus

If that's the case your are right.
Did this people change back to the 2.1-version again? I would do that to be sure PRS is the root of the error.

I'm not sure as it isn't my ereader and they didn't want to test

Originally Posted by Analogus

To me power-drain seems to occur mainly on PRS650-readers, not on 350.

Mainly as I've read, yes.

[sengian]

Originally Posted by Analogus

How did you remove the games?

Change the build.xml to exclude games, removed gamesave from installer, remove the game action from StandardActions_x50.js, remove all I can find pertaining to games in 650_config.js.

I have still some modifications in prsp.js and StandardActions.js I have not tried but that sums it up.

I was interested in your method but not able to clearly see it in your clone ie what was the corresponding commit.

[Analogus]

Sengian:

My method is rougly the same so far as I can remember (this have been my first tries to alter PRS+). Have a look into 650_config.js.
Remove the line

{ name: "games", title: "NODE_GAMES", shortName: "Games", icon: "GAME"}

Below this line change everything pointing to 'games' to 'more'.

Ah, and you could change lang.ods. Just rename whatever you want. I think I made even a change there to rename something with 'games' into whatever...


That should do.

PS: there is no special commit for the time I removed games 'cause I've done it before the time offering custom-builds on the web.

[sengian]

Originally Posted by Analogus

Sengian:

My method is rougly the same so far as I can remember (this have been my first tries to alter PRS+). Have a look into 650_config.js.
Remove the line

{ name: "games", title: "NODE_GAMES", shortName: "Games", icon: "GAME"}

Below this line change everything pointing to 'games' to 'more'.

Ah, and you could change lang.ods. Just rename whatever you want. I think I made even a change there to rename something with 'games' into whatever...

I have done exactly what you did minus the part about lang.ods as it should not be a problem and may be easier to update in this case.
I purely remove all game so no need to change them to more but I still have this problem with the action launcher.
I think in this case the launcher is putting the calculator into a game node somewhere but I don't know where.
Well it is not a real problem, just less neat that what I would like

[Analogus]

Hi

I just looked into the code (back home now) and can confirm:

I renamed 'games' to 'applications' in lang.ods. But you could assign the calc to another group:

Have a look into calc.js --> line 29, there you find the responsible line for putting the calc-action into the game-node:

group: "Games",

A.

[sengian]

Originally Posted by Analogus

Have a look into calc.js --> line 29, there you find the responsible line for putting the calc-action into the game-node:

group: "Games",

Just call me stupid...I totally forgot to check calc.js
Thanks again

[EldRick]

Weird - I just installed analogus' version to my 950, and it made no changes at all. The installation folder vanished as expected, but no new options appear anywhere.

[Analogus]

Did you install the 'normal' version at least ONE TIME?

A.

PS: in case of PRS950 I would install the official version. The nightly build ('Analogus version') isn't that different now. If the official PRS+ is evolving and will bring new features I will compile a new build to be on the edge of developement.
But developing on PRS+ actually seems to be in a 'standby-mode' ;-)

[EldRick]

Yes - the official PRS+ version was installed and working, with custom CSS.

Your v50 shows up in the About, but none of the added function shows up...

How would I revert to the "Official" PRS+ ?

[DoctorOhh]

Originally Posted by EldRick

Your v50 shows up in the About, but none of the added function shows up...

Just a guess, but if you left the device attached to the USB port while it powered on then it should just show you the normal Sony firmware. Go to settings shutdown then turn back on and it should show all the PRS+ options.

[EldRick]

"Go to settings shutdown then turn back on..."

I've done that repeatedly.

[Analogus]

No problem:

Just install as always the normal PRS+ Version above the nightly build.

A.

[EldRick]

Thanks - I re-installed the v2.1 alpha, and it's back where it was on PRS+.

[EldRick]

Caecilia, used on the Kindles and Nooks is well-designed for a serif reading speed-font on the moderate resolution of current e-ink screens. PRS+ does a great job of allowing us set font and type size, and I use Caecilia in various sizes to set the line and character size.

However, at smaller sizes on my PRS-950, it seems a bit low-contrast to me, with too-thin strokes, so I've been looking for a darker (bolder) alternative. After B&N upgraded the rendering technology on the Nook Simple Touch, they delivered a slightly darker version of Caecilia, which I found more satisfactory than the Amazon rendition, and that's been my goal.

So here is my bolder version of Caecilia for PRS+. I think it is pretty close to the Nook Touch rendering.

I simply used Caecilia Bold 75 for the base font, and Caecilia Heavy 85 for bold type. This delivers a higher-contrast rendition than the Standard weight, and makes smaller sizes much more readable - almost like a higher-contrast e-ink screen. Bold Italic 76 and Heavy Italic 86 provide for the other two combinations.

Here's the .65em CSS file. I renamed the .otf font files to remind me what was in them, and then saved a series of CSS files in sizes from .65em to 1.00em (.65em, .70em, etc.). I select the CSS file based on the filename, and get the size I want.

(I also tell calibre to set .3em paragraph spacing, left-justify, and remove all other fonts when I prepare the file for sideloading.)

CaeciliaHv65m.css

@font-face { font-family: serif; font-weight: normal; font-style: normal; src: url(res:///Data/fonts/CaeciliaLT-75-Std-Bold.ttf);}
@font-face { font-family: serif; font-weight: normal; font-style: italic; src: url(res:///Data/fonts/CaeciliaLT-76-Std-BoldItalic.ttf);}
@font-face { font-family: serif; font-weight: bold; font-style: normal; src: url(res:///Data/fonts/CaeciliaLT-85-Std-Heavy.ttf);}
@font-face { font-family: serif; font-weight: bold; font-style: italic; src: url(res:///CaeciliaLT-86-Std-HeavyItalic.ttf);}

body, body.calibre, body.calibre1, body.calibre2, body.calibre3, body.book {
font-family: serif;
font-size: 0.65em;
line-height: 1.1}

[yolan]

Originally Posted by EldRick

I simply used Caecilia Bold 75 for the base font, and Caecilia Heavy 85 for bold type. This delivers a higher-contrast rendition than the Standard weight, and makes smaller sizes much more readable - almost like a higher-contrast e-ink screen. Bold Italic 76 and Heavy Italic 86 provide for the other two combinations.

Those are just the same fonts I've been using on my old 505, and now on my 650. The font in the Kindle seems to be just a little bit thinner than these, but not as thin as the standard Caecilia versions.

I have other .css and fonts to choose in the reader... but I alwasys stick to these....

I once compared a friend's Kindle 3 with my PRS-505 with those fonts installed, and the difference between the two devices (display-wise) was not so evident.
Since then, he always recommends buying Kindle OR Sony