archive-org.com » ORG » M » MERPROJECT.ORG

Total: 820

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • File:Architecture Packman Context.png - Mer Wiki
    at that time Date Time Thumbnail Dimensions User Comment current 18 38 27 April 2012 599 394 35 KB Stskeeps Talk contribs Edit this file using an external application See the setup instructions for more information File usage The following page links to this file Architecture Retrieved from https wiki merproject org wiki index php title File Architecture Packman Context png oldid 1430 Views File Discussion View source History Personal

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=File:Architecture_Packman_Context.png&printable=yes (2016-02-01)
    Open archived version from archive


  • Changes related to "File:Architecture Startupservices Context.png" - Mer Wiki
    Show last 50 100 250 500 changes in last 1 3 7 14 30 days Hide minor edits Show bots Hide anonymous users Hide logged in users Hide my edits Show new changes starting from 17 10 1 February 2016 Namespace all Main Talk User User talk Mer Wiki Mer Wiki talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Invert selection Associated

    Original URL path: https://wiki.merproject.org/wiki/Special:RecentChangesLinked/File:Architecture_Startupservices_Context.png (2016-02-01)
    Open archived version from archive

  • File:Architecture Systemcontrol Context.png - Mer Wiki
    a date time to view the file as it appeared at that time Date Time Thumbnail Dimensions User Comment current 18 47 27 April 2012 837 213 24 KB Stskeeps Talk contribs Edit this file using an external application See the setup instructions for more information File usage The following page links to this file Architecture Retrieved from https wiki merproject org wiki index php title File Architecture Systemcontrol Context

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=File:Architecture_Systemcontrol_Context.png&oldid=1444 (2016-02-01)
    Open archived version from archive

  • File:Architecture Systemcontrol Context.png - Mer Wiki
    appeared at that time Date Time Thumbnail Dimensions User Comment current 18 47 27 April 2012 837 213 24 KB Stskeeps Talk contribs Edit this file using an external application See the setup instructions for more information File usage The following page links to this file Architecture Retrieved from https wiki merproject org wiki index php title File Architecture Systemcontrol Context png oldid 1444 Views File Discussion View source History

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=File:Architecture_Systemcontrol_Context.png&printable=yes (2016-02-01)
    Open archived version from archive

  • Architecture - Mer Wiki
    System 1 5 1 Startup Services 1 5 2 Sensor Framework 1 5 3 System Control 1 5 4 Context Framework 1 6 Multimedia 1 6 1 GStreamer 1 6 2 PulseAudio 1 6 3 Codecs 1 6 4 ALSA 1 7 Qt 1 7 1 Qt 1 7 2 Qt Mobility 1 7 3 Qt WebKit 1 7 4 Qt Messaging Framework edit 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 edit Essentials edit Central Libraries Essentials Central Libraries in context Mer utilizes EGLIBC 2 15 as it s central C Library with Linaro GCC 4 6 as toolchain edit GNU utilities Essentials GNU utilities in context Mer standard build time and run time configuration utilizes GNU utilities such as bash coreutils sed ncurses gzip gawk findutils readline etc For the utilities making it into run time images we try to avoid GPLv3 versions In the future it will be possible to utilize busybox as a replacement for run time to solve this issue better edit Base Essentials Essentials Base Essentials in context edit Linux utilities Essentials Linux utilities in context edit D Bus Essentials D Bus in context For inter process communication Mer utilizes D Bus as messaging bus edit Software Management edit Package Manager Software Management Package Manager in context Mer utilizes the RPM package manager as backend for the Zypper package manager which handles repositories and fetching RPMs and looking for available updates etc edit Communications edit ConnMan Mer utilizes the ConnMan connection manager for managing internet connections edit Cellular Framework Mer utilizes the oFono telephony stack edit

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=Architecture&diff=prev&oldid=1446 (2016-02-01)
    Open archived version from archive

  • Architecture - Mer Wiki
    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 Essentials Central Libraries Essentials Central Libraries in context Mer utilizes EGLIBC 2 15 as it s central C Library with Linaro GCC 4 6 as toolchain GNU utilities Essentials GNU utilities in context Mer standard build time and run time configuration utilizes GNU utilities such as bash coreutils sed ncurses gzip gawk findutils readline etc For the utilities making it into run time images we try to avoid GPLv3 versions In the future it will be possible to utilize busybox as a replacement for run time to solve this issue better Base Essentials Essentials Base Essentials in context Linux utilities Essentials Linux utilities in context D Bus Essentials D Bus in context For inter process communication Mer utilizes D Bus as messaging bus Software Management Package Manager Software Management Package Manager in context Mer utilizes the RPM package manager as backend for the Zypper package manager which handles repositories and fetching RPMs and looking for available updates etc Communications ConnMan Mer utilizes the ConnMan connection manager for managing internet connections Cellular Framework

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=Architecture&direction=prev&oldid=1446 (2016-02-01)
    Open archived version from archive

  • Architecture - Mer Wiki
    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 Essentials Central Libraries Essentials Central Libraries in context Mer utilizes EGLIBC 2 15 as it s central C Library with Linaro GCC 4 6 as toolchain GNU utilities Essentials GNU utilities in context Mer standard build time and run time configuration utilizes GNU utilities such as bash coreutils sed ncurses gzip gawk findutils readline etc For the utilities making it into run time images we try to avoid GPLv3 versions In the future it will be possible to utilize busybox as a replacement for run time to solve this issue better Base Essentials Essentials Base Essentials in context Linux utilities Essentials Linux utilities in context D Bus Essentials D Bus in context For inter process communication Mer utilizes D Bus as messaging bus Software Management Package Manager Software Management Package Manager in context Mer utilizes the RPM package manager as backend for the Zypper package manager which handles repositories and fetching RPMs and looking for available updates etc Communications ConnMan Mer utilizes the ConnMan connection manager for managing internet connections Cellular Framework Mer utilizes the oFono telephony stack Bluetooth Communications Bluetooth in context Mer utilizes the BlueZ Bluetooth

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=Architecture&oldid=1446&printable=yes (2016-02-01)
    Open archived version from archive

  • All public logs - Mer Wiki
    18 40 27 April 2012 Stskeeps Talk contribs marked revision 1434 of page Architecture patrolled 18 39 27 April 2012 Stskeeps Talk contribs marked revision 1432 of page Architecture patrolled 18 33 27 April 2012 Stskeeps Talk contribs marked revision 1429 of page Architecture patrolled 18 31 27 April 2012 Stskeeps Talk contribs marked revision 1427 of page Architecture patrolled 18 30 27 April 2012 Stskeeps Talk contribs marked revision 1426 of page Architecture patrolled 17 58 27 April 2012 Stskeeps Talk contribs marked revision 1421 of page Architecture patrolled 17 56 27 April 2012 Stskeeps Talk contribs marked revision 1419 of page Architecture patrolled 17 56 27 April 2012 Stskeeps Talk contribs marked revision 1418 of page Architecture patrolled 17 55 27 April 2012 Stskeeps Talk contribs marked revision 1417 of page Architecture patrolled 17 52 27 April 2012 Stskeeps Talk contribs marked revision 1416 of page Architecture patrolled 17 49 27 April 2012 Stskeeps Talk contribs marked revision 1414 of page Architecture patrolled 17 48 27 April 2012 Stskeeps Talk contribs marked revision 1413 of page Architecture patrolled 08 25 1 April 2012 Stskeeps Talk contribs marked revision 1275 of page Architecture patrolled 08 14 1 April 2012 Stskeeps Talk contribs marked revision 1274 of page Architecture patrolled 08 10 1 April 2012 Stskeeps Talk contribs marked revision 1273 of page Architecture patrolled 08 09 1 April 2012 Stskeeps Talk contribs marked revision 1272 of page Architecture patrolled 08 08 1 April 2012 Stskeeps Talk contribs marked revision 1271 of page Architecture patrolled 08 07 1 April 2012 Stskeeps Talk contribs marked revision 1270 of page Architecture patrolled 08 03 1 April 2012 Stskeeps Talk contribs marked revision 1269 of page Architecture patrolled 08 01 1 April 2012 Stskeeps Talk contribs marked revision 1268 of page Architecture patrolled

    Original URL path: https://wiki.merproject.org/wiki/index.php?title=Special:Log&page=Architecture (2016-02-01)
    Open archived version from archive