Meego (was: Attitude of COOPERATION.)

[totallymaxed]

Thanks, I think I'm getting it !  

Just a last noob question: do you think it makes sense to put Touch Orbiter on a basic netbook, without a touch UI ?
I'm asking this because MeeGo for Netbooks:
* has a huge potential market, right now: http://wiki.meego.com/Devices
* is an easy target

Real touch devices like MeeGo tablets and phones will be important, but much later

Well yes I think it does. Touch Orbiter is in effect the functionality of Web Orbiter 2.0 wrapped up in C++ so that  it can run without the need for a Web Browser to act as a 'container'. We use Web Orbiter's from desktop & laptops a lot in our installations.

Go for it :-)

Andrew

[swift11]

OK, I'll try to find a MeeGo dev;
I'll send him to your Touch Orbiter thread:
http://forum.linuxmce.org/index.php?topic=10583.0

Another solution would be to include Touch Orbiter in the MeeGo Architecture:
http://meego.com/developers/meego-architecture
do you think this would be an acceptable option for these guys ?

Regards,
Olivier

[totallymaxed]

OK, I'll try to find a MeeGo dev;
I'll send him to your Touch Orbiter thread:
http://forum.linuxmce.org/index.php?topic=10583.0

Another solution would be to include Touch Orbiter in the MeeGo Architecture:
http://meego.com/developers/meego-architecture
do you think this would be an acceptable option for these guys ?

Regards,
Olivier

Well re including the Touch Orbiter in the Meego UX layer...that sounds like a big hill to climb as i guess that layer is sanctioned at some level. But making a compatible UX layer App is more like where we should start and finding someone in the Meego world to put that in place would seem possible. The Touch Orbiter is not a complex app to create.

All the best

Andrew

[swift11]

including the Touch Orbiter in the Meego UX layer...that sounds like a big hill to climb as i guess that layer is sanctioned at some level.

It would be a very attractive proposition for the MeeGo team if:
* the code is small , effective and maintained.
* the UI is "MeeGo-like"

Every MeeGo device would be a ready-to-use Orbiter:
this would be a killer-app for the MeeGo project and the LinuxMCE project, of course !  

But if we want Touch Orbiter to be included in MeeGo for Netbooks 1.1 (= commercial launch in october), we should start now !  

Regards,
Olivier

[totallymaxed]

including the Touch Orbiter in the Meego UX layer...that sounds like a big hill to climb as i guess that layer is sanctioned at some level.

It would be a very attractive proposition for the MeeGo team if the code is small , effective and maintained.
Every MeeGo device would be a ready-to-use Orbiter:
this would be a killer-app for the MeeGo project and the LinuxMCE project, of course !  

But if we want Touch Orbiter to be included in MeeGo for Netbooks 1.1 (= commercial launch in october), we should start now !  

Regards,
Olivier

To get an App into the Meego release I imagine is quite a big hurdle to jump over. But the engineering involved in getting Touch Orbiter onto Meego is fairly trivial so I would suggest just getting a Meego Dev interested in getting involved as the first step. Then once we have Touch Orbiter on Meego we can look at the next steps beyond.

All the best

Andrew

[nite_man]

I confuse a bit. We're going to port Orbiter to MeeGo or next release of LinuxMCE will be on MeeGo platform?

[posde]

Michael,

atm it seems some people want to have the touch orbiter running under Meego. In the long term, TSCHAK evaluates moving the whole stack to Meego. imho, the whole stack should be re-engineered to be as platform independent as possible (sans the Orbiter probably)

[nite_man]

Thanks, Posde, for clarification. Personally I like solution with proxy orbiter suggested by Andrew. IMHO it looks more universal then MeeGo port.

[swift11]

We shouldn't move the entire stack to MeeGo: it's not a universal OS:
Intel targets its Atom CPUs, Nokia targets Qualcomm CPUs and AMD (+ATI) is completely out of the picture.
MeeGo is an OS for specific mobile devices.

But we should try to get the Orbiter code into the MeeGo Architecture.
http://meego.com/developers/meego-architecture

The best way to achieve that is to have a LinuxMCE dev:
1) to code a "MeeGo for Netbooks" Orbiter
2) to "sell" his code to the MeeGo team
3) to adapt his code to the MeeGo "look"
4) to adapt his code for the upcoming tablets and phones.

This is a long-term commitment, that can only be achieved by a motivated LinuxMCE dev.
But the rewards will be huge: to have every MeeGo device as a ready-to-use Orbiter is the best possible promotion for the LinuxMCE project !  

Regards,
Olivier

[hari]

We shouldn't move the entire stack to MeeGo: it's not a universal OS:

are *you* going to move anything?

br Hari

[davegravy]

We shouldn't move the entire stack to MeeGo: it's not a universal OS:

are *you* going to move anything?

br Hari

swift11... welcome to the Linuxmce community where you can have the best idea in the world but you won't be listened to until you make significant contributions. For better or for worse, it's very much a meritocracy.

[tschak909]

davegravy, thanks as always for that snarky comment...

The simple fact is, the developers are overextended.

If someone wants something done, they have to do it themselves. This isn't about being listened to.

So please, your comment was superfluous and simply of no constructive use, dispense with it next time.

-Thom

[totallymaxed]

Michael,

atm it seems some people want to have the touch orbiter running under Meego. In the long term, TSCHAK evaluates moving the whole stack to Meego. imho, the whole stack should be re-engineered to be as platform independent as possible (sans the Orbiter probably)

I agree with that too.

Andrew

[tschak909]

My reasoning with evaluating MeeGo as a platform is two fold:

(1) it is a platform intended precisely for the appliance domain.
(2) It wioluld allow us to construct a reference platform of known hardware that will be supported now and in the future, across two current processor architectures, X86 and ARM.

I have not backed down from this assesment, and I am saddened to see that so many see my thoughts as being narrow minded or short sighted. They're not. I am trying to mitigate as many of the flaws inherent in this stack as humanly possible, and I have spent almost two years thinking on this very subject so far,

how about the rest of you?

-Thom

[totallymaxed]

This port of Touch Orbiter was completed in about 5 days with just a little encouragement from me by mihajzm (who is a new Dev here on the Forum). He's done a great job and has not made a great deal of fuss about doing so... he just got on did it. In my opinion we need a few more like him here;

http://forum.linuxmce.org/index.php?topic=10583.msg73082#msg73082

Taking Touch Orbiter to Meego would be a simple task to be frank... and I would like to see someone who is new to this Forum get excited about doing it - and just do it like mihajzm did.

The exciting thing about Touch Orbiter is that we can get outside developers interested in the project quickly without the steep learning curve of developing other aspects of the system - this will hopefully not only generate a whole raft of new device running Touch Orbiter but will also encourage at least a significant number of these new Devs to dig deeper and do more complex contributions later.

All the best


Andrew