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.
All I could think to improve it would be to turn it to AJAX, so only the GUI areas that actually change reload - not the whole page, with the HTTP Expires, If-Modified-Since and other caching headers skipping refreshes entirely on those section. If the Web GUI were split into widgets, instead of whole screen, with interactive widgets including all their visual states (eg. buttons offer both default and "pressed" looking images), and some javascript for immediate feedback for interaction (ie. click a button and it immediately appears depressed, while the browser sends the click to the server, then returns the message to the clicked button itself, whose Javascript decides whether to refresh just the button, or the whole page). But as "quick & dirty", the current functionality is perfectly adequate.
And for mobiles that support
Bluetooth PAN, Web Orbiter puts an orbiter on any mobile.
