[x3d-public] announce: X3D Java Scene AuthoringInterface(SAI)opensource, initial review release

Don Brutzman brutzman at nps.edu
Thu Dec 1 00:34:15 PST 2016 

Interesting idea - will have to think about it, has multiple implications for the class inheritance.  Such a change affects setters, getters and method names - nontrivial.

Perhaps utility methods for retrieval - getFieldSFBool() for example - but than those return nulls if programmer gets type wrong.  Or maybe a getFieldByType that returns an X3DConcreteField type which could be SFBoolObject, etc.

Gets even more twisty-turny when you get into "is that a field value or a fieldValue value?" kinds of description convolutionss.

Meanwhile those two classes are indeed stable.  Use of strings for simple types in fieldObject and fieldValueObject is just fine for creating and serializing back out a scene graph.  Using SFNode or MFNode will likely take more testing/work.


On 11/30/2016 7:48 PM, yottzumm at gmail.com wrote:
> I could be wrong, but I think that fieldValueObject.setValue and fieldObject.setValue should take more types that String.  Boolean, etc. would be nice.  There are probably other types which are possible.  Let me know if this will be accepted or not.  If I should not be using the classes fieldValueObject and fieldObject for concrete classes, let me know.
>
>
>
> John
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
>
>
>
> *From: *yottzumm at gmail.com <mailto:yottzumm at gmail.com>
> *Sent: *Wednesday, November 30, 2016 7:29 AM
> *To: *Roy Walmsley <mailto:roy.walmsley at ntlworld.com>; 'Don Brutzman' <mailto:brutzman at nps.edu>
> *Cc: *'SAVAGE Research Group' <mailto:savage at nps.edu>; 'X3D Graphics public mailing list' <mailto:x3d-public at web3d.org>
> *Subject: *RE: [x3d-public] announce: X3D Java Scene AuthoringInterface(SAI)opensource, initial review release
>
>
>
> This has to do with the Java SAI, not any rendering or OpenGL.  What interface is supported?
>
>
>
> John
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
>
>
>
> *From: *Roy Walmsley <mailto:roy.walmsley at ntlworld.com>
> *Sent: *Wednesday, November 30, 2016 6:50 AM
> *To: *yottzumm at gmail.com <mailto:yottzumm at gmail.com>; 'Don Brutzman' <mailto:brutzman at nps.edu>
> *Cc: *'SAVAGE Research Group' <mailto:savage at nps.edu>; 'X3D Graphics public mailing list' <mailto:x3d-public at web3d.org>
> *Subject: *RE: [x3d-public] announce: X3D Java Scene AuthoringInterface(SAI)open source, initial review release
>
>
>
> John,
>
>
>
> The code that you listed below looks to me  as though it meets the specification. The rest is up to the implementation.
>
>
>
> For example, does the implementation handle all the calls to OpenGL/WebGL to set up the shaders on the GPU within ComposedShader? Or does it do that for each ShaderPart within the ShaderPart code? If the former, then the fields are in the right place. If the latter, then the fields will have to be passed from down from ComposedShader to each ShaderPart.
>
>
>
> Unfortunately, I haven’t got these X3D nodes in my Coin3D implementation, so have no direct experience. However, my code does have shaders within it so I have seen the general principles.
>
>
>
> I looked on the X3D examples archive. There are two examples there of ComposedShader scenes. The first is at http://www.web3d.org/x3d/content/examples/Basic/Shaders/FlutterIndex.html. However, it does not have any shader code declared. The second is at http://www.web3d.org/x3d/content/examples/Basic/Shaders/SimpleShaderIndex.html. It does have shader code, although I noted that it does not render into the Window like other examples. So, maybe a problem there.
>
>
>
> Hope that helps,
>
>
>
> Regards,
>
>
>
> Roy
>
>
>
>
>
> *From:* x3d-public [mailto:x3d-public-bounces at web3d.org] *On Behalf Of *yottzumm at gmail.com
> *Sent:* 30 November 2016 06:54
> *To:* Don Brutzman <brutzman at nps.edu>
> *Cc:* SAVAGE Research Group <savage at nps.edu>; X3D Graphics public mailing list <x3d-public at web3d.org>
> *Subject:* Re: [x3d-public] announce: X3D Java Scene Authoring Interface(SAI)open source, initial review release
>
>
>
> I’m running into difficulties with shaders and I don’t know if it’s my code, or the Java SAI.
>
>
>
> Here’s the X3D excerpt:
>
>
>
> <ComposedShader DEF='ComposedShader' containerField='shaders' language='GLSL'>
>
>                     <field name='cubeMap' accessType='inputOutput' type='SFInt32' value='0'/>
>
>                     <field name='chromaticDispersion' accessType='inputOutput' type='SFVec3f' value='0.98 1 1.033'/>
>
>                     <field name='bias' accessType='inputOutput' type='SFFloat' value='0.5'/>
>
>                     <field name='scale' accessType='inputOutput' type='SFFloat' value='0.5'/>
>
>                     <field name='power' accessType='inputOutput' type='SFFloat' value='2'/>
>
>                     <ShaderPart url='"x3dom.vs"' containerField='parts' type='VERTEX'>
>
>                     </ShaderPart>
>
>                     <ShaderPart url='"bubbles.fs"' containerField='parts' type='FRAGMENT'>
>
>                     </ShaderPart>
>
>                     </ComposedShader>
>
>
>
> Note the fields are under the ComposedShader and not the ShaderPart.  Do I need to follow the container field up and get the fields to put in the shader part objects?  That’s not how the JSON is produced from the XML afaik (but I haven’t tried recently).
>
>
>
> Should I move the fields into the shader part?
>
>
>
> On to the next…
>
>
>
> John
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
>
>
>
> *From: *Don Brutzman <mailto:brutzman at nps.edu>
> *Sent: *Wednesday, November 30, 2016 12:22 AM
> *To: *yottzumm at gmail.com <mailto:yottzumm at gmail.com>
> *Cc: *X3D Graphics public mailing list <mailto:x3d-public at web3d.org>; SAVAGE Research Group <mailto:savage at nps.edu>
> *Subject: *Re: [x3d-public] announce: X3D Java Scene Authoring Interface(SAI)open source, initial review release
>
>
>
> Gee whiz, you are already at the far horizon!  8)  You will see that they are not yet present or tested in HelloWorldProgram.java since I just got prototypes sorted out.
>
>
>
> Will look at it.
>
>
>
>
>
> On 11/29/2016 8:22 PM, yottzumm at gmail.com <mailto:yottzumm at gmail.com> wrote:
>
>> Waiting for instructions on how to use IS/ISObject/IS statements.  I’m not sure how to hook them under material, etc.
>
>>
>
>>
>
>>
>
>> Thanks,
>
>>
>
>>
>
>>
>
>> John
>
>>
>
>>
>
>>
>
>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
>
>>
>
>>
>
>>
>
>> *From: *Don Brutzman <mailto:brutzman at nps.edu>
>
>> *Sent: *Tuesday, November 29, 2016 12:04 PM
>
>> *To: *X3D Graphics public mailing list <mailto:x3d-public at web3d.org>
>
>> *Cc: *SAVAGE Research Group <mailto:savage at nps.edu>
>
>> *Subject: *Re: [x3d-public] announce: X3D Java Scene Authoring Interface (SAI)open source, initial review release
>
>>
>
>>
>
>>
>
>> Another significant release has been deployed today:
>
>>
>
>>
>
>>
>
>> - Support for prototypes: ProtoDeclare, ProtoInterface/ProtoBody, ExternProtoDeclare, ProtoInstance.
>
>>
>
>> - Further validation checks, making it hard for programmers to create a broken scene graph.
>
>>
>
>> - Support for X3D, ClassicVRML and VRML97 file export (.x3d .x3dv .wrl)
>
>>
>
>> - "Principle of least surprise" when null values are encountered from author (e.g. clear a field, etc.)
>
>>
>
>> - Further unit tests in example program to confirm proper operation of correct and incorrect constructs.
>
>>
>
>> - Internal package refactoring to improve inheritance, leaving exposed programming API unchanged.
>
>>
>
>> - Performance looks great, despite complexity am unable to get execution time above "O seconds" - deserves profiling on large models.
>
>>
>
>>
>
>>
>
>> Key links:
>
>>
>
>>
>
>>
>
>>                 http://www.web3d.org/specifications/java/X3dJavaSceneAuthoringInterface.html
>
>>
>
>>
>
>>
>
>>                 http://www.web3d.org/specifications/java/examples
>
>>
>
>>
>
>>
>
>>                 http://www.web3d.org/specifications/java/javadoc
>
>>
>
>>
>
>>
>
>> Test reports and improvement suggestions welcome.  Have fun with X3D Java!
>
>>
>
>>
>
>>
>
>>
>
>>
>
>> On 10/21/2016 8:19 AM, Don Brutzman wrote:
>
>>
>
>>> Second release is out, the X3D Java SAI Library is now in beta.
>
>>
>
>>>
>
>>
>
>>> Latest release include autogeneration of concrete classes for field types.  Quite a tricky business because a number of specification definitions are contradictory or simply missing, because the published Java SAI specification was based on X3D v3.0 capabilities.
>
>>
>
>>>
>
>>
>
>>> Still in collection mode, but have started a text document listing specification problems and potential improvements.
>
>>
>
>>>
>
>>
>
>>>     http://www.web3d.org/specifications/java/X3dJavaSpecificationChangesAndIssues.txt
>
>>
>
>>>
>
>>
>
>>> Active TODO list, more to follow:
>
>>
>
>>>
>
>>
>
>>> * In progress. Test concrete field-type classes for SFBool/MFBool through SFNode/MFNode to support value instantiation, including creation of type-checked new values from strings. A number of new data types have been added since X3D version 3.0, extra attention is needed to ensure that new classes and methods consistently support new specification additions. Method stubs need to be implemented (typically adapting source code from the Xj3D implementation).
>
>>
>
>>> * In progress. Confirm generation of default attribute values and constructors.
>
>>
>
>>> * In progress. Continue testing concrete classes for X3D statements, also confirming that attributes are properly reflected as fields.
>
>>
>
>>> * In progress. Add support for persistent scene-graph comments and comment blocks.
>
>>
>
>>>
>
>>
>
>>> Initial testing: HelloWorldProgram.java model, online at
>
>>
>
>>>
>
>>
>
>>>     http://www.web3d.org/specifications/java/examples/HelloWorldProgram.java
>
>>
>
>>>
>
>>
>
>>> The X3D Object Model is looking very solid.  Changes to X3D specification and schema are automatically integrated in this codebase.  When complete, this will be a big step forward for rigourously maintaining all X3D specifications, quality assurance tools and Web3D Consortium resources completely correct and in synch.  I expect it will be especially helpful when we get to the stage of experimentation with X3D version 4.
>
>>
>
>>>
>
>>
>
>>> Scrutiny by Java experts on the class structures and design patterns is appreciated.  More work to follow on X3D Java SAI Library, of course, but it looks like all the major building blocks are now in place.  Incremental implementation improvements and TODO capability addition can now proceed.
>
>>
>
>>>
>
>>
>
>>> As ever, all feedback and comments are welcome.  Have fun with X3D Java!
>
>>
>
>>>
>
>>
>
>>> ==================================================================================
>
>>
>
>>> On 6/27/2016 8:03 AM, Don Brutzman wrote:
>
>>
>
>>>
>
>>
>
>>> Now available for review: X3D Java Scene Authoring Interface (SAI) Library.
>
>>
>
>>>
>
>>
>
>>>     http://www.web3d.org/x3d/stylesheets/java/X3dJavaSceneAuthoringInterface.html
>
>>
>
>>>
>
>>
>
>>> The X3D Java Scene Access Interface (SAI) is a strongly typed Java library that provides access to a browser and its contained scene graph. This package contains X3D SAI interfaces that support the X3D Specifications.
>
>>
>
>>>
>
>>
>
>>> Available products include javadoc, source code, build classes and draft specification annexes.
>
>>
>
>>>
>
>>
>
>>>     http://www.web3d.org/x3d/stylesheets/java/javadoc/index.html
>
>>
>
>>>     http://www.web3d.org/x3d/stylesheets/java/source/org/web3d/x3d/sai
>
>>
>
>>>     http://www.web3d.org/x3d/stylesheets/java/build/org/web3d/x3d/sai
>
>>
>
>>>
>
>>
>
>>>     http://www.web3d.org/x3d/stylesheets/java/draftJavaLanguageBindingAnnexes/Part2/nodeTypeInterfaces.html
>
>>
>
>>>     http://www.web3d.org/x3d/stylesheets/java/draftJavaLanguageBindingAnnexes/Part2/nodeInterfaces.html
>
>>
>
>>>
>
>>
>
>>> Intended uses include
>
>>
>
>>>
>
>>
>
>>> * Current: compiling Java source code for an X3D Script node.
>
>>
>
>>> * Future: support creation of standalone Java applications by providing a Plain Old Java Object (POJO) implementation for X3D.
>
>>
>
>>> * Future: serve as a design template for future autogeneration of similar codebases for ECMAScript, C++/C# and Python.
>
>>
>
>>>
>
>>
>
>>> Special thanks to Roy Walmsley for X3D Object Model creation and ongoing design discussions.  Further notes about API Codebase Production autogeneration and design considerations appear on the topmost page listed above.
>
>>
>
>>>
>
>>
>
>>> Work continues on matching autogenerated interfaces to the specification, noting corrections, and testing actual Script code in Java.
>
>>
>
>>>
>
>>
>
>>> Comments are always welcome.  Have fun with X3D using Java!
>
>>
>
>>> ==================================================================================
>
>>
>
>>
>
>>
>
>>
>
>>
>
>> all the best, Don
>
>>
>
>> --
>
>>
>
>> Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu <mailto:brutzman at nps.edu>
>
>>
>
>> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
>
>>
>
>> X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman
>
>>
>
>>
>
>>
>
>> _______________________________________________
>
>>
>
>> x3d-public mailing list
>
>>
>
>> x3d-public at web3d.org <mailto:x3d-public at web3d.org>
>
>>
>
>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
>>
>
>>
>
>>
>
>
>
>
>
> all the best, Don
>
> --
>
> Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu <mailto:brutzman at nps.edu>
>
> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
>
> X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman
>
>
>
>
>
>
>


all the best, Don
-- 
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman

More information about the x3d-public mailing list