Kevin McAllister Posted September 24, 2015 Share Posted September 24, 2015 I am curious how NV and other developers would recommend handling versioning of Marionette nodes. I can see it happening already in the few test files I've been working in - multiple versions of various nodes. This forum is already filling up with various files and examples too. I am wondering - - how are we going to tell over time which nodes are official nodes installed with VW? Or released by NV as supplementary nodes? - how are we going to tell when official nodes are fixed or updated with Service Packs? - are there best practices for labelling different iterations of nodes/code? Its easy enough to have my own versioning strategy using a simple line of commenting in the code of anything I build or alter but I wondered how others with more experience were doing it. Thanks, Kevin Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted September 24, 2015 Vectorworks, Inc Employee Share Posted September 24, 2015 Best Practices have yet to be developed really, Marionette was unfinished until later in the beta process so there are no experts yet apart from the creators of the feature, who havent used them in a versioned manner so far. For now I would treat them the same as symbols, building libraries of them for easy access later, but I'm sure more methods will develop as the first (us) to gain experience with node and networks come up with them. We are in uncharted waters. Quote Link to comment
Kevin McAllister Posted September 24, 2015 Author Share Posted September 24, 2015 Thanks Jim! (I'll admit it all feels a bit uncharted.... perfect for someone like me :-) and for anyone who's worked in theatre and live performance.) Quote Link to comment
Dieter @ DWorks Posted October 24, 2015 Share Posted October 24, 2015 If you want versioning, just write python plugins, which Marionette actually does.... Quote Link to comment
Vectorworks, Inc Employee Dave Donley Posted October 27, 2015 Vectorworks, Inc Employee Share Posted October 27, 2015 The Python node scripts could have comments about which version they are, as well as a history. Not sure if people would go to the trouble of that because old versions of nodes will continue to work fine I think as long as the API they refer to hasn't changed (like "vs" or other). Quote Link to comment
Kevin McAllister Posted October 27, 2015 Author Share Posted October 27, 2015 Dave, The impetus for asking was someone posted a newer version of a NV node that shipped with VW. The old node was generating an error message so it wasn't working fine. Without a change log and a versioning system it would be hard to troubleshoot a Marionette script containing this node since it should just work. Kevin Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.