What devices are you running Web orbiter 2.0 on?

[totallymaxed]

Andrew.......

Thnx once again.... I can Kick myself.....
After all this time my weborbiter must have been working....
I installed firefox on my laptop and VIOLA!!!!! its working. 

The IE7 seemed to be the problem as it is still not working...... but who cares hey... typical MS.... 

Karel

Actually i should also 'kick myself' as I should have diagnosed the problem for you :-(...yep IE is not supported currently due to weirdness in the way it handles some of the Javascript code we use in Web Orbiter. This same code works fine in all other browsers we've tested against to date...but not for some reason in IE!

Check out the Web Orbiter 2.0 wiki page for the latest news/changes/browser support etc - http://wiki.linuxmce.org/index.php/Web_Orbiter_2.0

Also please add some brief notes to the Web Orbiter 2.0 Wiki page on your experiences with using Web Orbiter 2.0 on any devices/browsers you use.

All the best


Andrew

[purps]

Andrew,

Got it working on a Nintendo DSi, was certainly usable.

Wiki has been updated.

Cheers,
Matt.

Hi Matt,

Hey thats great :-)... very cool indeed!

I think it would be great see some pics added to the wiki page of the WO running on the DSi (and any of the other hardware people have success with too)

Thanks for working on the DSi :-)

All the best


Andrew

My mate and his DSi are coming round tonight, so will have more of a play with resolutions/skins and try to get some photos as well. Will do my Nokia XpressMusic at the same time.

[b4rney]

Andrew, don't want to hijack the thread but ..... should Web Orbiter 2.0 be implemented for the N800 as per the old wiki entry with the CHT installers ... and configured as 'This device uses a wi-fi connection'?
http://wiki.linuxmce.com/index.php/Nokia_N800#Set_Up_the_N800_Orbiter_in_LinuxMCE

Or is there a new method?
Barney

[totallymaxed]

Andrew, don't want to hijack the thread but ..... should Web Orbiter 2.0 be implemented for the N800 as per the old wiki entry with the CHT installers ... and configured as 'This device uses a wi-fi connection'?
http://wiki.linuxmce.com/index.php/Nokia_N800#Set_Up_the_N800_Orbiter_in_LinuxMCE

Or is there a new method?
Barney

That Wiki page describes how you configure your Core to work with standard N800/810 Orbiter (you need to install the N800/810 Orbiter package). It has nothing to do with the old Web Orbiter or indeed the new Web Orbiter 2.0 either.

The new Web Orbiter 2.0 does work well on the N800/810 however and if you are planning to use it on these devices then use the steps described in the Web orbiter 2.0 Wiki page - http://wiki.linuxmce.org/index.php/Web_Orbiter_2.0 to set it up.

All the best


Andrew

[b4rney]

Thanks for that.

Do you have a preferred method? I'm tempted to stick with the old package. Have you compared speed etc?
Barney

[totallymaxed]

Thanks for that.

Do you have a preferred method? I'm tempted to stick with the old package. Have you compared speed etc?
Barney

We are moving all of our standalone Orbiter over to either the Web Orbiter 2.0 or the Touch Orbiter as this means that updating the system with new screens etc only involves an update to the proxy_orbiter - the Orbiter running on the device does not need any updates at all. So this is a pretty big advantage.

Secondly over time we expect that we will extend proxy_orbiter to allow it to support more advanced UI components on individual hardware devices. An example of this would be an upgraded proxy_orbiter that would allow the use of dynamically scrollable UI lists etc on iPhone's or Android phones for media browsing or possibly dynamically updating slider & on/off controls on these devices etc etc.

So I would suggest trying Web Orbiter on your N800.

All the best

Andrew

[maverick0815]

has anyone tried it on the htc hd2? So far no matter what resolution I put (currently n770) it never fits on the screen. Opera always zooms in...if I zoom out again, I can see that there is some cropping on the right side too.

[totallymaxed]

has anyone tried it on the htc hd2? So far no matter what resolution I put (currently n770) it never fits on the screen. Opera always zooms in...if I zoom out again, I can see that there is some cropping on the right side too.

Whats the resolution of the display? Whatever it is you need to create a resolution to match that.

Andrew

[purps]

has anyone tried it on the htc hd2? So far no matter what resolution I put (currently n770) it never fits on the screen. Opera always zooms in...if I zoom out again, I can see that there is some cropping on the right side too.

I believe the N770 resolution is the correct one to use for that phone. Maverick, is it a setting on the phone itself perhaps, landscape vs portrait?

[purps]

Thanks for that.

