Re: [Development] Feature freeze exception for QTBUG-95587

2021-09-27 Thread Alberto Mardegan
On 13/09/21 21:58, Elvis Stansvik wrote: > I don't see what's inherently wrong with a plain function like > Qt.resolvedUrl. It's very obvious - it says what it does on the tin. > Names are good that way. FWIW I've been using it for ages, and yes, if it initially it sounded a bit verbose, now I'm

Re: [Development] Feature freeze exception for QTBUG-95587

2021-09-14 Thread Ulf Hermann
I am wondering if the change was a good idea at all then. To me, it feels like the change at the root of all this was not well thought out. If it is expected that this change is going to hit so many users and they need some facility to make it easier on them than littering their code with

Re: [Development] Feature freeze exception for QTBUG-95587

2021-09-14 Thread Edward Welbourne
On 2021 Sep 13, at 20:58, Elvis Stansvik mailto:elvst...@gmail.com>> wrote: >> Yes, URLs are vital to QML I guess, but are they *that* vital? The >> bar should be quite high IMO. In the apps I've worked on, URLs and >> URL handling is really not central at all. IIUC, the present work has to do

Re: [Development] Feature freeze exception for QTBUG-95587

2021-09-14 Thread André Somers
Hi, On 14-09-2021 09:12, Shawn Rutledge wrote: On 2021 Sep 13, at 20:58, Elvis Stansvik > wrote: Yes, URLs are vital to QML I guess, but are they *that* vital? The bar should be quite high IMO. In the apps I've worked on, URLs and URL handling is really not central

Re: [Development] Feature freeze exception for QTBUG-95587

2021-09-14 Thread Shawn Rutledge
On 2021 Sep 13, at 20:58, Elvis Stansvik mailto:elvst...@gmail.com>> wrote: Yes, URLs are vital to QML I guess, but are they *that* vital? The bar should be quite high IMO. In the apps I've worked on, URLs and URL handling is really not central at all. We’re talking about potentially a lot of

Re: [Development] Feature freeze exception for QTBUG-95587

2021-09-13 Thread Elvis Stansvik
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 >

Re: [Development] Feature freeze exception for QTBUG-95587

2021-09-13 Thread Ulf Hermann
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

Re: [Development] Feature freeze exception for QTBUG-95587

2021-09-13 Thread Tor Arne Vestbø
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

Re: [Development] Feature freeze exception for QTBUG-95587

2021-09-13 Thread André Somers
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

Re: [Development] Feature freeze exception for QTBUG-95587

2021-09-13 Thread Edward Welbourne
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

Re: [Development] Feature freeze exception for QTBUG-95587

2021-09-13 Thread Ulf Hermann
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

Re: [Development] Feature freeze exception for QTBUG-95587

2021-09-13 Thread Oswald Buddenhagen
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

Re: [Development] Feature freeze exception for QTBUG-95587

2021-09-13 Thread Ulf Hermann
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

Re: [Development] Feature freeze exception for QTBUG-95587

2021-09-13 Thread Shawn Rutledge
> 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

[Development] Feature freeze exception for QTBUG-95587

2021-09-09 Thread 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 https://codereview.qt-project.org/c/qt/qtdeclarative/+/369987 Now the question is whether