Orbited For A New WebOrbiter
|Version||Status||Date Updated||Updated By|
Concept - What is a WebOrbiter
A web-based orbiter is basically a web page that one can browse from any device.
Today we have our Web Orbiter. It utilize the BD stack to transmit Orbiter images to a web browser. When user click somewhere on the showed picture (Orbiter screen), coordinates are sent back and translated into a command/button click that is interpreted and executed by lmce. If that result in another Orbiter screen that screen is rendered into a picture and sent to web browser.
What would be really nice to have is a weborbiter that consist of code and graphics renderad in webbrowser on client (no more transmit of static pictures). In my opinion there´s a couple of ways to implement this.
- json and rpc. Don´t have much information on how this can be done or if it is possible.
There´s a couple of solution/ideas how to do this. One issue that we need to overcome is that it is very hard to communicate from a server to a webbrowser.
- User browse media in weborbiter and click on a media file. A command is sent from webbrowser to Orbited proxy and then through tcpsocket to router plugin. Router plugin what for update and send data back thourgh tcpsocket to Orbited proxy and in the end to the webbrowser.
- User have a remote control screen opened on his weborbiter. Some other Orbiter send a message to MD to change to play another media file. Router plugin will get inforamtion about what have changed and transmit send that information to Orbited proxy which forward it to the webrowser where our weborbiter is running.
- We need to have a way to identify webbrwser and store static information on the device it is running to be able to identify that particular device later on. Otherwise we cannot assign the weborbiter a unique id in lmce.
- Python competence
- UI Design
- C++ knowledge to implement a dce router plugin.