[Development] Some Qt3D feedback

[Oswald Buddenhagen]

On Thu, Jun 11, 2015 at 12:29:34PM +0200, Marc Mutz wrote:
> So even if we follow your reasoning, Qt3D is doing nothing that QtConcurrent 
> and QtXmlPatterns, combined, haven't been doing for years. So the only new 
> thing is that instead of separate libraries, it's now used in one.
> 
the thing is that both your precedents are *bad*:
- qtconcurrent has intentionally been isolated, as a prelude to
  deprecation
- there is a pretty uniform perception that xmlpatterns feels alien in
  the qt api, and i have a slight suspicion that the naming convention
  contributes to that

so at this point, qt3d *is* setting the precedent for a widely reviewed
new module that is meant to stay.

and ftr, i'm entirely with steve on that one.

> And that's fine, at least from my pov. But we can certainly discuss
> whether that's valid for the Qt project as a whole

> (if we ain't got anything else to do).
> 
glad you're taking the matter seriously.

> It anyway doesn't block the release, since Qt3D is only released as a
> tech preview.
> 
while this is technically true, it's plain dishonest to suggest that
what is released now will not develop enough momentum to make later
changes of that scale hard.