Re: [Development] New feature to qstring | QString::toBool()

2011-10-27 Thread Thiago Macieira
On Thursday, 27 de October de 2011 21:25:28 Andre Somers wrote: > QString("1,234").toDouble() also isn't all that clear either, only the > QLocale version of those is localized. > With a US locale, that would result in 1234.0 (more than a thousand), > while in the Netherlands, it would be 1.234 (on

Re: [Development] New feature to qstring | QString::toBool()

2011-10-27 Thread Andre Somers
Op 27-10-2011 20:13, Andreas Aardal Hanssen schreef: > 2011/10/26 Christoph Feck >> As far as I remember, POSIX locales offer strings or regexps for YES >> and NO, so it might be possible to add something to QLocale to access >> those strings. > By auto-converting a QString to a bool we'll be addin

Re: [Development] New feature to qstring | QString::toBool()

2011-10-27 Thread Andreas Aardal Hanssen
2011/10/26 Christoph Feck > As far as I remember, POSIX locales offer strings or regexps for YES > and NO, so it might be possible to add something to QLocale to access > those strings. By auto-converting a QString to a bool we'll be adding ambiguity to Qt APIs. If there's no intuitive way to con

Re: [Development] Keep dependent projects in mind when approving changes

2011-10-27 Thread paivi.rajala
Hi Robin, We thought that having an integer QContactLocalId is a bit too restricting. E.g. if you have a uuid as backend contact id (as the case is in JsonDb backend), it's lot simpler to treat it as a string than as an integer. Changing QContactLocalId to QString was the first step in trying t

Re: [Development] QTBUG-10481: Adding support for DNS SRV lookups

2011-10-27 Thread Jeremy Lainé
> I suggest QDnsServiceInfo and QDnsServiceRecord for the API class names. > While a "host" is well known enough for the QHostInfo class name you started > with, a "srv" isn't obvious. > It is a "service" (with "SRV" being a DNS abbreviation, like "A") > To avoid ambiguity with other types of serv

Re: [Development] QtWeb

2011-10-27 Thread Dhaivat Pandya
So, as far as I see it, we will not be needing the Filter, or Access Control mechanisms for FCGI (at least to begin with), what do you guys say? On Wed, Oct 26, 2011 at 5:02 PM, Dhaivat Pandya wrote: > I also agree. Javascript just never occurred to me... > > > On Wed, Oct 26, 2011 at 1:13 AM, Ma

Re: [Development] [Interest] Qt 5 worries - A plea for software rendering fallbacks

2011-10-27 Thread lars.knoll
On 10/27/11 12:21 PM, "ext Simon Hausmann" wrote: [snip] > >On a related note: The Chromium folks seem to be rather successful in >shipping >WebGL on Windows on top of Angle ( http://code.google.com/p/angleproject/ >). >It would be nice to try out Angle for QtQuick/OpenGL in Qt 5 on Windows. Abso

Re: [Development] [Interest] Qt 5 worries - A plea for software rendering fallbacks

2011-10-27 Thread lars.knoll
On 10/27/11 11:48 AM, "ext Frans Klaver" wrote: >Hi, > >On Thu, Oct 27, 2011 at 11:37 AM, Schimkowitsch Robert > wrote: > >> I see there's no Qt5-Feedback list up and running, so I'll post here in >>the >> meantime. > >AFAIK all qt5 feedback can go onto the development mailing list now. >It's pro

Re: [Development] [Interest] Qt 5 worries - A plea for software rendering fallbacks

2011-10-27 Thread Simon Hausmann
On Thursday, October 27, 2011 11:48:52 AM ext Frans Klaver wrote: > Hi, > > On Thu, Oct 27, 2011 at 11:37 AM, Schimkowitsch Robert > wrote: > > > I see there's no Qt5-Feedback list up and running, so I'll post here in the > > meantime. > > AFAIK all qt5 feedback can go onto the development mail

Re: [Development] [Interest] Qt 5 worries - A plea for software rendering fallbacks

2011-10-27 Thread Frans Klaver
Hi, On Thu, Oct 27, 2011 at 11:37 AM, Schimkowitsch Robert wrote: > I see there's no Qt5-Feedback list up and running, so I'll post here in the > meantime. AFAIK all qt5 feedback can go onto the development mailing list now. It's probably best to continue the discussion there. Cheers, Frans

Re: [Development] Keep dependent projects in mind when approving changes

2011-10-27 Thread Rohan McGovern
marius.storm-ol...@nokia.com said: > Hi Maintainers and Approver, > > Please keep in mind dependent modules when you approve and merge in > changes which can lead to dependent projects failing. If you know that a > commit has a risk of destabilizing other modules, please ensure that you > are prep

Re: [Development] Keep dependent projects in mind when approving changes

2011-10-27 Thread Robin Burchell
Hi Lars, On Thu, Oct 27, 2011 at 8:21 AM, wrote: > In addition, I'd like to be added as a reviewer for changes that break > source compatibility with the public API of Qt 4.x. Please also add some > comment in the changes file in this case. Following up on this, do you have any information abou