me (obviously) :)
It would be really awesome if we, as a community, could agree on a
"recommended way".
It could make way for a much improved plugin environment for vanilla
Nuke as well as make the nuBridge more powerful (I know I'm way behind
schedule for it's release, sorry!).
Thanks Erwan for bringing this up!
frank
On 09/01/2016 08:09 PM, Erwan Leroy wrote:
Hello Folks,
I haven't been able to find any unified guidelines on how to neatly
package python plugins.
From looking at what is being done on Nukepedia, everyone seems to do
their own recipe.
When I asked him, Frank Rueter pointed me to the mail with
subject "Nukepedia - nuBridge coming soon" where a conversation was
started about standard good practices.
I would like to get the conversation restarted and try to write down a
set of guidelines for future reference. We could create a shared
google doc (or other collaborative tool, not sure google docs is the
most appropriate) to work on these guidelines as a group.
Who would be interested in collaborating on that?
Cheers.
*Erwan* LEROY
www.erwanleroy.com <http://www.erwanleroy.com/>
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
