On 2019-05-25 21:55, Bernhard Lindner wrote:
Using XML without using a schema validator is (or at least should be)
a no-go. So even if
the Qt XML component should be continued in some way, Qt should also
not lack a schema validator.
Have you tried other C++ schema validators ?
We should be ca
Hi!
> For Qt XML Patterns, the situation is IMO a bit different. The module has
> some architectural problems
Do you think this is true for all parts of the component?
I am asking because I can not imagine using XML without a schema validator,
which is part
of Qt Xml Pattern. Do you consider it
24.05.2019, 12:44, "Kai Köhne" :
>> -Original Message-
>> From: Development On Behalf Of
>> Bernhard Lindner
>> Subject: Re: [Development] Qt XML and Qt Xml Patterns
>>
>> > It's good that Bernhard has received an official st
> -Original Message-
> From: Development On Behalf Of
> Bernhard Lindner
> Subject: Re: [Development] Qt XML and Qt Xml Patterns
>
> > It's good that Bernhard has received an official statement.
>
> I agree! Thank you!
Indeed, thanks for bringing this up
> It's good that Bernhard has received an official statement.
I agree! Thank you!
> In general, I think the Qt Company could make a little more effort to
> communicate such decisions, educate its user community, and attract new
> potential maintainers. Actually, communication should start before
> This was a case where I thought it is obvious already. The definition of
> "Done" (given by Thiago earlier in this thread) has not applied for a
> long time anymore. There hasn't been maintainer for a long time. I
> understand this leave use cases in the dust but this can only by averted
> if so
Il 22/05/19 09:11, Alex Blasche ha scritto:
This was a case where I thought it is obvious already. The definition of "Done"
(given by Thiago earlier in this thread) has not applied for a long time anymore. There
hasn't been maintainer for a long time. I understand this leave use cases in the du
> -Original Message-
> From: Development On Behalf Of
> Giuseppe D'Angelo via Development
> I think both XML and XMLPatterns are Done, not Deprecated.
>
> Reasoning: only the former has an explicit note in the documentation (can't
> find
> an equivalent for the latter):
>
> > https:
> 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
-
> 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
> > 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
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
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 Monday, 20 May 2019 19:35:03 PDT Kevin Kofler wrote:
> Thiago Macieira wrote:
> > The replacement for QtXml are the streaming classes in QtCore. They've
> > been available for 10 years.
>
> But those are no replacement for the QDom* DOM API. They are also not
> idiomatic SAX, by design. Both th
Thiago Macieira wrote:
> The replacement for QtXml are the streaming classes in QtCore. They've
> been available for 10 years.
But those are no replacement for the QDom* DOM API. They are also not
idiomatic SAX, by design. Both those limitations make them an insufficient
replacement for QtXml ev
On Monday, 20 May 2019 15:41:16 PDT Bernhard Lindner wrote:
> Hi!
>
> Is it correct that the Qt XML and Qt Xml Patterns components are both
> deprecated?
Yes, they are.
>
> If yes, are there any details known like:
> - How long or up to which Qt version will these components be part of Qt?
> -
Hi!
Is it correct that the Qt XML and Qt Xml Patterns components are both
deprecated?
If yes, are there any details known like:
- How long or up to which Qt version will these components be part of Qt?
- Will replacment components be available?
- Are security fixes still be implemented?
- Are th
22 matches
Mail list logo
