[Fiware-miwi] thu 13: meet about webtundra dom-integration & xml3d net sync vs. tundra components

Torsten Spieldenner torsten.spieldenner at dfki.de
Wed Jan 15 09:23:31 CET 2014


Hello,

we are currently planning to have version 0.2 of FiVES finished very 
soon (in 1 or 2 weeks), until then you find a stable version on develop 
branch. Features in this branch include, as Philipp already said, 
synchronization of XML3D scenes that consist of a static environment 
(e.g. city scene) and user controlled, animated avatars. Physics / 
Collision is not included yet, but work in progress.

The client code will be revised right after the next release as well. It 
works nicely, but the code needs some refactoring and nicer separation 
of responsibilities as well as optimization in several classes. But the 
current way the scene manager works already gives a good impression of 
how linking the ECA model to XML3D works (see for example lines 122 to 
140 for how position, orientation and mesh updates are applied):

https://github.com/rryk/FiVES/blob/develop/WebClient/scripts/resources/scene_manager.js

Data is read from and kept in sync with the server in the 
fives_communicator class. That class actually creates the function 
wrappers to communicate with the server using KIARA:

https://github.com/rryk/FiVES/blob/develop/WebClient/scripts/communication/fives_communicator.js

Upon receiving updates for an entity, this entity updates the internal 
data representation (java script objects) and updates the respective 
fields in its XML3D DOM element via sceneManager, if necessary:

https://github.com/rryk/FiVES/blob/develop/WebClient/scripts/models/entity.js 
(Line 43)

  I'm happy to answer any detailed question, either on the mailing list 
directly, or in a separate discussion.

A short demo video of how our Web-client currently looks like can be 
found here:

https://www.dropbox.com/s/sdgr7wxf0t0bixu/FIVES-Demo.avi

Best,
Torsten

Am 1/15/2014 8:01 AM, schrieb Philipp Slusallek:
> Hi Toni, all,
>
> Its great to hear that you are making good progress here. And its a 
> good idea to talk about that today.
>
> Yes, we have a sync server, a simple KIARA-based API and JSON 
> protocol, as well as mapping to the XML3D scene, movement and 
> animation of characters implemented and roughly working.
>
> The KIARA layer in our C#-based sync server and the JS layer in the 
> browser are still primitive and hard coded but we are making very good 
> progress on the C/C++ KIARA implementation (Advanced Middleware GE). 
> An initial Version will be published by the end of the month. Its not 
> yet connected to the C#/JS-Version but we are currently looking into 
> that.
>
> I am currently preparing a presentation on KIARA that I can share in 
> about two weeks.
>
> Torsten, maybe you can send pointers to the code and a video or so?
>
> I will take care of setting up the call today. Christof seems to still 
> be ill but (according to his colleagues last Friday) it is no too 
> serious. Get well soon again, Christof!!
>
>
> Best,
>
>     Philipp
>
>
>
> Am 15.01.2014 07:44, schrieb Toni Alatalo:
>> Another note from yesterday: we decided to have a little meet / 
>> working session about the DOM integration and xml3d etc. in the 
>> WebTundra context.
>>
>> Lasse has Sync.DomIntegration as a feature tracker entry in the 
>> fi-ware forge, and as evident for many posts here we've worked on it 
>> a lot from the 3DUI perspective at Playsign.
>>
>> One topic is net sync of full xml3d, xflow, and perhaps arbitrary DOM 
>> elements. Basic 3d things like transforms and meshes we can (and 
>> already do, in Erno's xml3d reader) map between xml3d xml elements 
>> and Tundra components. For xml elements for which there is no 
>> existing nor need for a Tundra component, an option is just to use 
>> DynamicComponent's where use the name feature to have the XML element 
>> name (for example for Xflow <data> and <computation> elements). But 
>> is that the best idea or would something else be better? Hierarchy is 
>> coming per Lasse's plan to add normal xml-style hierarchy to Tundra.
>>
>> Idea is mostly for us (me & Erno) and Lasse to plan next steps in the 
>> work but anyone interested can participate, Jarkko said that 
>> Cyberlightning folks working on xml3djs & xflow may join in, and 
>> Jonne or someone from Admino may come too. We can discuss it in the 
>> weekly today as well, or set it so that DFKI folks can participate 
>> remotely tomorrow if it seems like a good idea.
>>
>> If DFKI Fives already does e.g. full sync of xml3d (and xhtml?) using 
>> a similar entity-component model, or if there's designs for that 
>> etc., those would be obviously good to check too --- pointers are 
>> welcome.
>>
>> Cheers,
>> ~Toni
>> _______________________________________________
>> Fiware-miwi mailing list
>> Fiware-miwi at lists.fi-ware.eu
>> https://lists.fi-ware.eu/listinfo/fiware-miwi
>>
>
>
>
>
> _______________________________________________
> Fiware-miwi mailing list
> Fiware-miwi at lists.fi-ware.eu
> https://lists.fi-ware.eu/listinfo/fiware-miwi

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20140115/58d25050/attachment.html>


More information about the Fiware-miwi mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy