You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The proposal is to make nodegraphs be declared as implementations for node definitions in a consistent manner to how non node-graph implementations are declared.
The modification would be to have an explicit association within an <implementation> element.
The new supported attribute would be called something like "nodegraph".
Options:
Nodegraphs are considered to be language independent so language has no meaning
Q: Should target be allowed ?
implname should still be allowed
file filename option does not really make sense
Upgrade Path:
For current nodegraphs which have a reference to the definition it is implementing, this would be no longer be supported. The upgrade path would convert these to implementation declarations.
Currently implementation files are solely used for per shader API associations with implementations. Where would these new implementations reside? (In a new file at the sample level as the _defs, _ng mtlx files?
Currently when querying for an implementation from a NodeDef an Implementation reference or a NodeGraph reference is returned. The change would be that there would always be an Implementation type returned and the type of implementation is determined by examining the Implementation itself (nodegraph attribute usage). This requires another level of indirection to provide consistency.
Note that consistency between the NodeDef and a NodeGraph is still based on Outputs and Inputs/Parameters adherence left to the user of each interface.
The text was updated successfully, but these errors were encountered:
Proposal
The proposal is to make
nodegraphs
be declared as implementations for node definitions in a consistent manner to how non node-graph implementations are declared.The modification would be to have an explicit association within an
<implementation>
element.Note that this proposal and this companion explicit input change proposal can work independently or together.
Example:
Somethng like this:
would instead be an association specified as follow.
The new supported attribute would be called something like "nodegraph".
Options:
language
has no meaningtarget
be allowed ?implname
should still be allowedfile
filename option does not really make senseUpgrade Path:
_defs
,_ng
mtlx files?nodegraph
attribute usage). This requires another level of indirection to provide consistency.The text was updated successfully, but these errors were encountered: