Thread: MeeGo Reconstructed - a plan of action and direction for MeeGo
View Single Post
abill_uk is offline abill_uk
2011-10-06 , 09:27
Banned | Posts: 3,412 | Thanked: 1,043 times | Joined on Feb 2010
#39
Originally Posted by erendorn View Post
Yes it seems you never really understood what it was, and still ranted so much about it.
In my understanding, MeeGo was a common core:
- entirely open source (like, 100%).
- with reference UI for the targetted platforms. These were never meant to be consumer UI. Just an example of what can be done, and a base framework to test your app in for developpers.

Then, the MeeGo Hardware Adaptation project was adding the Nxxx specific drivers and tuning for having the core booting and running correctly on these devices, without care for the UI.

Finally, the MeeGo CE project (different project but same people) was adding a UI on the Hardware Adaptation project, and bundling some application with the goal of making it "daily use ready". This was at first based on the reference handset UI, but there was discussions at some point to use the tablet UI, and they could have used/devellopped a completely different one in the future.

And after that, there was the abill_uk project, complaining that MeeGo (from netbook to IVI) was failling because the MeeGo CE project was not progressing rapidly enough for him.

In order to stop logicless people from ranting, the Mer project is now without reference UI
Not much of this actually makes sense to me because it seems all self inflicting.

Meego is common core you say but what "core" was it? was it a UI/GUI or was it an OS?.

If it is supposed to be an OS then it must have all source available for the device this OS is to be written for OR are you saying it will be a "common" OS?.

My god you got some work to do if you are to make this a common OS because you then have to incorporate every single driver for every single CPU and component within any device that has been manufactured, the same as Windows is capable of being programmed into any computer as it has all the needed drivers incorperated within its entirety as a multi OS for any device/computer.

"Then, the MeeGo Hardware Adaptation project was adding the Nxxx specific drivers and tuning for having the core booting and running correctly on these devices, without care for the UI."

This is non logical because without care of the UI it cannot be accomplished and this kind of dumfounds me.

"Finally, the MeeGo CE project (different project but same people) was adding a UI on the Hardware Adaptation project, and bundling some application with the goal of making it "daily use ready". This was at first based on the reference handset UI, but there was discussions at some point to use the tablet UI, and they could have used/devellopped a completely different one in the future."

What is the "hardware adaption project" ? is it OS or UI/GUI ?.

What i am trying to esablish here is knowledge of the actual understanding of the meego "build" and just what is it actually meant to be.