[x3d-public] concern over sourceforge as repository

Don Brutzman brutzman at nps.edu
Sun Jan 28 16:26:08 PST 2018


On 1/28/2018 2:03 PM, John Carlson wrote:
> I am using test.bat in the stylesheets folder to build and test.bat in the nashorn folder for building/testing

Well OK but the names are non-descriptive and seemed transient, which is likely why they got lost/tossed earlier.

Also please note existence of a 'test' subdirectory.  Just added a README.test.txt description there:
==================================================
The test subdirectory contains a variety of files used as inputs and outputs
for test routines, mostly triggered by test.* targets by Ant build.xml
found in the parent stylesheets directory.
==================================================

Wondering why you don't want to use test.nashorn in build.xml as trigger, as before?  Your local copy can easily vary during testing efforts, then we merge changes into version control when ready.

May I suggest that any test worth repeating is better launched via one of these Ant build.xml targets.  They are repeatable across operating systems using this Java-based infrastructure, rather than being shared in a Windows-only batch files that have the same name.

> coderextreme at DESKTOP-DOPK2VD MINGW64 /c/x3d-code/www.web3d.org/x3d/stylesheets
> 
> $ svn !*
> 
> svn diff . | grep ^Index
> 
> Index: CreateX3dSceneAccessInterfaceJava.xslt
> 
> Index: java/build.xml

These are the critical files that I am modifying and developing with.  Changing those is bad, rather suggestions (or patches for subsequent consideration/modification/integration) are welcome.

> Index: java/lib/specifications/x3d-3.0.xsd
> 
> Index: java/lib/specifications/x3d-3.1.xsd
> 
> Index: java/lib/specifications/x3d-3.2.xsd
> 
> Index: java/lib/specifications/x3d-3.3.xsd
> 
> Index: java/lib/specifications/x3d-4.0.xsd
> 
> Index: java/lib/specifications/x3d-schema-changelog.txt
> 
> It appears if I commit, those files will have differences again.

Please do NOT commit changes to those files, ever.  They are copies of primary resources maintained elsewhere.

For more detail, please see message posted this morning along with updated README.lib.txt in that directory.

Change requests for X3D schema design/implementation are welcome.

> Please let me know what you have decided about “Nashorn Folder” Configuration Property versus X3dToES5.xslt.

OK will look.  But initial impression is quite confusing.

a.  The "nashorn/" subdirectory is where you have a variety of code checked into subversion.  Any such directory name shouldn't change via properties, rather it should be stable if in version control.

b. What is intention and design of new stylesheet X3dToES5.xslt ?  Are you creating an EcmaScript language binding for X3D?  If so, there is a lot to talk about.

It would further help to know what you thought about previous suggestions in email threads like this, not sure that we are connecting.  Perhaps a skype call to review?

Step by step please, am hoping we can achieve a common understanding, thanks John.

> John
> 
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
> 
> *From: *Don Brutzman <mailto:brutzman at nps.edu>
> *Sent: *Sunday, January 28, 2018 1:00 PM
> *To: *John Carlson <mailto:yottzumm at gmail.com>
> *Cc: *x3d-public at web3d.org <mailto:x3d-public at web3d.org>
> *Subject: *Re: concern over sourceforge as repository
> 
> More progress.  Successfully tested and deployed new X3DJSAIL build last night.
> 
> Looking in the lib directory now, I think I better understand your concerns about how files there are handled.
> 
> Updated README.lib.txt:
> 
> - Currently X3D schemas, DTDs and stylesheets are copied from master versions
> 
>     (maintained separately) to ensure latest working versions are included.
> 
> - Intent is to be sure best copies are included, deploys do not include any
> 
>     lib assets with known errors (though test development may be in progress).
> 
> - Updated lib copies are periodically checked in, reflecting updates here.
> 
> https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/stylesheets/java/lib/README.lib.txt
> 
> Previously I was not checking those lib copies back into subversion on a consistent basis, thinking that you were using the online deployment.  If instead you were using subversion, that could have been the cause of different outputs during testing.  Sorry about that, if it occurred.
> 
> On 1/26/2018 2:21 AM, John Carlson wrote:
> 
>  > Okay my other changes were to java/build.xml and stylesheets/test.bat and java/test.bat.  That is all.
> 
> Looking forward to getting any further changes you might have, there is time today to carefully integrate them.  TIA.
> 
>  > It was my mistake not to specify a file name for the commit.
> 
> I think you mean "message" describing each change.  Yes that is a good practice that helps collaboration.
> 
>  > I haven’t figured out how to get an interactive editor which shows files to be changed yet.
> 
>  >
> 
>  > John
> 
> Netbeans and X3D-Edit plugin work nicely with subversion for this project!  Am also using Netbeans/X3D-Edit for editing X3D and HAnim specifications on github.
> 
>                  https://netbeans.org
> 
>                  https://netbeans.org/features/ide/versioning.html
> 
>                  https://savage.nps.edu/X3D-Edit
> 
> Hope everything is now working for you too.  Onward...  8)
> 
>  > *From: *Don Brutzman <mailto:brutzman at nps.edu>
> 
>  > *Sent: *Friday, January 26, 2018 4:45 AM
> 
>  > *To: *John Carlson <mailto:yottzumm at gmail.com>
> 
>  > *Cc: *x3d-public at web3d.org <mailto:x3d-public at web3d.org>
> 
>  > *Subject: *Re: concern over sourceforge as repository
> 
>  >
> 
>  > John, sorry to not be clearer earlier.
> 
>  >
> 
>  > Almost all of these assets have a slew of acceptance testing associated with them.  Additionally, am only making schema changes that are discussed first by X3D Working Group (and usually documented in minutes/mantis).  Additionally I have to keep it all straight in my head as we evolve these complex tools.
> 
>  >
> 
>  > Might you please back out the commit, then just commit freely within nashorn subdirectory?
> 
>  >
> 
>  > .. then we keep working on other changes to stylesheets schemas etc. via email dialog and patches. That will keep us synchronized without collisions.
> 
>  >
> 
>  > Thanks for your efforts.  Getting these collaboration patterns sorted out yields powerful progress (and avoids problematic confusion).
> 
>  >
> 
>  > p.s. what don't you like about java/lib subdirectory?  please advise and then I can document lib contents better in a README there.
> 
> 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
> 


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