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".
  • Architecture - Mer Wiki
    etc Revision as of 17 56 27 April 2012 Contents 1 Mer Architecture 1 1 Essentials 1 1 1 Central Libraries 1 1 2 GNU utilities 1 1 3 Base Essentials 1 1 4 D Bus 1 2 Software Management 1 2 1 Package Manager 1 3 Communications 1 3 1 ConnMan 1 3 2 Cellular Framework 1 3 3 Bluetooth 1 3 4 Proxy Management 1 4 Graphics 1 4 1 X11 1 4 2 OpenGL ES 1 4 3 Font management 1 4 4 Input Adaptation 1 4 5 Display Graphics Adaptation 1 4 6 Imaging 1 4 7 Fonts 1 5 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 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 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 File Architecture Gnuutilities Context png 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

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


  • Architecture - Mer Wiki
    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 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 File Architecture Gnuutilities Context png 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 D Bus For inter process communication Mer utilizes D Bus as messaging bus Software Management Package Manager 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

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

  • Architecture - Mer Wiki
    http www gnu org software ncurses ncurses http www gnu org software gzip gzip http www gnu org software gawk gawk http www gnu org software findutils findutils http www gnu org software readline readline etc Mer standard build time and run time configuration utilizes GNU utilities such as http www gnu org software bash bash http www gnu org software coreutils coreutils http www gnu org software sed sed http www gnu org software ncurses ncurses http www gnu org software gzip gzip http www gnu org software gawk gawk http www gnu org software findutils findutils http www gnu org software readline readline etc Revision as of 17 55 27 April 2012 Contents 1 Mer Architecture 1 1 Essentials 1 1 1 Central Libraries 1 1 2 GNU utilities 1 1 3 Base Essentials 1 1 4 D Bus 1 2 Software Management 1 2 1 Package Manager 1 3 Communications 1 3 1 ConnMan 1 3 2 Cellular Framework 1 3 3 Bluetooth 1 3 4 Proxy Management 1 4 Graphics 1 4 1 X11 1 4 2 OpenGL ES 1 4 3 Font management 1 4 4 Input Adaptation 1 4 5 Display Graphics Adaptation 1 4 6 Imaging 1 4 7 Fonts 1 5 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 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

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

  • Architecture - Mer Wiki
    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 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 File Architecture Gnutilities Context png 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 D Bus For inter process communication Mer utilizes D Bus as messaging bus Software Management Package Manager 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

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

  • Architecture - Mer Wiki
    OpenGL ES Image Architecture Opengles Context png frame none alt alt text Graphics OpenGL ES in context 3D accelerated Software built against Mer should be utilizing the http www khronos org opengles 2 X OpenGL ES 2 0 and http www khronos org egl EGL native platform interface APIs Mer Core provides the open source http mesa3d org Mesa 3D Graphics Library containing OpenGL ES 2 0 and EGL libraries to link and build against which can at image build time be replaced with device specific OpenGL ES 2 0 EGL implementations 3D accelerated Software built against Mer should be utilizing the http www khronos org opengles 2 X OpenGL ES 2 0 and http www khronos org egl EGL native platform interface APIs Mer Core provides the open source http mesa3d org Mesa 3D Graphics Library containing OpenGL ES 2 0 and EGL libraries to link and build against which can at image build time be replaced with device specific OpenGL ES 2 0 EGL implementations Line 69 Line 87 Font management Font management Image Architecture Fontmanagement Context png frame none alt alt text Graphics Font Management in context Input Adaptation Input Adaptation Line 75 Line 95 Imaging Imaging Image Architecture Imaging Context png frame none alt alt text Graphics Imaging in context Fonts Fonts Image Architecture Fonts Context png frame none alt alt text Graphics Fonts in context Mer provides a minimum of freely distributable fonts the http www freedesktop org wiki Software CJKUnifonts CJKUni fonts http www droidfonts com Droid fonts https fedorahosted org liberation fonts Liberation fonts Mer provides a minimum of freely distributable fonts the http www freedesktop org wiki Software CJKUnifonts CJKUni fonts http www droidfonts com Droid fonts https fedorahosted org liberation fonts Liberation fonts Line 83 Line 108 Startup Services Startup Services Image Architecture Startupservices Context png frame none alt alt text System Startup Services in context Sensor Framework Sensor Framework System Control System Control Image Architecture Systemcontrol Context png frame none alt alt text System System Control in context Mer utilizes the http www freedesktop org wiki Software systemd systemd system and service manager for Linux This approach is much different from typical SysV init scripts but is also more suitable for mobile systems due to on demand starting of daemons Mer utilizes the http www freedesktop org wiki Software systemd systemd system and service manager for Linux This approach is much different from typical SysV init scripts but is also more suitable for mobile systems due to on demand starting of daemons Latest revision as of 18 49 27 April 2012 Contents 1 Mer Architecture 1 1 Essentials 1 1 1 Central Libraries 1 1 2 GNU utilities 1 1 3 Base Essentials 1 1 4 Linux utilities 1 1 5 D Bus 1 2 Software Management 1 2 1 Package Manager 1 3 Communications 1 3 1 ConnMan 1 3 2 Cellular Framework 1 3 3 Bluetooth 1 3 4 Proxy Management 1 4 Graphics 1 4 1 X11

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

  • Architecture - Mer Wiki
    D Bus 1 2 Software Management 1 2 1 Package Manager 1 3 Communications 1 3 1 ConnMan 1 3 2 Cellular Framework 1 3 3 Bluetooth 1 3 4 Proxy Management 1 4 Graphics 1 4 1 X11 1 4 2 OpenGL ES 1 4 3 Font management 1 4 4 Input Adaptation 1 4 5 Display Graphics Adaptation 1 4 6 Imaging 1 4 7 Fonts 1 5 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 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 Essentials Central Libraries Mer utilizes EGLIBC 2 15 as it s central C Library with Linaro GCC 4 6 as toolchain GNU utilities 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 D Bus For inter process communication Mer utilizes D Bus as messaging bus Software Management Package Manager Mer utilizes the RPM package manager as backend for the Zypper package manager which handles repositories and fetching RPMs and looking

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

  • Architecture - Mer Wiki
    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 Essentials Central Libraries Mer utilizes EGLIBC 2 15 as it s central C Library with Linaro GCC 4 6 as toolchain GNU utilities 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 D Bus For inter process communication Mer utilizes D Bus as messaging bus Software Management Package Manager 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

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

  • Architecture - Mer Wiki
    0 and http www khronos org egl EGL native platform interface APIs Mer Core provides the open source http mesa3d org Mesa 3D Graphics Library containing OpenGL ES 2 0 and EGL libraries to link and build against which can at image build time be replaced with device specific OpenGL ES 2 0 EGL implementations 3D accelerated Software built against Mer should be utilizing the http www khronos org opengles 2 X OpenGL ES 2 0 and http www khronos org egl EGL native platform interface APIs Mer Core provides the open source http mesa3d org Mesa 3D Graphics Library containing OpenGL ES 2 0 and EGL libraries to link and build against which can at image build time be replaced with device specific OpenGL ES 2 0 EGL implementations Line 65 Line 87 Font management Font management Image Architecture Fontmanagement Context png frame none alt alt text Graphics Font Management in context Input Adaptation Input Adaptation Line 71 Line 95 Imaging Imaging Image Architecture Imaging Context png frame none alt alt text Graphics Imaging in context Fonts Fonts Image Architecture Fonts Context png frame none alt alt text Graphics Fonts in context Mer provides a minimum of freely distributable fonts the http www freedesktop org wiki Software CJKUnifonts CJKUni fonts http www droidfonts com Droid fonts https fedorahosted org liberation fonts Liberation fonts Mer provides a minimum of freely distributable fonts the http www freedesktop org wiki Software CJKUnifonts CJKUni fonts http www droidfonts com Droid fonts https fedorahosted org liberation fonts Liberation fonts Line 79 Line 108 Startup Services Startup Services Image Architecture Startupservices Context png frame none alt alt text System Startup Services in context Sensor Framework Sensor Framework System Control System Control Image Architecture Systemcontrol Context png frame none alt alt text System System Control in context Mer utilizes the http www freedesktop org wiki Software systemd systemd system and service manager for Linux This approach is much different from typical SysV init scripts but is also more suitable for mobile systems due to on demand starting of daemons Mer utilizes the http www freedesktop org wiki Software systemd systemd system and service manager for Linux This approach is much different from typical SysV init scripts but is also more suitable for mobile systems due to on demand starting of daemons Latest revision as of 18 49 27 April 2012 Contents 1 Mer Architecture 1 1 Essentials 1 1 1 Central Libraries 1 1 2 GNU utilities 1 1 3 Base Essentials 1 1 4 Linux utilities 1 1 5 D Bus 1 2 Software Management 1 2 1 Package Manager 1 3 Communications 1 3 1 ConnMan 1 3 2 Cellular Framework 1 3 3 Bluetooth 1 3 4 Proxy Management 1 4 Graphics 1 4 1 X11 1 4 2 OpenGL ES 1 4 3 Font management 1 4 4 Input Adaptation 1 4 5 Display Graphics Adaptation 1 4 6 Imaging 1 4 7 Fonts 1 5 System 1 5 1 Startup Services

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