hi guys, that would certainly suite our workflow too. we are manually copying these to a global location, but the way paul describes the idea seems pretty solid for the way we would see it working too ...
ben On 23/11/11 14:35, Paul Raeburn wrote: > Hi Peter, > > I would think that if there was an existing sub-dir in the NUKE path then it > would be available to all users, but if the user had their own identically > named sub-dir then it would come up as [user] . Meaning that you would > respect the NUKE_PATH order of loading as to where was looked for first. > > > So you would still have to manually make the sub-dir > /server/nuke/config/ToolSets/myShow, but after that if a user makes > myShow/imatool.py it would go to the server location, not make a new myShow > in their ~/.nuke. > > Would that make sense? > > > On 21/11/2011, at 10:52 PM, Peter Crossley wrote: > >> Hi Paul, >> >> Yes, currently all Toolsets get saved in the .nuke directory and must be >> manually copied to a shared location if you'd like them to be made available >> to ther users. I guess it would be possible to add a preference for Toolset >> save location, but this could be have a potential for problems if a user >> forgets that they have this option set and accidentally polutes a shared >> location with all their personal toolsets ... >> >> How would you like this to work? Is it literally just being able to override >> the default location? >> >> Regards, >> >> Peter. >> >> On 20/11/2011 20:13, Paul Raeburn wrote: >>> I'm trying to work out how to allow users to save toolsets for other people >>> to pick up. By default when you use the Create function, they get saved in >>> your ~/.nuke/ToolSets directory. If you make a toolsets directory in the >>> nukepath elsewhere the menu items show up for everybody, which is great, >>> but I would like users to be able to be able to save a snippet for other >>> people to be able to grab. >>> >>> I have tried making a sub dir in the communal nuke path location of >>> ToolSets/stuff and then creating a stuff/test toolset, but I get the an >>> additional "[user] stuff" menu item and it still gets saved in mu >>> ~/.nuke/ToolSets >>> >>> Is this just not possible, do you have to manually copy to make communal >>> tools?_______________________________________________ >>> Nuke-users mailing list >>> [email protected], http://forums.thefoundry.co.uk/ >>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >> >> _______________________________________________ >> Nuke-users mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users -- ben roberts compositing supervisor [email protected] | rising sun pictures | www.rsp.com.au phone +61(0)8 8400 6400 | fax +61(0)8 8400 6401 | direct line +61(0)8 8400 6447 level 1, 180 pulteney street, adelaide, sa 5000 _______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
