Hey Franke, been a while :) Hope you're doing good!
Will nuBridge become mandatory for nukepedia? Because no matter what is being agreed on, there is a 99% chance it wont't work for us (and possibly other larger shops with custom deployment strategies in place). Cheers, Thorsten --- Thorsten Kaufmann Production Pipeline Architect Mackevision Medien Design GmbH Forststra?e 7 70174 Stuttgart T +49 711 93 30 48 661 F +49 711 93 30 48 90 M +49 151 19 55 55 02 thorsten.kaufm...@mackevision.com www.mackevision.com<http://www.mackevision.com/?utm_source=E-Mail-Signatur&utm_medium=E-Mail&utm_campaign=Mackevision-Link> Gesch?ftsf?hrer: Armin Pohl, Joachim Lincke, Jens Pohl HRB 243735 Amtsgericht Stuttgart --- NEW PRODUCT: Innovation in moving images - Motionbox<http://www.mackevision.com/motionbox/?utm_source=E-Mail-Signatur&utm_medium=E-Mail&utm_campaign=Motionbox-Signatur> VFX: Game of Thrones, Season 5 - VFX making of reel<http://www.mackevision.com/references/got-5-making-of/?utm_source=E-Mail-Signatur&utm_medium=E-Mail&utm_campaign=GoT-S5-making-of-Signatur>. SOCIAL: Follow us on Facebook<https://www.facebook.com/mackevision.global>, Twitter<https://twitter.com/Mackevision>, Behance<https://www.behance.net/mackevision> and Vimeo<https://vimeo.com/mackevision> From: nuke-python-boun...@support.thefoundry.co.uk [mailto:nuke-python-boun...@support.thefoundry.co.uk] On Behalf Of Frank Rueter|OHUfx Sent: Freitag, 2. September 2016 06:46 To: nuke-python@support.thefoundry.co.uk Subject: Re: [Nuke-python] Python Plugins Guidelines Nice one, thanks. On 09/01/2016 11:16 PM, Erwan Leroy wrote: Just created a basic google doc, almost empty for now, feel free to contribute: https://docs.google.com/document/d/1aiAWTc-BwIyZBd4jSspzOYTvBD0G3RdvPSrftCVutzs/edit?usp=sharing Erwan LEROY www.erwanleroy.com<http://www.erwanleroy.com/> On Thu, Sep 1, 2016 at 6:10 PM, Ant Nasce <a...@thefoundry.co.uk<mailto:a...@thefoundry.co.uk>> wrote: Hi all, Probably stating the super obvious here, but distributing code as a package, stored in a directory, with a top level __init__.py per package would be my preferred approach. See: http://mikegrouchy.com/blog/2012/05/be-pythonic-__init__py.html Doing it in a package-way would allow nuBridge to do a validation step at the top-level __init__.py file, to check for required things like: 'docs', 'version', 'description', 'author', 'copyright' etc. Hiero+NukeStudio put all auto-scanned Python packages containing a __init__.py (found in .nuke/Python/Startup) into a hiero.plugins<https://docs.thefoundry.co.uk/hiero/10/hieropythondevguide/setup.html>.* namespace... So plonking these into nuke.nuBridgePlugins, might be something to consider? If there's a Google Doc link I'd be happy to check it out and contribute! Cheers, A On Thu, Sep 1, 2016 at 9:57 AM, Justin GD <j.grosde...@gmail.com<mailto:j.grosde...@gmail.com>> 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://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://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://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://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://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
