Default scrips location

[tomczak]

I'm not sure how to simplify it. Some scripts are saved with files, but I'm building a library of generic processing scripts. I figured that I will store them in Scripts folder that made under Documents/PWP along with all other settings, for an easy backup. Then when I want to open a particular script from the library, and then an image to use it on, I have to keep fishing through folder structure on 2 different drives...

Unless I missed it, I can't figure out how to do that gracefully: go to Scripts folder when I want to open a script, and then get this script to go to default images folder for me to choose an image to use it on.

[den]

My current approach is to place folder shortcuts on the Desktop to Scripts and Workspace Scripts.

To open a script: click on the folder's link; select a script; and then drag-drop it on the PWP8 Desktop link.

PWP8 Desktop Links.jpg (12.32 KiB) Viewed 3665 times

Depending on the selected script, you still may have to browse for its start image.

...den...

[jsachs]

Scripts always start navigation in the folder you last opened an image from. I could probably add a setting to the File Open dialog box to set where you want to start.

[tomczak]

Cheers! That would be helpful.

A related question:

If the objective is to build a library of generic processing scripts that can be applied to an arbitrary image, is there a reason for saving them as Workspace Scripts as opposed to just Scripts?

Addendum:
Just before I posted it, I got myself at least one reason to save Workspaces rather than Scripts: I inadvertently overwrote a proper batch script with a faulty one (I saved the script while the Top image was current, not the last one, which saved the script just for this image, not the whole branch...).

So I thought I learned the lesson and wanted to be smarter. I build my batch processing branch, ending with JPG Export. I used 'Convert to Copy' to replace Open File with Copy and make it generic.

Then I made another branch consisting of File Open only, made the Input Image in 'Copy' of the first branch to be the file opened in the File Open of the second branch, and save the whole thing as a Workspace without Images.

When I closed the All Images and reopened the saved workplace, the Open Image of the second branch asked me to open the images (with an 's' at the end! I'm winning!)

Then I ran the batch off the Open File in the second branch, hoping that the subsequent images will enter the first branch via Copy on top of it and leave through Export at the bottom.

Pretty clever, isn't it?

This semi-elaborate setup kind of works, but stops at Export and asks me to save a strangely-versioned nameless file after processing each image...

Could you please look at it (attached) and tell me what I'm doing wrong. Maybe the idea is too complicated to begin with? All I wanted is to create a bunch of generic recipes that I could apply to any bunch of generic images and run that in batch...

p.s. The Board doesn't let me attach the .workspace or .zip file, so here is a link to it.

Off the press: I think I know why the workflow stops at the Export: it's the Original File Name that somehow doesn't get transferred from one branch to the other. If I change it to Rename files sequentially in Export the workflow goes!

[priort]

Cheers! That would be helpful.

A related question:

If the objective is to build a library of generic processing scripts that can be applied to an arbitrary image, is there a reason for saving them as Workspace Scripts as opposed to just Scripts?

So I am not sure exactly why this has to be so complex...but I must re read all your post I admit...so if you saved a script with no image names as your "preset" or "style" in effect why can you not simply open it and when asked for a file drag all the files you want to the file open transform to process the batch......you could likely set them to read only or keep a copy of the scripts somewhere if you are worried about overwriting them?? I admit I have to re read all your post to figure out what the issue is??

[priort]

Could you do this ..Jonathan said the file opens to the last directory so what if you place your scripts in the same folder as your photos in a folder called scripts. You create a symbolic link to that folder that uses a relation ship to the PW scripts directory so effectively PW thinks they are where it normally puts them. So now when you open them in PW as usual they will actually open from the pictures directory and you will already be there so just a matter of going to the right subfolder and opening your images....

[jsachs]

Yes, currently Export with original name only works if there is a File Open at the top of the branch.

I have fixed this however for the next release, so Copy will resolve back to the original pathname. There is a similar issue with File Save of a Copy which also gets fixed at the same time.

The difference between Script and Workspace scripts is that Scripts just save the subset of the current workspace that is needed to rebuild the current image. Workspace scripts save the entire workspace, potentially including multiple unrelated branches. Otherwise Scripts and Workspace Scripts are pretty much the same.

[tomczak]

Related: if the scenario is that I open an image first (File Open) then decide which of the saved scripts to use on it, would saving/opening script with Copy as a top-level and then pointing its Copy to the Opened File be the easiest way to do it?

[jsachs]

BTW, den - you can launch a script or workspace script by double-clicking on it in Explorer which is usually more convenient than dropping it on the PWP8 icon.

[jsachs]

Yes, that would be the easiest way.