Re: [Development] fixing name of QNetworkAccessManager::createRequest
Giuseppe D'Angelo gmail.com> writes: > Being an API break, do you see any good motivation to justify it? Yes, it can only be done in new major version. When if not now? > (I agree that the method name is wrong since it creates the reply, but > breaking software "just because" doesn't sound good to me either) Well, having method createX which creates Y doesn't sound good to me either. Regards, Piotr Dobrogost ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Linking source with docs
Hi! Linking source with docs - I think it's nice idea. Python does it and Qt could also. From "Open Source Challenge: Open Your Source, More " by Raymond Hettinger: "Large code bases and obscure installation paths are a fact of life, but there is something we can do to reconnect our users with the source code. Starting with Python 3.2, I’ve gone through the module documentation and added direct links to the relevant source code." http://rhettinger.wordpress.com/2011/01/28/open-your-source-more/ Regards Piotr Dobrogost ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] fixing name of QNetworkAccessManager::createRequest
Hi! Is QNetworkAccessManager::createRequest (http://doc.qt.nokia.com/qt5/qnetworkaccessmanager.html#createRequest) going to be renamed to proper name QNetworkAccessManager::createReply in Qt5? Regards Piotr Dobrogost ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
