Thanks for bringing this up,
It looks like when we finally got the sync to work yesterday, it has only been
syncing new changes.
I just run a full sync and now everything should be uptodate.
Sorry for the delay.
--Jukka
From: "Stottlemyer, Brett (B.S.)"
Date: Tuesday, 21 May 2019 at 19.
> I think both XML and XMLPatterns are Done, not Deprecated.
What a relief!
> Reasoning: only the former has an explicit note in the documentation
> (can't find an equivalent for the latter):
>
> > https://doc.qt.io/qt-5/qtxml-index.html
> > https://doc.qt.io/qt-5/qtxmlpatterns-index.html
>
>
Il 21/05/19 16:58, Thiago Macieira ha scritto:
On Tuesday, 21 May 2019 00:15:04 PDT Bernhard Lindner wrote:
Unlucky me. Deprecation of these two components literally broke every
application I have ever written using Qt. I hope they will have new
maintainers some day.
Note I said QtXml is deprec
> Qt modules and features can be in one of 5 states:
>
> - Active Development
> Receiving new features, changing quickly, bugs fixed
> - Maintained
> Receives occasional features, changes slowly, bugs fixed
> - Done
> No new features, changes very slowly, P2 bugs and up fixed only
> - Deprecat
On Tuesday, 21 May 2019 08:55:34 PDT Bernhard Lindner wrote:
> I heared about "deprecated" and, well, not deprecated. I had no idea there
> is such a state like "Done".
Qt modules and features can be in one of 5 states:
- Active Development
Receiving new features, changing quickly, bugs fixed
-
21.05.2019, 19:03, "Bastiaan Veelo" :
> [skipping many interesting points, sorry]
>
> On 21/05/2019 16:06, Shawn Rutledge wrote:
>> Anyway I think Assistant is one of those cases where I would prefer to
>> keep using QTextBrowser and fix it up a bit more to suit, rather than
>> switching to a
21.05.2019, 18:01, "Jean-Michaël Celerier" :
>> (of all Qt applications, only a minority use either QSS or CSS)
>
> Are there sources for that ? From what I can see it has plenty of usage.
> https://github.com/search?l=C%2B%2B&q=setStyleSheet&type=Code
Also, it's possible to start any Qt applica
> Yes, they were done, not deprecated. See
> https://wiki.qt.io/Qt_Modules_Maturity_Level
That is good news!
In https://wiki.qt.io/New_Features_in_Qt_5.13 it says Qt XmlPatterns would be
deprecated.
Somebody in the interest list pointed me there.
Also I heard a lot (and it is written in the d
On 2019-05-21 15:58, Thiago Macieira wrote:
On Tuesday, 21 May 2019 00:15:04 PDT Bernhard Lindner wrote:
Unlucky me. Deprecation of these two components literally broke every
application I have ever written using Qt. I hope they will have new
maintainers some day.
Note I said QtXml is deprecat
On Tue, May 21, 2019 at 04:41:42PM +0300, Danila Malyutin wrote:
> Exhibit C:
>
> foo().contains(x)
>
> https://godbolt.org/z/KlIcFc
-std=c++2a
But yes, I am aware of that, and I am perfectly happy with the tendency
to chose practically sensible approaches in Standard C++ for a while now.
Bu
Hi all,
Passing this one for general awareness. I've been hit by
https://bugreports.qt.io/browse/QTQAINFRA-2980.
The referenced issue is closed but with a note "I assume it will take awhile to
finish." The symptoms, as I understand it, are that various mirrors are not
current.
I was able to
On Tue, May 21, 2019 at 08:32:07AM +0200, Mutz, Marc via Development wrote:
>
> By that line of reasoning, the change from
>
>Q3Slider *sl = new Q3Slider(0, 100, 50, 10, 1, this);
>
> to
>
>Q4Slider *sl = new Q4Slider(this);
>sl->setRange(0, 100);
>sl->setValue(50);
>sl->set
[skipping many interesting points, sorry]
On 21/05/2019 16:06, Shawn Rutledge wrote:
Anyway I think Assistant is one of those cases where I would prefer to
keep using QTextBrowser and fix it up a bit more to suit, rather than
switching to a real browser engine. Light weight is a real advantage.
> > Unlucky me. Deprecation of these two components literally broke every
> > application I have ever written using Qt. I hope they will have new
> > maintainers some day.
>
> Note I said QtXml is deprecated, but it might actually be in Done state. I
> don't remember. Does anyone? Where's our au
On 5/21/19 4:58 PM, Thiago Macieira wrote:
Note I said QtXml is deprecated, but it might actually be in Done
state. I don't remember. Does anyone? Where's our authoritative
source?
The difference between Done and Deprecated is whether we're telling
you to start porting code away.
My use ca
Am 21.05.2019 um 14:06 hat Shawn Rutledge geschrieben:
I wish that were true for me. We need colours in table cell borders
and SVG images (and better CSS support would be real nice). This
might help, but is stalled:
https://codereview.qt-project.org/c/qt/qtbase/+/177256
I was just putting some
On Tuesday, 21 May 2019 00:54:49 PDT Kai Köhne wrote:
> Hi,
>
> The deadline for submissions indeed got extended to * 2nd of June *... which
> is already end of next week!
> So feel free to still submit proposals, but hurry up 😊
>
> https://www.surveymonkey.com/r/K7PMKC8
Do we have an idea whe
On Tuesday, 21 May 2019 00:15:04 PDT Bernhard Lindner wrote:
> Unlucky me. Deprecation of these two components literally broke every
> application I have ever written using Qt. I hope they will have new
> maintainers some day.
Note I said QtXml is deprecated, but it might actually be in Done state
> (of all Qt applications, only a minority use either QSS or CSS)
Are there sources for that ? From what I can see it has plenty of usage.
https://github.com/search?l=C%2B%2B&q=setStyleSheet&type=Code
Best,
---
Jean-Michaël Celerier
http://www.jcelerier.name
On Tue, May 21, 2019 at 4:07 PM
> On 20 May 2019, at 18:56, Bastiaan Veelo wrote:
>
> On 20/05/2019 17:56, Konstantin Tokarev wrote:
>> 20.05.2019, 18:27, "Bastiaan Veelo" :
>>> On 20/05/2019 16:51, Konstantin Tokarev wrote:
>>> ...
>> However, it would better to avoid duplicating work with Qt Creator,
>> which also implements
Exhibit C:
foo().contains(x)
https://godbolt.org/z/KlIcFc
пн, 20 мая 2019 г. в 23:14, André Pönitz :
> On Fri, May 17, 2019 at 10:17:10AM +0200, Mutz, Marc via Development wrote:
> > [...] There is no readability difference between the use of a Qt
> container and
> > that of an STL container.
>
21.05.2019, 15:47, "Bastiaan Veelo" :
> On 20/05/2019 19:02, Konstantin Tokarev wrote:
>> 20.05.2019, 19:58, "Bastiaan Veelo" :
>>> On 20/05/2019 17:56, Konstantin Tokarev wrote:
20.05.2019, 18:27, "Bastiaan Veelo" :
> On 20/05/2019 16:51, Konstantin Tokarev wrote:
>> No
On 20/05/2019 19:02, Konstantin Tokarev wrote:
20.05.2019, 19:58, "Bastiaan Veelo" :
On 20/05/2019 17:56, Konstantin Tokarev wrote:
20.05.2019, 18:27, "Bastiaan Veelo" :
On 20/05/2019 16:51, Konstantin Tokarev wrote:
Note that it should be possible to rebuild QtTools with QtWebKit su
вт, 21 мая 2019 г., 14:25 Mutz, Marc via Development <
development@qt-project.org>:
> On 2019-05-21 13:03, Konstantin Ritt wrote:
> > вт, 21 мая 2019 г., 11:32 Mutz, Marc via Development
> > :
> >
> >> And while the partially-formed
> >> state can be extended to non-pimpled classes easily:
> >>
>
On 21/05/2019 12:24, Kai Köhne wrote:
-Original Message-
From: Development On Behalf Of
Subject: [Development] Assistant WebKit/WebEngine support
Hi,
I am prepared to do some work on Qt Assistant, and I'd like to know how that
will be received.
Cool, great you want to tackle this 😊
On 2019-05-21 13:03, Konstantin Ritt wrote:
вт, 21 мая 2019 г., 11:32 Mutz, Marc via Development
:
And while the partially-formed
state can be extended to non-pimpled classes easily:
class QRect {
int x, y, w, h;
public:
QRect() = default;
};
QRect r; // partially-formed
r.x(); // compilers
On 2019-05-21 12:52, Julien Cugnière wrote:
Le mar. 21 mai 2019 à 10:32, Mutz, Marc via Development
a écrit :
It is, however, be an acceptable stop-gap measure, and here a
compromise
may emerge, for keeping old code working while preparing for a
fully-implemented partially-formed state. This w
вт, 21 мая 2019 г., 11:32 Mutz, Marc via Development <
development@qt-project.org>:
> And while the partially-formed
> state can be extended to non-pimpled classes easily:
>
> class QRect {
> int x, y, w, h;
> public:
> QRect() = default;
> };
> QRect r; // part
Le mar. 21 mai 2019 à 10:32, Mutz, Marc via Development
a écrit :
> It is, however, be an acceptable stop-gap measure, and here a compromise
> may emerge, for keeping old code working while preparing for a
> fully-implemented partially-formed state. This would mean we do assign
> meaning to a null
> -Original Message-
> From: Development On Behalf Of
> Subject: [Development] Assistant WebKit/WebEngine support
>
> Hi,
>
> I am prepared to do some work on Qt Assistant, and I'd like to know how that
> will be received.
Cool, great you want to tackle this 😊
I'm sure Jarek (the offici
Den tis 21 maj 2019 kl 10:57 skrev Giuseppe D'Angelo via Development
:
>
> Il 21/05/19 10:26, Elvis Stansvik ha scritto:
> > They will not show up in the web search (I think).
> >
> > They are however available in the debian-debug archive, see
> > https://wiki.debian.org/AutomaticDebugPackages
>
>
> On 21. May 2019, at 08:32, Mutz, Marc via Development
> wrote:
>
> On 2019-05-20 23:43, André Pönitz wrote:
>> On Mon, May 20, 2019 at 11:23:13PM +0200, Mutz, Marc via Development wrote:
>>> On 2019-05-20 23:21, André Pönitz wrote:
>>> > > > Exhibit A:
>>> > > >
>>> > > > foo().contains
On 20/05/2019 23:11, André Pönitz wrote:
> On Mon, May 20, 2019 at 08:44:47PM +, Marco Bubke wrote:
>> On May 20, 2019 22:16:11 André Pönitz wrote:
>>
>>> On Fri, May 17, 2019 at 10:17:10AM +0200, Mutz, Marc via Development wrote:
[...] There is no readability difference between the use
Il 21/05/19 10:26, Elvis Stansvik ha scritto:
They will not show up in the web search (I think).
They are however available in the debian-debug archive, see
https://wiki.debian.org/AutomaticDebugPackages
[snip]
Genuine question, are those just the debug builds of a release build, or
are thos
Il 21/05/19 10:30, Konstantin Shegunov ha scritto:
That's a hard one. Especially since very few could keep in their brain a
list of the sizes of each and every one class from Qt. It also differs
depending on architecture.
I know. That's my point: we can't just break this level of source
compa
On Tue, May 21, 2019 at 11:26 AM Elvis Stansvik wrote:
> They will not show up in the web search (I think).
>
> They are however available in the debian-debug archive, see
> https://wiki.debian.org/AutomaticDebugPackages
Oh! You got me there. I was not aware of that. Thanks for pointing it out!
On Tue, May 21, 2019 at 11:04 AM Giuseppe D'Angelo via Development <
development@qt-project.org> wrote:
> which ones of the following guarantee
> integrity of references, i.e., _heap allocate every single element?
>
That's a hard one. Especially since very few could keep in their brain a
list of
Hi Lars,
There is a fine line between a proper partially-formed state and
basically folding std::optional into every value class.
The former is a compile-time state. It is not observable at runtime,
because any code which would observe a difference invokes UB. This is
the same principle as C
Den tis 21 maj 2019 kl 09:55 skrev Konstantin Shegunov :
>
> On Tue, May 21, 2019 at 9:49 AM Mutz, Marc via Development
> wrote:
>>
>> Oh, a nullptr deref is pretty clear in a backtrace.
>
>
> Indeed, but my point is that it's relatively useless for the user (or for the
> developer for that matt
On Tue, May 21, 2019 at 9:34 AM Mutz, Marc via Development <
development@qt-project.org> wrote:
> [...]
> This does not make the API simple to use.
Actually it does. Simple, as "easily understood or done" and
self-explanatory, which isn't the case for the Q3Slider's constructor. Yes,
familiarity
Il 20/05/19 19:08, NIkolai Marchenko ha scritto:
This rather nicely proves my point. Jason isn't even new to this list
and he didn't realize the problems.
No, community as a whole did _not _ have "years and years" to port away
from QList
Here's the practical QList test: which ones of the follo
Hi,
The deadline for submissions indeed got extended to * 2nd of June *... which is
already end of next week!
So feel free to still submit proposals, but hurry up 😊
https://www.surveymonkey.com/r/K7PMKC8
Regards
Kai
> -Original Message-
> From: Interest On Behalf Of Giuseppe
> D'Ang
On Tue, May 21, 2019 at 9:49 AM Mutz, Marc via Development <
development@qt-project.org> wrote:
> Oh, a nullptr deref is pretty clear in a backtrace.
Indeed, but my point is that it's relatively useless for the user (or for
the developer for that matter). As you pointed out the dev sees the null
> On 20 May 2019, at 20:18, Mutz, Marc via Development
> wrote:
>
> On 2019-05-20 17:16, Thiago Macieira wrote:
>> On Monday, 20 May 2019 05:51:49 PDT Mutz, Marc via Development wrote:
>>> Or maybe we don't disagree at all and Thiago would accept allocating
>>> memory (or, by extension, anythi
Hi Thiago!
Thanks a lot for the information!
However, the streaming classes are absolutely no replacement for the DOM
classes. In
theory yes, they both read and write XML. In reality they are different to a
degree that
it is practically impossible to replace DOM by stream. For legacy code anway
On dinsdag 21 mei 2019 02:04:42 CEST Quinn Romanek via Development wrote:
> Is there any current support/plan to support HDR pixel formats within Qt?
Dmitry prepared a number of patches to make it possible to display HDR images
in Qt:
Implement openGL surface color space selection in Angle
46 matches
Mail list logo
