> While that it would be awesome to have a system which could compile test each
> uploaded patch set, and preferably have the results available before
> developers would review them, I think it something that will not scale; at
> least not without a system which can guarantee proper incremental
Hi,
I was looking at toHtmlEscaped() method in QString class which converts
metacharacters <, >, &, and " replaced by HTML entities.
is there any other method which can replace other metacharacters for example (:
, = ) etc ?
Also is there a method which will do the other way round eg: fromHtml
On 28/01/2012, at 1:03 AM, ext Stephen Kelly wrote:
> On Friday, January 27, 2012 13:30:35 Thiago Macieira wrote:
> > Correct. What do we need extending them with? The only virtuals you left in
> > the API were stream (which I didn't get) and utcOffset, which doesn't seem
> > to need to be a virt
On Fri, Jan 27, 2012 at 6:27 PM, Olivier Goffart wrote:
> /me wonder why we still even care about QT_NO_STL
I was originally on the side of caring about QT_NO_STL, but your
message made me wonder (again) about just how necessary this is. I
think the only target I'd consider really valid for this
Torsdag 26. januar 2012 17.04.39 skrev Christiansen Kenneth.R:
> Hi there,
>
> I wonder how the accessibility work for editors relates to input methods,
> because the input methods need about the same information (selected text,
> surrounding text, etc), and basing it on top of that would mean tha
On Friday, 27 de January de 2012 18.00.55, Olivier Goffart wrote:
> On Friday 27 January 2012 17:32:28 Pau Garcia i Quiles wrote:
> > On Fri, Jan 27, 2012 at 5:27 PM, Olivier Goffart wrote:
> > > /me wonder why we still even care about QT_NO_STL
> >
> > Embedded?
>
> Care to elaborate?
>
> (I dese
On Friday, 27 de January de 2012 16.03.51, Stephen Kelly wrote:
> On Friday, January 27, 2012 13:30:35 Thiago Macieira wrote:
> > Correct. What do we need extending them with? The only virtuals you left
> > in
> > the API were stream (which I didn't get) and utcOffset, which doesn't seem
> > to nee
On Friday 27 January 2012 18:02:02 André Pönitz wrote:
> On Friday 27 January 2012 17:49:01 ext Jonas M. Gastal wrote:
> > On Friday 27 January 2012 09:42:19 Charley Bay wrote:
> > > > /me wonder why we still even care about QT_NO_STL
> > > >
> > > >
> > > > Embedded?
> > >
> > > +1
> > >
> > >
On Friday 27 January 2012 17:49:01 ext Jonas M. Gastal wrote:
> On Friday 27 January 2012 09:42:19 Charley Bay wrote:
> > > /me wonder why we still even care about QT_NO_STL
> > >
> > >
> > > Embedded?
> >
> > +1
> >
> > Further, half of C++ developers *hate* STL. (Long story, off-topic for
>
On Friday 27 January 2012 17:32:28 Pau Garcia i Quiles wrote:
> On Fri, Jan 27, 2012 at 5:27 PM, Olivier Goffart wrote:
> > /me wonder why we still even care about QT_NO_STL
>
> Embedded?
Care to elaborate?
(I deserved that response with my IRC syle message :-))
I mean webkit uses the stl, v8
On Friday 27 January 2012 09:42:19 Charley Bay wrote:
> > /me wonder why we still even care about QT_NO_STL
> >
> >
> > Embedded?
>
> +1
>
> Further, half of C++ developers *hate* STL. (Long story, off-topic for
> here.)
>
> --charley
So? It's not like we are telling them to use, just having
>
> /me wonder why we still even care about QT_NO_STL
>>
>>
> Embedded?
>
+1
Further, half of C++ developers *hate* STL. (Long story, off-topic for
here.)
--charley
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/ma
On Fri, Jan 27, 2012 at 5:27 PM, Olivier Goffart wrote:
> /me wonder why we still even care about QT_NO_STL
>
>
Embedded?
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
___
Development mailing list
Dev
/me wonder why we still even care about QT_NO_STL
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Robin Burchell wrote:
> 2012/1/27 João Abecasis :
> > - Provide standard-compliant implementations of the algorithms in
> > QtAlgorithms (no 'q' prefixes, no camel casing -- sorry!) and
> > selectively import those into a known namespace when QT_NO_STL is
> > defined:
> >
> >namespace QtPriva
hello,
2012/1/27 João Abecasis :
> - Provide standard-compliant implementations of the algorithms in
> QtAlgorithms (no 'q' prefixes, no camel casing -- sorry!) and
> selectively import those into a known namespace when QT_NO_STL is
> defined:
>
> namespace QtPrivateStd {
> #ifdef QT_NO_STL
Hello everyone,
[ The topic at hand was discussed on IRC this morning. Thiago agreed on
the general idea/concept. We also agreed on bringing the discussion to
the list. ]
Qt has historically offered some common algorithms, arguably a very
limited but still useful subset of what is available in th
On Friday, January 27, 2012 13:30:35 Thiago Macieira wrote:
> Correct. What do we need extending them with? The only virtuals you left in
> the API were stream (which I didn't get) and utcOffset, which doesn't seem
> to need to be a virtual.
Different timezones (and countries) have daylight saving
Den 27. jan. 2012 14:07, skrev ext Olivier Goffart:
> On Friday 27 January 2012 09:09:46 Kent Hansen wrote:
> [...]
>> If there is no quick fix, the last resort is to "pin" one or
>> more of the dependencies' to a particular SHA1 (e.g. from the qt5.git
>> submodule) in the sync.profile until the is
On Friday 27 January 2012 09:09:46 Kent Hansen wrote:
[...]
> If there is no quick fix, the last resort is to "pin" one or
> more of the dependencies' to a particular SHA1 (e.g. from the qt5.git
> submodule) in the sync.profile until the issue has been resolved, then
> "unpin" it again later.
Why
On Friday, 27 de January de 2012 12.48.13, Stephen Kelly wrote:
> > > It might also make sense to use QSharedPointer in the APIs.
> >
> > Before you argue for QSharedPointer of QTimeScheme, you need to tell us
> > why
> > pointers are necessary. Are people supposed to new them?
>
> I was imagining
On Friday, January 27, 2012 12:16:15 Thiago Macieira wrote:
> On Thursday, 26 de January de 2012 23.43.45, Stephen Kelly wrote:
> > Some of the API, eg 'void setUtcOffset(int seconds);' could be
> > implemented by creating a new QTimeScheme properly configured with a
> > UTC offset, but I took it o
On Thursday, 26 de January de 2012 23.43.45, Stephen Kelly wrote:
> Some of the API, eg 'void setUtcOffset(int seconds);' could be implemented
> by creating a new QTimeScheme properly configured with a UTC offset, but I
> took it out anyway rather than attempting to show a port in the patch.
What
On Fri, Jan 27, 2012 at 4:51 AM, Samuel Rødal wrote:
> On 01/26/2012 08:21 PM, ext Anselmo L. S. Melo wrote:
>> Hi,
>>
>> A window is a top level window if it has no parent, correct? Code and
>> comments in qwindow.cpp also confirm that.
>>
>> With that in mind, it seems reasonable that
>> QGuiA
On Thursday, January 26, 2012 23:11:27 lorn.pot...@nokia.com wrote:
> There is also this one:
> https://bugreports.qt-project.org/browse/QTBUG-71
>
> I had working code (for 4.6), but lacked time to fix a few bugs and such. I
> started with the QTimeZone class in Qtopia. It did use the timezone
>
+1
I like this idea. It would allow you to both test a change before integrating
and check if preventive changes (whenever possible) already applied in upstream
modules are working as expected.
Since this would effectively offer another commonly requested feature (namely,
a dry run of the CI)
Den 27. jan. 2012 09:20, skrev Alan Alpert:
> On Fri, 27 Jan 2012 18:09:46 ext Kent Hansen wrote:
>> Hi,
>> Sometimes there are changes to qtbase that the author and/or reviewers
>> strongly suspect will break one or more modules on top of it (e.g. in
>> qt5.git). For example, source-incompatible c
On Fri, 27 Jan 2012 18:09:46 ext Kent Hansen wrote:
> Hi,
> Sometimes there are changes to qtbase that the author and/or reviewers
> strongly suspect will break one or more modules on top of it (e.g. in
> qt5.git). For example, source-incompatible changes (removing
> QEventLoop::DeferredDeletion),
Hi,
Sometimes there are changes to qtbase that the author and/or reviewers
strongly suspect will break one or more modules on top of it (e.g. in
qt5.git). For example, source-incompatible changes (removing
QEventLoop::DeferredDeletion), or changes to the meta-type/QObject
internals (which qtdec
29 matches
Mail list logo
