How did you do your translations ?

Did you take the "en" folder under languages, create a new "es" folder and translated the constants in these .lang.php files ?

If yes, just zip the folder and get it to me. I will be happy to include it into next build for you ...

Foxi352

It's with the new multilingual backend works.

Can you post me the first 20 lines or your config.inc.php please. Will check a.s.a.p.

I suppose the build has been done while checking in, and that not all files of your install are up to date ....

You know, posting bugs like this is already a great help. A greater help would be opening a ticket for it in http://svn.linuxmce.org :-)

Cheers,

Serge

If ever someone that posted here is still alive :-)

I am working on an official french translation and i have finished the major and important parts of it. If someone wants to test / debug / help please reply.

Serge

WhateverFits: http://blog.projectnibble.org/2010/08/08/how-ubuntus-broken-bluetooth-support-came-to-be/

WhateverFits: Thank you for reporting this. I can confirm the bluez-utils part and i opened ticket #1144 for this.
As a temporary fix postinst of proxy-orbiter first tests if bluez-utils exists. If not it ignores the bluetooth part.

We will investigate bluetooth package changes and come up with a definitive fix.

Meanwhile, after next package build, proxy-orbiter should install again ...

$DeviceID was already fixed by Uplink ...

Ok, then i think the easiest, and the proposed solution for Beeker is to do an sqlCVS update and then simply choose the iPhone resolution with standard horizontal UI.

Just to verify: The iPhone sizes (both) are in 810. If you don't see them, do a sqlCVS update and they should appear.

However, the UI style has nothing to do with size. Each UI has its own set of buttons and screens, i.e. PDA UI has different screens that Normal Horizontal.

Strange. I have these resolutions @ home, and i have a standard 0810 install and only do my aptitude dist-upgrades from time to time. I did not manually add them ...

Uh ? I thought on a full regen all screens would be generated regardless of orientation and size ?

Why does he not have the iphone and iphone 4 in his selection ? Could an apt-get update / upgrade fix this ?

The PDA vertical style has quite a few missing screens, iirc

As far as I know...and i think posde is confirming this in the post above...currently these resolutons are not in the 0810 builds as standard. The iPad resolution is as it is a normal desktop resolution that has been supported for ages. Each resolution has to be added specifically... they are not autogenerated based on what you add to the device template. So currently these new resolutions need to be added manually...


Andrew

Uh ? I thought on a full regen all screens would be generated regardless of orientation and size ?

Why does he not have the iphone and iphone 4 in his selection ? Could an apt-get update / upgrade fix this ?

The PDA vertical style has quite a few missing screens, iirc

Well, i have "480x320 (iPhone)" and "960x640 (iPhone 4)" in my list. Which version of lmce are you using ?

If not, try the 320 x 480 and down on the screen set the "Normal horizontal (3:4) to "PDA (4:3 vertical style)". Did never try this, but it may work ...

Thanks Serge much appreciated so I should create another proxy orbiter to match the iPhone......one stupid question there is 320 x 480 not 480 x 320 so how do we deal with that

Cheers
Beeker

Hi !

Normally this happens when you have a wrong resolution set up for your iPhone.

That means for example when you have an iPhone 4 the touches are send in 960 x 640 resolution, but if your orbiter is set to iphone 3 resolution of 480 x 320 the touches are not properly recognized.

This is of course also true for the reverse example, meaning having an iphone 3 and settings orbiter resolution to iphone 4.

Please check ...

Cheers,

Serge

Well done to Foxi352
Great App just need help with a small issue I have set it up and it displays on the iPhone as per the attached picture except when I try to select anything on the screen I get a rotating circle but nothing changes no matter what button I touch................any help much appreciated

Beeker

Hi guys,

Just a quick note to let you know V 1.0.2 is available on app store now. There are no improvements but it does run on older iPod's with iOS 3.1.3 now. I know there are many lying around that could probably serve and be reused now :-)

Another version with many new features is currently in dev. We will keep you informed as we progress ....

Serge

Theres only 1 thing I need to do to make it work and I can't even do that!

"When inside you have at least to set the server IP and the server port of your proxy orbiter"
Where do I find out this info?
-The IP is that of the core? Router=127.0.0.1 or Internal= 192.168.80.1 (Eth0:1) or External=192.168.1.102 dhcp(eth0)?

192.168.80.1 is the default core IP, unless you want to be able to use RoamingOrb outside of your home network (via 3G). In that case you need to use your public internet IP which you can find by visiting http://www.whatsmyip.org/ from your CORE.

-Where do I find the port?

Have you created a weborbiter in the past? If not, follow the wiki instructions.

If you have, go to your webadmin. Show Devices Tree>Expand CORE>Expand Generic Web Device>Click on Generic Proxy Orbiter. Under device data, look for "Listen Port". By default this is 3461.

Cheers.

I think one of the next top priorities for the app is the automatic orbiter generation. We will keep contact with los93sol and try to get that working asap...

Serge

Like you say, when you open reopen the app it has to reconnect to the proxy_orb which is why the splash-screen gets displayed. I'm wondering if the reconnect can be bypassed somehow.

When RoamingOrb is backgrounded maybe it can tell the core "i've been backgrounded" so that the core doesn't think it's dead when it stops responding to pings (I'm assuming this is how the protocol currently works). When re-opening RoamingOrb, the app can resume functioning as if it was never closed (maybe it just does a screen refresh).

Again, I don't know the details of the communication protocol, so this may be impossible without major structural changes. Thanks for listening to my ideas!

Hmmm ... When you start the app it opens a connection to the core and that connection keeps open until you exit the app, or until it is broken (example: quick reloading the dce router).

What i probably could do is backgrounding the app and keeping the connection open (not sure if that is possible as long as i don't have a corresponding device). But you have to keep in mind that the app can also be used over 3G where disconnections are not rare.

Anyhow, i will investigate in that direction as soon as i have a multitasking enabled device ....

Another factor is that on a 3G connection where the user may have limitations on their mobile dataplan they might leave the App open but in the background and chew up a lot of their data plan allowance - without realising it. On the other hand the amount of data we're moving when the app is idle and no screen changes are happening is pretty tiny so this may not really be an issue. On a Wifi connection this is not a problem of course.

I still think the big win with multi-tasking is the ability for a future version of the App to alert you, when its in the background, to some system event...eg the door bell was pressed, A security alert has been triggered...if the App is sitting their it can alert the user and bring the event to the users attention etc.

All the best


Andrew

I am investigating with push notifications for that, so even if your app is not started you could be notified of such events.

Concerning the data plan: I am atm evaluating another technique together with uplink. We try to use weborbiter_command and weborbiter_image instead of directly speak to the proxy_orb plugin.
This will then work on standard http port (future remote access) and this may touch battery life. It will also make backgrounding easier as you simply don't poll while in background, but you don't have to disconnect and reconnect everytime.
I am just concerned if this have the same performance. I will do first tests on weekend and let you know.

Serge