[Development] Adding new third party component three.js to Qt?

[Lisandro Damián Nicanor Pérez Meyer]

On Tuesday 13 January 2015 03:20:38 Kevin Kofler wrote:
> Sorry for raining on your parade, but…
> 
> Keränen Pasi wrote:
> > I¹d like to open the discussion on including the three library as part of
> > Qt 5.6 and onwards. Mainly because this would give our users a better
> > experience if we¹d bundle the right, tested version of Three.js together
> > with the Qt version it was tested on.
> 
> … we distribution packagers REALLY hate bundled libraries…

Same here.

> > The library will for now at least need some porting effort to make it run
> > on top of Canvas3D as there are some HTML depencencies that need to be
> > handled, plus V4VM has a few quirks that need to be accounted for.
> > Hopefully some of the V4VM quirks are bugs and will be fixed in due time,
> > but the HTML dependencies do remain. And my current experience with
> > graphics APIs is that you want to test the whole stack together. If we
> > e.g. add support for new extensions in Canvas3D, that can activate new
> > codepaths in Three.js that again need testing and possibly new Qt specific
> > delta must be added to the three.js for those parts.
> 
> … and especially FORKED bundled libraries (where we stand no realistic
> chance of actually unbundling them).

I couldn't agree more.

And also thanks Thiago for pointing that the lib should be minimized by the 
build system, else we wouldn't be able to ship it, even in it's embedded form.


-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20150113/f09c5df2/attachment.sig>