HowTo: Run arbitrary backend scripts in recipes
The weakest part of C1 is the I/O section, not only is it quite idiosyncratic, it is also hobbled by only allowing Apps as external commands, but no other executables or scripts, making it even harder to work around the limitations of the recipes.
So if you for example want to run a script that moves files programmatically or adds parametric watermarks, you’re stuck.
Thanks to a nifty little App called Platypus (http://www.sveinbjorn.org/platypus), this can be fixed.
It can generate standard Mac Apps from scripts. It converts the drag and drop mechanism used by
C1 to provide the full path name of the image to a command line parameter for the script.
Once the App has been generated and put in /Applications it can be selected in C1 for “Open Withâ€.
So if you need to run ImageMagick based scripts or want to move files to parallel paths it can be done with this little helper.
cheers
afx
So if you for example want to run a script that moves files programmatically or adds parametric watermarks, you’re stuck.
Thanks to a nifty little App called Platypus (http://www.sveinbjorn.org/platypus), this can be fixed.
It can generate standard Mac Apps from scripts. It converts the drag and drop mechanism used by
C1 to provide the full path name of the image to a command line parameter for the script.
Once the App has been generated and put in /Applications it can be selected in C1 for “Open Withâ€.
So if you need to run ImageMagick based scripts or want to move files to parallel paths it can be done with this little helper.
cheers
afx
0
Post is closed for comments.
Comments
0 comments