as i said before, it works. you just make a Size definition for the iphone.
Well, I was looking for a realworld review from someone evidently about to try it. I'm impressed by the Web Orbiter (that it mirrors the real Orbiter, its proxy architecture, that it's responsive), so I was looking to see how well it performs on an iPhone to meet their use case they started this thread about.
The Web Orbiter is a bit of a hack that has been around since the early Pluto days. Basically the UI1 screen is rendered as a complete clickable map and the whole screen is re-rendered every time you interact with the UI. It needs a fast and low latency connection. Having said that it does work on pretty much any web enabled device (I have not found anything it wont work on so far) so it is useful from that perspective.
Is it literally regenerated from the UI1, so whenever developers change UI1 the Web Orbiter interface automatically "just works"? So there's no chance of diverging the Web Orbiter GUI from the UI1 GUI? If so, that's really excellent.
And for mobiles that support Bluetooth PAN
, Web Orbiter puts an orbiter on any mobile.