[x3d-public] [x3d] Goals for V4

[Roy Walmsley]

Len,

 

Thanks for your response. I agree with your sentiment re maximising adoption. I am, as you probably already realise, also of the opinion that most of the changes could be in a browser based encoding.

 

The event model, as I see it at the moment, is almost certainly going to mean changes to 19775-1. Thinking out loud I wonder if the current event model in 19775-1 could be described as ‘synchronous’. While what we need for HTML5 is an ‘asynchronous’ model. Could we have both? With a way of selecting one or the other?

 

If you think you can have an initial version in a week or so, or even just a plan of what changes you see going where, then that sounds great. I look forward to seeing your ideas.

 

Regards,

 

Roy

 

From: Leonard Daly [mailto:web3d at realism.com] 
Sent: 16 September 2015 01:04
To: Roy Walmsley; 'x3D WG'; x3d-public at web3d.org
Subject: Re: [x3d] Goals for V4

 

On 9/15/2015 1:54 PM, Roy Walmsley wrote:

Len,

 

I have looked through your goals and would like to comment on your goal 4 – compatibility with V3.3.

 

I would say that the goal should be to maximise compatibility with V3.3. I would also be very interested to hear in what way you think compatibility might be broken. I suspect one would be the event model. I have a germ of an idea about that.


Roy,

I am not opposed to full backwards compatibility with V3.x and V2.x. There are a number of areas where (I think) that kind of compatibility may severely limit X3D in the marketplace. As you point out, the event model is one area. Another is the Script node. I know there is a recent release that includes a Script node, but it appears to do it at the expense of access to the X3D DOM. I need to investigate that further.

I wish to maximise the adoption of X3D. I am looking at how people currently build 3D environments, from modeling to final assembly. I think it may be more of an optimization problem with so many things to maximize.

I am working on a design philosophy that I think addresses those issues. A lot is only stored in my mind, and I would prefer to get most of it in a transportable media before going into much detail. I hope to have at least an initial version in a week.





 

I would like to see, if at all possible, a situation where my development X3D V3.3 in C++ can also handle what is carried over to V4 (obviously extensions would be required for new features) without needing a converter. Perhaps this is a goal we can aim for together.


I think it might. I am not sure about how features will land when interacting in a web-browser environment vs. non-browser. Some/many/all (?) of the features may be in a browser-based encoding.


Leonard Daly






 

Regards,

 

Roy

 

From: x3d [mailto:x3d-bounces at web3d.org] On Behalf Of Leonard Daly
Sent: 15 September 2015 01:18
To: 'x3D WG'; x3d-public at web3d.org
Subject: [x3d] Goals for V4

 

I have been developing several ideas for X3D V4 to align X3D with current development practice while maintaining important links to the past. I have posted my goals for my work at http://realism.com/blog/declaractive-3d-goals (also listed below). There is public comment capability at http://tools.realism.com/forums/x3d-evolution/declaractive-3d-goals

1.	Very long life to support physical objects with long lifespans (e.g., industrial & transportation facilities)
2.	Runs directly in browser without the need for plug-ins
3.	Not required to run in a browser
4.	Compatible with existing X3D V3.3 standard
Note that this does not require full backwards compatibility; but the ability to handle pre V4 content, perhaps with a converter.
5.	Allows for creation, storage, and use of content in a manner consistent with current and anticipated future practices
6.	Runs on as wide of variety as possible of devices capable of displaying 3D content

 

-- 
Leonard Daly
X3D Co-Chair
Cloud Consultant
President, Daly Realism - Creating the Future 

 

-- 
Leonard Daly
X3D Co-Chair
Cloud Consultant
President, Daly Realism - Creating the Future 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20150916/59187929/attachment.html>