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

[BenChen]

Originally Posted by kartu

Hi Ben,

the reported problem is, that capturing is not mandatory.

PS
Wanted to raise issue of not being able to capture backwards, but I guess it's ok according to English Draughts rules.

Hi everyone,

Just wanted to say that I have added one setting to Draughts. You now have the option of allowing pawns to capture backwards or not. (I should note that I have not changed the AI so the reader will never capture backwards.)

I am afraid that mandatory capturing ("if you can jump you have to jump") is beyond me. The way that things have been programmed, I don't think it will be possible without a major code re-write. But if anyone else wants to step in and have a go...

The update has been pushed to both repositories (default and apps).

Sincerely,
Ben.

[Mark Nord]

Hello Ben,

as a matter of fact Core.lang.getLocalizer is available in the sim.
Calling getLocalizer: function (category, strings) with a set of localized strings should be possible.
If the resource-strings will be included in lang.ods then there might be a problem with passing the params to the "sandboxed" JS-code of calendar.
Kind regards
Mark

[BenChen]

Originally Posted by Mark Nord

Hello Ben,

as a matter of fact Core.lang.getLocalizer is available in the sim.
Calling getLocalizer: function (category, strings) with a set of localized strings should be possible.
If the resource-strings will be included in lang.ods then there might be a problem with passing the params to the "sandboxed" JS-code of calendar.
Kind regards
Mark

Hi Mark,

Hmmm, to be honest, I don't quite understand what to do!

I think the idea would be to put the strings into lang.ods so that it is easier for the translators. So would it be necessary, then, to do all the calls to Core.lang.getLocalizer in the Calendar.js (the calling code), putting the strings into variables which can then be used in the sandboxed code? But if that were the case, then I don't see how it would work in the Sim...

Sincerely,
Ben.

[Mark Nord]

Another thought:
define var L = Core.lang.getLocalizer("Calendar");
in the startup-code (Calendar.js) and export it via kbook.autoRunRoot.sandbox.L = L;
In calendar.js it should be possible to use
L = kbook.autoRunRoot.L;
and then
L("anyString");

As Sim dosn't read lang.ods you will have to copy appropriate xx.js language files (e.g. from a beta-build) to eBookSim\core\lang
HTH
Mark

[BenChen]

Originally Posted by Mark Nord

Another thought:
define var L = Core.lang.getLocalizer("Calendar");
in the startup-code (Calendar.js) and export it via kbook.autoRunRoot.sandbox.L = L;
In calendar.js it should be possible to use
L = kbook.autoRunRoot.L;
and then
L("anyString");

As Sim dosn't read lang.ods you will have to copy appropriate xx.js language files (e.g. from a beta-build) to eBookSim\core\lang
HTH
Mark

Hi Mark,

That makes sense. I will try this when I get a chance...

Sincerely,
Ben.

[BenChen]

Hi everyone,

By the way, I slept on it, and realised the Draughts code could handle compulsory jumping. So when I get time, I will have another go.

Sincerely,
Ben.

[VICTORSJG]

Ben i've seen in calendar.js the keyboard is loaded once at startup, i don't know if the different keyboards could be loaded selecting them via a menu on prs settings wich user wants to choose, once these keyboards have been defined in calendar.js.

[BenChen]

Originally Posted by VICTORSJG

Ben i've seen in calendar.js the keyboard is loaded once at startup, i don't know if the different keyboards could be loaded selecting them via a menu on prs settings wich user wants to choose, once these keyboards have been defined in calendar.js.

Hi Victor,

Yes, the plan is to be able to choose different keyboards using the Calendar options popup. However, this involves extending the number of keys on the popup which will also affect the format of the keyboard file. So, while the potential is there, the actual implementation of alternate keyboards might take a while.

However, for people like yourself who build your own PRS+, you can modify the western.kbd file and put in your own characters. This will then be loaded when the Calendar starts. (Note that if this file is missing, Calendar just loads the regular western keyboard anyway! So it is not strictly required, I just did it this way so that people could do their own keyboards.)

It should be obvious how the file works. There are basically 4 "pages" of characters, 2 for letters and 2 for symbols, with SHIFT to switch between the lower and uppercase letters, and the 2 symbol pages. You will quickly find, however, that there is only room for 26 characters each on the four different "pages". This is why we need to extend the number of keys on the popup. In the meantime, you will need to sacrifice some of the symbol keys for any extra letters your language requires.

