sad not a single reply 😞
well, i'm not good at taking hints.
So this weekend I've starting creating the Java classes and interfaces that will make up Roku Components, Interfaces and Events.
Now my thoughts is not to implement my own version of Roku device in Java, but to create something simple that I and others can use to more easily develop Roku applications (Channels and Screensavers).
I've based my work on past emulators that I have used such as those for smart phones, just a little less functional, but no less useful.
By that I mean that the components will basically not much more than mock objects to begin with that the developers can use with some command line and/or gui to monitor the state of the emulated device and to interact with the emulated device, in this case the Roku player and the program that they are running.
So just like on my smart phone emulator I can use the gui to make it look like there is an incoming phone call and the software running on the emulator will react just like there is an incoming phone call, but in all reality there is no incoming phone call.
And the same way that the software being runned on the emulator can make a phone call or do other things that result in nothing more taking place than it being returned what the develop indicated to the emulator. So I can in response to my smart phone software return line busy or some other valid outcome without making any phone call at all. Arent mock objects great!
Same will be for the Roku emulator. It will be able to ask for things from the mock components and what is returned or happens is based not on reality, but what the developer needs to test a section of code. So for example the software that is running can being playing a video and later on the emulator can return that the video ended or that the video was not found, ect but it's all fake, it was just how the developer and/or tester indicated, not that there was ever any video at all being played.
Anyways, I've been making good progress on creating stubs for the components. The next step is to finish some work I have to finish on around xml serialization and iScript and that will free me to be able to some not too distant weekend dumb down iScript to syntax level close to BrightScript.
Then I should be able to craft some magic to expose the Java components that I've been putting together in a manner simular to how they are accessed by BrightScript...
Then, I will need to do a little work to make iScript more like BrightScript, not too much work...
Then, I will need to cook up some Swing/AWT thingy that will be the emulator UI that the developer and or tester will use for example to say that the video has stopped playing...
Finally, I will need to change iBuild (the IDE) to be able to package and deploy to the Roku player and to bake package for distribution... So that the user can just press some button or select some menu item and not have to go to the Web interface, but that has lower priority.
Oh, one more thing, as soon as I have something, I'll post it for all...
cheers
when i do get something out I can use some help by people who are familiar with developing on Roku and the Roku Components and Language testing my work and maybe even getting involved in its development...