Actions + Connect

[Carl Claesson 13]

New topic to discuss how Actions and Connect could work better together making it easier to add new Actions to Connect without the need of know how to write Python.

[Milan Kolar 33]

As a very first step I'll just say what we are doing now, to make it a bit easier to manage. Instead of treating actions as a standalone piece of script we only ever run them as connect hooks. So we have a directory with all our actions in it and this directory is set in the `FTRACK_EVENT_PLUGIN_PATH`. That way every machine running connect has access to all the actions straight away.

 

There is a small difference when writing action for this workflow as it has to include register function for it to be picked up by connect. Here is the boilerplate code that let's you run action as standalone or as connect hook.

https://bitbucket.org/snippets/milankolar/gE577

 

 

My point is. I everyone wrote actions in a way that runs as ftrack hook out of the box, then it's a simple matter of dropping them into studio wide `hooks` directory. 

 

Another thing is, that writing action themselves should probably be simplified if possible.