That is exactly the idea for nuBridge. But it'd be good to define a
standard way with or without nuBridge, so we all agree and and don't
have "multiple standards".
On 09/01/2016 08:57 PM, Justin GD wrote:
Hi guys,
I'm not sure I've followed all the feature of nuBridge; but I believe
it would make sense to agree and define coding 'standards' to make it
accessible to a larger users & developers community.
Also, it would be nice to develop a new layer of python functions that
we could use as a standard 'high level API' in order to deal once and
for all with any required coding when installing a script (adding
menus, dealing with init.py and menu.py, etc ). Is this what nuBridge
does already ?
I'll be interested to be part of the conversation as well.
Thanks,
Justin
2016-09-01 9:17 GMT+01:00 Frank Rueter|OHUfx <fr...@ohufx.com
<mailto:fr...@ohufx.com>>:
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
<mailto:Nuke-python@support.thefoundry.co.uk>,http://forums.thefoundry.co.uk/
<http://forums.thefoundry.co.uk/>
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python>
_______________________________________________ Nuke-python
mailing list Nuke-python@support.thefoundry.co.uk
<mailto:Nuke-python@support.thefoundry.co.uk>,
http://forums.thefoundry.co.uk/ <http://forums.thefoundry.co.uk/>
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
<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
_______________________________________________
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
