Wrapping in an if block might have been easier, I didn't think of that.
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 CascadeHush
-
RE: Duplicate/Copy a workflow
-
RE: Duplicate/Copy a workflow
@enceladus said:
This worked for me.
Thanks
Here's what I ended up doing, based on your info.
1 Open the template you want to copy.
2 Copy the workflow ( tapping the title and tapping copy workflow)
3 Rename the existing template to something new (this will be the new copy)
4 In safari, paste into the address bar (this is what was copied in step 2) and open the URL which will give you the original template backI think that makes it a bit more clear what is what, for anyone who may come along in the future.
That's some pretty crazy stuff, when all we need is a copy template button, but at least I can do it.
Thanks again.
-
RE: Duplicate/Copy a workflow
Neither the new template nor the new workflow buttons offer to create a template/workflow from the copied workflow.
-
RE: Duplicate/Copy a workflow
There is almost no documentation on Templates at all. It is possible to essentially turn them off, which may be why there is some confusion as to what we are actually talking about here. If you're used to creating a new blank document and then running workflows from there, then that's a totally different approach to what I'm trying to do here.
I'm all but certain there is no way to copy a template. Nor does there seem to be a way to paste a workflow into a template (either would do).
So I had to save the individual steps as presets (the ones that I wanted to copy over) and then create a new workflow one step at a time - adding the presets in order.
It's not quite as tedious as it sounds, and at least the option is there. Workflow (the app) doesn't allow you to copy actions at all, which is a major reason why I"m transition to Editorial. I'm sick of rebuilding the same functionality over and over.
-
RE: Duplicate/Copy a workflow
The docs may be clear, but in the apps interface they are called Document Templates. The screen where you run them calls them templates. To get to the 'workflow' editor (if that is what it's called), you select 'Edit Template'. At every step of the way, they are called templates, except when you want to share or copy them, and suddenly they are called Workflows (something I've only just learned in the last hour, when I tried to do this for the first time).
So there are 2 different names for the same thing (maybe, I"m still not convinced)
The fact that the documentation, and one of the menus refers to them as Workflows, when the app itself begins by calling them Templates, is just weird.
I've never used the wrench icon. I don't know how I could have known they would be there.
I don't see what good they do me there. I would have to create a blank document first to get access to the spanner menu, which is just an extra step and creates an unnecessary extra document.
So I guess I actually am after a 'copy template' option, which it appears doesn't exist. It also doesn't seem possible to turn a workflow into a template, unless that is hidden somewhere else.
-
RE: Duplicate/Copy a workflow
I tried downloading this workflow
http://www.editorial-workflows.com/workflow/5248159185895424/K8u6w6ZPJZQ
Again, nothing happened at all. It asked me if I wanted to Add Workflow, and then... nothing. No new template or preset, nothing.
-
Duplicate/Copy a workflow
I have a template, which I think may be also called a workflow (some clarification on this would be good).
I want to copy it so I can make a similar template.
I can click the template name in the editor (workflow editor??) and there is a Copy Workflow option... and then what. It doesn't seem to do anything except say 'copied'. There doesn't seem to be any way to paste it anywhere, and it doesn't create a new template identical to the existing one (which would be the preferred option). It just disappears into a black hole.
I can't see anything in the documentation on this. Maybe I"m missing something really obvious, but this particular thing is not at all intuitive. What I really want is a copy template function, but there doesn't seem to be one of those.
So then I even tried sharing a workflow using the online function, and renaming the existing workflow and then downloading the original workflow to create a copy that way. But even though the workflow appeared on a website, and I clicked the install button, and it said it had added the workflow... but nothing happened. No new template, no new workflow, just nothing happening.
It seems that template and workflow are synonymous, which is unnecessarily confusing. It also seems the installing templates from the website is broken too.
-
RE: Open python files from Dropbox
Thanks. That's helpful. I'll see how I go with just Editorial for now. When I want to start working on stuff outside of that, I'll think about my next steps. I can continue to use Workflow for some stuff and Editorial for the rest.
-
RE: Open python files from Dropbox
Maybe I haven't communicated effectively.
Can Pythonista open .py files from Dropbox the way editorial opens text files from Dropbox?
I'm not working on complex multi-file projects, just converting relatively simple workflows from the Workflow app to Python.
Otherwise, the workflow you explained seems no simpler than what I'm already doing in Editorial.
-
A simple menu with submenus
I thought someone might find this useful. Also, feedback on code style ('the python way of doing things') would be appreciated, I've been coding in Python for less than 12 hours.
It is a way to present a simple menu with submenus, and returns the selections for further processing. The example provided is from a food diary script I'm converting from Workflow that I used to use with Day One.
I know there is no kind of error checking at all, for my purposes I don't really think that's necessary.
Should work in Pythonista too.
import dialogs def menuWithSubmenus(menuTitle, menuList): #Present main menu and get user choice mainMenu = ([d['mainMenuOption'] for d in menuList]) choice = dialogs.list_dialog(title=menuTitle, items=mainMenu, multiple=False) #Present sub-menu and get user choice subMenu = (next((item for item in menuList if item['mainMenuOption'] == choice))['subMenuOptions']) subChoice = dialogs.list_dialog(title=menuTitle, items=subMenu, multiple=False) return { 'mainMenuOption':choice, 'subMenuOption': subChoice } #Example Usage menuItems = ( { 'mainMenuOption':'Cereal', 'subMenuOptions': ('Saltana Bran', 'Wheat Biscuits') }, { 'mainMenuOption':'Fruit', 'subMenuOptions': ('Apple', 'Banana', 'Mandarine') } ) print (menuWithSubmenus('Meal/Snack Type',menuItems))
-
Open python files from Dropbox
Can Pythonista open python files from Dropbox?
I am mostly only interested in Editorial, and have some basic Python scripts running there, but I'd like to do a lot more. Currently my workflow is to write the script in a text file on Windows in an IDE, saved in a Dropbox folder. I then have to open the file in Editorial and copy the code from the text file to the Editorial template builder action. This has already become very tiresome. I can't see any other way to do it, and Editorial specifically refuses to open .py files directly.
So I'm thinking (hoping) that if Pythonista can open .py files directly from Dropbox, it may be a much quicker workflow to get stuff running, and then when they are, I can paste the final code into the Editorial template.
(All my stuff so far was built using the Pythonista documentation, so for what I want to do, they seem to run the code the same way)
But there is nothing anywhere about how/where Pythonista stores it's files, and any search for Pythonista+Dropbox yields results that have nothing to do with simply saving/syncing the source .py files. Neither the website nor iTunes mention saving/loading your scripts to/from Dropbox.
I don't want to spend $15 unless I know this is going to solve my problem, but OTOH I'm happy to support the developer if it will, even though I'd be spending double again what I've already spent :)