Re: [Development] Support for *Notes and UpstreamFiles fields in qt_attributions.json files

2023-02-15 Thread Ulf Hermann via Development
QML supports comments, but not multi-line string literals. You can concatenate them, though. Sure it does. You can use ECMAScript template strings: property string longthing: `a multi line string` (In fact you can also just sprinkle line breaks into your regular

Re: [Development] Support for *Notes and UpstreamFiles fields in qt_attributions.json files

2023-02-15 Thread Thiago Macieira
On Wednesday, 15 February 2023 02:15:02 PST Ulf Hermann via Development wrote: > Or QML, in fact: QML supports comments, but not multi-line string literals. You can concatenate them, though. > That would be all nicely human-readable and easily verified with > qmllint. Which you also get with

Re: [Development] Support for *Notes and UpstreamFiles fields in qt_attributions.json files

2023-02-15 Thread Thiago Macieira
On Tuesday, 14 February 2023 23:35:57 PST Kai Köhne via Development wrote: > I'd be open to all kinds of formats if we'd start on a green field. But > we're not, and I don't think reimplementing qtattributionsscanner + redo > the build system integration + convert all existing >

Re: [Development] Support for *Notes and UpstreamFiles fields in qt_attributions.json files

2023-02-15 Thread Kai Köhne via Development
> -Original Message- > From: Edward Welbourne > Sent: Wednesday, February 15, 2023 10:45 AM > To: Kai Köhne > Cc: Development@qt-project.org > Subject: Re: Support for *Notes and UpstreamFiles fields in > qt_attributions.json > files > > Kai Köhne (15 February 2023 08:50) replied: > >

Re: [Development] Support for *Notes and UpstreamFiles fields in qt_attributions.json files

2023-02-15 Thread Edward Welbourne via Development
So I finally found time to look at the JSON specification [0] and find that (in section 6) it says, of the name/value pairs in an object: The JSON syntax does not impose any restrictions on the strings used as names, does not require that name strings be unique, [0] PDF linked from ECMA 404,

Re: [Development] The QT_SCREEN_SCALE_FACTORS rounding problem is still annoyingly valid

2023-02-15 Thread Morten Sørvig via Development
On 27 Jan 2023, at 18:04, Ilya Fedin wrote: My patch doesn't modify setScreenFactor, so the rounding is applied only to the variable value (and to the property on QScreen object, as it's the only remaining source without rounding in QHighDpiScaling::screenSubfactor), so the programmatic

[Development] QUIP 18: License specification in Qt's modules

2023-02-15 Thread Jörg Bornemann via Development
Hi, we're proposing a new QUIP: License specification in Qt's modules Please review https://codereview.qt-project.org/c/meta/quips/+/436096 Cheers, -- Jörg Bornemann | The Qt Company -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] Support for *Notes and UpstreamFiles fields in qt_attributions.json files

2023-02-15 Thread Ulf Hermann via Development
Or QML, in fact: // Attribution.qml in QtAttribution module: QtObject { property string name property list files property list upstreamFiles // } // Actual attribution.qml in source tree: import QtAttribution Attribution { // allows comments as much as you like

Re: [Development] Support for *Notes and UpstreamFiles fields in qt_attributions.json files

2023-02-15 Thread Edward Welbourne via Development
Kai Köhne (15 February 2023 08:50) replied: > did you intentionally sent this off-list? oops - no, outlook's UI tricked me :-( And, in fact, it just did it again, although I'm sure I hit Reply All this time. Manually adding development to CC... For the benefit of everyone else, my reply is