Here's is a short video of the work my colleague Uplink has been doing on re-engineering the Touch Orbiter to allow it to display dynamic UI elements - currently we support scrolling datagrids... with other dynamic UI elements to follow eg sliders and other dynamic controls. This video was shot in Apple's xCode Development systems device simulator. This is not a mockup I might add this is real code running in the xCode simulator - I will upload some video of this version running on an iPad next week. I will be posting some more video demo's of the new Touch Orbiter in the next few days;

Once the new proxy_orbiter is installed and a Touch Orbiter 2.1 has been installed on your devices then any current Orbiter screen that uses standard datagrids will automatically get translated into a Dynamic datagrid on your device - this requires no changes to be made in HAD. It maybe though that some UI screens might benefit from a re-design around datagrids however ie the User or Room's screen so that large numbers of Users/Rooms could be accommodated by making the list scroll vertically.

We expect to have the source code for the new proxy_orbiter and a QT based Touch Orbiter 2.1 available for download in about two weeks or so (we were hoping to have this available earlier but we are in the build-up to the CEDIA London Home Technology Event in late June). An updated Dianemo iOS Orbiter 2.1 will be released in early July and will be a free download from Apple's iOS App Store.

The loading time of thumbnails and grid elements - is this expected to be typical for the final product, or is this delay introduced by the simulator?

The xCode simulator is definitely a performance bottleneck so you can expect a real device to perform considerably better. But the other even more important factor that I did not mention is that the Touch Orbiter in the demo video is connecting to a remote NerveCentre via our encrypted ssh based remote assistance platform as a test of using the new Orbiter features remote from your home. This obviously exacts some performance penalties... approx 15-20% slower depending on how the remote Touch Orbiter is connecting to the NC.

great work, looks amazing!can't wait to be able to use it myself will it be implemented into lmce 810 and 1004?

br,Raymond

I would hope so. It will be standard in Dianemo 10.10 and later releases though. We hope that Forum members will take the QT Touch Orbiter 2.1 and use it, as they did with Touch Orbiter, as an example of how to build versions for other devices & OS's.

Here is another video of the latest Dianemo iOS Touch Orbiter but this time its running on a real iPad1 and has undergone another round of bug fixes and improvements since the last video. This video include an attempt at a voice-over by me...Hmmm... I hate hearing my own voice!...and 'attempt' is all you can call it really :-)

We hope to release the source code for the companion proxy_orbiter 2.1 together with the source for a QT based version of the new Touch Orbiter to use as a guide and working example as soon as possible. I hope this will be in the next 10 days or so.

You'll notice that at several points in the video the Orbiter does not do whats its told... ie there is a lack of response. This is something we're still trying to debug in the App. Also I should point out and important point about what your seeing in this video... the Skin in question is our standard UI skin that ships with every Dianemo 10.10 system currently. This Skin was not changed or adapted in anyway for this demo video. The new Touch Orbiter will work automatically with any standard UI1 skin and will automatically convert any static data-grid into a dynamic scrollable on screen object. No adaption of the Skin is necessary as the new Orbiter will overlay the new dynamic elements over the old static ones. This means that all your existing skins should work 'out of the box' with the new Orbiter;