> -Original Message-
> From: Rose Todd (Nokia-M/Alpharetta)
> Sent: Tuesday, January 24, 2012 5:26 PM
> To: Koehne Kai (Nokia-MP/Berlin); development@qt-project.org
> Subject: RE: Work on qDebug and friends
>
> [...]
> The "additional things we need" question is pretty subjective, but ther
Does anyone feel responsible for/have an interest in these?
I'd like to add an overloaded constructor to QDropEvent and which takes values
for the proposedAction and source properties as an alternative to the current
method querying the values from a global instance of QDragManager. Something
Hello,
On 20/01/12 11:53 PM, "ext Laszlo Papp" wrote:
>> Hoe about QtAudio3D then?
>
>I am not familiar with Qt module naming conventions, but I think it is
>better than Qt3DAudio (ie. 3D would be more logical at the end of the
>module name) since:
>
>a) It is less likely to confuse someone into
On Tuesday, January 24, 2012 20:36:53 Thiago Macieira wrote:
> On Tuesday, 24 de January de 2012 22.45.54, Stephen Kelly wrote:
> > I think it makes sense, but that is an often used and overridden virtual
> > method, and changing it would not make the compiler notify about the
> > porting need (Ca
On Tuesday, 24 de January de 2012 22.45.54, Stephen Kelly wrote:
> I think it makes sense, but that is an often used and overridden virtual
> method, and changing it would not make the compiler notify about the
> porting need (Can't expect downstream to be using Q_DECL_OVERRIDE
> already).
Change
Hi,
https://bugreports.qt.nokia.com/browse/QTBUG-1072
This bug is essentially a request to change the QAIM API:
virtual void fetchMore(const QModelIndex &parent);
virtual bool canFetchMore(const QModelIndex &parent) const;
into:
virtual void fetchMore(const QModelIndex &parent,
I would also suggest adding (renamed, modified) non-qwidget libraries that
are moved to 'widgets' module. Concrete suggestion: QStandardItemModel
On Jan 24, 2012 5:11 PM, wrote:
> This project is to host the source code of APIs which have been removed in
> Qt5, where the replacement does not cove
On 01/23/2012 04:27 PM, ext Jonas Gastal wrote:
> P.S. Sorry if this is kinda of OT.
No problem but it is better that you use the mailing list created
precisely for topics like this:
http://lists.qt-project.org/mailman/listinfo/geg
There you can also get help from other Gerrit contributors.
Th
> Hi,
>
> I've been working on a patch to the Qt logging framework:
> http://codereview.qt-project.org/#change,13433,patchset=14 . Basically it
> redefines qDebug() and friends as a macro so that we can automatically
> capture the source file, line, and function a particular message comes from:
>
This module should be able to host any removed classes if they are technically
feasible to build on top of Qt5 after removal from the current library they
live in.
You will need to:
get agreement from the maintainer(s) to remove those models from Qt5
submit a patch to actually remove them
submit
On Tuesday, January 24, 2012 15:11:08 shane.kea...@accenture.com wrote:
> This project is to host the source code of APIs which have been removed in
> Qt5, where the replacement does not cover all features. Initially it will
> be used for static library versions of QFtp and QHttp. As previously
> d
This project is to host the source code of APIs which have been removed in Qt5,
where the replacement does not cover all features.
Initially it will be used for static library versions of QFtp and QHttp.
As previously discussed on this mailing list, some applications depend on
features of these c
On Tuesday 24 January 2012 11:03:11 kai.koe...@nokia.com wrote:
> KDE & kDebug
>
> Here debug categories are basically ints, which have to be registered
> 'kdelibs/kdecore/kdebug.areas'. You can pass your specific as an argument
> to kDebug(..) et al., but usually you just set a define
> (KDE_DEFA
On Tue, Jan 24, 2012 at 2:39 PM, wrote:
>
> Well, I plan to work on a simple environment switch which will enable the
> default logger to show the file, line, and the log level. My idea is that an
> IDE e.g. Qt Creator sets this environment variable, and voila, you can
> suddenly click on your
> -Original Message-
> From: ext Diego Iastrubni [mailto:diegoi...@gmail.com]
> Sent: Tuesday, January 24, 2012 1:18 PM
> To: Koehne Kai (Nokia-MP/Berlin)
> Cc: development@qt-project.org
> Subject: Re: [Development] Work on qDebug and friends
>
> So, if I want to have also time/date on my
> Honestly I don't think that "long" names are a bad thing /per se/.
It depends.
I think it's bad for types that are often instantiated as anonymous objects
within larger expressions.
Especially for constructors that are often called with just one string
parameter, so when used as anonymous ob
On Tuesday, 24 de January de 2012 11.59.26, lars.kn...@nokia.com wrote:
> QTextStream should always stream in the "C" locale if the base is not
> decimal.
0x123.456,7 ftw or ftl? :-)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
On Tue, Jan 24, 2012 at 12:41 PM, wrote:
> I've been working on a patch to the Qt logging framework:
> http://codereview.qt-project.org/#change,13433,patchset=14 . Basically it
> redefines qDebug() and friends as a macro so that we can automatically
> capture the source file, line, and function a
Working on it :)
Cheers,
Lars
On 1/23/12 12:07 AM, "ext Giuseppe D'Angelo" wrote:
>Hello,
>
>as per the CLA, I'd like to formally ask the Chief Maintainer and
>Nokia to give their consent for inclusion of the PCRE [1] library in
>the Qt Project. Being under the 3-clause BSD license [2], it sati
On 1/24/12 9:47 AM, "ext John Layt" wrote:
>
>On 24 Jan 2012 00:23, "John Layt" wrote:
>>
>> On Monday 23 Jan 2012 22:48:12 lars.kn...@nokia.com wrote:
>>
>> > I am very tempted to simply break this. localized binary numbers
>>simply
>> > don't make any sense.
>> >
>> > Cheers,
>> > Lars
>>
>> A
On Tuesday, 24 de January de 2012 11.32.19, Giuseppe D'Angelo wrote:
> On 24 January 2012 11:02, André Pönitz wrote:
> > But I think this case is special. "regex" (or "regexp") are used as
> > "proper" words in normal talk, like "url", and we do have "QUrl" for
> > that, and we also try to make th
On 24 January 2012 11:02, André Pönitz wrote:
> But I think this case is special. "regex" (or "regexp") are used as "proper"
> words in normal talk, like "url", and we do have "QUrl" for that, and we
> also try to make the API convienient to use.
>
> For the similarity of QRegExp and QRegex I agre
> -Original Message-
> From: Goddard Michael (Nokia-MP/Brisbane)
> Sent: Tuesday, January 24, 2012 11:57 AM
> To: Koehne Kai (Nokia-MP/Berlin); development@qt-project.org
> Subject: Re: [Development] Work on qDebug and friends
>
> Hello,
>
> > QMessageLogger(__FILE__, __LINE__, Q_FUNC_IN
> -Original Message-
> From: ext Frans Klaver [mailto:franskla...@gmail.com]
> Sent: Tuesday, January 24, 2012 11:46 AM
> To: Koehne Kai (Nokia-MP/Berlin)
> Cc: development@qt-project.org
> Subject: Re: [Development] Work on qDebug and friends
>
> [...]
> Sounds good. What, if any, will be
Hi,
One of the things still missing in the current debugging framework is to
categorize messages by area: This would allow you to enable/disable e.g. debug
messages for only one part of your app ...
KDE & kDebug
Here debug categories are basically ints, which have to be registered
'kdelibs/k
On Tuesday 24 January 2012 11:30:50 ext Giuseppe D'Angelo wrote:
> Hello,
>
> On 24 January 2012 09:10, Davet Jacques wrote:
> > "QRegularExpression" is such long and inconvenient name, even worse with
> > suffix like "QRegularExpressionMatch".
> >
> > Why not simply use "QRegex"? In addition to
Hello,
> QMessageLogger(__FILE__, __LINE__, Q_FUNC_INFO):debug("Hello World")
Yay, I don't have to do that any more :) Although now I'll have to remove
the existing ones..
>The patch is almost ready to go in ... Anyhow, the question is whether
>there's additional things we need to have in QtC
On Tue, Jan 24, 2012 at 11:41 AM, wrote:
> I've been working on a patch to the Qt logging framework:
> http://codereview.qt-project.org/#change,13433,patchset=14 . Basically it
> redefines qDebug() and friends as a macro so that we can automatically
> capture the source file, line, and functi
Hi,
I've been working on a patch to the Qt logging framework:
http://codereview.qt-project.org/#change,13433,patchset=14 . Basically it
redefines qDebug() and friends as a macro so that we can automatically capture
the source file, line, and function a particular message comes from:
qDebug("
Hello,
On 24 January 2012 09:10, Davet Jacques wrote:
> "QRegularExpression" is such long and inconvenient name, even worse with
> suffix like "QRegularExpressionMatch".
>
> Why not simply use "QRegex"? In addition to shorter, it would also fall in
> line with "std::regex" and "Boost.Regex".
>
"QRegularExpression" is such long and inconvenient name, even worse with suffix
like "QRegularExpressionMatch".
Why not simply use "QRegex"? In addition to shorter, it would also fall in line
with "std::regex" and "Boost.Regex".
I realize it may be easier to confuse with the old "QRegExp", but
On 24 Jan 2012 00:23, "John Layt" wrote:
>
> On Monday 23 Jan 2012 22:48:12 lars.kn...@nokia.com wrote:
>
> > I am very tempted to simply break this. localized binary numbers simply
> > don't make any sense.
> >
> > Cheers,
> > Lars
>
> Agreed it makes no sense.
>
> My initial thought was just to
32 matches
Mail list logo
