Full agreement with Konstantin. It's two weeks before the feature freeze and we
haven't seen any more then a draft. I am against any new classes going into Qt
essential modules that do not have direct and proven use cases.
Develop it in a playground project, show why it makes sense and once you
Ok, let's use QtWin for the namespace. For the module itself it makes IMO
to keep the 'Extras' in the name.
Cheers,
Lars
On 06.09.13 15:52, Sorvig Morten morten.sor...@digia.com wrote:
I agree, QtWin::foo looks much better. We can rename the QtMacExtras
namespace as well.
What about the module
On Mon, Sep 9, 2013 at 11:40 PM, Konstantin Ritt ritt...@gmail.com wrote:
2013/9/9 Sune Vuorela nos...@vuorela.dk
The api has been stabilized and well tested since like forever.
Let's get a QAbstractJob heavily inspired by KJob in now.
A nice side effect of getting it in now is that the
Thanks for the additional information. I'm not an export on OpenGL but
if I give it a try I'll report my findings here.
Cheers,
Conny
On Mon, 2013-09-09 at 05:52 +, Abrahamsen-Blomfeldt Eskil wrote:
Hi,
So far there hasn't been much research on this, but the idea was to render it
into
Hello guys,
At attempt to do fetch, git failed, e.g.:
...
User@Host /e/git/ng/789/qtserialport (stable)
$ git fetch https://codereview.qt-project.org/p/qt/qtserialport
refs/changes/27/64927/1 git checkout FETCH_HEAD
efrror: RPC failed; result=22, HTTP code = 503
atal: The remote end hung up
Hello,
You can try the SSH command instead of the Anonymous HTTP command.
(Don't know why it isn't working)
Cheers,
Jerome P.
Documentation Engineer - Digia, Qt
Fra: development-bounces+jerome.pasion=digia@qt-project.org
On 09/10/2013 03:34 PM, Denis Shienkov wrote:
Hello guys,
At attempt to do fetch, git failed, e.g.:
...
User@Host /e/git/ng/789/qtserialport (stable)
$ git fetch https://codereview.qt-project.org/p/qt/qtserialport
refs/changes/27/64927/1 git checkout FETCH_HEAD
efrror: RPC failed;
Guys, thanks in any case.
I was logged in, but for the unknown reason was active the Anonymous HTTP
button instead of SSH. After switching to SSH - all works.
Thanks.
Best regards,
Denis
10.09.2013, 17:58, Sergio Ahumada sergio.ahum...@digia.com:
On 09/10/2013 03:34 PM, Denis Shienkov wrote:
On 10 September 2013 14:27, Knoll Lars lars.kn...@digia.com wrote:
Ok, let's use QtWin for the namespace. For the module itself it makes IMO
to keep the 'Extras' in the name.
Cheers,
Lars
QtWin or QWin?
Comparison with other namespaces: http://qt-project.org/wiki/Qt_5_Structure
Earlier
On terça-feira, 10 de setembro de 2013 22:31:53, Sze Howe Koh wrote:
On 10 September 2013 14:27, Knoll Lars lars.kn...@digia.com wrote:
Ok, let's use QtWin for the namespace. For the module itself it makes IMO
to keep the 'Extras' in the name.
Cheers,
Lars
QtWin or QWin?
QtWin,
Alright guys, let's try to complete the feature. As I heard from sides
now that you want a key-value store, I'll do it that way.
Feature list:
1. Q_INFO is a new macro (which expands to nothing):
#define Q_INFO(key, value)
2. Q_INFO can be prepended to:
- Classes
- Signals, slots and
Hi,
Other people have suggested adding the info to the Q_PROPERTY
expansion.
This would avoid a sequence of Q_INFO / Q_PROPERTY pairs in the class
that
might be difficult to read:
Q_INFO(foo, bar)
Q_PROPERTY(int bar READ bar)
Q_INFO(foo, baz)
Q_PROPERTY(int
On terça-feira, 10 de setembro de 2013 19:27:48, Stefan Merettig wrote:
Hi,
Other people have suggested adding the info to the Q_PROPERTY
expansion.
This would avoid a sequence of Q_INFO / Q_PROPERTY pairs in the class
that
might be difficult to read:
Q_INFO(foo, bar)
On 05.09.2013 12:10, Daniel Teske wrote:
QScopedPointer has never been a scoped pointer. It has always had a .reset()
method. That should never have been part of QScopedPointer.
I wonder if this would happen again with the current review process.
daniel#
On 06.09.2013 19:52, David Faure wrote:
connect(job, SIGNAL(result(QJob*)),
this, SLOT(handleResult(QJob*)));
This looks so old-school like in times of futures and monads.
Couldn't such a class be part of the hopefully coming QtConcurrent replacement?
Peter
Am 10.09.2013 20:28, schrieb Thiago Macieira:
Right. I'd be fine with supporting something like
Q_PROPERTY( ... INFO foo = bar)
Though IMO that's way less easy to read. Would be fine as alternative
syntax.
(Sidenote: In this case, multiple INFO's should be allowed to appear)
Sure.
On 10.09.2013 08:16, Knoll Lars wrote:
Develop it in a playground project, show why it makes sense and once you have
a stable API let's discuss into which module it should go.
An idea I already had when I saw the QUniquePoiner implementation:
Couldn't we add a new branch to
On terça-feira, 10 de setembro de 2013 21:03:24, Stefan Merettig wrote:
Ah, sorry for that. I'm fine with that for now, the only little
behaviour I want to add to this is the guarantee, that values
appear sorted by their key in the same sequence they appear in
in the code. So it behaves like a
On terça-feira, 10 de setembro de 2013 21:01:51, Peter Kümmel wrote:
On 10.09.2013 08:16, Knoll Lars wrote:
Develop it in a playground project, show why it makes sense and once you
have a stable API let's discuss into which module it should go.
An idea I already had when I saw the
Am 10.09.2013 22:26, schrieb Thiago Macieira:
What does Q_CLASSINFO do?
From looking at the code, it maintains the order of entries.
The documentation of QMetaClassInfo doesn't say anything on this.
___
Development mailing list
On Tue, Sep 10, 2013 at 4:46 PM, Thiago Macieira
thiago.macie...@intel.comwrote:
On terça-feira, 10 de setembro de 2013 22:31:53, Sze Howe Koh wrote:
On 10 September 2013 14:27, Knoll Lars lars.kn...@digia.com wrote:
Ok, let's use QtWin for the namespace. For the module itself it makes
IMO
21 matches
Mail list logo
