Orbitor requirements

[wizard]

From what I read the orbitor appears a "dumb" screen set to browse to a Core or Media Director URL (nuances here) but could not find the requirements...obviously ActiveX is not one.  Is a Flash plugin?  Kiosk mode?  DT370 is available on Linux as are other purposed kiosk-URL platforms for command and control but want to insure interoperability before posting final release.

[tschak909]

Basically, the orbiter can run under these platforms:

* Windows 98/XP/Vista using the Windows Orbiter Software
* Windows CE
* Nokia 770/N800
* Linux (netbooting a system as a Media Director)
* Cisco 7970 (uses a proxy orbiter)
* any Web Based device with Javascript support (The Web Orbiter - Also a Proxy orbiter)

For anything that there is not a native port, you can try the Web Based orbiter by using the following URL, after creating a new orbiter of type Generic Proxy Orbiter inside the Orbiters Wizard:

http://192.168.80.1/pluto-admin/weborbiter.php

There is detailed setup information inside the wiki about this particular device, and in the absence of other supported options, it works quite well.

-Thom

[wizard]

Thus when the need arises to have an elegant locked down, URL-purposed touchscreen, we offer an in-wall 8.4" TFT.  Includes steel pre/post drywall backbox, power supply and updateable Linux/Utonium firmware.  See http://www.convergentliving.com/index.php?option=com_docman&task=doc_download&gid=213&Itemid=80

[tschak909]

yup, the Web Orbiter could run there out of the box, but an orbiter could be built specifically for it as well, all the Linux Orbiter needs is SDL and the Pluto libraries. It is very thin in that respect. (if it can run on my teeny little Nokia 770, it can run on anything)

native orbiters perform MUCH faster than the proxy web orbiter. (and without the page refresh action.)

to answer your question further, only Javascript is needed.

-Thom