On Sep 13, 2013, at 9:55 AM, Torsten Spieldenner <Torsten.Spieldenner at dfki.de> wrote: Hi, a basic question about the server -> client entity transmission that you described: > Thus, to sum up, at the moment I am aiming at an entity being transmitted in a format, that may look like this in JSON notation: > > entity = > { > id, > components: { component1, component2, .... component_n }, > viewElement: <XML3D - representation> > } I don't understand what these two separate members are, the components list and the viewElement. What would the XML3D representation entail there? In the EC model the idea is that everything is in the components, the structure is like this: entity = { id, components: { component1, component2, .... component_n } } And information about how visible objects display is in the respective components: for example the scene node position in EC_Placeable and the geometry for meshes in EC_Mesh etc. So what's that viewElement for? Isn't the idea that the xml3d data is the component data? > ~ Torsten ~Toni
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy