Hi,
A little while ago Lars and I proposed to introduce physical units in the QML
language for use in QtQuick. The idea was to make it easier to write user
interfaces that adapt to different display resolutions by "pinning" your UI to
physical dimensions. For example you could say
Image {
I like it!
Some questions though:
* Does (2) include coverage for cases like 5cm ?
* Could we have a solution for writing `width: 90%` instead of `width:
parent.width * 0.9` as well?
Regards,
Konstantin
2016-02-18 14:50 GMT+04:00 Hausmann Simon :
> Hi,
>
> A little while ago Lars and I proposed
Simon
From: Ирина Flora
Sent: Thursday, February 18, 2016 11:57
To: Hausmann Simon
Cc: development@qt-project.org
Subject: Re: [Development] Scalable UIs in QtQuick (take 2)
I like it!
Some questions though:
* Does (2) include coverage for cases like 5cm ?
* Could we have a solutio
y, February 18, 2016 11:57
>To: Hausmann Simon
>Cc: development@qt-project.org
>Subject: Re: [Development] Scalable UIs in QtQuick (take 2)
>
>I like it!
>
>
>Some questions though:
>* Does (2) include coverage for cases like 5cm ?
>* Could we have a solution for writing
2016-02-18 12:50 GMT+02:00 Hausmann Simon :
> (1) In order to make it really easy to scale "logical" pixels without having
> to introduce your own context property or factor in a .qml file that you
> multiply everywhere, we could turn the regular "pixels" in QtQuick into truly
> logical pixels t
Hi
so (1) is what happens on iOS/OSX retina displays already right?
and (2) lets you turn it off?
Question then would be: would you ever need to mix?
If not, then having a global/window switch would be a lot easier than putting
px everywhere…
And if you do want to mix, but mostly use px, then se
On Thu, Feb 18, 2016 at 11:50 AM, Hausmann Simon
wrote:
>I recall was that this would seem like a nice feature on paper but in practice
>people create their resolution independent interfaces using the current
>"pixels" and a scale factor that they introduce in a qml file or as a context
>property
> -Original Message-
> From: Development [mailto:development-
> bounces+mitch.curtis=theqtcompany@qt-project.org] On Behalf Of Nikita
> Krupenko
> Sent: Thursday, 18 February 2016 12:36 PM
> To: development@qt-project.org
> Subject: Re: [Development] Scalable U
> On 18 Feb 2016, at 12:35, Nikita Krupenko wrote:
>
> 2016-02-18 12:50 GMT+02:00 Hausmann Simon :
>> (1) In order to make it really easy to scale "logical" pixels without having
>> to introduce your own context property or factor in a .qml file that you
>> multiply everywhere, we could turn t
Yet another question: when we write Item { id: item; width: 5cm }, what
would item.width return? value expressed in logical pixels?
Konstantin
2016-02-18 15:05 GMT+03:00 Sorvig Morten :
>
> > On 18 Feb 2016, at 12:35, Nikita Krupenko wrote:
> >
> > 2016-02-18 12:50 GMT+02:00 Hausmann Simon <
>
18, 2016 13:20
To: Sorvig Morten
Cc: Qt Project Development Mailing-List
Subject: Re: [Development] Scalable UIs in QtQuick (take 2)
Yet another question: when we write Item { id: item; width: 5cm }, what would
item.width return? value expressed in logical pixels?
Konstantin
2016-02-18 15:05
Op 18/02/2016 om 11:50 schreef Hausmann Simon:
Hi,
A little while ago Lars and I proposed to introduce physical units in the QML language
for use in QtQuick. The idea was to make it easier to write user interfaces that adapt to
different display resolutions by "pinning" your UI to physical d
On Thu, Feb 18, 2016 at 10:50:22AM +, Hausmann Simon wrote:
> What do you think?
>
that it's a bit silly that we're having this discussion *yet again*. ;)
http://thread.gmane.org/gmane.comp.lib.qt.devel/6572/focus=6807
i find the point about using arcminutes as a truly device independent
unit
> On Thu, Feb 18, 2016 at 10:50:22AM +, Simon Hausmann wrote:
>> What do you think?
Oswald Buddenhagen replied:
> that it's a bit silly that we're having this discussion *yet again*. ;)
> http://thread.gmane.org/gmane.comp.lib.qt.devel/6572/focus=6807
I was amused that the discussion related t
Am 18.02.2016 um 11:50 schrieb Hausmann Simon:
> A little while ago Lars and I proposed to introduce physical units in
the QML language for use in QtQuick. The idea was to make it easier to
write user interfaces that adapt to different display resolutions by
"pinning" your UI to physical dimens
I'm just evaluating mobile development with Qt 5.6Beta,
qt.labs.controls, Android, Material
and have set Qt::AA_EnableHighDpiScaling
now it would be cool to "think" in cm or mm
for my device (BlackBerry PRIV, Android 5.1.1)
with 544 ppi, where devicePixelRatio (scaling factor) is 3.5
would be mo
Le jeudi 18 février 2016 à 14:20 +0100, Oswald Buddenhagen a écrit :
> On Thu, Feb 18, 2016 at 10:50:22AM +, Hausmann Simon wrote:
> > What do you think?
> >
> that it's a bit silly that we're having this discussion *yet again*. ;)
> http://thread.gmane.org/gmane.comp.lib.qt.devel/6572/focus
On Thu, Feb 18, 2016 at 11:50 AM, Hausmann Simon
wrote:
> Hi,
>
> A little while ago Lars and I proposed to introduce physical units in the QML
> language for use in QtQuick. The idea was to make it easier to write user
> interfaces that adapt to different display resolutions by "pinning" your U
2016-02-19 0:08 GMT+02:00 Dominik Haumann :
> Interestingly, I once wrote a Value class [1] that does exactly this.
> It allows to have
> constructs like this:
>
> Value v1(2, Unit::Centimeter);
> Value v2 = Value::fromString("1in)"; // see also: toString()
> Value v3 = v1 * v2; // Restult is 4.45
> On 18 Feb 2016, at 13:05, Sorvig Morten
> wrote:
>
>>
>> On 18 Feb 2016, at 12:35, Nikita Krupenko wrote:
>>
>> 2016-02-18 12:50 GMT+02:00 Hausmann Simon :
>>> (1) In order to make it really easy to scale "logical" pixels without
>>> having to introduce your own context property or factor
> On 18 Feb 2016, at 15:24, Welbourne Edward
> wrote:
>
> To meet all the actual use cases, we need three different *kinds* of
> size for things:
> * fraction of the available display area - good for top-level
>sub-division of the space an app has at its disposal to work in;
> * physical
> On 18 Feb 2016, at 11:50, Hausmann Simon
> wrote:
>
> Hi,
>
> A little while ago Lars and I proposed to introduce physical units in the QML
> language for use in QtQuick. The idea was to make it easier to write user
> interfaces that adapt to different display resolutions by "pinning" your
> On 19 Feb 2016, at 10:44, Gunnar Sletta wrote:
>
>
> One obvious usecase which always comes back to haunt is when those logical
> units need to be translated to actual pixels, such as when dealing with
> graphics. Up until some time ago, Something::size() was enough to decide the
> pixel d
Shawn said:
> So maybe the best way to design the visual aspect of most applications
> is to use font-based units (like the em space) for physical sizes, but
> for touch UIs, to also use physical measurements as a minimum.
> e.g. width: Math.max(7mm, 3em) - will it be possible, or can we have
> nic
Am 19.02.16 um 18:27 schrieb Welbourne Edward:
>> The user should choose the text size,
> Indeed - ideally as a device setup action that configures a
> device-global parameter that all apps get to work with. All font sizes
> should be specified in terms of the user-selected "comfortable size to
>
> On 19 Feb 2016, at 10:44, Gunnar Sletta wrote:
>
> Now every piece of code needs to also know about device pixel ratio and that
> needs to passed down to image loaders, icon generators
This is essential complexity, not accidental complexity. With
high-DPI displays in use raster images now v
Hey Simon,
I can try offering the Ubuntu Touch perspective on units with QML (sorry
if late, was busy for MWC).
We created a units system for our QML apps, called grid unit: units.gu(x).
We did this as we needed the ability to scale the UI for different
devices, from phones with highDpi screens
round.
Regards,
Michael
From: Development
on behalf of Hausmann Simon
Sent: Thursday, February 18, 2016 4:50 AM
To: development@qt-project.org
Subject: [Development] Scalable UIs in QtQuick (take 2)
Hi,
A little while ago Lars and I proposed to intr
On Wednesday 24 February 2016 14:24:58 Gerry Boland wrote:
> Hey Simon,
> I can try offering the Ubuntu Touch perspective on units with QML (sorry
> if late, was busy for MWC).
>
> We created a units system for our QML apps, called grid unit: units.gu(x).
Just to keep the picture complete to see
On Donnerstag, 18. Februar 2016 14:20:45 CET Oswald Buddenhagen wrote:
> On Thu, Feb 18, 2016 at 10:50:22AM +, Hausmann Simon wrote:
> > What do you think?
>
> that it's a bit silly that we're having this discussion *yet again*.
> ;) http://thread.gmane.org/gmane.comp.lib.qt.devel/6572/focus=6
Andreas Hartmetz said:
> Arcminutes are a really good idea. The size of screen elements isn't
> really about physical dimensions, it's about size on retina (the
> actual biological thing ;) really, or legibility.
[...]
> If the system had "known" that the typical user to screen distance was
> 2-3 m
> On 2 Mar 2016, at 09:37, Welbourne Edward
> wrote:
>
> Andreas Hartmetz said:
>> Arcminutes are a really good idea. The size of screen elements isn't
>> really about physical dimensions, it's about size on retina (the
>> actual biological thing ;) really, or legibility.
> [...]
>> If the syst
32 matches
Mail list logo
