Anyone interested in touch orbiter auto-configuration should really follow along with http://svn.linuxmce.org/trac.cgi/ticket/857 That's the ticket documenting the development/changes Merkur and I are working to implement which makes it relatively quick and painless to incorporate this feature.
I've been following along, great stuff so far. I plan to try it. I have heard from others working on a touch orbiter and they will likely try to use this as well. Thank you so much for all the work you and Merkur have been doing.
To help us all re-orientate ourselves and get this thread back on-track again... could you summarise where your at or what your planning for Auto configuring new Touch Orbiters? As step by step description what should happen would be useful. This will also help anyone developing a Touch Orbiter variant to get their head around what needs to be added (if anything) to their Apps.
Well my initial thoughts of the process went a little like this:
1) check if device exists/is defined in database, based on say a .conf file (like maemo) or a MAC (like padorbiter or windows orbiter)
2) if device exists in database then connect to it's defined port #, if it fails proceed to 3) else proceed to 9)
3) detect the native display resolution of the device
4) ask the user if this is a new orbiter and therefor if a new device should be created (a la padorbiter)
5) create the new device -> proxy_orbiter, perhaps an orbiter to go with it if creating proxy_orbiter doesn't do this
6) query the user and set orbiter template attributes for: Language, Room, User, available Skin, etc...
7) query user for display resolutions that are <= native resolution of device and set template attributes
9) use... if selected resolution == native resolution would trigger a fullscreen display (no window dressing)
and then 10) should be 'profit' or something like that but I havn't figured out the origin of this little inside joke yet to know why.... <:-P
I may have missed something there but that was the general idea of it. I'm hoping for something fairly generic that runs (or at least compiles) easily on multiple systems: mini2440, maemo(s), debian. The functionality exists in Orbiter and I wanted to mimic the behaviour/code in Orbiter that padorbiter uses to auto-configure. My issue was, more or less, with the backend code required to implement the auto-creation of proxy_orbiter as I havn't really had a chance to explore the dce commands that Orbiter uses to do this. los93sol seems to have documented these commands somewhat in the code referenced in the ticket above (thanks!). I'm am really busy right now but I am going to try to use them.
The maemo build env isn't too difficult to setup. I don't know if you are happier on a windows or linux box. There is a VM image available ...
Then from the scratchbox env you can either symlink to your existing LinuxMCE src or do an svn co from within. I have a script that builds the other necessary libs for the orbiter, I'll attach it here once I get home.
p.s. Oops, just noticed this is under Touch Orbiter - if this discussion continues maybe we should break it out under a PadOrbiter topic?
Thanks coley. Yes we should start a new thread for this. I'll try to set up a build-env and see what happens. I'd love to access any scripts/changes you already have. You could PM or e-mail me what you have (phenigma at hotmail dot you know) and I'll post a new thread with my progress.