I'm not sure if this makes sense, but in Editorial, is there any way to get Taskpaper mode for markdown files? Specifically, I’d like to have the tagging/row highlights, ability to move lines, and task behavior (checkbox, done, etc) mixed with full markdown support.

I tried setting one of the markdown extensions to be .taskpaper but that didn't seem to stick. I'm guessing that a document is in either Markdown or TaskPaper mode, and those can't be combined? It would be nice if they could (and then I could set the TaskPaper settings to apply for .md files), but I'm not sure how feasible this is from an implementation standpoint.

I can already get some of the line movement through a workflow, so I can probably solve that (albeit not as cleanly as the drag handles support for TaskPaper mode). Check boxes aren't critical (more a nicety) but I suppose maybe I could get some of the tagging/row highlights via a custom template for markdown mode that responds based on how a line is tagged?

Thanks,
Ed

Any plans to add support for accessing the calendar or contact databases, perhaps through a Python module? I have some ideas for workflows (mainly around taking meeting notes) that would work better if I could pull up a list if meetings from the calendar or a list of contacts.

Ed

Thanks - looking forward to the calendar module for access to event info. Will make my meeting notes workflows easier and less reliant on an external connection.

Ed

I included an example of how I did this with my Dropbox Auth workflow. Scroll to the bottom of the workflow for the example actions with code.

Ed

Thanks - I was going to do something like that initially, but after moving the file, I wanted to be 'done' with that file if it make any sense?

Right now, I'm going to try and write up something that just opens the next file in the directory, and if there are no more files, then just an empty file.

I have a python action to move a file from the local library to the dropbox library. It uses editor.set_file_contents() to create the copy in Dropbox, and then os.remove() to delete the local file, followed by editor.reload_files() to update the library.

Everything seems to work (ie the file is moved as expected), but a file with that name/contents is open in the editor. If anything changes with this file, it's written back to its original location as a new copy. Is there any way to clear the editor contents or close the file?

The only workaround I can think of is to have a scratch file that I open after the above steps to discard the current contents, but I was wondering if there was something cleaner.

Thanks,
Ed

Yes I am. Thanks for the update.

I have a workflow that creates a local file with Set File Contents and then tries to open it with Open Document. Every time, I get an error that says the file doesn't exist. The file is created (I can view it in the document browser just fine), but it doesn't seem to be available to the workflow after it's created.

I've reverted to opening the file via Editorial's URL scheme, which works fine for now. Is there something else that needs to be done to allow Open Document to work (something like refreshing Editorials cache or file list)?

Ed

Is there a way to open a file in edit mode (I.e. with the keyboard open and cursor at a location)? I'd like to open a file ready to enter new text at a specific location. Right now I'm opening the file via Editorial's URL scheme and passing a selection parameter to scroll the cursor to the end of the document, but I don't see a way to put the file in edit mode.

Thanks,
Ed

Also, FWIW, I was running iOS 6 (NO jailbreak) on an iPad Mini when I saw the crashes. The only way to get around it was to kill editorial and restart it (it would still be in the multitasking list after the crash), but even that wasn't 100% reliable.

Ed