Re: [Development] Tagging private symbols as such

2016-12-13 Thread Lisandro Damián Nicanor Pérez Meyer
On miércoles, 7 de diciembre de 2016 08:02:20 ART Thiago Macieira wrote: [snip] > But the extra versioning is a further safety check: if something was missed > in the update, like for example some code compiled by the user (regardless > of use of package management), it will necessarily stop

[Development] Fwd: [Interest] QtIFW 2.0.4 Release?

2016-12-13 Thread Konstantin Podsvirov
Hello guys!QtSDK maintenance now based on 2.0.4 framework, but what about 2.0.4 tag and binaries for QtIFW? ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Rules for Third-Party components in Qt 5.8 onwards

2016-12-13 Thread Kai Koehne
Hi, (I'll try to answer some comments made in the gerrit review here. IMO gerrit works great for editorial stuff, but not for more substantial things). > [Tobias Hunger] > I would make the homepage mandatory in the attribution file. That information > is critical IMHO when you want to find out

Re: [Development] A new approach for Qt main()

2016-12-13 Thread Edward Welbourne
Morten Sorvig supplied: > For some background, here’s what typical application startup looks > like on macOS, NaCl, and Emscripten: I've updated [0] to illustrate these. [0] https://wiki.qt.io/Application_Start-up_Patterns > macOS: Define the application delegate, create instance of it in

[Development] Rules for Third-Party components in Qt 4.8 onwards

2016-12-13 Thread Kai Koehne
Hi, I'd like to put down the rules on how we handle code in Qt that we as Qt contributors do not have copyright over ourselves in a QUIP: https://codereview.qt-project.org/#/c/177201/6/quip-0004.txt I suggest that - Every third party component must be documented by a qt_attribution.json file -

Re: [Development] A new approach for Qt main()

2016-12-13 Thread Simon Hausmann
Hi, I don't think it does handle those cases. But we're not talking about eliminating main(), we're talking about a second supported "launch" method. That said, it's still possible to run code before the constructor, although it's not pretty. Simon From:

Re: [Development] A new approach for Qt main()

2016-12-13 Thread Laszlo Agocs
Hi, How does this handle the cases that need code before the QGuiApplication construction? AFAICS it does not. Laszlo From: Development [mailto:development-bounces+laszlo.agocs=qt...@qt-project.org] On Behalf Of Simon Hausmann Sent: Tuesday, December 13, 2016 10:37 AM To: Mathias Hasselmann

Re: [Development] A new approach for Qt main()

2016-12-13 Thread Simon Hausmann
Hi, The joke of the bikeshedding aside I for one do like the idea of exporting a QObject sub-class instead of a function. That makes it easier to extend in the future with more entry-points as slots for example. Simon From: Development