[Development] Qt 4.8.2 content freezed

Hi all, Qt 4.8.2 sha1 is going to be on commit 1af008733c4b0ab94f8d4c272359b8f34b177a0b "Do not force OpenGL sample buffers on in the qnx qpa plugin" unless someone points out a very good reason to change it by sending email to releas...@qt-project.org mailing l

Re: [Development] The place of QML

Hi Alan, On Wed, Apr 25, 2012 at 6:16 AM, wrote: >>From: ext Girish Ramakrishnan [gir...@forwardbias.in] >>Sent: Tuesday, April 24, 2012 12:50 PM >>To: Donald Carr >>Cc: Alpert Alan (Nokia-MP/Brisbane); development@qt-project.org >>Subject: Re: [Development] The place of QML I do think we s

Re: [Development] The place of QML

>From: development-bounces+alan.alpert=nokia@qt-project.org >[development->bounces+alan.alpert=nokia@qt-project.org] on behalf of ext >d3fault [d3faultdot...@gmail.com] > Sent: Monday, April 23, 2012 9:33 PM > To: development@qt-project.org > Subject: Re: [Development] The place of QML

Re: [Development] The place of QML

>From: ext Girish Ramakrishnan [gir...@forwardbias.in] >Sent: Tuesday, April 24, 2012 12:50 PM >To: Donald Carr >Cc: Alpert Alan (Nokia-MP/Brisbane); development@qt-project.org >Subject: Re: [Development] The place of QML >>> I do think we should evaluate exposing the QML implementations to C++ for

Re: [Development] QString::fromAscii & toAscii's future

> > > There's no use in 'fixing' fromAscii(), toAscii() if we're deprecating it > anyway (which I support). So just let it be a synonym to fromLatin1(), > toLatin1(), which it was by default anyway in Qt4. I think this is a good idea. 2012/4/24 > > -Original Message- > > From: developme

Re: [Development] QString::fromAscii & toAscii's future

> From: Thiago Macieira > Subject: Re: [Development] QString::fromAscii & toAscii's future > On terça-feira, 24 de abril de 2012 07.33.41, BRM wrote: >> Question: is there are reason not to support the US-Extended ASCII >> (128-255)? I know it's not used often, but sometimes those characters >

Re: [Development] QString::fromAscii & toAscii's future

On Tue, Apr 24, 2012 at 8:01 AM, wrote: > There's no use in 'fixing' fromAscii(), toAscii() if we're deprecating it > anyway (which I support). So just let it be a synonym to fromLatin1(), > toLatin1(), which it was by default anyway in Qt4. > I like the idea. _

Re: [Development] [Interest] Building 32-bit Qt 5 on Mac

On terça-feira, 24 de abril de 2012 11.41.14, Stephen Chu wrote: > So I grabbed Qt 5 from git to give it a shot again. I am now more > confused then before. :) > > The configure script uses pre-processor output from > qtbase/config.tets/arch/arch.cpp to determine the host and target > architectures

Re: [Development] QString::fromAscii & toAscii's future

On terça-feira, 24 de abril de 2012 15.01.15, kai.koe...@nokia.com wrote: > There's no use in 'fixing' fromAscii(), toAscii() if we're deprecating it > anyway (which I support). So just let it be a synonym to fromLatin1(), > toLatin1(), which it was by default anyway in Qt4. Right, that's the mini

Re: [Development] QString::fromAscii & toAscii's future

> -Original Message- > From: development-bounces+kai.koehne=nokia@qt-project.org > [mailto:development-bounces+kai.koehne=nokia@qt-project.org] On > Behalf Of ext Thiago Macieira > Sent: Tuesday, April 24, 2012 4:54 PM > To: development@qt-project.org > Subject: Re: [Development] QS

Re: [Development] QString::fromAscii & toAscii's future

On terça-feira, 24 de abril de 2012 07.33.41, BRM wrote: > Question: is there are reason not to support the US-Extended ASCII > (128-255)? I know it's not used often, but sometimes those characters are > very useful. There's no such encoding. "The use of the term is sometimes criticized, because

Re: [Development] QString::fromAscii & toAscii's future

