On 02 Nov 2013, at 09:09, Philipp Slusallek <Philipp.Slusallek at dfki.de> wrote: > Nice stuff. from my perspective there are two ways to look at this work: One is to provide high level UI elements on top of a three.js implementation and the other is the start of creating a declarative layer on top of the three.js renderer. This seems more along the first line but both should be similarly interesting to us. Indeed. > It great to see that other people are coming up with similar ideas now. It would be good to get the message about our XML3D design and implementation to these people out there. That way we could improve what we already have instead of reinventing the wheel. That was my immediate first thought as well: it seemed like people have started to reinvent declarative 3d for the web from scratch. That’s why I asked whether they knew about the existing work — I understood that this Josh Galvin person (don’t know him from before) who made the Spinner demo, did (am not sure). Thanks for the views and pointers, I’ll keep an eye open for talks about this (actually just joined the #three.js irc channel on freenode yesterday, haven’t been involved in their community before really — Tapani from us has been hanging out there though). They seem to communicate most in the github issue tracker and pull requests (which I think is a great way). I also did not find an e-mail address to the polymer-threejs person, but kaosat.net is his personal site and apparently he made the original announcement of the declarative three.js thing in August in Google+ so I figure e.g. replying there would be one way to comment: https://plus.google.com/112899217323877236232/posts/bUW1hrwHcAW .. I can do that on Monday. BTW it seems that this guy is into hardware and cad and all sorts of things and declarative 3d xml is just a side thing for fun, perhaps related to his work on some cad thing — is not like he’d be pursuing a career or a product or anything out of it. It seems like a straightforward mapping of the three.js API to xml elements: what I struggle to understand now is whether that’s a good abstraction level and how does it correspond to xml3d’s vocabulary. ~Toni > It would be good if you can point people also to our papers from this year (http://graphics.cg.uni-saarland.de/publications/). They explain a lot of the background of why we have chose thing to work the way they work. > > More specifically: > -- The "xml3d.js" paper explain a lot about the design of XML3D and its implementation (https://graphics.cg.uni-saarland.de/2013/xml3djs-architecture-of-a-polyfill-implementation-of-xml3d/). > -- The "Declarative image processing" paper explains all the advantages one gets from exposing processing elements to the DOM instead of implementing them only in some JS libraries (https://graphics.cg.uni-saarland.de/2013/declarative-ar-and-image-processing-on-the-web-with-xflow/). > -- And the 2012 paper on "XFlow" shows this usage for animation (https://graphics.cg.uni-saarland.de/2012/xflow-declarative-data-processing-for-the-web/) > > Getting into a constructive discussion with some of these three.js people would be a good thing. I tried to find an email address for the polymer-threejs person but could not find any. Feel free to farward this email to him (and maybe others). I would love to get their feedback and engage in discussions. > > > Best, > > Philipp > > Am 02.11.2013 00:38, schrieb Toni Alatalo: >> Apparently some three.js user/dev has gotten inspired by WebComponents & >> the Polymeer and written https://github.com/kaosat-dev/polymer-threejs :) >> >> Now another guy has continued with >> https://github.com/JoshGalvin/three-polymer — there’s a demo of custom >> element (‘spinner’), similar to the Door case discussed here earlier. >> >> Had a brief chat with him, will return to this later but was fun to see >> the minimal webgl web component example there as that has been in our >> agenda. >> >> ~Toni >> >> 01:01 *<* galv*>* https://github.com/JoshGalvin/three-polymer added >> support for more basic geometry types >> 01:02 *<* galv*>* Going to do materials next >> 01:25 *<* *antont**>* galv: hee - are you aware of these btw? >> http://www.w3.org/community/declarative3d/ , e.g. >> https://github.com/xml3d/xml3d.js >> 01:27 *<* galv*>* yeah, different level of abstraction >> 01:27 *<* *antont**>* perhaps >> 01:28 *<* galv*>* I expect people to wrap up their game objects >> 01:28 *<* galv*>* aka "spinner" >> 01:28 *<* galv*>* (index.html) >> 01:29 *<* *antont**>* we've been also planning to enable saying things >> like <door> if that's what you mean >> 01:30 *<* *antont**>* right, seems like the same idea >> 01:31 *<* *antont**>* very cool to see, gotta check the codes etc later >> .. but sleep now, laters >> >> >> >> _______________________________________________ >> Fiware-miwi mailing list >> Fiware-miwi at lists.fi-ware.eu >> https://lists.fi-ware.eu/listinfo/fiware-miwi >> > > > -- > > ------------------------------------------------------------------------- > Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH > Trippstadter Strasse 122, D-67663 Kaiserslautern > > Geschäftsführung: > Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) > Dr. Walter Olthoff > Vorsitzender des Aufsichtsrats: > Prof. Dr. h.c. Hans A. Aukes > > Sitz der Gesellschaft: Kaiserslautern (HRB 2313) > USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 > --------------------------------------------------------------------------- > <slusallek.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy