Absolutely. Even if only with one machine I'll set is up as a central set up.
Howard On 3 Sep 2012, at 18:48, Diogo Girondi <[email protected]> wrote: > True. But setting up a central Nuke repository that is accessible to every > Nuke seat and renderbox in my opinion is a must. Managing revisions and > versions of grizmos in scripts that are being versioned themselves can > quickly become a real nightmare. > > > -diogo > > On Mon, Sep 3, 2012 at 2:10 PM, Hugo Léveillé <[email protected]> wrote: > One advantage of grizmo over gizmo is that you can install it only for you > and it will still works on the renderfarm unlike gizmo that needs to be > accessible or deployed > > On Mon, Sep 3, 2012, at 12:54, Diogo Girondi wrote: >> Sure. >> >> Usually you use gizmos when you don't want people to go wildly creative on >> things without knowing what they are doing, and want to easily maintain >> certain bits throughout a project. Since gizmos are external to scripts you >> can easily update a single file and have it updating every script that is >> using it. This doesn't happen when you're working with groups. >> >> Each one has it's advantages and disadvantages, so there is not right or >> wrong. >> >> But debugging a gizmo is not that different than debugging a group. They are >> basically the exact same thing from a dev pov. >> >> >> -diogo >> >> On Mon, Sep 3, 2012 at 1:13 PM, sh4dow <[email protected]> >> wrote: >> Well... I think what is "proper" depends on one's approach to things. I like >> to keep things as open as possible, so that capable people have an easy time >> changing things if they need to. >> >> Also, gizmos can be a pain to debug. For instance, nuke is for some reason >> creating key frames on a gizmo even though it doesn't if I change it to be a >> group inside the gizmo. Plus, I can't easily see what the code I put into >> the callbacks is actually doing inside the gizmo. >> So... from my perspective, it only makes things unnecessarily annoying. >> >> _______________________________________________ >> 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 > > > -- > Hugo Léveillé > TD Compositing, Vision Globale > [email protected] > > _______________________________________________ > 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
