I just got my hands on a WebDT 366 GX and I'm pretty sure its the sameone Ive seen on the videos. Seems like the ultimate remote, but the link on the wiki is down and I couldn't find a link here so I figured I ask to see if someone knew of a working like to the WebDT366 orbiter image.
Another approach you could look at would be to install some flavor of Linux on the DT366 and install a reasonably modern Firefox or WebKit based browser too. Next grab the new Web Orbiter from svn and install that on your Core. Create a new Web Orbiter in Web Admin, setup its screen size etc to suit the DT366 and point the DT366's browser at http://192.168.80.1/pluto-admin/weborbiter.php
and your in business.
We're using the new Web Orbiter on iPad's, iPod Touches, iPhone's and the N800 & N8100 too as well as desktop & laptops. From a performance perspective its as fast as a full Orbiter in our tests and sometimes faster (mainly based on Nokia testing).
An alternative approach we are working on now is to not use a Web Browser at all - an 'Un-Web Orbiter' in effect! In this case we are creating a very lightweight little app that pulls in the png/jpeg's using a socket interface to the dcerouter/proxy_orbiter. We are testing this approach on an old in-wall WinCE touchscreen to see what issues we hit. Once we have done a little more work on this we will write up a Wiki page and make our source available in svn on this approach so that anyone can use our experiences to build an Orbiter for pretty much any piece of hardware that has a touchscreen.
One big advantage of both of the above approaches is that as the system acquires new UI screens etc over time you only have to add support for these once in the proxy_orbiter and then all of your Web Orbiters automatically get the updated UI screens :-)
I'll update this thread with news on the above asap... in the meantime post any questions here and i will try to answer them.
All the best