Nah, I hardly spent much time on it, I just grabbed the code that mihajzm submitted and made a few changes.So far I find it way more responsive than the native one. Where is the source for the native one? I can't find it in SVN.

Because the native orbiter has no current maintainer, and the native orbiter has the draw back of needing to be rebuild, whenever a screen is added.

At least, that could be an answer...

We 100% agree with that sentiment...not having to update the native Nokia Orbiter is a big reason...also if you analyse what we do with the native Orbiter its just 'bloat-ware' and completely unnecessary.

The native Orbiter has its merits for MDs. Apart from that, I don't see any advantage at the moment. This might change, once interaction other than press is implemented.

One thing the Touch Orbiter should do, is the ability to create a device for itself, i.e. the first time it gets executed, it prompts the user for the Orbiter to use, or, if none of the existing Orbiter devices fits the bill, have the option to create a new Orbiter device.

I'm with the Touch Orbiter on this one. I rebuilt the native Orbiter for the N810 last time I added a screen and it's been broken since. For some reason, although I didn't do anything wrong, the launcher fails to start the Orbiter, even though the Orbiter itself works when started from the console.

Except being a "native" Orbiter, what extra work does the native Orbiter do on the N800 compared to the Touch Orbiter? It speaks DCE. And MySQL. And pulls images from the server and sends clicks back And that's it. Please let me know if I'm ignorant, otherwise on this basis alone I'd rather run the "native" bit on the Core (Proxy_Orbiter) and just do the image and click bits on the tablet (Touch Orbiter).

Hmmm... well if the MID device has an uPnP renderer app we could just use that...even if the Touch Orbiter was also running on the same device. Touch Orbiter would need minimal to zero changes to make that work...we're already working on bits of this now in fact. So if your MID in the near future had a suitable app installed it would just work.

UPnP keeps proving to be the standard that everybody adopts, but nobody can agree on ANYTHING, at the expense of ever increasing complexity of plumbing... I mean seriously guys, have you actually PUT together a UPnP system?

UPnP keeps proving to be the standard that everybody adopts, but nobody can agree on ANYTHING, at the expense of ever increasing complexity of plumbing... I mean seriously guys, have you actually PUT together a UPnP system?

with control points?media renderers?

media storage units?

and USED IT?

it's a god damned nightmare!

but whatever.

-Thom

Yes we have... we are doing just that now...which is what i alluded to in my previous post. We have media renderers being controlled and we already have a basic control point working and being driven from the Orbiter.

...but this is off topic. If you want to debate the merit or lack it then lets start a new thread to debate that. This thread is meant for the discussion of topics related to implementing Touch Orbiter and various ports of that code that forum members are actively involved in.

Foxi352 has been implementing a version of Touch Orbiter for IOS and we have been testing it here for several weeks on iPhone3g, iPhone3GS, iPhone4, iPod Touch & iPad. Foxi352 has done a great job of implementing the first true IOS Orbiter App. I think that Foxi352 plans to submit it to the App Store soon (he may have already done so in fact). So keep checking back there to see if the RoamingOrb App has appeared.