Welcome!
This is the community forum for my apps Pythonista and Editorial.
For individual support questions, you can also send an email. If you have a very short question or just want to say hello — I'm @olemoritz on Twitter.
Editorial 1.2 Ideas/Requests
-
After reading up on Editorial 1.2 features, I am wondering if some old ideas I had before are not possible. If not, then here are a few requests:
Document Variables
It would be nice if we could store workflow variables globally to use as variables in documents. Now, with the new HTML, CSS, and Javascript modes, it would be nice to create a workflow that saves the content of a .css as a variable within the CSS document (in the head section of course) rather than having to put the actual content in the document.
It would look something like the CSS variables do in the default .css template for the editable previews.
Python syntax mode
Since we have modes now, it would be nice to also have a Python syntax mode. Perhaps we can run python scripts stored in documents in the document library?
Fountain mode
All fountain syntax like the @ sign to force a character is not implemented. Also using ~ for lyrics would be nice.
Preview theme PDF export
We can now make nice looking themes for preview, but the PDF export does not export the current theme. This addition would be nice.
More to come as I think of them and test the new version.
By the way, THANK YOU FOR THE AWESOME UPDATE!
-
There is a place for HTML in the "generate PDF document" step of the new "convert to PDF" workflow. Just copy your preferred theme's HTML into that slot.
If you want the ability to export with different themes, make multiple copies of the workflow and edit accordingly.
Just a suggestion.