[x3d-public] Class grammars? and maintaining or reproducing templated method bodies from non-templated method bodies

[John Carlson]

Merging conversation into x3d-public to get experience of others.

I think we can keep line number information in each artifact, like

<!--file://..../Scene.java#15--> (line 15 of Scene.java in referenced 
from an XML or XSLT file)

/* file://...../X3dUnifiedObjectModel-4.0.xml#25 */ (line 25 of 
X3dUnifiedObjectModel-4.0.xml referenced from a Java file)

/* file://..../CreateX3dSceneAccessInterfaceJava.xslt#34 */ (line 34 of 
CreateX3dSceneAccessInterfaceJava.xslt referenced from a Java file)

These might as file annotations in comments.   Full paths or relative 
paths may be provided.  This information might not be stored in the the 
source and target files, but rather in a metadata file.

I guess that hyperlink anchors could be provided to jump between the files.

Am I missing anything? Is this already done?  Is there a way to jump to 
a line number from another file in NetBeans?

Is that what you do for maintaining method bodies in source between 
class grammar modifications, Cameron?

How easy are these things to add to the Java, XML and XSLT files, Don?  
Should we add a complete anchor tag, and a @see?

How are line numbers typically referenced in XML, XSLT and Java? My 
guess is it might be possible.

I really am a NetBeans newbie.

I hope I am being helpful.  I'm trying to provide programmers better 
ways to navigate between XML and Java. Vim really is not cutting it.

Am I ready yet?  I'm feeling a disturbance. I feel this is adequate for 
"decompiling" back to XML or for providing hints in Java for reaching 
back to source documents. I do not know if XML and XSLT needs to know 
the Java line number, unless the Java already exists.

Thanks,

John

On 8/21/21 1:18 PM, John Carlson wrote:
>
> Hi, all: I'm getting ready to aim at another target now.  We'll see 
> what it means for XSLT, and whether a better tools could be developed 
> (or have been). Your assistance is welcome.  We have experience with 
> XSLT, Java, Aspect, Domain-specific modelling, object models, class 
> grammars, game development,dynamic weaving, etc.
>
> Background:  We are generating Java classes and interfaces from 
> XSLT+Java (especially Java method body snippets)+comments and an 
> X3DUOM (unified object model in XML).  I do not have aspects. If they 
> would be useful, I could generate some--if we could we could round 
> trip the Java to XSLT+X3DUOM and back, plus also generate the object 
> model from the transformed Java.  I am referring to cross-cutting 
> concerns in the method bodies (see subject), but the names change in 
> the cross-cutting concerns at a per class level.   We have a rich 
> hierarchy of Java classes and interfaces.  We can get the classes and 
> fields from the X3DUOM, important/unique method names are more in the 
> Java code, either in the transformed result or the XSLT+Java.
>
> If you would prefer to do the same in Python, we have that too, to a 
> lesser extent (can't read XML yet, that I know of).
>
> If there was something that could be added to XSLT 2 to help with this 
> task, what would it be? Is there something better than XSLT 2?
>
> John
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20210821/0ce38fa0/attachment.html>