Preview of new Touch Orbiter UI Capabilities (video demo)

[totallymaxed]

Hi all,

Another pair of short videos showing some last minute features that made it into the iOS Orbiter 2.1 release;

- UI Buttons can open integrated WebKit browser
- Dedicated Cameras button in Tab Bar
- Access to IP cameras using secure encrypted remote access

Enjoy!

http://www.youtube.com/watch?v=-QtNoM83xQM

http://www.youtube.com/watch?v=P4pCuZHucs0

[totallymaxed]

The Dianemo iOS Orbiter v1.2 has been released for Approval to Apple today (7 July). Which means that typically in about 7 days from now it should be available in the iOS App Store. As with previous releases this version is FREE for download by any iOS device owner. Here is a short video showing some last minute cosmetic changes;

http://www.youtube.com/watch?v=5nXoRJ9RaN4

Enjoy!

All the best


Andrew

[rages]

Very nice !!!!
Great Job 

[RayBe]

Looking good, great work!
The thing i am missing a bit are the left-hand alphabet-search-keys, are they going to be implemented in another way?

br,
Raymond

[totallymaxed]

Looking good, great work!
The thing i am missing a bit are the left-hand alphabet-search-keys, are they going to be implemented in another way?

br,
Raymond

We plan to introduce the alpha search in a later update. The code for that under iOS was not finished enough to include and wanted to get the release out.

All the best


Andrew

[RayBe]

Very cool! Thanks a lot.
Will you guys implement other iOs-UI elements in the future as well?
Is your goal to replace the whole (proxy) orbiter-UI with native-OS elements?

Br
Raymond

[totallymaxed]

Very cool! Thanks a lot.
Will you guys implement other iOs-UI elements in the future as well?
Is your goal to replace the whole (proxy) orbiter-UI with native-OS elements?

Br
Raymond

Thanks for your comments :-)

I think you can assume that our ultimate goal is to re-invent the way UI's for LinuxMCE & Dianemo are designed/created/implemented making the whole process more accessible to UI designers. The iOS Touch Orbiter 1.2 and our QT Touch Orbiter is a step along that road and you will see some more enhancements to the Interactive Layer in the near future. However the Interactive Layer is probably just a 'stepping stone' technology - its a fast win in that we can deliver a good level of new capability and to a large extent it does not require any new effort in terms of UI development ie it enhances existing Skins for no additional effort etc. However 'under the hood' we still have all that nasty legacy code being executed and the new proxy_orbiter does an 'on the fly' conversion of some design objects into XML and hands that back to the Touch Orbiter. This approach probably cant be extended to the whole UI though without it becoming another big mess of 'goo' on top of the mess that is the current implementation of Orbiter!

So ultimately something cleaner more extensible and complete is needed and that is likely to be something more like golgoj4's QML based Orbiter approach as it will allow designers to build UI's in QML. However whether we implement this approach or another in future versions of Touch Orbiter is still not decided. What you can be sure of is that we will deliver something in this area and that the Touch Orbiter codebase will be updated - and the iOS App will be part of this too.

All the best


Andrew

[bongowongo]

How does your orbiter project relate to golgoj4's experiments?

[totallymaxed]

How does your orbiter project relate to golgoj4's experiments?

It doesn't really. As i describe in the response above the Interactive Layer in Touch Orbiter 1.2 is probably not a long term solution but it does give us some real usable capability in terms of delivering some more dynamic UI right now.

Golgoj4's approach is a more funder mental re-engineering of the Orbiter and ultimately is probably pretty close to where we think we need to be but its not deliverable today and will need a lot more work before its something that could replace what we have today. So the two work along side one another really delivering new capability now on one hand while the other technology is worked up and completed.

All the best


Andrew

[l3mce]

It doesn't really. As i describe in the response above the Interactive Layer in Touch Orbiter 1.2 is probably not a long term solution but it does give us some real usable capability in terms of delivering some more dynamic UI right now.

Golgoj4's approach is a more funder mental re-engineering of the Orbiter and ultimately is probably pretty close to where we think we need to be but its not deliverable today and will need a lot more work before its something that could replace what we have today. So the two work along side one another really delivering new capability now on one hand while the other technology is worked up and completed.

