hi, > -----Original Message----- > From: qt-components-bounces+leo.cunha=nokia....@qt.nokia.com > [mailto:qt-components-bounces+leo.cunha=nokia....@qt.nokia.com] On > Behalf Of Hartz Henrik (Nokia-MS-Qt/Oslo) > Sent: Wednesday, December 15, 2010 10:56 AM > To: thiago.lace...@openbossa.org > Cc: qt-compone...@trolltech.com > Subject: Re: [Qt-components] MeeGo Components themebridge dependency > removal > > Is it just me or is removing the implicit conversion from libmeegotouch > CSS pixel independant metrics a mistake? IMO we could abstract this > into a QML Item with properties. If we use libmeegotouch under the hood > until further notice, that would be an implementation detail. Or is > this the last feature that imposes a direct libmeegotouch dependancy?
yes, we want to remove the dependency on libmeegotouch completely. cheers, // leo > > Henrik > > > On Dec 9, 2010, at 6:47 PM, ext Thiago Lacerda wrote: > > > Ok. > > Thanks for the feedback guys. For now I am going to use fixed > pixel sizes. > > Regards > > > On Wed, Dec 8, 2010 at 9:02 AM, <vesa.ranta...@nokia.com> wrote: > > > Hi, > > Density-independent pixels (naturally together with some > other > scalability-handling measures) would be worth considering. > > Conceptually, both DIPs and other units of physical > measurement, such as > millimeters, are the same but DIPs tend to be in a nice > integer scale. > 64dp x 40dp is just nicer than 10mm x 6.4mm. > > Br, > > - Vesa. > > On 08.12.2010 11:41, "ext Kenneth Rohde Christiansen" > > <kenneth.christian...@gmail.com> wrote: > > >In Android and in WebKit we use DIPs (device independent > pixels) for > >some things, such as the viewport meta tag and the - > webkit-pixel-ratio > >media features which applies to CSS and which is query- > able from > >JavaScript. > > > >A nice resource explaining this: > > >http://developer.android.com/guide/practices/screens_support.htm > l > > > >Kenneth > > > >On Tue, Dec 7, 2010 at 10:21 PM, Thiago Lacerda > ><thiago.lace...@openbossa.org> wrote: > >> Hi, > >> Currently I am working on getting rid of the previous > themebridge > >>dependency > >> of MeeGo components. > >> I order to accomplish that we have to get the values of > each style at > >>the > >> .css files and hardcode it on the QML source. Hence, one > question that > >>rose > >> was regarding the conversion between the component's > dimensions. > >> For instance, at mbuttonstyle.css we have: > >> minimum-size: 10mm 6.4mm; > >> QML only support pixel units and libmeegotouch used to > do the dirty job > >>of > >> converting milimeters to pixels, taking into account the > device display > >> resolution, etc... > >> For now, I am using a constant (10) to multiply the > values. After > >>looking at > >> some display resolutions and dimensions. > >> Libmeegotouch do such conversion looking at the device > profile. > >> What do you think that might be a nice solution for > that? Maybe a > >> Qt::<functionToConvert>? Make QML support millimeters? > Establish a > >>constant > >> value to convert from millimeters to pixel? > >> Regards > >> -- > >> Thiago de Barros Lacerda > >> OpenBossa - INdT > >> > > > _______________________________________________ > Qt-components mailing list > qt-compone...@trolltech.com > http://lists.trolltech.com/mailman/listinfo/qt-components > > > > > > -- > Thiago de Barros Lacerda > OpenBossa - INdT > > <ATT00001..txt> > _______________________________________________ Qt-components mailing list Qt-components@qt.nokia.com http://lists.qt.nokia.com/mailman/listinfo/qt-components
