Quote:
Originally Posted by m-land
1) Do I understand well that I can use Core calls as I do on "real" device? Any limits?
|
Yes you can.
Execpt of runScript, as I haven't ported "libfskLoad.so" to Windows-Dll and all "real-device-kbook" related stuff.
With release x.02 Core is loaded via JS new Function, therewith "sandboxed" and can be called from autorun-js direct.
With release x.03 Core is loaded via prsp.compile and executed in the scope of bytecode. So all nonscriptable
fsk and
fskin objects could be adressed, but Core-functions are invisible to "sandbox" JS like in autorun.js.
Here you have to used the wrapped functions
_Core. or reference it via
var Core = _Core. (See the dictionary code in the last sim package)
Quote:
|
2) I need to have my "keyboard driver" loaded "on startup" (e.g. just after another core files. Is it enough to put my vk.js file to directory .../FSK Test\eBookSim\core? Or is there any other way?
|
This should do it.
Quote:
|
3) What to do to use it on notebook (1024x768 screen res)?
|
You can try to modify the eBookSimMain800.xml to have it work with 768 lines, but you have to decide if you want to cut off top or bottom.
- Eventualy you will place your keyboard in a dialog, which will automaticaly collect all keyboard actions.
- You may have a look on defsked kbook.so for the PRS-600/650
Firmware-packages are over at the-ebook.org
[Edit/Add] Keyword is "KEYS" and the function which pop up additional characters to chose if a key is hold. E.g. hold "A" and get ÄÂÀÁÃÅ [/Edit]
- I'am fantasizing of porting this keyboard (and maybe dictionary) to the 505/300 and have it controled by events send to it.