Do you have a preferred method? I'm tempted to stick with the old package. Have you compared speed etc?
Barney

We are moving all of our standalone Orbiter over to either the Web Orbiter 2.0 or the Touch Orbiter as this means that updating the system with new screens etc only involves an update to the proxy_orbiter - the Orbiter running on the device does not need any updates at all. So this is a pretty big advantage.

Secondly over time we expect that we will extend proxy_orbiter to allow it to support more advanced UI components on individual hardware devices. An example of this would be an upgraded proxy_orbiter that would allow the use of dynamically scrollable UI lists etc on iPhone's or Android phones for media browsing or possibly dynamically updating slider & on/off controls on these devices etc etc.

So I would suggest trying Web Orbiter on your N800.

All the best

Andrew

This is certainly not a complaint, but I do have to comment. As good as the web orbiter 2.0 is, I am surprised you are recommending its use over the standard N800 orbiter? One thing that springs straight to mind is volume control - I find it slightly cumbersome on my phone (using web orbiter), but quite responsive on the standard N800 orbiter. Is this an issue with my phone, or with the web orbiter? I suppose I should at least try the web orbiter on my N800 for a direct comparison, but would be interested in any other opinions.

[totallymaxed]

Thanks for that.

Do you have a preferred method? I'm tempted to stick with the old package. Have you compared speed etc?
Barney

We are moving all of our standalone Orbiter over to either the Web Orbiter 2.0 or the Touch Orbiter as this means that updating the system with new screens etc only involves an update to the proxy_orbiter - the Orbiter running on the device does not need any updates at all. So this is a pretty big advantage.

Secondly over time we expect that we will extend proxy_orbiter to allow it to support more advanced UI components on individual hardware devices. An example of this would be an upgraded proxy_orbiter that would allow the use of dynamically scrollable UI lists etc on iPhone's or Android phones for media browsing or possibly dynamically updating slider & on/off controls on these devices etc etc.

So I would suggest trying Web Orbiter on your N800.

All the best

Andrew

This is certainly not a complaint, but I do have to comment. As good as the web orbiter 2.0 is, I am surprised you are recommending its use over the standard N800 orbiter? One thing that springs straight to mind is volume control - I find it slightly cumbersome on my phone (using web orbiter), but quite responsive on the standard N800 orbiter. Is this an issue with my phone, or with the web orbiter? I suppose I should at least try the web orbiter on my N800 for a direct comparison, but would be interested in any other opinions.

In our tests we can see no significant performance degradation when moving from say the N800 Orbiter to Web Orbiter 2.0. You also then avoid the need to re-build the Orbiter binary whenever new screens or other changes are made to the system - just update proxy_orbiter once and your done. An alternative approach would be to build a version of Touch Orbiter for your devices as this also uses proxy_orbiter as its backend. However Web Orbiter 2.0 is easier as it involves no software installation on your control device at all.

All the best


Andrew

[b4rney]

Have now got the web orbiter running on my N800. It runs very nicely.

As purps points out the volume is ever so slightly slower to respond to repeated presses, but overall I like it a lot. Perhaps the volume could be programmed to increment several steps per click. I guess this would be done in javascript.

Got full screen by following this guide:
http://www.tech-recipes.com/rx/2671/nokia_n800_hide_web_browser_toolbar_full_screen_mode/

The scroll bar on the right was distracting at first but I quickly got used to it.

Excellent work guys. Thank you.
Barney

[totallymaxed]

Have now got the web orbiter running on my N800. It runs very nicely.

As purps points out the volume is ever so slightly slower to respond to repeated presses, but overall I like it a lot. Perhaps the volume could be programmed to increment several steps per click. I guess this would be done in javascript.

Got full screen by following this guide:
http://www.tech-recipes.com/rx/2671/nokia_n800_hide_web_browser_toolbar_full_screen_mode/

The scroll bar on the right was distracting at first but I quickly got used to it.

Excellent work guys. Thank you.
Barney

Volume rate changes really need to be changed in the device template not the Web Orbiter. Glad to here WO is working well for you.

All the best

Andrew

[b4rney]

Changed my AV device template (Denon amp ruby codes) to increment 4x with a 0.2s sleep in between each step. This means my amp now increases/decreases volume by 2db per single click rather than 0.5db per click.

I can recommend this change for users with similar problems with repeated key presses.
Barney

[RayBe]

a tip i would like to share,
saves somebode hopefully some time (took me a hour to figure out )
DO NOT select Normal Horizontal (16:9) in the UI dropdown menu.
if u do so and u press any button u will get a black screen and nothing happens.

HTH

br,
Raymond