Exactly Michael. That's what I've been doing for the past 10 years in Nuke and so far it has worked just fine.
Also any menu I create in Nuke that creates a gizmo I've authored always calls the latest version of that gizmo. This seems enough to ensure people are always creating/using the latest version available while older versions remain there for backwards compatibility proposes if needed. It also allows me to notify the user when opening a script that is not using the latest version available. And any script that is archived automatically get it's gizmos converted into groups in order to make sure people won't have many problems when opening such scripts in the future. Cheers, Diogo On 04/09/2012, at 05:17, "Michael Habenicht" <[email protected]> wrote: > If a gizmo changes that much that you can not be sure it still works with > older scripts than you have to version it up. There is no way breaking things. > If you update the menu entry to create the latest version of the gizmo you > make sure your artists are always working with the latest version but old > scripts are still working. And if you want to use an older version of a gizmo > you can still create it manually. > > Best regards, > Michael > ------------------------------------------ > DI (FH) Michael Habenicht > Digital Film Compositor & TD > > http://www.tinitron.de > [email protected] > ------------------------------------------ > > > > ----- Original Message ----- > From: [email protected] > To: [email protected] > Date: 04.09.2012 09:48:22 > Subject: [Nuke-python] Re: Assigning a custom nodeclass to a gizmo? > > >> >> Diogo Girondi wrote: >>> Managing revisions and versions of grizmos in scripts that are being >>> versioned themselves can quickly become a real nightmare. >> >> >> Well but what about opening an old comp that uses a gizmo that has been >> changed? An artist should always be able to rely on the fact that whatever >> he used in the comp still works as it did back when he first created it. >> >> And of course not every little gizmo people create may make it to a >> company's repository right away, in which case grizmos help should it be >> necessary for a different artist to edit a comp. >> >> @ NathanR: >> >> So what function can be used to change class names? >> >> >> >> _______________________________________________ >> Nuke-python mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > > _______________________________________________ > Nuke-python mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python _______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
