RE: [Nuke-python] Python Plugins Guidelines

2016-09-02 Thread Thorsten Kaufmann
rank Rueter|OHUfx Sent: Freitag, 2. September 2016 10:23 To: nuke-python@support.thefoundry.co.uk Subject: Re: [Nuke-python] Python Plugins Guidelines Hola. No way, I won't make it mandatory for anybody. It's meant to become a convenience thing for people who want it. And it probably will h

Re: [Nuke-python] Python Plugins Guidelines

2016-09-02 Thread Frank Rueter|OHUfx
/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: [Nuk

Re: [Nuke-python] Python Plugins Guidelines

2016-09-02 Thread Erwan Leroy
ision> > > *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: [N

RE: [Nuke-python] Python Plugins Guidelines

2016-09-02 Thread Thorsten Kaufmann
f 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

Re: [Nuke-python] Python Plugins Guidelines

2016-09-01 Thread Frank Rueter|OHUfx
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

Re: [Nuke-python] Python Plugins Guidelines

2016-09-01 Thread Frank Rueter|OHUfx
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

Re: [Nuke-python] Python Plugins Guidelines

2016-09-01 Thread Erwan Leroy
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 On Thu, Sep 1, 2016 at 6:10 PM, Ant Nasce wrote: > Hi all, > > Probably stating the s

Re: [Nuke-python] Python Plugins Guidelines

2016-09-01 Thread Ant Nasce
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

Re: [Nuke-python] Python Plugins Guidelines

2016-09-01 Thread Justin GD
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 standa

Re: [Nuke-python] Python Plugins Guidelines

2016-09-01 Thread Frank Rueter|OHUfx
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 Erwa