+1
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Wed, Oct 02, 2019 at 11:22:33AM +, Shawn Rutledge wrote:
> Hi all,
>
> I would like to nominate Vitaly Fanaskov as approver for the Qt Project.
> Vitaly joined the Qt Quick and Widgets team about a year ago. He has been
> fixing bugs in widgets and Qt Quick, making it easier to use and
On 10/2/19 5:19 PM, Pierre-Yves Siret wrote:
While using layouts in the Qt Quick world, you use Layout attached
properties to give hints to the layout system :
Sure it is a subset of the options you have with the corresponding
layouts of the widgets world.
It is possible to set the
>
> With Widgets, GraphicsView or my framework the system depends on the
> min/preferred/max hints being evaluated by a size policy. F.e
> QSizePolicy::hasHeightForWidth() tells the layout classes, what to do.
>
> QQuickItem has the implicitSize ( = implicit preferred size ) only - no
> other
Simon Hausmann (2 October 2019 15:21)
> I'd like to nominate Fabian as approver as well.
His contributions to Volker's pool allocator reviews have left a positive
impression here, +1.
For reference:
https://codereview.qt-project.org/q/owner:fabian.kosmale%40qt.io
On 10/2/19 4:36 PM, Jason H wrote:
There is fontSizeMode: Text.Fit, .HorizontalFit and .VerticalFit.
Horizontal fit is what you want in that situation. But the whole
implementation is lacking because you can't actually ask the Text
what size it used to render so that other text items on the
+1
and, since Shawn's fancy HTML links actually linked to a different
URL than their text claimed, let's have the real ones:
https://codereview.qt-project.org/q/owner:vitaly.fanaskov%40qt.io
https://codereview.qt-project.org/q/reviewer:vitaly.fanaskov%40qt.io
Eddy.
> Also the implicit size of longish texts is usually irrelevant as in most
> situations the layout needs a height-for-width value. IIRC Qt/Quick does
> not even has a concept for how to deal with this type of constraints.
There is fontSizeMode: Text.Fit, .HorizontalFit and .VerticalFit.
Hi,
Here's a new update on the merge of wip/qt6 to dev:
The culprit that broke the Windows 7 tests has been identified, a fix (revert)
merged into qtbase 5.15 and merged up to dev. Unfortunately qtdeclarative is
still failling because for declarative the CI configuration adds
developer-build
+1
(The usual disclaimers about locations and employment apply ...)
On 10/2/19 3:21 PM, Simon Hausmann wrote:
> Hi,
>
> I'd like to nominate Fabian as approver as well. He started about four
> months ago digging deep into pretty much all aspects of the Qml engine -
> from grammar fixes,
+1
> On 2. Oct 2019, at 15:21, Simon Hausmann wrote:
>
> Hi,
>
> I'd like to nominate Fabian as approver as well. He started about four months
> ago digging deep into pretty much all aspects of the Qml engine - from
> grammar fixes, public C++ API, ES promise implementation, new language
>
Hi,
I'd like to nominate Fabian as approver as well. He started about four months
ago digging deep into pretty much all aspects of the Qml engine - from grammar
fixes, public C++ API, ES promise implementation, new language features
(required properties) all the way to a brand new linter. As a
The links were intended to be plain text instead of misleading HTML… sorry
about that.
And here’s one more link: Vitaly’s commits to KUserFeedback.
https://github.com/KDE/kuserfeedback/commits?author=vt4a2h
> On 2 Oct 2019, at 13:22, Shawn Rutledge wrote:
>
> Hi all,
>
> I would like to
+1 from me :)
Cheers,
Frederik
On onsdag 2. oktober 2019 13:22:33 CEST Shawn Rutledge wrote:
> Hi all,
>
> I would like to nominate Vitaly Fanaskov as approver for the Qt Project.
> Vitaly joined the Qt Quick and Widgets team about a year ago. He has been
> fixing bugs in widgets and Qt Quick,
Hi all,
I would like to nominate Vitaly Fanaskov as approver for the Qt Project.
Vitaly joined the Qt Quick and Widgets team about a year ago. He has been
fixing bugs in widgets and Qt Quick, making it easier to use and customize
color palettes in Qt Quick, working on the speech module,
Hi,
swiftui is the new declarative way from Apple to develop applications for
the Apple devices.
https://developer.apple.com/xcode/swiftui/
I'd like similar approach - c++ within qml (declarative) :)
Nicola
Il Mer, 2 Ottobre 2019 10:36 am, André Somers ha scritto:
> Hi,
>
>
> On
On tirsdag 1. oktober 2019 08:10:20 CEST Jukka Jokiniva wrote:
> Hi,
>
> You supposed to press the "Stage" button like before.
> The greyed Submit button is kind of technically ok, but creates confusion
> because it was previously hidden.
> I created a task to Jira to hide it,
>
On Mittwoch, 2. Oktober 2019 00:02:01 CEST Lorn Potter wrote:
> Hi Martin,
>
>
> On 1/10/19 4:38 PM, Martin Koller wrote:
> > Hi,
> >
> > I see that compiling Qt for wasm produces .a static libs.
> > This however leads to a couple of duplicate symbols when linking my
> > existing large
On 02.10.19 10:57, Palaraja, Kavindra wrote:
> +1 , he’s my star example of a Developer who actually reads and writes
> documentation
Also +1, although I'd dispute the "star" status ;)
cu
Robert
> Disclaimer: We used to work in the same team.
Same for me.
+1 , he’s my star example of a Developer who actually reads and writes
documentation
Disclaimer: We used to work in the same team.
From: Development on behalf of Simon
Hausmann
Date: Wednesday, 2. October 2019 at 10:18
To: "development@qt-project.org"
Subject: [Development] Nominating
On 2 Oct 2019, at 10:18, Simon Hausmann
mailto:simon.hausm...@qt.io>> wrote:
Hi,
I would like to nominate Dominik for approver status. He started contributing
to Qt back in 2013 and has been working primarily on the Qt automotive and
embedded related bits. After such a long time of steady
having worked with him on Qt Auto: +1 from me
> On 2 Oct 2019, at 09:18, Simon Hausmann wrote:
>
> Hi,
>
> I would like to nominate Dominik for approver status. He started contributing
> to Qt back in 2013 and has been working primarily on the Qt automotive and
> embedded related bits. After
Hi,
On 02-10-19 09:39, Nicola De Filippo wrote:
Hi,
is possible think will Qt6/qml c++ binding similar to swiftui?
Perhaps it would be helpful to explain a bit more about how such things
work in swiftui, for those not familiar with it?
André
Hi,
I would like to nominate Dominik for approver status. He started contributing
to Qt back in 2013 and has been working primarily on the Qt automotive and
embedded related bits. After such a long time of steady contributions and code
peer-review in the automotive "corner", I do trust him to
Hi,
is possible think will Qt6/qml c++ binding similar to swiftui?
N.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
Hi Chris,
should individual items have to know/track this ...
Well, anchoring is also based on size changes, but uses a different type
of notification -> item change listeners.
Not sure why the authors decided to introduce yet another type of
notification - instead of using event + event
26 matches
Mail list logo
