Meego (was: Attitude of COOPERATION.)

[tschak909]

We intend to move to 1004 for the immediate future. I am doing research to move the stack to MeeGo.

-Thom

[Enigmus]

I took a quick look at MeeGo.  It looks exciting, but it seems like it would be a lot of work to convert to a new foundation.  However, I trust you would know better then I.

[B34N]

I am doing research to move the stack to MeeGo.

Is it the consensus of LMCE developers that MeeGo will be the open source OS of choice for portable devices in the future? It looks very promising to me but I'm not qualified to make that judgment. I installed 1.0 it on my netbook and it looked ok.

[tschak909]

Let me make this very clear,

at this point, there is no indication of where MeeGo will Go.

I am doing this, as a systems analysis and feasibility research project.

My intention is to present a working system as a proof of concept, and ask for developers to test, review, and to make a decision.

-Thom

[philtrick]

Let me make this very clear,

at this point, there is no indication of where MeeGo will Go.

I am doing this, as a systems analysis and feasibility research project.

My intention is to present a working system as a proof of concept, and ask for developers to test, review, and to make a decision.

-Thom

This is very interesting from a couple of directions:

I think a base like meego will provide a solid platform to build on
The screens and layouts for the handset versions of meego will be invaluable to the project
I have an O2joggler and I am going to try to get meego running on it as a device, but I was thinking that booting gPXE from the Efi and using that to load the joggler as an MD for the bedside table or similar.

(Mind you, that will happen when I get linuxmce working which at the moment is proving to be a bit of a nightmare, but that is the subject of another post....)


Right, that is my 2cents worth, off to sleep!
Phil

[totallymaxed]

Let me make this very clear,

at this point, there is no indication of where MeeGo will Go.

I am doing this, as a systems analysis and feasibility research project.

My intention is to present a working system as a proof of concept, and ask for developers to test, review, and to make a decision.

-Thom

This is very interesting from a couple of directions:

I think a base like meego will provide a solid platform to build on
The screens and layouts for the handset versions of meego will be invaluable to the project
I have an O2joggler and I am going to try to get meego running on it as a device, but I was thinking that booting gPXE from the Efi and using that to load the joggler as an MD for the bedside table or similar.

(Mind you, that will happen when I get linuxmce working which at the moment is proving to be a bit of a nightmare, but that is the subject of another post....)


Right, that is my 2cents worth, off to sleep!
Phil

Why not look at porting Touch Orbiter to the 02joggler? See here for info http://wiki.linuxmce.org/index.php/Touch_Orbiter_-_for_the_CUWIN3500_in-wall_Touch_Panel

This will get you today's Orbiter functionality on the Joggler and in the future we plan to enhance Touch Orbiter so that local UI capabilities of the host device/OS can be integrated eg if the host device/OS support dynamic scrollable lists or any other UI widget these will be part of the UI experience on that device...on other simpler device the Ui experience might be much more spartan & basic.

Anyway getting Touch Orbiter ported to any OS/Dev environment only requires limited knowledge of developing for the target device/OS and no requirement to understand the internals of the Orbiter sources themselves...and we provide full source code for the WinCE 5.0 reference implementation to use as your base.

All the best


Andrew

[swift11]

Let me make this very clear,
at this point, there is no indication of where MeeGo will Go.

Hi all,
This is my first post: let me breefly introduce myself:
I live in Brussels (hence my poor english), I'm an economist and have been a Linux fan for years.

back to the discussion:
The MeeGo option looks very good to me:

* backed by the biggest CPU players: Intel and ARM (I hope AMD will join the party)
* backed by Linaro, a big budget Linux tools player (ARM, IBM, Samsung, ST-Erisson, TI)
http://www.linaro.org/why-linaro/
* MeeGo is Linux, 100% open source
http://www.linuxfoundation.org/lp/page/meego
* for developers: Qt, a cross-platform application and UI framework to target desktops, notebooks, netbooks, tablets and phones
http://qt.nokia.com/

* MeeGo for Netbooks 1.1 will be available in october and deployed in the Intel-ecosytem:
 Asus, Acer, MSI, etc. will have MeeGo netbooks and tablets.
http://www.youtube.com/watch?v=m4vv7yFaqxw&feature=player_embedded
* MeeGo for Handsets 1.1 (Nokia high-end phones) will be available in november-december.
 Nokia is by far the biggest mobile phone manufacturer in the world, but the US market and the high-end segment are Nokia's weak points at the moment. MeeGo phones based on the latest and greatest Qualcomm CPUs and playing nice with the US carriers will remedy this anomaly.

MeeGo's website explains it probably better than me: http://meego.com/
One last thing: Windows dominates the desktop, but Linux will rule the mobile world ! 


Hope this helps,
Olivier

[totallymaxed]

Let me make this very clear,
at this point, there is no indication of where MeeGo will Go.

Hi all,
This is my first post: let me breefly introduce myself:
I live in Brussels (hence my poor english), I'm an economist and have been a Linux fan for years.

back to the discussion:
The MeeGo option looks very good to me:

* backed by the biggest CPU players: Intel and ARM (I hope AMD will join the party)
* backed by Linaro, a big budget Linux tools player (ARM, IBM, Samsung, ST-Erisson, TI)
http://www.linaro.org/why-linaro/
* MeeGo is Linux, 100% open source
http://www.linuxfoundation.org/lp/page/meego
* for developers: Qt, a cross-platform application and UI framework to target desktops, notebooks, netbooks, tablets and phones
http://qt.nokia.com/

* MeeGo for Netbooks 1.1 will be available in october and deployed in the Intel-ecosytem:
 Asus, Acer, MSI, etc. will have MeeGo netbooks and tablets.
