[Development] Proposing reversal of the Math3D qreal->float change

[André Pönitz]

On Tue, Sep 11, 2012 at 10:34:50PM +0100, Sean Harmer wrote:
> On 11/09/2012 13:34, Thiago Macieira wrote:
> > I propose we revert it.
> I propose we (I) fix the affected classes in QtMultimedia
> and Qt3D. I'm away on business this week but I will make a
> start asap.

I believe I mentioned that before. Anyway:

I think there are (medium term) only two acceptable solutions,
none of them perfect:
(a) keep everything as it is (or, rather, "was")
(b) have fully functional real/double "verticals"

Version (a) means the current mess will go on. but it has the
distict charme of (a.1) not breaking anyones existing code and
(a.2) sticking to feature freeze rules.

Version (b) is somewhat closer to a proper solution, but fails
(a.1) and (a.2). It has also the disadvantage of requiring real
work, and therefore to tie up resources.

Even with my usual "let's break feature freeze if the feature is
cool enough" hat on, I am tempted to lean towards (a). We are
late in the game, and there are one or two rather essential
things to be done for Qt 5. Having applications lock up regularly
does not exactly sound like a strong sell to me. And while partial
and/or extremly slow window updates might give that warm and cosy
sense of being back in Qt 2.1 times to some, I have ths nagging
feeling that not everyone out there will appreciate it.

So, please, make the things that were there work again, and do
not open up new construction sites. And yes, that may mean
postpone stuff to Qt 6 (or maybe convincing the Chief in a year
or two that having a QT_NO_COMPATIBILITY would be a feasible
approach)

Andre'