Re: [Development] Scalable UIs in QtQuick (take 2)

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

Re: [Development] Scalable UIs in QtQuick (take 2)

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

Re: [Development] Scalable UIs in QtQuick (take 2)

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*. > ;)

Re: [Development] Scalable UIs in QtQuick (take 2)

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

Re: [Development] Scalable UIs in QtQuick (take 2)

Hi, Regarding (2), last time around I had concerns about the proposed limitations associated with language-level unit support (see some of the discussion at https://codereview.qt-project.org/98288). I'd be interested to hear the particulars of what unit support might look like this time

Re: [Development] Scalable UIs in QtQuick (take 2)

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

Re: [Development] Scalable UIs in QtQuick (take 2)

> 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

Re: [Development] Scalable UIs in QtQuick (take 2)

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 >

Re: [Development] Scalable UIs in QtQuick (take 2)

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 >

Re: [Development] Scalable UIs in QtQuick (take 2)

> 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

Re: [Development] Scalable UIs in QtQuick (take 2)

> 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

Re: [Development] Scalable UIs in QtQuick (take 2)

> 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

Re: [Development] Scalable UIs in QtQuick (take 2)

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

Re: [Development] Scalable UIs in QtQuick (take 2)

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*. ;) >

Re: [Development] Scalable UIs in QtQuick (take 2)

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

Re: [Development] Scalable UIs in QtQuick (take 2)

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

Re: [Development] Scalable UIs in QtQuick (take 2)

> 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

Re: [Development] Scalable UIs in QtQuick (take 2)

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

Re: [Development] Scalable UIs in QtQuick (take 2)

@qt-project.org> on behalf of Konstantin Ritt <ritt...@gmail.com> Sent: Thursday, February 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 }

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 GMT+03:00 Sorvig Morten : > > > On 18 Feb 2016, at 12:35, Nikita Krupenko wrote: >

Re: [Development] Scalable UIs in QtQuick (take 2)

> 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

Re: [Development] Scalable UIs in QtQuick (take 2)

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

Re: [Development] Scalable UIs in QtQuick (take 2)

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

Re: [Development] Scalable UIs in QtQuick (take 2)

t; >Simon > > > >From: Ирина Flora <ritt...@gmail.com> >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 lik

Re: [Development] Scalable UIs in QtQuick (take 2)

From: Ирина Flora <ritt...@gmail.com> 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 w

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