The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Architecture
(New page: = Mer Architecture = Mer architecturally derives from the MeeGo 1.3 architecture. The big changes in MeeGo 1.3 compared to MeeGo 1.2 was systemd inclusion, which simplified much of the st...) |
(→Mer Architecture) |
||
| Line 7: | Line 7: | ||
Another difference from MeeGo is that in Mer, we do not contain hardware adaptations and reference user interfaces. Architecturally, hardware adaptations are plugging into abstract 'adaptation interfaces' of the Mer Core, which means that when you couple the Mer Core with a hardware adaptation, you get a booting system. If you add a user interface of your selection on top, you have a working device with UI. | Another difference from MeeGo is that in Mer, we do not contain hardware adaptations and reference user interfaces. Architecturally, hardware adaptations are plugging into abstract 'adaptation interfaces' of the Mer Core, which means that when you couple the Mer Core with a hardware adaptation, you get a booting system. If you add a user interface of your selection on top, you have a working device with UI. | ||
| − | The reasoning for no hardware adaptations or reference user interfaces stems from experiences within MeeGo, where hardware adaptations were often completely out of sync with the release schedule of the Core and the reference user interfaces reflected badly on the MeeGo Core's actual abilities, along with release pressures giving a lesser quality Core, | + | The reasoning for no hardware adaptations or reference user interfaces stems from experiences within MeeGo, where hardware adaptations were often completely out of sync with the release schedule of the Core and the reference user interfaces reflected badly on the MeeGo Core's actual abilities, along with release pressures giving a lesser quality Core, UIs and hardware adaptations. |
| + | |||
| + | == Essentials == | ||
| + | |||
| + | === Base Essentials === | ||
| + | |||
| + | === D-Bus === | ||
| + | |||
| + | == Software Management == | ||
| + | |||
| + | === Package Manager === | ||
| + | |||
| + | == Communications == | ||
| + | |||
| + | === ConnMan === | ||
| + | |||
| + | === Cellular Framework === | ||
| + | |||
| + | === Bluetooth === | ||
| + | |||
| + | === Proxy Management === | ||
| + | |||
| + | == Graphics == | ||
| + | |||
| + | === X11 === | ||
| + | |||
| + | === OpenGL ES === | ||
| + | |||
| + | === Font management === | ||
| + | |||
| + | === Input Adaptation === | ||
| + | |||
| + | === Display & Graphics Adaptation === | ||
| + | |||
| + | === Imaging === | ||
| + | |||
| + | === Fonts === | ||
| + | |||
| + | == System == | ||
| + | |||
| + | === Startup Services === | ||
| + | |||
| + | === Sensor Framework === | ||
| + | |||
| + | === System Control === | ||
| + | |||
| + | === Context Framework === | ||
| + | |||
| + | == Multimedia == | ||
| + | |||
| + | === GStreamer === | ||
| + | |||
| + | === PulseAudio === | ||
| + | |||
| + | === Codecs === | ||
| + | |||
| + | === ALSA === | ||
| + | |||
| + | == Qt == | ||
| + | |||
| + | === Qt === | ||
| + | |||
| + | === Qt Mobility === | ||
| + | |||
| + | === Qt WebKit === | ||
| + | |||
| + | === Qt Messaging Framework === | ||
Revision as of 20:48, 23 March 2012
Contents |
Mer Architecture
Mer architecturally derives from the MeeGo 1.3 architecture. The big changes in MeeGo 1.3 compared to MeeGo 1.2 was systemd inclusion, which simplified much of the startup process and services handling. Mer architecture was based around the need for a minimal Core that could be the basis of many different kinds of products.
As such, in the transformation of MeeGo to Mer, only packages and dependencies that served a practical purpose for the criteria of booting up to a Xorg+Qt qmlviewer with connectivity and ability to expand upon that was left in. This meant a much smaller set of packages were put together and hence your favourite package will probably not be part of Mer.
Another difference from MeeGo is that in Mer, we do not contain hardware adaptations and reference user interfaces. Architecturally, hardware adaptations are plugging into abstract 'adaptation interfaces' of the Mer Core, which means that when you couple the Mer Core with a hardware adaptation, you get a booting system. If you add a user interface of your selection on top, you have a working device with UI.
The reasoning for no hardware adaptations or reference user interfaces stems from experiences within MeeGo, where hardware adaptations were often completely out of sync with the release schedule of the Core and the reference user interfaces reflected badly on the MeeGo Core's actual abilities, along with release pressures giving a lesser quality Core, UIs and hardware adaptations.
