On quarta-feira, 15 de fevereiro de 2012 11.00.35, Lincoln Ramsay wrote:
> I'm not in a position to say "we can use variadic macros in QtCore"
> which is why I didn't actually try to do that.
You can use it if you add the necessary #ifdef for the compilers that support
it or for C++11 support (Q_C
On Wednesday 15. February 2012 02.00.35 ext Lincoln Ramsay wrote:
> On 02/14/2012 08:22 PM, Koehne Kai (Nokia-MP/Berlin) wrote:
> > Just wanted to point out that there are variadic macros
>
> I'm aware of this but last time I checked, they weren't in the C++
> standard. It seems they're new to C99
This is a heads-up regarding the renaming of QML C++ classes. As per
https://bugreports.qt-project.org/browse/QTBUG-23737 class names that currently
begin with QDeclarative* will be renamed Qml*, for example QDeclarativeEngine
will become QmlEngine.
This change is needed because QtQuick 1 has
On quarta-feira, 15 de fevereiro de 2012 07.38.44, gunnar.sle...@nokia.com
wrote:
> Our initial idea was to change "qreal" to "double" to avoid any potential
> regression but the impact on size combined with the fact that the added
> precision is almost never needed changed our minds
> (https://bug
Den 15. feb. 2012 08:38, skrev ext gunnar.sle...@nokia.com:
> For some time we have wanted to unify the behavior of qreal on desktop and
> embedded. Currently, qreal is defined to be double on desktop and to a float
> on embedded.
>
> The reasons for unifying are:
>
> - Using "double" is pure w
On Wednesday 15. February 2012 08.38.44 ext gunnar.sle...@nokia.com wrote:
> For some time we have wanted to unify the behavior of qreal on desktop and
> embedded. Currently, qreal is defined to be double on desktop and to a
> float on embedded.
>
> The reasons for unifying are:
>
> - Using "dou
On quarta-feira, 15 de fevereiro de 2012 08.22.17, martin.jo...@nokia.com
wrote:
> This is a heads-up regarding the renaming of QML C++ classes. As per
> https://bugreports.qt-project.org/browse/QTBUG-23737 class names that
> currently begin with QDeclarative* will be renamed Qml*, for example
> Q
On 2/15/12 9:26 AM, "ext Thiago Macieira"
wrote:
>On quarta-feira, 15 de fevereiro de 2012 07.38.44,
>gunnar.sle...@nokia.com
>wrote:
>> Our initial idea was to change "qreal" to "double" to avoid any
>>potential
>> regression but the impact on size combined with the fact that the added
>> precis
On Wed, 15 Feb 2012 18:46:34 ext Thiago Macieira wrote:
> On quarta-feira, 15 de fevereiro de 2012 08.22.17, martin.jo...@nokia.com
>
> wrote:
> > This is a heads-up regarding the renaming of QML C++ classes. As per
> > https://bugreports.qt-project.org/browse/QTBUG-23737 class names that
> > cur
Hi,
As part of http://codereview.qt-project.org/#change,14763 (new
meta-object data format) it would be good to change the return type of
QMetaMethod::signature() from const char * to QByteArray.
In the new meta-data format, the raw, 0-terminated signature string is
no longer stored; the signat
On quarta-feira, 15 de fevereiro de 2012 08.49.31, lars.kn...@nokia.com wrote:
> I don't think it'll break too many places though, so I'm not too worried
> about the change.
It will. Ask Ubuntu packagers for how much work they had to put in to fix the
mismatches in KDE. We can assume that work is
On quarta-feira, 15 de fevereiro de 2012 18.59.45, Alan Alpert wrote:
> > Q followed by lowercase letters used to be reserved for third-party
> > implementations. The Q in Qt classes means Qt itself, it's not the first
> > letter in another acronym. So these classes should actually be called
> > "Q
Hi,
On 15/02/2012, at 9:44 AM, ext Thiago Macieira wrote:
> How big are the Qt Quick 1 language support classes? I'm asking so we can
> have
> an idea of how much maintenance effort those classes will be. I assume that
> they will continue to use V8, which will be continually updated and modif
On quarta-feira, 15 de fevereiro de 2012 09.53.29, aaron.kenn...@nokia.com
wrote:
> Hi,
>
> On 15/02/2012, at 9:44 AM, ext Thiago Macieira wrote:
> > How big are the Qt Quick 1 language support classes? I'm asking so we can
> > have an idea of how much maintenance effort those classes will be. I
>
On 2/15/12 10:28 AM, "ext Thiago Macieira"
wrote:
>On quarta-feira, 15 de fevereiro de 2012 08.49.31, lars.kn...@nokia.com
>wrote:
>> I don't think it'll break too many places though, so I'm not too worried
>> about the change.
>
>It will. Ask Ubuntu packagers for how much work they had to put in
2012/2/15 Thiago Macieira
> On quarta-feira, 15 de fevereiro de 2012 09.53.29, aaron.kenn...@nokia.com
> wrote:
> > Hi,
> >
> > On 15/02/2012, at 9:44 AM, ext Thiago Macieira wrote:
> > > How big are the Qt Quick 1 language support classes? I'm asking so we
> can
> > > have an idea of how much ma
2012/2/15 Mark :
> Why would you still support QML 1? Qt5 is going to have QML 2 which should
> be superior to QML 1 in about every single way so why not just drop it for
> Qt5?
Because one of the central points of Qt 5 is maintaining compatibility
with Qt 4 as far as is possible. That means not b
On Wed, Feb 15, 2012 at 11:17 AM, Robin Burchell wrote:
> 2012/2/15 Mark :
> > Why would you still support QML 1? Qt5 is going to have QML 2 which
> should
> > be superior to QML 1 in about every single way so why not just drop it
> for
> > Qt5?
>
> Because one of the central points of Qt 5 is mai
On Wednesday 15 February 2012 10:44:46 Thiago Macieira wrote:
> On quarta-feira, 15 de fevereiro de 2012 18.59.45, Alan Alpert wrote:
> > > Q followed by lowercase letters used to be reserved for third-party
> > > implementations. The Q in Qt classes means Qt itself, it's not the first
> > > letter
Op 2/15/2012 11:21 AM, Mark schreef:
On Wed, Feb 15, 2012 at 11:17 AM, Robin Burchell
mailto:robin%2...@viroteck.net>> wrote:
2012/2/15 Mark mailto:mark...@gmail.com>>:
> Why would you still support QML 1? Qt5 is going to have QML 2
which should
> be superior to QML 1 in about e
On 15/02/2012, at 8:58 PM, wrote:
> On 2/15/12 10:28 AM, "ext Thiago Macieira"
> wrote:
>
>> On quarta-feira, 15 de fevereiro de 2012 08.49.31, lars.kn...@nokia.com
>> wrote:
>>> I don't think it'll break too many places though, so I'm not too worried
>>> about the change.
>>
>> It will. Ask
On Wednesday 15 February 2012 22:02:10 craig.sc...@csiro.au wrote:
> On 15/02/2012, at 8:58 PM,
wrote:
> > On 2/15/12 10:28 AM, "ext Thiago Macieira"
> >
> > wrote:
> >> On quarta-feira, 15 de fevereiro de 2012 08.49.31, lars.kn...@nokia.com
> >>
> >> wrote:
> >>> I don't think it'll break to
On 2/15/12 12:11 PM, "ext Olivier Goffart" wrote:
>On Wednesday 15 February 2012 22:02:10 craig.sc...@csiro.au wrote:
>> On 15/02/2012, at 8:58 PM,
>>
>wrote:
>> > On 2/15/12 10:28 AM, "ext Thiago Macieira"
>> >
>> > wrote:
>> >> On quarta-feira, 15 de fevereiro de 2012 08.49.31,
>>lars.kn...@
On quarta-feira, 15 de fevereiro de 2012 11.43.35, Olivier Goffart wrote:
> > To be honest, QMLEngine is better than QmlEngine.
>
> No.
> Qt naming convention says otherwise. (QXmlFoo, QUrl)
> It was changed in Qt4.0: Acronyms are writen CamelCase as every other words.
Indeed, which is why I'm say
On Wednesday 15 February 2012 10:56:54 Thiago Macieira wrote:
> On quarta-feira, 15 de fevereiro de 2012 09.53.29, aaron.kenn...@nokia.com
>
> wrote:
> > Hi,
> >
> > On 15/02/2012, at 9:44 AM, ext Thiago Macieira wrote:
> > > How big are the Qt Quick 1 language support classes? I'm asking so we
>
On Wed, Feb 15, 2012 at 8:31 AM, Olivier Goffart wrote:
>
> Anyway, this is a compatibility library. It's sole role is to be there to help
> transition (just like qt3support was)
I had the impression that most people agreed that qt3support was a
mistake. Are we going to take the same strategy for
> Sletta Gunnar (Nokia-MP/Oslo) wrote:
> - Using "double" is pure waste for a lot of use cases. QRectF, QPointF,
> QPainter, QPolygonF,
> OpenGL, QMouseEvent, QTouchEvent, to name a few. None of these require the
> precision
> offered by double precision floating point.
Whether having doub
On quarta-feira, 15 de fevereiro de 2012 12.11.27, Olivier Goffart wrote:
> Then I tought about Qt has its own typedef for quintptr and quint64 and what
> not, so we could as well keep qreal.
> (But i'm far from being opposed, but then we can also deprecate all the
> other ones)
Those have other r
On Wednesday 15 February 2012 07:38:44 gunnar.sle...@nokia.com wrote:
> The only questionable use case is geolocation. We know for a fact that
> floats have limitations in this area and both Qt3D and QtLocation make use
> of QVector[2|3|4]D and QMatrix4x4 which will now be a float. However, this
>
On 2/15/12 12:53 PM, "ext andre.poen...@nokia.com"
wrote:
>
>> Sletta Gunnar (Nokia-MP/Oslo) wrote:
>> - Using "double" is pure waste for a lot of use cases. QRectF,
>>QPointF, QPainter, QPolygonF,
>> OpenGL, QMouseEvent, QTouchEvent, to name a few. None of these require
>>the precision
>> off
On 02/15/2012 01:17 PM, ext Olivier Goffart wrote:
> On Wednesday 15 February 2012 07:38:44 gunnar.sle...@nokia.com wrote:
>> The only questionable use case is geolocation. We know for a fact that
>> floats have limitations in this area and both Qt3D and QtLocation make use
>> of QVector[2|3|4]D an
On quarta-feira, 15 de fevereiro de 2012 12.33.18, lars.kn...@nokia.com wrote:
> Just a small nitpick: You won't end up on the wrong side of the river. The
> earth has a diameter of around 4km. With 24 bits precision, you end up
> with a jitter of just above 2m. You might get wet feet though ;-
> From: Lincoln Ramsay
> To: development@qt-project.org
> Cc:
> Sent: Tuesday, February 14, 2012 8:05 PM
> Subject: Re: [Development] QLog ( Work on qDebug and friends)
>
> On 02/15/2012 01:47 AM, ext BRM wrote:
>> I'd much rather see a Category object being pushed via
> operator<<()
>> inste
> From: "lars.kn...@nokia.com"
> On 2/15/12 12:11 PM, "ext Olivier Goffart" wrote:
>> On Wednesday 15 February 2012 22:02:10 craig.sc...@csiro.au wrote:
>>> On 15/02/2012, at 8:58 PM,
>>>
>> wrote:
>>> > On 2/15/12 10:28 AM, "ext Thiago Macieira"
>
>>> >
>>> > wrote:
>>> >> On quarta-f
On 15/02/2012 07:45, ext Thiago Macieira wrote:
> On quarta-feira, 15 de fevereiro de 2012 12.33.18, lars.kn...@nokia.com wrote:
>> Just a small nitpick: You won't end up on the wrong side of the river. The
>> earth has a diameter of around 4km. With 24 bits precision, you end up
>> with a jitt
Hi,
On Wednesday 01 February 2012 01:59:49 Stephen Kelly wrote:
> On Tuesday, January 31, 2012 22:50:51 you wrote:
> > * I'd prefer if we don't have to ship the database. As noted it can
> > change easily
> > and a compiled in database would get out of sync.
Look for the system database - on syst
On 15/02/2012 11:53, andre.poen...@nokia.com wrote:
> Anyway. It's probably better to go for any kind of uniformity. If that's
> single precision, it should be made clear that QPolygonF/QRectF are not
> meant for applications needing "polygons" in general. Maybe one should
> consider adding som
On Wednesday, February 15, 2012 21:55:54 Konrad Rosenbaum wrote:
> The
> calculation results are almost identical. Almost.
Is that enough?
John Layt mentioned the existence of such a mapping too.
>
> A parser for Olson DB files is not overly complex to write - I did that
> within a weekend.
I understand that QML/Quick is young, which justifies breaking backwards
compatibility as it matures... but thinking longer-term, wouldn't it be
better to call the newest QtQuick (2.0) just QtQuick and the 1.0 version
Qt4Quick... to retain backwards compatibility? Does this promise of
backwards com
On Wed, 15 Feb 2012 21:41:06 ext Artur Souza (MoRpHeUz) wrote:
> On Wed, Feb 15, 2012 at 8:31 AM, Olivier Goffart wrote:
> > Anyway, this is a compatibility library. It's sole role is to be there to
> > help transition (just like qt3support was)
>
> I had the impression that most people agreed th
On Thu, 16 Feb 2012 12:07:54 ext d3fault wrote:
> I understand that QML/Quick is young, which justifies breaking backwards
> compatibility as it matures... but thinking longer-term, wouldn't it be
> better to call the newest QtQuick (2.0) just QtQuick and the 1.0 version
> Qt4Quick... to retain bac
Dear All:
When I compile qt5 webkit it give the error message below:
=
"qtwebkit/Source/WebKit/qt/declarative/qdeclarativewebview_p.h:25:28: fatal
error: QDeclarativeItem: No such file or directory
=
but I found this file is in the qtquick1 module, so I try add this module via
some pro f
On 02/16/2012 02:14 AM, ext BRM wrote:
>> This fails the "do nothing quickly" test so the cost of leaving
>> such statements in shipping code is high, even when the categories
>> are disabled.
>>
>> This works fine though.
>>
>> qLog(category1)<< "message for category1";
>> qLog(category2)<< "messa
> From: Lincoln Ramsay
>To: BRM
>On 02/16/2012 02:14 AM, ext BRM wrote:
>>> This fails the "do nothing quickly" test so the cost of leaving
>>> such statements in shipping code is high, even when the categories
>>> are disabled.
>>>
>>> This works fine though.
>>>
>>> qLog(category1)<< "messa
Hi,
On Wed, Feb 15, 2012 at 3:26 AM, wrote:
> On 2/15/12 12:11 PM, "ext Olivier Goffart" wrote:
>
>>On Wednesday 15 February 2012 22:02:10 craig.sc...@csiro.au wrote:
>>> On 15/02/2012, at 8:58 PM,
>>>
>>wrote:
>>> > On 2/15/12 10:28 AM, "ext Thiago Macieira"
>>> >
>>> > wrote:
>>> >> On quar
On Thu, Feb 16, 2012 at 8:01 AM, Girish Ramakrishnan
wrote:
> I think changing qreal to float will result in subtle porting bugs:
> like when a Qt4 QDataStream (a double) is read by Qt5 (which is now
> suddenly float).
Huh? QDataStream doesn't have any stream operators for qreal, does it?
The doc
46 matches
Mail list logo
