Re: [Development] Json support for QtCore

On Sun, Dec 11, 2011 at 6:40 PM, Robin Burchell wrote: > You're missing the bit where the binary format is not the only > representation. JSON can be parsed into it, it's stored like this in > memory, and it can be serialised back to it (obviously), but it can > also be serialised back to JSON. Or

Re: [Development] Removing QtWebkit from gerrit (& qt5.git)

Robin Burchell said: > On Thu, Dec 8, 2011 at 12:20 AM, Rohan McGovern > wrote: > > Unfortunately the qtwebkit pointed at by qt5.git is outdated and known > > not to work. > > Given that webkit is developed upstream inside webkit.org, I'd second > that there's no reason having it there, aside per

Re: [Development] How to create new Qt modules or tools

On 13/12/2011, at 12:09 AM, wrote: > What is it that you require to upload the results to a cdash, and why > wouldn't qmake be able to do so? > I thought cmake simply ran cdash to upload the results, and certainly qmake > can easily add the rules for doing the same? I guess it would be pos

Re: [Development] V8's location

On Monday, 12 de December de 2011 18.03.53, aaron.kenn...@nokia.com wrote: > > $ git reset --hard d28b6a024826aaa48a8b3e69c096d01c91aff2c9 > > Checking out files: 100% (894/894), done. > > HEAD is now at d28b6a0 Add flag to avoid breakpoint relocation > > The Qt v8 repo is a clone of the official v

Re: [Development] V8's location

Hi, On 12/12/2011, at 2:15 PM, ext shane.kea...@accenture.com wrote: >> This would help a bit for one problem. >> >> But the other problem is that it makes working with qtbase harder >> because of >> the submodule. (while comitting you have to remember not to commit the >> v8 >> stuff) >> >> I

Re: [Development] How to create new Qt modules or tools

On Monday, 12 de December de 2011 16.27.40, Laszlo Papp wrote: > This topic brings my next question: what about projects migrating to > Qt Playground, but had been using doxygen rather than qdoc? qdoc is recommended, of course. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Archit

Re: [Development] How to create new Qt modules or tools

On Mon, Dec 12, 2011 at 3:09 PM, wrote: > What is it that you require to upload the results to  a cdash, and why > wouldn't qmake be able to do so? > I thought cmake simply ran cdash to upload the results, and certainly qmake > can easily add the rules for doing the same? > > What's the command

[Development] Feature defines in Qt 5?

Hi there, Is there any plan to keep or remove the defines in features.txt in Qt 5? (eg, QT_NO_SQL, QT_NO_DATESTRING etc) A colleague told me about talk of removing all the ifdefs, but he thought he'd convinced whoever it was he was talking to that the stuff should be kept. Is it something tha

Re: [Development] V8's location

> This would help a bit for one problem. > > But the other problem is that it makes working with qtbase harder > because of > the submodule. (while comitting you have to remember not to commit the > v8 > stuff) > > I think having a submodule in qtbase causes a lot of trouble for very > little > gai

Re: [Development] How to create new Qt modules or tools

What is it that you require to upload the results to a cdash, and why wouldn't qmake be able to do so? I thought cmake simply ran cdash to upload the results, and certainly qmake can easily add the rules for doing the same? What's the command line you need to run after a 'make check', and which

Re: [Development] Json support for QtCore

Not serialized, mmapped. Big difference, both in the resources needed to load/save and in complexity. -- .marius > -Original Message- > From: development-bounces+marius.storm-olsen=nokia.com@qt- > project.org [mailto:development-bounces+marius.storm- > olsen=nokia@qt-project.org] O

Re: [Development] Json support for QtCore

On 12/12/11 1:16 AM, "ext Thiago Macieira" wrote: >On Sunday, 11 de December de 2011 14.47.21, lars.kn...@nokia.com wrote: >> I now redid the benchmarks comparing qjson (as provided by my Ubuntu >> install, linked against Qt 4.7), qjsonparser (latest HEAD, linked >>against >> Qt 5) and my qtbinar

Re: [Development] NOTE: Gerrit going down for quick fix deployment (13:00 CET)

On 12/12/2011 12:44 PM, Sergio Ahumada wrote: > Hi, > > Gerrit will go down at 13:00 CET > today, for deployment of fixes. > > It should only take a few minutes to deploy and restart the service, > should nothing unexpected happen. > > I'll will send out a follo

[Development] NOTE: Gerrit going down for quick fix deployment (13:00 CET)

Hi, Gerrit will go down at 13:00 CET today, for deployment of fixes. It should only take a few minutes to deploy and restart the service, should nothing unexpected happen. I'll will send out a follow-up once the service is back up. Cheers, -- Sergio Ahuma

Re: [Development] Trying to setup environment to contribute. Error building webkit

> -Original Message- > From: development-bounces+kai.koehne=nokia@qt-project.org > [mailto:development-bounces+kai.koehne=nokia@qt-project.org] On > Behalf Of ext Jordi Pujol > Sent: Monday, December 12, 2011 8:42 AM > To: Mcgovern Rohan (Nokia-MP-Qt/Brisbane) > Cc: development > Su

Re: [Development] How to create new Qt modules or tools

> I really like the model of enabling the community to submit build results to > a central dashboard. It allows those with an interest in a particular > platform/compiler combination to put in the initial setup work and have their > combination included in the automated build/test infrastructure

Re: [Development] Trying to setup environment to contribute. Error building webkit

El dj 08 de 12 de 2011 a les 09:20 +1000, en/na Rohan McGovern va escriure: > Hi, > > Unfortunately the qtwebkit pointed at by qt5.git is outdated and known > not to work. Maybe it makes sense to remove it. (IMHO qtwebkit there > is not making sense since it is more of a "project which uses Qt"

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

Hi Stephen, Stephen Kelly wrote: > This week: > > == QSound removed == > == Talk of removing QWorkspace == > == QTemporaryDir arrives == > == Building v8 on MIPS == > == -bsymbolic-functions used by default == > == Extend the API for touch events == > == On screen keyboard and better Input Meth