Hi,
I have no horse in these particular races, but I am going to throw my
2c in regardless:
In my opinion, 6 months or so delay on some reviews is fairly
acceptable (there can be higher-priority items which take attention,
it's understandable).
But beyond that, especially if the contributor is
Hi Gaurav,
First, I want to make clear: I know nothing about printing at all,
either in Qt or in general.
But I did a quick archive search and found the following:
https://lists.qt-project.org/pipermail/development/2020-May/039584.html
On Fri, Sep 16, 2022 at 8:22 AM Gaurav Guleria wrote:
>
>
Hi Lars,
Best of luck on your new endeavour!
It was a pleasure working with you throughout the years.
I think you have done a fantastic job ensuring that Qt has moved in a
good direction in your capacity as Chief Maintainer.
It is no easy task to balance commercial objectives as well as
Hi,
I'm not related at all to QBS development, but I am a maintainer of another
module or two (add-on modules like QtPIM, QMF), and I've never noticed an
"override review" button (similar to the "override sanity bot" button).
Although I can't ever remember having seen a -2 in those modules, so
Hi,
On Thu, May 27, 2021 at 7:34 AM Alberto Mardegan <
ma...@users.sourceforge.net> wrote:
> On 26/05/21 23:31, Christian Ehrlicher wrote:
> > Your observation looks correct even though I wonder why this was never
> > found before since this was not changed since the initial Qt5 import :)
> >
Hi Aleix,
Comments inline.
On Thu, May 6, 2021 at 12:43 AM Aleix Pol wrote:
> On Tue, Apr 27, 2021 at 2:28 AM Chris Adams
> wrote:
> >
> > Hi Jonah,
> >
> > I'm not part of the Qt Company, so please consider my comments as
> discussion only ;-)
> >
&
Hi Jonah,
I'm not part of the Qt Company, so please consider my comments as
discussion only ;-)
I'm the maintainer of the QtFeedback module, at least insofar as I am
willing to review commits and keep things building. Sailfish OS uses this
module, which is why I am still interested in keeping
Hi,
On Wed, Mar 3, 2021 at 7:08 AM Robin Burchell
wrote:
> On Tue, 2 Mar 2021, at 8:36 PM, Valery Volgutov wrote:
> > Could you please let me know why I have no any performance improvements
> > after quickcompiler apply?
>
> The QML compiler affects the performance of parsing and compiling the
Hi,
On Fri, Jul 24, 2020 at 5:17 AM Volker Hilsheimer
wrote:
> > On 23 Jul 2020, at 15:56, Stottlemyer, Brett (B.S.)
> wrote:
> >
> > Hi,
> >
> > I'm still trying to wrap my head around this concept, and starting a new
> thread to distinguish from the technical implementation discussion.
> >
>
Hi Mike,
On Tue, Mar 31, 2020 at 12:29 AM Mike Gabriel <
mike.gabr...@das-netzwerkteam.de> wrote:
> Hi Chris,
>
> On Di 17 Mär 2020 01:42:11 CET, Chris Adams wrote:
>
> >> [...]
> >
> > Potentially. The licensing of QtPIM only changed recently (in
Hi,
On Mon, Mar 16, 2020 at 8:49 PM Mike Gabriel <
mike.gabr...@das-netzwerkteam.de> wrote:
> Hi Chris,
>
> On Mo 16 Mär 2020 01:55:44 CET, Chris Adams wrote:
>
> > Hi Mike,
> >
> > On Sun, Mar 15, 2020 at 5:47 AM Mike Gabriel <
> > mike.gabr...@
Hi Mike,
On Sun, Mar 15, 2020 at 5:47 AM Mike Gabriel <
mike.gabr...@das-netzwerkteam.de> wrote:
> Hi Chris,
>
> thanks for following up on my questions.
>
> On Fr 13 Mär 2020 01:32:24 CET, Chris Adams wrote:
>
> > Hi Mike,
> >
> > I don't kn
Hi Mike,
I don't know much / anything about QtSystems, perhaps Lorn has more
information about that.
I am currently the maintainer of QtFeedback and QtPIM, although the amount
of time I have to spend on them is currently very limited, unfortunately.
In regards to API and ABI stability:
Hi Lorn,
On Mon, Dec 2, 2019 at 11:03 AM Lorn Potter wrote:
>
>
>
> On 29/11/19 7:05 PM, Alex Blasche wrote:
> > Hi,
> >
> > I would like to remove some of the ancient submodules from qt5.git. They
> > never were part of the Qt 5 offering anyway and mostly we were not sure
> > whether we
Hi Alex,
Does this have any effect on CI for those submodules? Jolla uses
QtDocGallery, QtFeedback and QtPIM, and have been upstreaming changes,
and at least for QtPIM the CI has been useful in ensuring that changes
don't cause issues on any platforms etc.
Aside from that, I have no complaints
On Mon, Nov 25, 2019 at 9:34 PM Ulf Hermann wrote:
>
> > I think one of the biggest problems is that ID resolution crosses
> > file boundaries. This essentially means that the ids chosen can very
> > easily become part of the "API" of a component unless you are very
> > vigilant to not allow that
Hi Uwe,
On Sat, Sep 28, 2019 at 9:29 PM Uwe Rathmann wrote:
>
> On 9/28/19 8:49 AM, Simon Hausmann wrote:
>
> > Instead of an idle timer, all imperative triggered onFooChange
> > handlers are queued up and called right before the next frame.
>
> Property binding is not the only notification
t; natural.
>
> I understand though that not everybody agrees on that, so perhaps this needs
> to be an opt-in mechanism that we can enable for QtQuick.
>
> Simon
>
> > On 27. Sep 2019, at 03:51, Chris Adams wrote:
> >
> > Hi Simon,
> >
> > Nice work! T
Hi Simon,
Nice work! This was one of the things which Aaron mentioned as being
a goal he had for QML way back in the day, and I'm glad to see that
someone is doing the work to make it a reality.
In theory, one of the issues with pull-style bindings is that large
dependency chains can be built
Thanks for all of your hard work, Simon! +1 for Ulf from me.
On Mon, Feb 18, 2019 at 11:27 PM Simon Hausmann wrote:
>
> Hi,
>
> I'd like to step down as the maintainer of the Qt QML module and pass the
> torch on to Ulf Hermann.
>
> He has been contributing to the module since 2013 with
Hi Eddy,
I'm willing to be listed as the maintainer of QtFeedback for now. If
it ever gets more development attention and released as a supported
module then someone with more time to give should probably take over,
but until then I'm more than happy to review any changes people might
contribute
On Sat, Oct 7, 2017 at 2:21 AM, Harri Porten wrote:
>
> On Fri, 6 Oct 2017, Tomaz Canabrava wrote:
>
>> > We have recently been working on a research project looking into
>> the possibilities for creating a lightweight server component that can
>> easily enable Qt
>>
I'm certain that it's possible. I suspect the reason why the code used
QVariant is that when it was originally written (in Qt 4.7 days, IIRC),
QJSValue didn't exist, and it simply hasn't been ported to newer interfaces
since then. Without knowing too much about the QML bindings in QtPIM, I am
Hi,
Recently, a few unit test failures[1] in the (unreleased) QtPIM module
showed that the recent change[2] which changes the semantics of null
assignment (from JS) to a QVariant Q_PROPERTY can affect existing client
code.
Certainly, the cases which are affected are most likely edge-cases (that
Hi,
On Mon, Feb 16, 2015 at 11:34 PM, Mike Verdone mike.verd...@ableton.com
wrote:
Hi all,
This is my first post to the Qt dev list. Apologies if I say something
dumb.
I’d like to propose some changes to the “meta” syntax in QtQuick .js
files. I propose this in order to support JavaScript
Hi Renato,
On Sat, Jan 24, 2015 at 5:51 AM, Renato Araujo rena...@gmail.com wrote:
Hi Cris,
On Mon, Jan 19, 2015 at 10:17 PM, Chris Adams chris.ad...@qinetic.com.au
wrote:
QContactType::TypeGroup is meant to represent a group of entities with
shared contact details (eg, a local football
QContactType::TypeGroup is meant to represent a group of entities with
shared contact details (eg, a local football club might have a mailing-list
email address, a clubhouse phone number, etc). Individual contacts can
have membership in groups (so various friends can be members of the
football
: Chris Adams chris.ad...@qinetic.com.au
An: Gunnar Roth gunnar.r...@gmx.de
Cc: Simon Hausmann simon.hausm...@theqtcompany.com,
development@qt-project.org development@qt-project.org
Betreff: Re: Re: [Development] QML instantiation performance
Hi Gunnar,
Can you get a backtrace which might
);
+}
+
QT_END_NAMESPACE
*Gesendet:* Montag, 01. Dezember 2014 um 05:51 Uhr
*Von:* Chris Adams chris.ad...@qinetic.com.au
*An:* Simon Hausmann simon.hausm...@theqtcompany.com
*Cc:* development@qt-project.org development@qt-project.org
*Betreff:* Re: [Development] QML instantiation performance
See
Sure. I think there are advantages to be had from bundling, obviously, but
those don't really exist right now. +1 from me.
www.qinetic.com.au - Qt And QML User Experience Specialists
On Tue, Dec 2, 2014 at 6:55 PM, Simon Hausmann
simon.hausm...@theqtcompany.com wrote:
Hi,
I'd like to
I don't recall, but a quick grep of the git log turned up the following
three changes:
https://codereview.qt-project.org/#/c/60447/
https://codereview.qt-project.org/#/c/60446/
https://codereview.qt-project.org/#/c/60445/
I guess this was the most important bit:
:39 PM, Simon Hausmann
simon.hausm...@theqtcompany.com wrote:
On Friday 28. November 2014 12.20.29 Chris Adams wrote:
Hi,
No worries. Interestingly, when I ran the benchmark against 5.3, I found
that it hangs after performing several tests.
Before each test, the benchmark will clear
Specialists
On Mon, Dec 1, 2014 at 2:16 PM, Chris Adams chris.ad...@qinetic.com.au
wrote:
The loop was due to the QtQuick2 plugin's defineModule() code initializing
the value type providers on load, but not deinitializing them on dtor,
resulting in future loads of that plugin adding the same ptr
Hi Gunnar,
Note that the results between versions may not be directly comparable.
The benchmark does some very specific things, including destroying the
engine and clearing all type registrations between each run. This is
intended to simulate application startup performance conditions, but is
Specialists
On Thu, Nov 27, 2014 at 4:37 PM, Juha Vuolle juvuo...@gmail.com wrote:
Hey Chris,
Thanks heaps. I'll have a look and get back with any findings (may
take a day or two before I get to it).
cheers,
Juha
2014-11-27 3:51 GMT+02:00 Chris Adams chris.ad...@qinetic.com.au:
Hi Juha
.
Kind regards,
Chris Adams.
www.qinetic.com.au - Qt And QML User Experience Specialists
On Wed, Nov 26, 2014 at 6:08 PM, Juha Vuolle juvuo...@gmail.com wrote:
Hello,
apologies for cross-posting. I find this such a fundamental issue that I
feel
at least having the best possible understanding
Hello Yam,
I can think of a couple of places in code I've written where that would be
very useful, personally.
However, when I looked at the repo I couldn't see any license information,
and I'm wondering what license you're planning on releasing it under.
Cheers,
Chris.
Hi,
My understanding is that the QtLocation module from QtMobility got split
into separate modules: QtPositioning and QtLocation (although they're
located within the same source repo in qt5 still, if memory serves).
Aaron McCarthy has been actively maintaining the QtPositioning module, but
Hi Lorn,
In regards to the publish/subscribe and serviceframework bits, I wonder
what the plan is with those. How much overlap between them and Replicant
is there? Perhaps Brett could quickly sum up the differences between the
pub/sub module and the Replicant framework, and whether Replicant
Hi,
On Fri, Sep 19, 2014 at 10:37 PM, BogDan bog_dan...@yahoo.com wrote:
Hello folks,
Singletons registered using qmlRegisterSingletonType, are deleted
*before*
the other active objects. I consider it to be wrong because some of the
active
objects may still need to access the singletons
A long time ago there were plans to add
https://codereview.qt-project.org/#/c/49155 but see the comments regarding
context deletion and also https://codereview.qt-project.org/#/c/84341/
On Sun, Jul 6, 2014 at 4:07 PM, Hausmann Simon simon.hausm...@digia.com
wrote:
I think setTimeout would be a
Hi Renato,
Is an address book a contactable entity? It seems like it's just a
collection of contacts, rather than a contactable entity, in which case I
would prefer something like the QOrganizerItemCollection API to be added to
QtContacts instead, perhaps, or some other solution.
To be more
Jumping on this bandwagon late because I was away on vacation, but +1 from
me :-)
On Fri, Jan 10, 2014 at 6:24 AM, Knoll Lars lars.kn...@digia.com wrote:
Hi,
I'd like to continue on filling gaps in our maintainer list and thus want
to propose Simon Hausmann as the new maintainer for QtQml.
Hi,
I don't know about QtJsonDb but QtPim has a few people interested in it
(Jolla for one, and Canonical for another). At the moment, development
resources dedicated to improving it are somewhat limited, but that
situation will change. If there's anything in particular which you think
needs
Hi,
On Sat, Aug 10, 2013 at 6:05 AM, André Pönitz
andre.poen...@mathematik.tu-chemnitz.de wrote:
On Thu, Aug 08, 2013 at 08:18:00PM +0200, Olivier Goffart wrote:
On Thursday 08 August 2013 08:59:26 Alan Alpert wrote:
I don't know specifically about why it wasn't built on top of QRC, but
Hi,
Alex Blasche is looking at various QtAddOn modules which are evolutions of
the old QtMobility modules. There's still some work to be done to
determine which modules are candidates for improvement up to the point
where they're releasable, and more work to be done to figure out how many
Hi,
This is really exciting news! Good stuff!
Hi,
Does that include to get rid of v8 as an JS engine option for QML2?
Yes, that's exactly the proposed change.
I have not tested it yet, but it would be interesting to know if the new
engine also uses just in time compilation, as we
qmlEngine() and qmlContext() are documented via qdoc comments in
qqmlengine.cpp and should show up in the related functions section of the
generated documentation. As you've noticed, however, for some reason the
documentation does not show up in the generated documentation. I don't
know why.
+1 from me.
On Sun, Feb 3, 2013 at 1:45 PM, Martin Jones martin.jo...@qinetic.com.auwrote:
Since the Nokia Brisbane office was closed QML/QtQuick has effectively
been maintainer-less. Recently Alan has been proactive in pushing QML
forward and has been very active in the community. He also
Hi,
(https://codereview.qt-project.org/#change,46020)
You are the only one who doesn't like that patch. Otherwise it could have
gone in before Qt 5.0.
https://codereview.qt-project.org/#change,39624
This patch is the opposite of the previous one, so only one will go in.
But why
Hi,
This is an interesting topic.
I'm not sure that I'm convinced by anyone's arguments so far, to be honest.
More comments inline:
import paths can achieve basically what we want, so for example
high_res/bla.qml will override bla.qml if the path is something like
high_res:. .
This should
Hi,
snip
The primary purpose of having QtQuick 1 in Qt5 is compatibility, that
your import QtQuick 1.1 QML works *as before* when you switch to Qt
5. Work on QtQuick 1.1 which is not eligible for a Qt 4 patch release
is clearly unacceptable. The question of a QtQuick 1.2 is less clear,
but
Hi,
On Wed, Dec 12, 2012 at 10:51 PM, Charley Bay charleyb...@gmail.com wrote:
Unto all so did sayeth Alan:
What should enumeration declarations in QML look like?
Did respondeth Erik:
And, also important: how much slower is it allowed to be than the current
implementation?
I
Hi,
maybe there's a case for adding a small QQmlApplicationEngine in QtQml
which adds the application runtime aspects?
It's early and I haven't had my second coffee yet, so maybe I'm
misunderstanding something, but are these application runtime aspects
completely non-gui, non-QtQuick related?
Hi,
I figured I weigh into this discussion:
But if you don't like those changes, you can do the var in a global
(.pragma library) script file and use that. Maybe this means proper
enum support isn't that urgent ;) .
It's not that the functionality is urgent; it's that currently,
On a slightly unrelated note...
Because this should be up to module maintainers and there is not so much
CI infrastructure to support all the projects under Gerrit
Who are the module maintainers, these days? I really don't think that
http://qt-project.org/wiki/Maintainers is up to date.
Sorry
Hi,
[snip]
Does anyone have any further feedback on QML tool renaming before
these get implemented?
+1 from me, but I don't mind if qmlbundle stays where it is as an
undocumented, internal, no guarantees, tool, just because it's less effort.
Cheers,
Chris.
Hi,
There are two points I'd like to add to the discussion. Firstly qmlbundle
isn't
really useful yet, I'd advocate moving it to the playground or somewhere
outside the qtdeclarative module until it's done.
I've been wondering about this too. There's zero documentation of it right
now,
Hi,
On Wed, Oct 31, 2012 at 8:17 PM, Sune Vuorela nos...@vuorela.dk wrote:
On 2012-10-30, Thiago Macieira thiago.macie...@intel.com wrote:
1) QML environment variables
The variable for import paths has been versioned from QML_IMPORT_PATH to
QML2_IMPORT_PATH. But I have not changed any of
On Thu, Nov 1, 2012 at 10:56 AM, Thiago Macieira
thiago.macie...@intel.comwrote:
On quinta-feira, 1 de novembro de 2012 10.01.11, Chris Adams wrote:
Regarding QML_IMPORT_PATH, I discussed this yesterday and this morning
with
Martin Jones and Andrew den Exter, and a couple of things deserve
Hi,
[snip]
Question: qml2scene or qml2viewer? If no one speaks up, it will be
qml2scene.
The patches for that are ready, pending approval.
[snip]
The relevant changes are:
Qt Quick 1 2:
https://codereview.qt-project.org/37104 (QQ1's imports with no
subdir)
Hi,
we are still having problems with the QmlImportPath. There is also already
a bug reported:
https://bugreports.qt-project.org/browse/QTBUG-
20539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel https://bugreports.qt-project.org/browse/QTBUG-
On Fri, Oct 19, 2012 at 2:06 AM, Jon Trulson j...@radscan.com wrote:
On Tue, 16 Oct 2012, Thiago Macieira wrote:
On terça-feira, 16 de outubro de 2012 15.25.40, Jon Trulson wrote:
However, compiling qtwayland fails with many errors - errors that
imply qtwayland cannot work with the wayland
63 matches
Mail list logo