Forum Archive

Are there any Editorial tips & tricks to allow to share one's own Python functions between multiple Editorial workflows, please?

Over time, I've ended up with nearly 170 workflows, and several of these are 'sets that do similar things', with a lot of Python helper functions in common with each other.

The developer in me finds this quite painful! If I want to change some behaviour in a helper function, I have to find all the copies and update them. And it makes it harder to find the small bits of interest in each workflow.

Characteristics I think this needs the shared code needs to be:

• editable with the Editorial Python editor somehow
• in a location that can just be pulled into workflows via import
• in a location that is included in Editorial backups

(I realise that doing this would make it impossible to just upload the resultant workflows to the Editorial Workflow Directory, to use on other devices - but I could like with that)

Thanks in advance,

Clare

Look at these workflows I made ...

RV: Workflow Installer - this allows you to install workflows with dependencies. In other words, it install workflows referenced by name.

RV: Workflow to Module - this allows you to convert workflow (with one Python script) to module, which will be installed in site-packages. You can reuse this module with simple import statement in your workflows / Python scripts.

RV: Module Manager - this allows you delete installed modules or convert them back to the workflow, so, you can utilize Editorial Python script editor with full syntax support. Convert them back to module with RV: Workflow to Module workflow.

My plan is to enhance RV: Workflow Installer to handle module dependencies as well.

Wow - that looks amazing!

Thank you very much, I'll give it a go.

Clare

Does anyone out there know if these workflows are compatible with the Editorial beta, please?

(I saw a message somewhere that it had only been tested with the current app-store version, but it would be good to know if that info is now out-of-date)

Tested in beta as well, nothing special there, ie. beta changes shouldn't affect these workflows.

Great - thank you!

Check out sub-workflows. If you have a sub-workflow with a Python script then you can use it in several workflows. Just as you want.

http://www.macstories.net/reviews/editorial-1-1/#sub-workflowsandx-callback-url

and

http://omz-software.com/editorial/docs/ios_workflows/special/action-sub-workflow.html

Thanks @peterh and @ccc for the suggestions. I'm aware of these features and use them heavily, but this question is specifically about sharing python code via import - which @rvolta's do allow.