This is a feature I would love.

I currently use my own workflow for a markdown HTML preview with links. However, I would rather use the standard Editorial preview (with its standard interface and custom markdown formatting). So it would be great if links were supported in the preview.

There is an issue that would have to be resolved though. The preview previews the current editor file, so there are two choices:

1. Should should the editor follow link traversal (to ensure the preview matches the currently edited file - as now)
2. Or should the link traversal be independent of the editor's file (that is how my HTML workflow works)

I prefer the second option as it allows me to browse my notes, but realise this doesn't fit with the current preview paradigm.

Either way, this feature would be great.

Martin

Hello,

I like to develop my workflows purely in Python (so, I can write unit tests for them on my Mac (using mocks for editor, workflow, etc), get the plugin working, then wrap it in json and deploy to Editorial).

Anyway, I was wondering if the 'Show HTML' workflow action was available as a call from Python? This would enable my latest workflow to be pure Python (and makes wrapping up the json easier, rather than have to add the 'Show HTML" action as a special case).

Thanks

Martin

Hello,

I was wondering if it is possible in Editorial to associate workflows with events that occur in Editorial.

For example, on opening a document it would be great if that could automatically run a workflow (that had been hooked up to that event). In this example I was thinking of automatically switching workspaces - based on the Workspaces workflow.

Any thoughts would be appreciated,

Martin

Thanks minniepicker, yes, that is a possible workaround for my example, though I am hoping for more general hooks support.

e.g.

• on_delete: (when a file is deleted in the file browser, as I am trying to maintain an index of all my documents to enable faster searching, but I don't know when documents are deleted)
• on_preview: so that small customisations can be made to the standard preview

My hope is that this would provide a mechanism for things to be "baked" into the UI, eg Global Search, but with that just being a hook to a standard workflow so it can be customised, etc

Obviously it ain't as easy as it sounds, but I can dream.

I am using SimpleHTTPServer in an Editorial workflow. This works well, except the stop button and the spinning button do not kill the workflow.

The background timeout will kill the workflow, but I am unable to do it manually.

Can anyone help?

Thanks

Martin

Thanks for the idea, but it am running the example at the end http://omz-software.com/editorial/docs/library/simplehttpserver.html

There isn't a place to put the raw_input.

I'll keep hunting for ways to stop it (it stops under pythonista, so I'm sure there is a way).

Martin