@omz, any idea / explanation form your side?
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.
Posts made by Stefano
-
RE: Combined Workflows With Python Scripts Crash / Freeze Editorial
-
RE: Combined Workflows With Python Scripts Crash / Freeze Editorial
That is exactly one setup I have @TutorialDoctor :
-
Main WF calls the ( modular ) Sub WF and processes the output with actions. Works fine.
-
Main WF calls the ( modular ) Sub WF and processes the output by calling a Python script — I have moved the previous second Sub WF one level up. Here Editorial crashes at every second Run of the Main WF. After killing Editorial the first run is fine again and ... crashes afterwards. Puzzling.
Maybe Editorial doesn't like to process Python in different WFs during one combined run?
-
-
RE: Combined Workflows With Python Scripts Crash / Freeze Editorial
Thanks to both of you @ccc and @TutorialDoctor for your replies.
@ccc : I have set up a simplified version of my modular approach and it works without flaws. There must be something else going on. I will investigate and keep you int the loop.
@TutorialDoctor : I have downloaded your WF — interesting approach! Here comes my way:
-- Main WF : defines some ( action ) variables, calls a first Sub WF, which mainly consists of a Python script for producing an out- / input. A second Sub WF ( again a Python script ) is run to construct the final result.
The reason for my approach: I can use the first Sub WF to build some other main WFs. All future bug fixes and enhancements in the WF module will immediately reflect in any Main WFs using it. Nice! No tedious copying etc.
-
Combined Workflows With Python Scripts Crash / Freeze Editorial
I am working on a side project that uses a modular workflow ( WF ) approach.
The main WF calls a sub WF, which contains a Python script, and afterwards uses its own Python logic to further enhance the output.
Running the main WF crashes / freezes Editorial every second time. Replacing the Python script in the main WF with Editorials Action logic runs flawlessly as expected. The only downside for this approach is the rather long chain of actions.
It looks like Editorial can handle only one ( or maybe more? ) Python script on the same "execution level" at a time.
Is this issue known ( to anyone ) and does someone have a possible solution for it?
-
RE: Editorial = Taskpaper on the iPad?
Yeah and pleasure! So you are adding / removing the
@done
tag, if one is using the checkboxes. Good.If you look at TaskPaper ( TP ) for Mac, notes are greyed out ( a little bit ) to make the difference, but on the font size side no changes are applied. I would like to suggest to stick as much to the original — at least in the beginning — as possible. It will attract even more people using TPM ( Mac ) and looking for an alternative for TPT ( Touch ).
-
RE: Editorial = Taskpaper on the iPad?
That already looks awesome Ole!
How are checked tasks being translated in the original file and how are you going to handle notes?
-
RE: Scripts not updating on import?
Right,
reload
works withmodule objects
— successfully imported before — only … -
RE: Scripts not updating on import?
Try
reload( helpfunc )
at the end ofmainprog.py
, it should do the math. -
RE: Previewing MMD tables (including spanning fields)
Ole is thinking of supporting MultiMarkdown in the future, see http://omz-forums.appspot.com/editorial/post/6488681971974144.
-
Literate Source Code Published
Explain and Code.
Let us change our traditional attitude to the construction of programs: Instead of imagining that our main task is to instruct a computer what to do, let us concentrate rather on explaining to human beings what we want a computer to do. — Donald E. Knuth
The workflow has been uploaded to the directory : http://editorial-app.appspot.com/workflow/6403405396312064/tV42vb3ZIGE.
It allows to extract source code from the
Markdown
( documentation ) file. See https://github.com/StefanoRausch/Literate-Source-Code for more information.Happy literate source coding!
-
RE: Literate Source Code Published
Sure. Have a look at the Gruntfile.js implementation for a JavaScript example.
You can use LSC for any programming / markup language. I do primarily use it for Java / CoffeeScript, CSS / Sass and HTML.
-
RE: How do I perform simple read/ write operations on a plain text file in Dropbox?
Have you had a look at Editorial's manual? You'll find the answers to your question there ;)
Regarding the other applications you are mentioning take a peek at the respective documentation.
-
RE: Tiny WebDav Server for Pythonista
Nice! Haven't tried it out, but could come in handy.
-
RE: Subscript
You're right in that respect that Editorial does ( mostly ) support Markdown.
However, Ole is thinking about switching to MultiMarkdown, see https://omz-forums.appspot.com/editorial/post/6488681971974144.
-
RE: Subscript
While Super <sup>scripting</sup> works fine as you have detailed out, unnfortunately you will have to revert to
HTML
for Sub <sub>scripting</sub> something : use the<sub></sub>
tag.Note : the forum Markdown parser does not support the
^
shortcut, while Editorial does. -
RE: Outline view
Not quite what you are looking for, but
tap
on the file's name and you get a list of the existing headings — sort of outline.Otherwise you need to define a dedicated workflow for it.
-
RE: problem with python script
Ole did reply in the Phytonista forum : duplicate post https://omz-forums.appspot.com/pythonista/post/5780668424388608.
-
RE: iPhone App?
+1 !
However, it should not be a stripped down version. I like to have the same feature set on both the iPad and the iPhone.
-
Full MultiMarkdown Support
Hi Ole,
What are your plans to fully support MultiMarkdown?
Currently only a small subset can be correctly previewed.
Keep up the excellent work!
Cheers
-
RE: Reassigning the keys at the bottom of the edit screen
Try out the workflow editor. It really is easy to implement your requirements.