>> > 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 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.

Best Wishes
Karoliina

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?
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

Reply via email to