> yeah, 6.0 is a joke given that you intend to break binary
> compat in 6.1 - that's the wisdom of linking r's bonus payments to
> release dates even for major versions
Thank you for saying what no one else dared to say.
--
Best Regards,
Bernhar
forming us.
Funny, this is pretty much how I would phrased it as well.
--
Best Regards,
Bernhard Lindner
signature.asc
Description: This is a digitally signed message part
___
Development mailing list
Development@qt-project.org
https://lists.qt-pr
> ... resulting in users complaining about "high priority bugs get ignored".
They're still complaining? Impressive. I have already passed the phase of
resignation and
just wonder why there is still a public bug tracker.
--
Best Regards,
Ber
tal (or at least qWarning).
--
Best Regards,
Bernhard Lindner
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
gs about
deprecation of
operator < for QVariant.
--
Best Regards,
Bernhard Lindner
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
egards,
Bernhard Lindner
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
ve. And they're way too slow for a regular run.
I thought of something like a simple, manually maintained ABI version. Sure, on
the one
hand this wouldn't prevent uninentional BC breaks. On the other hand, BC
changes could be
done intentionally and managed in a safe way (without strange cra
Hi!
> Breaking BC means subtle errors that are hard do detect and debug.
Couldn't those subtle errors be replaced by some clear and understandable
error? Like some explicit binary compatibility check?
--
Best Regards,
Bernhard Lind
On Monday, June 15, 2020 14:06 CEST, Jani Heikkinen
wrote:
> Hi Everyone,
>
> We have published first Qt6.0.0 snapshot today, see more info from Tuukka's
> blog post: https://www.qt.io/blog/first-qt-6.0-snapshot-available
Hi,
is the source available somewhere? Can't find any 6.0 tarballs
Hi,
On Monday, February 24, 2020 18:19 CET, Ulf Hermann wrote:
> > Is there a better way to determine what modules are provided?
>
> You could scan the plugins.qmltypes files. There you get a detailed
> listing that tells you what components are available under what imports
> and
Hi,
I'm adding a Requires:/Provides: autogenerator for QML modules to rpm (so
packages containing a qml file will automatically pull in the right library
dependencies).
I have a more or less working prototype that extracts relevant information from
qmldir files, but given "module" statements
I agree completely with Jason.
--
Best Regards,
Bernhard Lindner
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
s://bugreports.qt.io/browse/QTBUG-77020
--
Best Regards,
Bernhard Lindner
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
> * enable templated QObjects. There's a prototype from Olivier, so is that
> possible?
Yes, this is long overdue.
--
Best Regards,
Bernhard Lindner
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/li
r) replacement is an MCA in my
book. And it
heavily damages Qt's reputation.
The criteria that allows to deprecate a component without proper replacement
should be
EXTREMELY defensive.
--
Best Regards,
Bernhard Lindner
___
Development mailing list
Dev
le templates).
Any proposals for a Qt 6 story?
I hope my suspicion is wrong that Qt has spent so much on a few cash cows that
it is no
longer capable of any other major advances (but must even go backwards, see XML
thread).
--
Best Regards,
Bernhard Lindner
__
trategic goals if the limits or goals are unknown?
Actions out of frustration are never a good idea. And pushing into a
(technical) direction
that does not solve the underlying (strategical) problem is futile.
--
Best Regards,
Bernhard Lindner
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
itely
> but to actively develop them further?
No answer to my question above?
--
Best Regards,
Bernhard Lindner
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
actively develop them further?
--
Best Regards,
Bernhard Lindner
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
nsider it broken? I consider that class fundamental.
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.
--
Best Regards,
Bernhard L
> 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
nfusion is perfect. Especially notice issue 71784 above. That is what I
talked about
earlier when I said without clean documentation you can not do clean Qt6
planning.
--
Best Regards,
Bernhard Lindner
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
ion instead of ambiguous sentences like the one I cited?
--
Best Regards,
Bernhard Lindner
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
> I don't think the "Done" nomenclature stuck though. In half the cases it
> just meant unmaintained rather than actually done.
That document should be revised. It obviously is very important. How can you
even do
strategical planing without such a fundamental docu
nd their meaning? Is there a
component/state
table where we could lookup the specific states?
--
Best Regards,
Bernhard Lindner
signature.asc
Description: This is a digitally signed message part
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
rogress, such as the QList discussion. Those two
> modules
> are not in the way of anything else, so the decision can change.
>
> All it takes is someone stepping up to maintain either or both of them.
>
--
Best Regards,
Bernhard Lindner
_
?
- Are the deprecations irrevocable?
--
Best Regards,
Bernhard Lindner
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
Then compare this thread/answer: https://stackoverflow.com/a/18549053/1421332
With this thread/answer: https://stackoverflow.com/a/421615/1421332
And, LOL, do not skip the comment below the first answer!
Nothing more to say.
--
Best Regards,
Bernhard Lindner
_
till requiring a few changes
> though, e.g. std::unordered_map iterators are forward, QHash ones are
> bidirectional. If the SIC is acceptable, something to consider for Qt 6.
Are there any plans/discussions how to procede with that experiment?
should be
done...
I start wondering if it is possible to wrap the STL containers in Qt6 and give
them a
nice, intuitive, Qt-like API while still providing full STL compatibility. I am
sure this
has been evaluated. Are the results documented somewhere?
--
Best Regards,
Be
Actually the Qt update behavior annoys my as well.
I wish there would be two checkbox options in the maintenance tool:
"Install new bug fix versions automatically"
"Install new minor versions automatically"
This is reasonable, isn't it?
--
Best Regards
Bernhard Lind
Why not use one of the continous integration services like travis-ci or
circle-ci?
Cheers,
Bernhard
Uwe Rathmann schrieb am So., 17. März 2019,
14:55:
> Hi,
>
> all arguments for doing Continuous Integration for Qt ( https://
> blog.qt.io/blog/2016/08/08/coin-continuous-integr
r forever.
--
Best Regards,
Bernhard Lindner
signature.asc
Description: This is a digitally signed message part
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
ems
> somewhat arbitrary.
> 4) Default values of object properties being context dependent is not that
> unusual
>
>
> Cheers,
> Volker
>
--
Best Regards,
Bernhard Lindner
On 11 Feb 2019, at 22:47, Bernhard Lindner wrote:
> >
> > Hi!
> >
> > I just
lt default of true to
buttons with
QDialogButtonBox parents instead of QDialog parents?
4. Anyway, is it good style to change the default value (!) of a property
dynamically like
this?
Thanks in advance!
--
Best Regards,
Bernhard Lindner
signature.asc
Description: This is a
Hi everybody!
Are there any plans for Qt6' API to use standard types like size_t (or special
replacements like qsizetype) for return values and parameters that have
platform dependent
width?
--
Best Regards,
Bernhard Lindner
___
Development mailing
egy of yours (simply asking for an all-inclusive proof and
guarantee) ever work before?
--
Regards Bernhard
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Resisting to have anything and everything in black and white is hard and is not
popular
and surely not zeitgeist but sometimes the better way.
Please do not make me discuss about that as well, I prefer to wrangle with item
delegate
code ;)
--
Best regards,
Bernhar
a recent example.
I didn't say "technical". Also I didn't say "number of e-mails".
Anyway I think engineering and politics should be separated. On any level.
Politics is
extremly harmful to engineering. CoCs are always politi
I wish any one discussion about Qt software quality would have attracted so much
attention, passion and effort as this CoC topic.
--
Best Regards,
Bernhard Lindner
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org
a side note: Do you know an estimated timeframe for when it will be
publicly available?
Would be really interested in the details.
2018-06-19 23:13 GMT+02:00 Thiago Macieira :
> On Tuesday, 19 June 2018 14:04:45 PDT Bernhard B wrote:
> > Sorry, I don't get it. But what's the point of providi
Sorry, I don't get it. But what's the point of providing a link to the
Intel github rpo if we can't access it?
Am Dienstag, 19. Juni 2018 schrieb Thiago Macieira :
> On Tuesday, 19 June 2018 13:15:18 PDT Jason H wrote:
> > > Currently, we use https://github.com/clearlinux/cve-check-tool. This
>
that it laggs, but
on iOs it's smooth. But again, I haven't profiled it yet, so it most
probably could be related to the complex bindings in the delegate and not
due to the GC.
Bernhard
Am Dienstag, 25. Juli 2017 schrieb Phil Bouchard :
> On 07/25/2017 02:50 AM, Tomasz Siekierda wrote:
>
>> On
ot; button
//and the tab bar
if(verticalVelocity > flickTabBarTreshold){
backToTopButton.visible = false;
tabBar.hide();
}
}
I don't know if this is the best solution, but it seems to work.
Thanks,
Bernhard
2017-01-26 15:38 GMT+01:00 Bernhard B <schluc...@gmail
ow() === 0, I a signal will be emitted. In QML I am
connecting on that signal and execute backToTopButton.visible = false;
I haven't tested it yet, but I think it should work.
For the other two conditions however, I am a little bit clueless.
Does anyone of you guys maybe have an idea on how to impr
> 3/ as generic : it should be able to use any QIODevice for transport/storage
+1
> 1/ discards XML and JSON, and 3/ discards QSettings and D-Bus.
Thanks for pointing this out!
P.S.: https://bugreports.qt.io/browse/QTBUG-25237
--
Regards, Bernhard
signature.asc
Description: This is a digitall
For example, with moc removed we support template classes that inherit
from QObject.
Wow. I would (almost) kill for having that feature in Qt!
--
Regards
Bernhard Lindner
___
Development mailing list
Development@qt-project.org
http://lists.qt
?
Are there other significant differences that I should consider?
--
Kind Regards
Bernhard Lindner
-Ursprüngliche Nachricht-
Von: development-bounces+private=bernhard-lindner...@qt-project.org
[mailto:development-bounces+private=bernhard-lindner.de@qt-
project.org] Im Auftrag von Knoll Lars
is dropping the web engine component or dropping old compilers I
wouldn't need to think a second about the decision.
--
Kind Regards
Bernhard Lindner
-Ursprüngliche Nachricht-
Von: development-bounces+private=bernhard-lindner...@qt-project.org
[mailto:development-bounces+private
an invisible but harmful character that can't be
compiled (seems the character is inserted directly in front if the
showEvent function name).
Has something changed in the formatting Assistant's pages from Qt 5.3.2 to
Qt 5.4? Can someone confirm/explain this?
--
Kind Regards
Bernhard Lindner
50 matches
Mail list logo