Hope this helps!

Sincerely,
Ben.

[BenChen]

Originally Posted by kartu

Hi Ben,

the reported problem is, that capturing is not mandatory.

PS
Wanted to raise issue of not being able to capture backwards, but I guess it's ok according to English Draughts rules.

Hi kartu,

You can inform the person who made the original request that I have added the option to make capturing compulsory. I have also added the option to allow pawns to capture backwards. The changes have been pushed to the default and apps repositories.

Sincerely,
Ben.

[VICTORSJG]

Originally Posted by BenChen

Hi Victor,

Yes, the plan is to be able to choose different keyboards using the Calendar options popup. However, this involves extending the number of keys on the popup which will also affect the format of the keyboard file. So, while the potential is there, the actual implementation of alternate keyboards might take a while.

However, for people like yourself who build your own PRS+, you can modify the western.kbd file and put in your own characters. This will then be loaded when the Calendar starts. (Note that if this file is missing, Calendar just loads the regular western keyboard anyway! So it is not strictly required, I just did it this way so that people could do their own keyboards.)

It should be obvious how the file works. There are basically 4 "pages" of characters, 2 for letters and 2 for symbols, with SHIFT to switch between the lower and uppercase letters, and the 2 symbol pages. You will quickly find, however, that there is only room for 26 characters each on the four different "pages". This is why we need to extend the number of keys on the popup. In the meantime, you will need to sacrifice some of the symbol keys for any extra letters your language requires.

Hope this helps!

Sincerely,
Ben.

I had already modified this file to create one with the characters i want to use.

thanks

[Mark Nord]

Originally Posted by Mark Nord

Another thought:
define var L = Core.lang.getLocalizer("Calendar");
in the startup-code (Calendar.js) and export it via kbook.autoRunRoot.sandbox.L = L;
In calendar.js it should be possible to use
L = kbook.autoRunRoot.L;
and then
L("anyString");

You sure noticed that I mixed up real-device and Sim
For the Sim it should read
define var L = _Core.lang.getLocalizer("Calendar");
in the startup-code (setView.js) and export it via
kbook.autoRunRoot.L = L;

default language is set in ebookSim\user.config

Regards
Mark

[BenChen]

Originally Posted by Mark Nord

You sure noticed that I mixed up real-device and Sim
For the Sim it should read
define var L = _Core.lang.getLocalizer("Calendar");
in the startup-code (setView.js) and export it via
kbook.autoRunRoot.L = L;

default language is set in ebookSim\user.config

Regards
Mark

Hi Mark,

I tried the following in setView.js, but the Calendar app won't start.

      	 case "Calendar" : {
      					kbook.autoRunRoot._icon = 22;
      					kbook.autoRunRoot._title = "Calendar";				
      					kbook.autoRunRoot.getFileContent = _Core.io.getFileContent;
						kbook.autoRunRoot.setSoValue = _Core.system.setSoValue;
      					kbook.autoRunRoot.startsWith = _Core.text.startsWith;
						var L = _Core.lang.getLocalizer("Calendar");
						kbook.autoRunRoot.L = L;
      					this.MAIN.EINK.VIEW.setURI("../addons/Calendar/calendar.xml");				
      					break;
      					}

If I comment out "var L = _Core.lang.getLocalizer("Calendar");" the app starts, but obviously the localised strings don't work. Any thoughts?

Sincerely,
Ben.

[VICTORSJG]

Ben, this image appears when the chess is started the first time on prs 505, the following starts once other apps is opened and closed, chess works well.

[kartu]

AI opponent doesn't make a move reported here.

[BenChen]

Originally Posted by kartu

AI opponent doesn't make a move reported here.

Hi kartu,

I am not sure there is much I can do. When the Reader is in slow mode, it is really slow (even with only a few black pieces to work through). There has been one occasion where I waited for ten minutes and it never moved. I gave up waiting: it may have hung, I couldn't tell.

But when I have some time, I will make a save game of the screenshot, load it onto my reader and see what happens when I force an AI move for black.

Sincerely,
Ben.