Gizmo are useful to pack in 1 node a big bunch of stuff controlled from
the panel and limited a little the access of the artists into its guts.
Now, with the toolsets wich are just scripts loaded, it simplify the
process for those that don't want to get into create a menu as it is
created for you.
you can even still make groups without make them gizmo. The advantage is
it will never brake like a gizmo if some people in your pipeline don't
the gizmo.
We try here to stop people using gizmo or at least convert them back to
group. Because we have to pass over some shots and if some users gizmo
are used, the comp is broken if you don't have them, that force people
to grab and install the gizmo that you don't really want anyway.
So in my opinion. For sharing the whole pipline if all is set centrally,
gizmos are good. if each user has is own stuff not shared, no gizmo, use
toolsets.
chrissowa wrote:
Good morning,
i ve got a question about inserting own nodes in a pipeline. I ve seen
two major possibilities atm:
1. Gizmo: Group a Node, make it a Gizmo, Import it in the menu.py for
general using
2. Nukeskript in a special folder, python script for importing just
this one node in the script; the import is also located in the menu.py
i dont get the difference, why you do it once with a gizmo and once
with a nukeskript and nodecopy.
can someone tell me the advantage / disadvantage of both methods,
i m just interested in this.
thanks in advance.
------------------------------------------------------------------------
_______________________________________________
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
