[MeeGo-dev] Should I use MeeGo Touch Framework or Qt Framework for MeeGo tablets
kevron_m_rees at linux.intel.com
Thu Mar 3 13:38:13 PST 2011
On Thu, 2011-03-03 at 00:08 +0200, karoliina.t.salminen at gmail.com wrote:
> >> > Let's make difference, duicontrolpanel is just an application that is made with
> >> > MtF UI toolkit ads is many other MeeGo application. Before MtF UI toolkit
> >> > can be removed, all of them need to be rewritten with Qt Components.
> >> I have been already thinking of duicontrolpanel2 (maybe we can name it
> >> now properly mxxxx).
> > If you are thinking of creating a settings/control panel application,
> > there is already one in the Tablet UX (that I understand will be open
> > sourced in a 'couple weeks'). It supports loading 'applets' similarly
> > to how duicontrolpanel did.
> > That said, there's always need for individual settings applets that do
> > various things ;).
> Sure there is, but I was just thinking of adding one more layer and separating
> the UI.
> E.g. display applet now has brightness slider, but what if you wanted to place
> brightness slider elsewhere than in the applet (this happened, there
> have been several rounds of new design
> decisions of where different settings should be placed). This idea is
> to give freedom to
> not limit certain settings to certain applets but provide additional
> layer of flexibility.
I'm not sure what you mean here. Without going into too much detail
about how Tablet Settings works, individual settings applets can be a
mix-match of c++ and qml where the QML is just the UI layer. A quick
example is the connection settings where the backend is a c++ library
that talks to connman (connman-qt) and the QML applet is just the UI
presentation of that information. The great thing about QML is it
allows you the flexibility to change the look without having to mess
with any of the backend code. Is this what you are talking about?
> I will check tablet ux, but I have a feeling it may not give the
> solution we were after but rather is more like the
> current generation of duicontrolpanel.
> With Qt Components being the UI abstraction, this would not come even
> with any significant
> complication, quite in contrary for the applet developers. I have not
> yet finalize the idea, but
> I have been just prototyping with the Qt components + C++ to get idea
> how the api could work.
I don't doubt your idea is good, but it may be advisable to wait and
check out what the meego/tablet settings offers and maybe build on that
with your ideas.
> Best Wishes
> P.S. Our datetime applet looks horrible on MeeGo because it uses
> placeholder on place of closed source
> time picker and date picker. Making datetime applet really great would
> be a low hanging fruit.
> Would someone be interested innovating a community replacements for
> those components?
I suggest putting things like this on temporary hold until the tablet ux
opens up (unless it's an educational exercise, in which case, by all
means continue). After it opens, it will be clear where the gaps are
and aren't. This will reduce duplication of effort.
More information about the MeeGo-dev