[Fiware-miwi] Fwd: glTF Three.js loader status & plans?

[Toni Alatalo]

Just for info: mr. Parisi said he will upgrade the three.js glTF loader shortly and didn’t seem to need help with that so we’ll just wait for that now and test it then.

In the meantime we’ll continue work on other areas (now sync & 3dui integration and basic client feats continues) and on the glTF side test animations and materials with the plain glTF viewer.

~Toni

Begin forwarded message:

> From: Tony Parisi <tparisi at gmail.com>
> Subject: Re: glTF Three.js loader status & plans?
> Date: 10 Dec 2013 23:05:28 GMT+2
> To: Toni Alatalo <toni at playsign.net>
> Cc: tapani at playsign.net, Erno Kuusela <erno at playsign.net>, Fabrice Robinet <fabricerobinet at me.com>
> 
> Hi Toni and team,
> 
> I am finishing up the glTF loader over the next few weeks. There was a big syntax change about a month ago, and I need to catch up with that. I also need to add morphs. Then it's essentially feature complete. Once that is done, I will merge it into trunk, and also set up a Three.js pull request so that Mr.doob can include it with the Three.js distro. That's the general plan.
> 
> It's totally OK to add an issue to the glTF Github. We like doing that!
> 
> Fabrice, my working group chair, cc'ed here.
> 
> Tony
> 
> 
> 
> On Mon, Dec 9, 2013 at 4:35 AM, Toni Alatalo <toni at playsign.net> wrote:
> Hi,
> 
> may I ask what’s the status of the Three.js glTF loader and your plans for it?
> 
> We do know the info that’s out there on the web, your presentation about the status at the SF WebGL meetup in August etc. Also what the github log says :)
> 
> So, more specifically: what version of the glTF spec / converter should we use with the current Three loader? The example files in the branch say ‘0.1.0’ which I think basically means that some version from before the converter got the nice feature that it puts the exact git version hash in the json files. So far we have been unable to get any own data converted so that it would work with the three.js loader. We tried with an old version of the converter from spring, the last one that still puts the hardcoded ‘0.1.0’ versioning, but it crashed on our test scene (later versions of the converter work for that file).
> 
> We have been able to convert our test scene with the version of the converter that the plain webgl-glTF viewer works with, that test is online at http://playsign.tklapp.com:8000/glTF-webgl-viewer/ (the default ‘Oulu’ model, takes a while to load). However we’d like to move on to testing with three.js as that’s our target for actual use — and also to test animations etc. Was thinking it would be good to proceed by testing first with the kind of data your loader should already work with.
> 
> If things look good and it makes sense regarding your plans etc. we can then perhaps help with the effort — for example start porting the loader to the current version of the spec / converter if that’s needed. We are doing this work here at Playsign for the open source realxtend.org platform with funding from the EU Future Internet (FI) effort. We have no need to keep any work nor communications secret, I just didn’t know a public forum to post this to. I like how Three.js uses the github issue tracker almost like a forum and it seems to be in good use for glTF too — I just didn’t want to blindly hijack that for this three.js loader specific talk without knowing about your practices. If it’s good to open an issue in the main glTF tracker instead of talking here please do / hint us and we'll do so.
> 
> Cheers,
> ~Toni
> 
> 
> 
> 
> -- 
> Tony Parisi                             tparisi at gmail.com
> CTO at Large                         415.902.8002
> Skype                                     auradeluxe
> Follow me on Twitter!             http://twitter.com/auradeluxe
> Read my blog at                     http://www.tonyparisi.com/
> Learn WebGL                         http://learningwebgl.com/
> 
> Read my book! WebGL, Up and Running
> http://shop.oreilly.com/product/0636920024729.do
> http://www.amazon.com/dp/144932357X
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20131211/0fbe25f2/attachment.html>