PRS-505 FSK Test-Environment for Autorun Applications under MS-Windows

[kartu]

Great job, BenChen, I'll include it into PRS+ (don't expect it soonish, I'm busy with RL for a
while)

Mark, regarding IM corruption, there is an "evil" caching mechanism that affects anything loaded from a sandbox. (stuff loaded from "normal" code also gets cached, but there is an easy workaround (works at least on 300): rename old file, put new file, delete old file. This doesn't work with sandboxed cache, unfortunately).

Other than that, connect to USB during startup, format IM, shutdown from menu should fix existing IM problems.

[BenChen]

Hi all,

I found a minor bug: the "Player 2 won!" message did not appear. The attached version fixes this. I've also included Mark's loader script in the zip file.

Thanks, Kartu, for saying you will put it into PRS+. No hurry!

Sincerely,
Ben.

UPDATE: Latest version now found in post #145.

[surquizu]

I do not get it to work in the PRS+ for the 505

[Mark Nord]

Originally Posted by surquizu

I do not get it to work in the PRS+ for the 505

Me, too.
I was hoping that this was caused by still using an early 1.0.2+ version of PRS+ on my 505.
But if surquizu states it isn't working with v1.1.3, there must be an general problem with code in the Sim vs the real device.

With both, Sudoku and Fiverow, the UI shows up but didn't accept any input. The "do not enter oneway" sign shows up with each keypress.
With Fiverow all skins (Touch and nonTouch) are shown, so there must be a proplem in the JS-code probably within target.init, or even earlier in code.

I can think of two sources of the problem:

1. the handover of Core-functions in PRS+1.1.x vs PRS+v2.0.x, but that is still working in DictioLauncher.
2. the FSK-menu (consuming all input-events?)

Will try to figure out, any suggestions are highly welcome.

PS: @Ben: There are no problems with the PRS-600?
The touch-interface is still accessible after closing the app?

[BenChen]

@Mark: Absolutely no problems with the PRS-600. Game works perfectly, and after exiting, the PRS-600 is working normally.

Furthermore, I just converted FiveBalls to Touch using the Test Environment, and then incorporated it into my custom-build of PRS+ and loaded it onto my PRS-600. Everything works fine (with the exception that the high score is not saved). I was going to upload the code, but if there is an issue with Five In A Row, then perhaps we should try and get that fixed, so that the same can be done for FiveBalls.

[Mark Nord]

It seams, that I have tracked down the problem with v1.1.3 to the handover via kbook.autoRunRoot.xyz in the starter script.

By avoiding any references to Core I am able to have Fiverow on my PRS-505

Spoiler:

var getSoValue, newEvent, hasNumericButtons;
..
..
target.init = function () {
/* Core workaround  */

      	if(!kbook || !kbook.autoRunRoot || !kbook.autoRunRoot.getSoValue){ 
      	  		if (kbook.simEnviro) {
      	  			//	this.bubble("tracelog","505 branch - SimEnviro");
	      	  		getSoValue = _Core.system.getSoValue;
				hasNumericButtons = _Core.config.compat.hasNumericButtons;
      	  		} else {/* PRS-505 */
      	  			//	this.bubble("tracelog","505 branch - Device");
        	  		getSoValue = function (obj, propName) {
        			return FskCache.mediaMaster.getInstance.call(obj, propName);};
 				hasNumericButtons = true;
      			}
			var compile = getSoValue(prsp,"compile");
			newEvent = compile("param", "return new Event(param)");
	 }else { /* code is ok with PRS-600 */
		//	this.bubble("tracelog","600 branch");
		getSoValue = kbook.autoRunRoot.getSoValue;
		//	this.bubble("tracelog","getSoValue "+getSoValue);
		newEvent = prsp.compile("param", "return new Event(param)");
		hasNumericButtons = kbook.autoRunRoot.hasNumericButtons;
		//	this.bubble("tracelog","hasNumericButtons "+hasNumericButtons);
	}

There are still problems:

1. "MENU to quit" is overlayed by the (blank) Volumebar (see screenshot)
2. buttons 1+2: there is no action at the moment !?
3. I tried the same workaround in my latest sudoku-code but the game refuses to accept button-input

After sorting out the Num-button problem, I will post a complete package.

Furthermore, I just converted FiveBalls to Touch using the Test Environment, and then incorporated it into my custom-build of PRS+ and loaded it onto my PRS-600. Everything works fine

If you will try Mahjong too, there is a non obfuscated version in clemenseken's thread here.

[Mark Nord]

Here you go..
As there are major changes between PRS+v1.1.x and PRS+v2.0.x this is only a temporary fix to get this working with Sony PRS-505.
As it is working for the PRS-600 with PRS+v2.0.x it will, probably, work unchanged in v2 for PRS-300 and the forthcoming v2 for PRS-505

Regarding the not working numeric buttons: part.key is character! So you have to typecast to numeric.

@surquizu will you please try too?

BenChen wrote:
I was going to upload the code, but if there is an issue with Five In A Row, then perhaps we should try and get that fixed, so that the same can be done for FiveBalls.

Please do so, as fiveballs is already integrated with the earlier versions, there is no etxra-need to be backward compatible to PRS+v1.1.3.

[surquizu]

Originally Posted by Mark Nord

Here you go..

@surquizu will you please try too?

I can not. Maybe it's my fault. Screen is displayed how the image but then stops the eReader.

[BenChen]

Here's my touch version of Fiveballs. I made a couple of cosmetic changes, too, getting rid of the diagnostic output showing which button was pressed, and showing the most recent score in brackets.

Note: on my PRS-600 the high score is not saved! Does anyone know how to fix that?

Note that to get this working in the Test Environment, you need to edit eBookSimMain.xml and change

				 case "Fiveballs" : {
								this.EINK.VIEW.setURI("../addons/Fiveballs/fiveballs.xml");				
								break;
								}

to

				 case "Fiveballs" : {
								kbook.autoRunRoot.getSoValue = _Core.system.getSoValue;
				 				kbook.autoRunRoot.hasNumericButtons = _Core.config.compat.hasNumericButtons;
								this.EINK.VIEW.setURI("../addons/Fiveballs/fiveballs.xml");				
								break;
								}

@Mark Nord: Actually, to make it work for Touch I needed to use the same variables that were causing problems. So, I applied the same fix that you worked out for Fiverow.

UPDATE: Latest version now found in post #145.

[Mark Nord]

Originally Posted by surquizu

I can not. Maybe it's my fault. Screen is displayed how the image but then stops the eReader.

Hi,
it's not your fault. prsp.xsb isn't scriptable in PRS+v1.1.3 and so target.init() fails. (It's more my fault to have not the release version on my reader, but a modified one, taking advantage of some v.2 features.)
Now I have put try catch blocks around prsp.compile and newEvent, and tested successful even as autorun-app on a completely untouched eReader.

Corrected fix and autorun are posted in Post #82

[BenChen]

And I've updated Fiveballs with the try catch code. Corrected fix in post #84

[surquizu]

It works well at 505 with PRS +. Thanks!

There was a small error in the code. Is already fixed. Upload files to copy to the PRS + installer.

Coming soon will be integrated into the PRS + for Spanish users of 505.

Thanks Mark Nord and thanks BenChen!

[BenChen]

You're very welcome!

[BenChen]

Hi everyone,

I just finished a first-pass attempt at a Touch-compatible version of Clemenseken's Mahjong game.

To activate Touch in the Test Environment, edit eBookSimMain.xml and change

				 case "Mahjong" : {
				 				this.EINK.VIEW.setURI("../addons/Mahjong/mahjong.xml");				
								break;
								}

to

				 case "Mahjong" : {
				 				kbook.autoRunRoot.getSoValue = _Core.system.getSoValue;
				 				kbook.autoRunRoot.hasNumericButtons = _Core.config.compat.hasNumericButtons;
								this.EINK.VIEW.setURI("../addons/Mahjong/mahjong.xml");				
								break;
								}

Hope it works for you!

Sincerely,
Ben.

EDIT 1: Removed some unnecessary graphics at the top of the screen.

EDIT 2: Fixed menu bug in non-Touch (thanks Mark!) and added two buttons to the Touch version: "New layout" and "Easy/Normal" (again, thanks to Mark for the redeployed Calculator buttons!). I think that's it...

UPDATE: Latest version now found in post #145.

[BenChen]

Just to say it worked well on my PRS-600, using my custom build of PRS+.