Re: [Development] Question about QCoreApplicationData::*_libpaths

On 23-1-2016 17:39, Milian Wolff wrote: On Freitag, 22. Januar 2016 22:51:30 CET Kevin Kofler wrote: Marc Mutz wrote: And this is where I stop taking you seriously, sorry. You can demand such nonsense, but if you do, _do_ the work yourself. Go. Implement those 80+ algorithms from the STL for Qt

Re: [Development] Question about QCoreApplicationData::*_libpaths

On 22-1-2016 22:51, Kevin Kofler wrote: I'd already be happy with those that were (are, actually) already there. I'd rather have 10-20 common algorithms with a convenient API than 80+ obscure ones that force me to use iterators (especially the boilerplate .begin() and .end() iterators that will

Re: [Development] Question about QCoreApplicationData::*_libpaths

On 21-1-2016 21:09, Milian Wolff wrote: On Donnerstag, 21. Januar 2016 07:25:21 CET André Somers wrote: Op 21/01/2016 om 05:35 schreef Thiago Macieira: On Thursday 21 January 2016 05:27:50 Kevin Kofler wrote: Thiago Macieira wrote: The copy constructor is called once, then the move constructo

Re: [Development] FW: Backwards compatibiltiy break in Qt 5.5

On 27-7-2015 18:13, Thiago Macieira wrote: > On Monday 27 July 2015 08:44:30 Knoll Lars wrote: >> I can understand the issues that non latin speakers are facing with this >> well. I’ve often used qDebug() to debug non latin use cases, and in 90% of >> the cases I just want to know what the string r

Re: [Development] Qt LTS & C++11 plans (CopperSpice)

On 27-7-2015 18:21, Thiago Macieira wrote: > On Monday 27 July 2015 08:01:53 André Somers wrote: >> I am not a lawer and I don't know the wording of the KDE Free Qt >> Foundation agreement, but are you sure that in case that agreement is >> triggered the verion you branched off off will fall under

Re: [Development] Container benchmark was HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO

On 12-7-2015 19:56, Smith Martin wrote: >> If it doesn't, then why not choose QVector? > My intent in getting the information from Marc is to change the documentation > of QList to say that. > > But QList is easy to use. How is it easier to use than QVector? I will grand you two: QList is two cha

Re: [Development] QTextStream::readLine(0) is an ambiguous overload in 5.5

On 13-5-2015 2:44, Thiago Macieira wrote: > On Wednesday 13 May 2015 02:34:28 Jan Kundrát wrote: >> Hi, >> this commit [1] added a new overload to QTextStream::readLine. As a result >> of that, calling stream.readLine(0) is now ambiguous: >> >> QString readLine(qint64 maxlen = 0); >> bool

Re: [Development] Future of Qt Quick 1 in Qt 5

On 8-5-2015 18:47, Hausmann Simon wrote: > Hi, > > If the public API would allow you to implement what the folks at KDAB did at > http://www.kdab.com/creating-pdf-qtquick-2-scene-slideviewer/ ‎, would that > help your use case? What they basicaly did was reimplement the Quick elements they were

Re: [Development] RFC: RAII for property changes

On 15-4-2015 21:05, Keith Gardner wrote: > QPropertyGuard g{this}; > g.addProperty("a"); // use QObject::property > g.addProperty("b", m_b); // take value member by reference > g.addProperty(m_c, &cChanged); // ...and also slot address There's type erasure going on, s

Re: [Development] RFC: RAII for property changes

On 15-4-2015 18:44, Matthew Woehlke wrote: > The second form would thus save the value <-> QVariant comparison and > not much else. The third form however eliminates the string look-up > entirely by having the user provide both the backing member variable > *and* what to do when a change should

Re: [Development] RFC: RAII for property changes

On 15-4-2015 17:08, Matthew Woehlke wrote: > On 2015-04-15 10:43, Marc Mutz wrote: >> On Wednesday 15 April 2015 11:49:56 André Somers wrote: >>> void MyClass::setFoo(QString value) >>> { >>> PropertyGuard guard(this, "foo"); //foo is the name of the Q_PROPERTY >>> Q_UNUSED(guard); >>> >>>

Re: [Development] RFC: RAII for property changes

On 15-4-2015 16:54, Keith Gardner wrote: On Wed, Apr 15, 2015 at 9:38 AM Marc Mutz > wrote: Hi André, On Wednesday 15 April 2015 11:49:56 André Somers wrote: > void MyClass::setFoo(QString value) > { >PropertyGuard guard(this, "foo"); //foo

Re: [Development] New company name for Qt part of Digia and unified web site

On 16-9-2014 20:50, Knoll Lars wrote: > On 16/09/14 16:51, "Mark Gaiser" wrote: > >> On Tue, Sep 16, 2014 at 2:11 PM, Knoll Lars wrote: >>> Hi everybody, >>> >>> I’m happy to tell you that we’re making significant progress towards the >>> new unified web page that I’ve first been talking about at

Re: [Development] [Interest] Direct-lookup translation, even for English (was Re: get english translation)

On 4-9-2014 18:26, Thiago Macieira wrote: > On Thursday 04 September 2014 13:03:12 Saether Jan-Arve wrote: >> Somebody already suggested to embed it as a resource, isn't that good >> enough? > As long as we also load it by default. We cannot depend on users loading the > translation file from the r

Re: [Development] Harmonizing the Qt 5.x Documentation

Matthew Woehlke schreef op 11-3-2014 17:04: > On 2014-03-11 05:01, Pasion Jerome wrote: >> Short summary: We will be redirecting viewers of Qt 5.0 and Qt 5.1 >> documentation >> to "Qt 5" documentation. Subsequently, we will remove the 5.0 and 5.1 >> documentation >> from qt-project.org and we wi

Re: [Development] Need suggestion for a new API

Mandeep Sandhu schreef op 31-1-2014 13:47: > Hi All, > > I needed a suggestion on an API I'm adding to QNetworkAccessManager > and co. > > I'm adding a HTTP redirect feature to QNAM. It can be enabled at a > global (QNAM) level, or can be enabled/disabled on a per request > (QNetworkRequest) bas

Re: [Development] A QtCore class for event-driven jobs

Op 6-9-2013 19:56, Matt Broadstone schreef: On Fri, Sep 6, 2013 at 1:52 PM, David Faure > wrote: I would like to propose the inclusion of a QJob class in QtCore, based on years of experience with KIO::Job and KJob. The idea is to encapsulate an event

Re: [Development] New online installers available for testing

Op 31-5-2013 11:50, Heikkinen Jani schreef: Hi all! There is new online installers available in http://download.qt-project.org/online/qt5/online_installers/ At the moment content is Qt5.0.2 but it will be updated to Qt5.1 RC1 w

Re: [Development] Evolving Qt's multithreading API

Op 4-3-2013 21:21, Thiago Macieira schreef: > On segunda-feira, 4 de março de 2013 17.25.35, André Somers wrote: >> QFuture runFunction(QFunction then, QFunction main); >> QFuture runFunction(QFuntion then, QFuntion main); >> QFuture runFunction(QFunction main); > I think this is going too far. If

Re: [Development] Evolving Qt's multithreading API

Op 22-2-2013 11:57, Sze Howe Koh schreef: >> Some more common use case would be (pseudo-code) >> > >> >auto watcher = new QFutureWatcher; >> >QObject::connect(watcher, SIGNAL(finished()), myObject, SLOT(doStuff())); >> >watcher->setFuture(QThrerad::run([]() { return computeStuff(); } )); >> >// who

Re: [Development] Qt Hebrew

Op 1-2-2013 17:41, Genghis Khan schreef: > On Fri, 1 Feb 2013 09:26:24 + > Knoll Lars wrote: > >> On Jan 31, 2013, at 4:13 PM, Genghis Khan wrote: >> >>> Hello, >>> >>> I would like to initiate a new group >>> called "Qt Hebrew" for Hebrew speakers, where new an

Re: [Development] Closing Jira Bugs

Op 30-1-2013 21:19, Shaw Andy schreef: > Just to muddy the waters here, but would it be possible to make sure > it only does this when the patch integrates? What happens if the bug > is reopened because it turns out to be still be an issue? Andy That can always happen, even after releasing. I do

Re: [Development] Closing Jira Bugs

Op 30-1-2013 19:34, Robin Burchell schreef: > On Wed, Jan 30, 2013 at 7:05 PM, Sergio Ahumada > wrote: >> How many changes do you need to close a jira task ? one, two, more, who >> knows ? > The person submitting the change. > > The way I've seen this done various other places is to stop trying to

Re: [Development] QAction-like API for QML

Op 12-12-2012 18:35, Stephen Kelly schreef: > On Wednesday, December 12, 2012 09:44:10 André Somers wrote: >> Op 11-12-2012 21:59, Alan Alpert schreef: >>> On Tue, Dec 11, 2012 at 10:49 AM, Shawn Rutledge >>> >>> wrote: On Tue, Dec 11, 2012 at 09:48:22AM -0800, Alan Alpert wrote: > Why ca

Re: [Development] New mailing list: web_AT_qt-project.org created

Op 26-11-2012 12:12, Verma Gurudutt schreef: Hi I am really happy to inform you all that new mailing list web_AT_qt-project.org is created now. We will be discussing open governance model of web development related stuffs for qt-project.org here and proposal for this was made few days ago

Re: [Development] HEADS UP: Changes in QStyle subclasses

Op 24-11-2012 12:09, Nurmi J-P schreef: Hi all, Thanks to QStyleFactory and QProxyStyle, it is possible to instantiate and customize any available style. This is not limited to the built-in styles in QtWidgets, but also works fine for any style plugin since it nicely avoids the build time dep

Re: [Development] QFileSystemWatcher and Recursive Monitoring

Op 28-7-2012 11:04, d3fault schreef: > > I've been thinking about it some more, and I think it would be a good > idea to add another optional bool to the opt-in custom interface > constructor. > Having (series of) bools in API's is usually a bad idea. See for instance this blog posting: http://

Re: [Development] Abandoning the container changes

Op 16-7-2012 23:52, Thiago Macieira schreef: > On segunda-feira, 16 de julho de 2012 21.34.10, André Pönitz wrote: >> On Thu, Jul 05, 2012 at 09:04:39AM +0300, Thiago Macieira wrote: >>> Hello all >>> >>> I think that, despite the potential benefits of the changes, we >>> should not apply them at t

Re: [Development] Notes from the QWidget session

Op 27-6-2012 22:17, Иван Комиссаров schreef: > Hm... What about adding new (maybe rather simple) widgets? QtCreator has > QtColorButton class, QtFontButton, lineedit for editing shortcuts (i have my > own modified copy). > Browser example has ModelMenu and ModelToolBar classes (rather useful in s

Re: [Development] Qt Summit 2012 Registration is now open!

Op 14-4-2012 12:08, Sivan Greenberg schreef: > On Fri, Apr 13, 2012 at 8:57 PM, Quim Gil wrote: >> Still "a third party" from a Qt Project point of view but I guess one >> that you are more used to trust. Sorry, it was the fastest and simplest >> way to save us from handling emails manually. > Who

Re: [Development] Dropping the Q prefix from class names

Op 2-4-2012 1:02, joao.abeca...@nokia.com schreef: Hello again, To every-concerned-one-of-you, I hope you do realize that we share all of those same concerns. We do! :-) I really enjoyed this joke. Thanks! :-D André ___ Development mailing list Dev

Re: [Development] QDoc can't ignore Q_PROPERTY

Op 9-3-2012 23:22, casper.vandonde...@nokia.com schreef: > Just to make sure everybody understands: > With this change applied all NOTIFY properties that are currently documented > will not be documented anymore. > > If there are no objections before coming Tuesday (13 March) 09:00 Oslo time I >

Re: [Development] videoPlayer crashed

Hi Brian, 1) It is rude to hijack somebody elses thread. The thread you are replying in is about a request for a UI Helpers repository, not about Phonon. 2) You're in the wrong mailing list. This list deals with developing Qt *itself*, not with developing *with* Qt. You are looking for the inter..

Re: [Development] RFC: The Future of QDoc

Op 10-2-2012 8:07, Andre Somers schreef: > Op 9-2-2012 19:13, marius.storm-ol...@nokia.com schreef: >> On 09/02/2012 10:33, ext Manuel Nickschas wrote: >>> On Thursday 09 February 2012 15:36:09 ext Olivier Goffart wrote: >>>>> I am working on QDoc part-time

Re: [Development] RFC: The Future of QDoc

Op 9-2-2012 19:13, marius.storm-ol...@nokia.com schreef: > On 09/02/2012 10:33, ext Manuel Nickschas wrote: >> On Thursday 09 February 2012 15:36:09 ext Olivier Goffart wrote: I am working on QDoc part-time and we have been discussing some changes that we would like to implement to make q

Re: [Development] Qt Contributors Summit: when and where

Op 3-1-2012 21:14, Richard Moore schreef: >>> - How many rooms, which capacity? No need to get into details but having >>> a rough idea would be useful in order to book the right amount of space. >>> For you this means what type of event do you want: was the event last >>> year good or would you pr

Re: [Development] Qt Contributors Summit: when and where

Op 3-1-2012 19:48, marius.storm-ol...@nokia.com schreef: > On 03/01/2012 12:25, ext Jonas M. Gastal wrote: >> On Tuesday 03 January 2012 18:11:08 marius.storm-ol...@nokia.com >> wrote: >>> On 03/01/2012 11:14, ext Quim Gil wrote: - When? There have been different opinions and the trend seems t

Re: [Development] QRegularExpression -- first round of API review

Op 16-12-2011 1:07, Giuseppe D'Angelo schreef: > >> fwiw, the usual elegant solution is having a value and a mask parameter. >> the mask could have two magic values meaning "un-/set all asserted in >> vlaue" to mean effectively what your bool means. the default argument >> would be the magic value

Re: [Development] Json support for QtCore

Op 11-12-2011 15:55, lars.kn...@nokia.com schreef: > The binary representation is optimized for fast reading. The binary > format > is relatively compact and stores the whole object in one blob. >> Is this a standard binary format of JSON, or something of your own devise? > It's something I wrote.

Re: [Development] This week in Qt 5 development (week 49)

Op 9-12-2011 20:18, Stephen Kelly schreef: On Friday, December 09, 2011 20:12:05 Stephen Kelly wrote: > This week: > Oops, sorry. This was not intended for the Qt mailing list. I was compiling it for colleages. Aren't we all, in a way? ;-) Anyway, thanks. I think it is informative! André

Re: [Development] Moving itemmodels classes to QtCore

Op 23-11-2011 14:52, shane.kea...@accenture.com schreef: Hi, I think moving the item models back into QtGui would be better than QtCore. * QML and Widgets applications both depend on QtGui * The item models have no use outside of a GUI application. * QtGui was the location of these classes

Re: [Development] QTemporaryDir API

Op 16-11-2011 18:56, David Faure schreef: > On Wednesday 16 November 2011 18:26:25 Andre Somers wrote: >> Op 16-11-2011 18:13, David Faure schreef: >>> Hello, >>> >>> As previously discussed on qt5-feedback, I wrote QTemporaryDir and >>> submitted it

Re: [Development] QTemporaryDir API

Op 16-11-2011 18:13, David Faure schreef: > Hello, > > As previously discussed on qt5-feedback, I wrote QTemporaryDir and submitted > it to gerrit at http://codereview.qt-project.org/#change,8297 > After a few reviews from Thiago (and redoing the implementation on Windows) > it's now ready for subm

Re: [Development] API review for a new QDnsResolver class

Op 9-11-2011 19:35, Jeremy Lainé schreef: > On 11/09/2011 07:21 PM, Peter Hartmann wrote: >> On 11/09/2011 06:43 PM, ext Jeremy Lainé wrote: >>> (...) >>> A/ static QDnsReply* QDnsReply::lookup(QDnsReply::Type, QString); >>> >>> pro: easy to connect to the QDnsReply's signal >>> con: it's entirely

Re: [Development] API review for a new QDnsResolver class

Op 4-11-2011 20:31, Jeremy Lainé schreef: > On 11/04/2011 10:15 AM, André Somers wrote: >> The more I think about it, the more I think it is important to fix this: who >> is >> responsible for the lifetime of the QDnsReply object? >> > Why not have the same pattern as QNAM for consistency? How abo

Re: [Development] New feature to qstring | QString::toBool()

Op 27-10-2011 20:13, Andreas Aardal Hanssen schreef: > 2011/10/26 Christoph Feck >> As far as I remember, POSIX locales offer strings or regexps for YES >> and NO, so it might be possible to add something to QLocale to access >> those strings. > By auto-converting a QString to a bool we'll be addin

Re: [Development] New feature to qstring | QString::toBool()

Op 26-10-2011 10:02, Frans Klaver schreef: > On Wed, Oct 26, 2011 at 9:21 AM, Andre Somers wrote: > >> IMHO, there is a big difference between a string that correctly converts >> to false, and one that can not be converted to a boolean. Do you really >> wish to make t

Re: [Development] New feature to qstring | QString::toBool()

Op 26-10-2011 8:39, Frans Klaver schreef: > On Wed, Oct 26, 2011 at 8:31 AM, wrote: > >> Consider this code: >> >> bool parseOk; >> if (str.toBool(&parseOk)) { >> if (parseOk) >> enableSuperFastRenderer(); >> } > I think that in most, if not all cases, the parseOk argument would or > e