[Meego-architecture] On MeeGo UX components

[Paul Plaquette]

Hi all,

Recently, a collection of software components  was released on gitorious 
meego-ux repository.
(http://meego.gitorious.org/meego-ux)

Most Applications in there are written using QML for their UI.
Some are fully written in QML, using or not some javascript.
Some are Qt Quick C++ applications embedding QML scripts for their UI.

Among these components, there are several applications (email, launcher 
calculator...), UX QML components, a UX daemon,  a UX sharing component 
and a mlite library.

I have a few questions on these components:

    *

      Are these components addressing  all variations of Meego UX for
      every Meego form factor devices (automotive to handset, and
      including tablets)?

    *

      Are all components relevant? or only some "system" components are
      to be available to all Meego form factors?
      (from my experience an application have to be adapted to the
      screen size and other devices specific hardware and  using
      context, for example a tablet form factor is different from a
      phone form factor)

    *

      Will all UX QML components be used for every Meego form factors
      (handset, ivi, tablets...) ?

    *

      Does the meego-ux-deamon similar to Meego handset SystemUI?
      managing status bar indicators, passive notifications (by passive
      I mean no user interaction)

    *

      Will UX sharing component be available to all Meego form factor
      (handset, ivi, tablets...) ?

    *

      mlite is a component that grants access to "still MTF written
      system components" from a QML application. Among available classes
      one, MConfig, is there to access to gConf settings. In my
      understanding, with the move to QML, I thought we were supposed to
      use QT Mobility and for gConf settings there is a set of classes
      (Publish and subscribe).

      In this case of dual choice are we supposed to use in priority a
      Meego component available in mlite or to use the Qt or QML or Qt
      Mobility component?

    *

      Will  mlite component be available to all Meego form factors
      (handset, ivi, tablets...) ?

    *

      Is there somewhere documents that are describing Meego
      Architecture in details?

Cordially,
Paul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.meego.com/pipermail/meego-architecture/attachments/20110420/e08eab6e/attachment.html>