My first impression is that this looks like nice syntax. However maybe we
should discuss a bit how it fits into the language design, since it seems like
we’re trying to have a cohesive language design nowadays. I’m never quite sure
to what extent QML is “our” language, or to what extent the
Hi,
perhaps this is the wrong place to raise this, but could one reconsider
to have the trivial fix for the more or less duplicated bugs
https://bugreports.qt.io/browse/QTBUG-96285
https://bugreports.qt.io/browse/QTBUG-96359
in Qt 6.2.0?
Without that fix, more or less all applications that
On Mon, Sep 13, 2021 at 09:56:23AM +0200, Ulf Hermann wrote:
However, if we nail down the meaning of @"string" to "create and
resolve a URL", then we cannot use a plain '@' for much else.
it would be kinda logical for @ applied to a structure to mean resolving
all urls inside it, which would
However, if we nail down the meaning of @"string" to "create and
resolve a URL", then we cannot use a plain '@' for much else.
it would be kinda logical for @ applied to a structure to mean resolving
all urls inside it, which would be a clear clash with
https://bugreports.qt.io/browse/QBS-58 (i
On 2021-09-13 11:19, Volker Hilsheimer wrote:
Hi Christoph,
I just cherry-picked the fix down into 6.2.0, the release team should
be able to stage the fix for the RC.
Great, thanks!
Greetings
Christoph
--
Ignorance is bliss...
https://cullmann.io | https://kate-editor.org
On 2021 Sep 9, at 17:32, Ulf Hermann wrote:
>> As Qt.resolvedUrl() is quite a mouthful, there should be a shorthand
>> for it: the '@' operator.
Shawn Rutledge (13 September 2021 08:24) wrote:
> I’m never quite sure to what extent QML is “our” language, or to what
> extent the rule is “just do
> On 2021 Sep 9, at 17:32, Ulf Hermann wrote:
>
> A user can fix this by explicitly calling Qt.resolvedUrl() in order to
> resolve the URL in a specific context and make it absolute. As we need URLs
> rather often in QML, we will see much more Qt.resolvedUrl() in Qt6 than we
> have seen in
On 9/10/21 4:58 PM, Thiago Macieira wrote:
Qt 6 supports using the moc from a different build of Qt, to help with the
bootstrapping issue and also so you don't always run a debug-mode moc in your
debug builds of Qt.
Is that moc required to be from the same Qt version as the Qt you're trying to
Hi Christoph,
I just cherry-picked the fix down into 6.2.0, the release team should be able
to stage the fix for the RC.
Thanks!
Volker
> On 13 Sep 2021, at 11:03, Christoph Cullmann (cullmann.io) via Development
> wrote:
>
> Hi,
>
> perhaps this is the wrong place to raise this, but
To me, the fact that this raises discussion on if this syntax should
have other applications perhaps already justifies a "no" to your actual
question: should this be allowed in a bugfix release.
I would think not just a small library tool but an actual language
change warrants a bit more
On 09-09-2021 17:32, Ulf Hermann wrote:
Hello,
due to the magnitude of the above mentioned bug, I'm considerng to
introduce a new feature in Qt 6.2.1. The new "@" operator in QML
relieves you from typing "Qt.resolvedUrl" over and over. See
I agree, this feels like it should have some wider discussion.
Cheers,
tor arne
> On 13 Sep 2021, at 13:27, André Somers wrote:
>
>
> On 09-09-2021 17:32, Ulf Hermann wrote:
>> Hello,
>>
>> due to the magnitude of the above mentioned bug, I'm considerng to introduce
>> a new feature in Qt
Am Freitag, 10. September 2021, 16:58:55 CEST schrieb Thiago Macieira:
> Qt 6 supports using the moc from a different build of Qt, to help with the
> bootstrapping issue and also so you don't always run a debug-mode moc in
> your debug builds of Qt.
>
> Is that moc required to be from the same Qt
On Monday, 13 September 2021 00:38:55 PDT Joerg Bornemann wrote:
> For a cross-build, currently, the host Qt needs to have the same version
> as the target Qt. When trying to build, let's say, Qt for Android 6.2.0
> with a host Qt 6.1.2, you're getting an error:
>
>Could not find a
On Monday, 13 September 2021 11:21:37 PDT Thiago Macieira wrote:
> Your way is easier on the packagers, though, since the cross-compilations
> are usually not critical content, but the host/native Qt is. But I don't
> think it's the typical scenario for cross-compiling. People usually
> download
On Monday, 13 September 2021 09:13:02 PDT Marius Kittler wrote:
> From my GNU/Linux user/distributor perspective it would be great if the host
> moc could be slightly newer than the target Qt libs. So if the distribution
> upgrades the regular Qt package the cross packages (targeting mingw-w64 and
Hello everybody
I would like to raise an issue about Oswald Buddenhagen abusing his maintainer
rights. He is constantly blocking the merge of the patchset which implements a
new feature in Qbs [0]. I started working on this almost a year ago and the
issue was approved for the first time in
Den tors 9 sep. 2021 kl 17:33 skrev Ulf Hermann :
>
> Hello,
>
> due to the magnitude of the above mentioned bug, I'm considerng to
> introduce a new feature in Qt 6.2.1. The new "@" operator in QML
> relieves you from typing "Qt.resolvedUrl" over and over. See
>
18 matches
Mail list logo