On terça-feira, 24 de abril de 2012 15.36.24, Olivier Goffart wrote: > On Tuesday 24 April 2012 14:27:10 Thiago Macieira wrote: > > The question I have is: what shall we do with QString::fromAscii? > > My personal preference would be to deprecate it. The name is confusing > compared to the others

Re: [Development] QLogger questions and proposal

On Mon, Apr 23, 2012 at 7:57 PM, Lincoln Ramsay wrote: > On 04/24/2012 04:47 AM, ext Mike Zraly wrote: > > First, what happens if QLogger is used inside a shared library, that > > library gets unloaded, and then settings are updated? > > > > From reading the code, it looks like once qCDebug is cal

Re: [Development] QString::fromAscii & toAscii's future

I'm with Olivier here. The default meaning in 4.x was :fromLatin1() (if you didn't use setCodecForCStrings()), so we could simply leave that behavior and simply deprecate the API. Cheers, Lars On 4/24/12 3:36 PM, "ext Olivier Goffart" wrote: >On Tuesday 24 April 2012 14:27:10 Thiago Macieira wr

Re: [Development] QString::fromAscii & toAscii's future

- Original Message - > From: Robin Burchell > 2012/4/24 Thiago Macieira : >> My recommendation is a variant of options 3: we document that it accepts > only >> US-ASCII and that it has undefined behaviour when the input isn't > US-ASCII >> compliant. That way, we can make it be equal

Re: [Development] QString::fromAscii & toAscii's future

2012/4/24 Thiago Macieira : > My recommendation is a variant of options 3: we document that it accepts only > US-ASCII and that it has undefined behaviour when the input isn't US-ASCII > compliant. That way, we can make it be equal to toLatin1() and avoid having to > write code for checking the hig

Re: [Development] QString::fromAscii & toAscii's future

On Tuesday 24 April 2012 14:27:10 Thiago Macieira wrote: > The question I have is: what shall we do with QString::fromAscii? My personal preference would be to deprecate it. The name is confusing compared to the others that explicitly specify the encoding. _

[Development] QString::fromAscii & toAscii's future

Since Qt 3 days[1], QString::fromAscii has stood for "from C strings" with "Ascii" standing for "that which the developer writes", instead of its proper definition of US-ASCII, a.k.a. ANSI X3.4-1986. By default, it was Latin 1 in Qt 3 and Qt 4. In addition, QTextCodec::setCodecForCStrings could be

Re: [Development] Qt Playground - Mock add-on module

> I would like to work on a Mock add-on module in Qt Playground that > might be beneficial later for certain projects. See the relevant > wikipage for a short introduction about the goals of mock objects in > testing: > http://en.wikipedia.org/wiki/Mock_object > > There were previous attempts to ad

Re: [Development] Suggested improvements to JIRA

On terça-feira, 24 de abril de 2012 03.22.40, mark.k...@nokia.com wrote: > -> We'll ask the subcons doing JIRA admin to get > https://plugins.atlassian.com/plugins/org.openmrs.jira.plugins.autowatchjir > a installed in the Sandbox and test if it is suitable for this task. That > should provide a s

Re: [Development] Towards a Qt 5 beta

On terça-feira, 24 de abril de 2012 14.48.10, techabc wrote: > 1. Does the beta will coming in end of this month aka. April ? No, probably a few weeks more. > 2. Is there binary packages with this upcoming beta ? That's the idea. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Ar

[Development] Qt Playground - Mock add-on module

Hi, I would like to work on a Mock add-on module in Qt Playground that might be beneficial later for certain projects. See the relevant wikipage for a short introduction about the goals of mock objects in testing: http://en.wikipedia.org/wiki/Mock_object Here you can find similar projects and sit

Re: [Development] Towards a Qt 5 beta: Documentation

On 4/24/12 9:53 AM, "ext casper.vandonde...@nokia.com" wrote: >Hi, > >I just cut out the rest of the email for clarity. (great that you would >want to help) > >I just want to talk about the inherits and inherited by problem. >"Inherits" should always work, because you compile the Qt code that way

Re: [Development] Towards a Qt 5 beta: Documentation

Hi, I just cut out the rest of the email for clarity. (great that you would want to help) I just want to talk about the inherits and inherited by problem. "Inherits" should always work, because you compile the Qt code that way (you cannot subclass a class that doesn't exist yet). I just want to