Yeah. I'd like to see that too, 'cause I am deeply convinced that change opens
up possibilities. Even when it comes in a rude, out the line and rough
packaging. :)
Go man show colours and good luck,
Mike
On Jun 25, 2012, at 1:10 AM, Wolfgang Baron wrote:
> Hi d3fault,
>
> please show us som
On Friday, June 22, 2012 08:47:34 am ext Rohan McGovern wrote:
> Alexis Menard said:
> > Hi,
> >
> > When I see recent behaviors, wording, comments on various mailing
> > lists, blog posts, or IRC against major contributors or regular
> > contributor I feel sad about it. I feel sad to hear bashing
Hi d3fault,
please show us some demo of your code and publish an LGPL project for
others to have a look at. Then we can see, whether you've created the
next best thing or not. Sure hope, you've got something there!
___
Development mailing list
Developme
+1.. like the bug description :)
From: development-bounces+aurindam.jana=nokia@qt-project.org
[development-bounces+aurindam.jana=nokia@qt-project.org] on behalf of ext
André Pönitz [andre.poen...@mathematik.tu-chemnitz.de]
Sent: Sunday, June 24, 20
On Sun, Jun 24, 2012 at 12:13:04PM -0700, BogDan wrote:
> +1 This guy looks very stupid to me, but someone else must approve.
That is https://bugreports.qt-project.org/browse/QTCREATORBUG-7578 now.
Andre'
___
Development mailing list
Development@qt-proj
On domingo, 24 de junho de 2012 22.13.58, André Pönitz wrote:
> For some reason I forgot to mention that with the current guarantee for
> fromRawData usage (user has to make sure that the base data will not be
> deleted or modified as long as the QString (or an unmodified copy of it)
> exists) this
QWidgetNG, the last iteration was 4On 6/24/12 21:13 BogDan wrote:
+1 This guy looks very stupid to me, but someone else must approve.
From: d3fault
To: "development@qt-project.org"
Sent: Sunday, June 24, 2012 9:22 PM
Subject: [Development] So I've made a QWidgets2 design/prototype... BUT...
On Sun, Jun 24, 2012 at 09:08:45PM +0200, Thiago Macieira wrote:
> André suggested a container main class as: class QString { ushort *data;
> int size; int d_offset; };
>
> so that d = reinterpret_cast(data) + d_offset.
>
> That class has 16 bytes in size. However, it breaks for fromRawData,
> si
On Sunday 24 June 2012 09:52:10 Marc Mutz wrote:
> A late-entry data point:
>
> libstdc++'s std::list is binary incompatible between -std=c++11
> and -std=c++98, because it adds a _M_size member.
>
> It's the most stupid change I can imagine, but it apparently means that the
> GCC devs don't shoo
+1 This guy looks very stupid to me, but someone else must approve.
>
> From: d3fault
>To: "development@qt-project.org"
>Sent: Sunday, June 24, 2012 9:22 PM
>Subject: [Development] So I've made a QWidgets2 design/prototype... BUT...
>
>
>Apparently I'm smart
We discussed the containers, including performance issues and why the design
was going to where it was going.
QList
~~~
Since QList is the most used container in Qt and by Qt users, it's probably
being used in unexpected ways. We preferred not to break compatibility. QList
will continue to have a
On Sun, 24 Jun 2012, d3fault wrote:
> Which brings me to my next question:
> Why should I do Nokia's work (rather, what I think should be their work)
> for them?
You don't have to. What you may do is to help other users (and in the long
run yourself).
> Sure, I could contribute QWidgets2 as an
Apparently I'm smarter than everyone at Nokia. I managed to make a "modern,
fluid" GUI API using the QSG* classes without incurring the additional
costs of: JIT Parsing of .qml files, a JavaScript Interpreter, and a
Virtual Machine. I also did it without using declarative, something claimed
by many
On Wednesday April 25 2012, Olivier Goffart wrote:
> > > We could implement a move setter (Foo::setText(QString&&)). But that
> > > would
> > > mean duplication, and it could not be inline (access to d_ptr) so
> > > binary incompatibility between Qt compiled with or without C++11.
> >
> > The rva
14 matches
Mail list logo