All the best


Andrew

Hi Andrew... very impressive work. Looks very smooth. Images seem to be loading much quicker now.

I know golgoj4 would appreciate the help reaching the common goal of re-engineering the UI. He is deep in the bowels now, and it is pretty murky in there. I understand you have limited resources to attach to day to day operations/support/development. I know spare time is probably a laughable concept... but clearly the work is overwhelming, and it would be a terrible shame if he drowned when you have such impressive and rare life preservers.

[totallymaxed]

Hi Andrew... very impressive work. Looks very smooth. Images seem to be loading much quicker now.

I know golgoj4 would appreciate the help reaching the common goal of re-engineering the UI. He is deep in the bowels now, and it is pretty murky in there. I understand you have limited resources to attach to day to day operations/support/development. I know spare time is probably a laughable concept... but clearly the work is overwhelming, and it would be a terrible shame if he drowned when you have such impressive and rare life preservers.

Hi,

Thanks. Yes the earlier versions I showed in my videos had a bug in the code that manages how the images are rendered and sometimes images hat had been downloaded were flagged as not available and this slowed things down a fair bit. That bug was squashed ;-).

We're still looking at the best way to deliver better UI technology and better UI design capability while making sure that we can move a future Orbiter to any device that seems appropriate with minimum effort. Golgoj4's work is impressive and we like it a whole lot but we have not come to a decision yet about our direction on this. Whatever we do in this area you can be sure it will be made available to the community under the GPL - that is a given.

Whichever way we go on this golgoj4 can always get some input from us if he needs to.

All the best


Andrew

[totallymaxed]

Just to let everyone know that the Dianemo iOS Orbiter v1.2 has been approved by the Apple iOS App store this evening. So inside the next 24 hours you will see the new App become available on the App store.

All the best


Andrew

[RayBe]

Just to let everybody know, now it IS available

br,
Raymond

[totallymaxed]

Just to let everybody know, now it IS available

br,
Raymond

Yep your right it is now live :-)

Andrew

[RayBe]

Andrew or Uplink, i got into a bit of trouble could one of you help?

i installed
http://deb.linuxmce.org/pluto-proxy-orbiter_2.0.0.44.11071224175_i386.deb
http://deb.linuxmce.org/pluto-website-admin_2.0.0.44.11071224175_i386.deb
and the new Dianemo iOS Orbiter v1.2.

also created a dir: sudo mkdir -p /usr/pluto/orbiter/bits

but the Dianemo iOS Orbiter v1.2 and the existing RoamingOrb are not working anymore

i did: /usr/pluto/bin/Proxy_Orbiter -d 40 -r localhost which gave me:

Code:

Proxy_Orbiter, v.2.0.0.44.11071224175
Visit www.plutohome.com for source code and license information


     =======================|  DirectFB 1.0.1  |=======================
          (c) 2001-2007  The DirectFB Organization (directfb.org)
          (c) 2000-2004  Convergence (integrated media) GmbH
        ------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2008-09-12 19:59)
(!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
    --> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable.
(!) DirectFB/Core: Could not initialize 'system' core!
    --> Initialization error!
Failed initializing SDL: DirectFBCreate: Initialization error!
01 07/14/11 11:34:55.485 X is not running! Starting X and the window manager: /usr/pluto/bin/Start_X.sh <0xb4ee96f0>
1 07/14/11 11:34:58 SetupAudioVideo (server) Starting
1 07/14/11 11:34:58 SetupAudioVideo (server) '
1 07/14/11 11:34:58 SetupAudioVideo (server) DBSetting: S Reboot:  Script Path: /usr/pluto/bin/
1 07/14/11 11:34:58 /usr/pluto/bin/Start_X.sh (server) Starting X server (client: /usr/bin/xfwm4; parms: --compositor=off)
1 07/14/11 11:34:59 /usr/pluto/bin/Start_X.sh (server) X server: backround; AlphaBlending: 0

any help would be much appreciated,
br,
Raymond