http://www.youtube.com/watch?v=m4vv7yFaqxw&feature=player_embedded
* MeeGo for Handsets 1.1 (Nokia high-end phones) will be available in november-december.
 Nokia is by far the biggest mobile phone manufacturer in the world, but the US market and the high-end segment are Nokia's weak points at the moment. MeeGo phones based on the latest and greatest Qualcomm CPUs and playing nice with the US carriers will remedy this anomaly.

MeeGo's website explains it probably better than me: http://meego.com/
One last thing: Windows dominates the desktop, but Linux will rule the mobile world ! 


Hope this helps,
Olivier

Touch Orbiter will run under Meego too. So I would see this as the best development path to take.

Andrew

[swift11]

It would be beneficial to LinuxMCE to have a presence on MeeGo, a high-profile project, to attract new developers.
An example: a small-scale project like "MeeGo Home" (Home automation) on a tablet would be very attractive !  

It could be even hosted here, to keep it simple for a newcomer:  
https://projects.forum.nokia.com/home

If we don't do it, someone else will, it's almost a certainty.
It's one of the biggest problems in open source: people reinventing the wheel ...

http://forum.meego.com/showthread.php?t=715
http://forum.meego.com/showthread.php?t=1010

[totallymaxed]

It would be beneficial to LinuxMCE to have a presence on MeeGo, a high-profile project, to attract new developers.
An example: a small-scale project like "MeeGo Home" (Home automation) on a tablet would be very attractive !  

But the problem is it would not be s 'small' project at all...it would be a very substantial undertaking and one requiring an enormous amount of effort from a team of devs who have a detailed understanding of LinuxMCE.

It could be even hosted here, to keep it simple for a newcomer:  
https://projects.forum.nokia.com/home

Believe me this would not be 'simple' and would certainly not be good newcomer territory.

If we don't do it, someone else will, it's almost a certainty.
It's one of the biggest problems in open source: people reinventing the wheel ...

http://forum.meego.com/showthread.php?t=715
http://forum.meego.com/showthread.php?t=1010

If your up for it why not kick the effort off yourself? No one here would be against it...or hold you back from trying. What I am pointing out is the scale of the task...LinuxMCE is not a single monolithic piece of software...its a very large rambling codebase that has truck loads of dependencies and therefore high complexity. But having said that if you can gather some like minded people alongside you then you can as a group get your heads into the code and create a new branch in svn and get started.

All the best

Andrew

[swift11]

The basic idea would be to engage a dialogue with developers interested in Home Automation in the MeeGo Forum.
I certainly couldn't do this: I'm not a programmer and my english is not good enough.  

Like you said, LinuxMCE is a "very large rambling codebase that has truck loads of dependencies and therefore high complexity."
So even if a young developer wants to do "his own thing", that's not a problem, just keep in touch.  

Regards,
Olivier

[totallymaxed]

The basic idea would be to engage a dialogue with developers interested in Home Automation in the MeeGo Forum.
I certainly couldn't do this: I'm not a programmer and my english is not good enough.  

Like you said, LinuxMCE is a "very large rambling codebase that has truck loads of dependencies and therefore high complexity."
So even if a young developer wants to do "his own thing", that's not a problem, just keep in touch.  

Regards,
Olivier

Hi Olivier,

I'd love to see some Meego devs build a version of our Touch Orbiter for Meego portable devices... this could be done really very easily indeed (you dont need any detailed understanding of LinuxMCE to implement Touch Orbiter) and would provide the starting point for bringing Meego handheld devices to a point where they could be used as touch based Orbiters (ie the user interface to the system).

See here for info & source code; http://wiki.linuxmce.org/index.php/Touch_Orbiter_-_for_the_CUWIN3500_in-wall_Touch_Panel

All the best


Andrew

[swift11]

yep, excellent idea !  

But I read in the wiki that the Orbiter software already works for Maemo (= +- MeeGo) and the Nokia N800/N900
http://wiki.linuxmce.org/index.php/Nokia_N800

Maybe the best option is to wait for MeeGo 1.1 in october: we'll have loads of netbooks, tablets and phones and a mature OS !  
All these devices (even Symbian phones) will be compatible with Qt.

[totallymaxed]

yep, excellent idea !  

But I read in the wiki that the Orbiter software already works for Maemo (= +- MeeGo) and the Nokia N800/N900
http://wiki.linuxmce.org/index.php/Nokia_N800

Maybe the best option is to wait for MeeGo 1.1 in october: we'll have loads of netbooks, tablets and phones and a mature OS !  
All these devices (even Symbian phones) will be compatible with Qt.

Yes there is an Nokia N800/N810 Orbiter - and there has been for a long time too. The problem is that the N800/Maemo Orbiter uses the full Orbiter codebase (ie whats running on an MD) but really makes no use of about 85-90% of that code. This makes it way too complex for the task it performs and also makes it a very big job porting it to new platforms or keeping it working on existing ones.

Thats why Touch Orbiter is so exciting - it light 7 simple because it uses proxy_orbiter (running on the Core) and this makes the code running on the target device very simple and easy to support/port. This brings the added advantage that someone coming into LinuxMCE from outside the community can get into Touch Orbiter without having to study the whole LinuxMCE codebase for a year first before writing a line of code! With Touch Orbiter the only skills you need are ones relating to the device/OS you are porting Touch Orbiter too.

Because of this simplicity we believe that Touch Orbiter is a perfect way to encourage development not only lots of new control devices but importantly a way to get more Devs to try LinuxMCE for the first time

All the best



Andrew

[swift11]

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