Prompt for text portion of new file name
Hi
I want to use AR to manage the import of photos from SD cards to replace lightroom doing this.
I normally use the format shotname_datetaken_timetaken for file names - I know I could type the shotname part into the method each time, but instead is there a way to have it prompt me for what this should be?
:-)
andy
I want to use AR to manage the import of photos from SD cards to replace lightroom doing this.
I normally use the format shotname_datetaken_timetaken for file names - I know I could type the shotname part into the method each time, but instead is there a way to have it prompt me for what this should be?
:-)
andy
Reply to #1:
This would be a nice feature. I also request it. :D
Or at least allow/get JavaScript's "prompt ()" function to work in a "Pre batch script". (But it probably shouldn't work in a normal, per file, script.)
This would be a nice feature. I also request it. :D
Or at least allow/get JavaScript's "prompt ()" function to work in a "Pre batch script". (But it probably shouldn't work in a normal, per file, script.)
Reply to #2:
Hi gents,
I've been thinking about this thread because I've long wished for a user input other than the F2 rename into the files list. Taking your last point first, Randy, I can foresee situations where prompt() could be useful in the main script--especially on shorter file lists ( or where a conditional were used to avoid prompting on many or most of the filenames). That could be extended to a Prompt method with an {if} clause to allow that same selectivity, or a <Prompt:promptString> tag that could be used in any applicable method that could include a similar {if} clause. The tag idea might not work, since you'd need some way to process a returned null value. Maybe another parameter in the tag, or maybe a modification of the {if} clause to handle the null value. Thoughts? Kim?
As an example of a way to use it, you could have, say, 3 folders that you want files placed into, but no way to programmatically distribute the files. Add a sequential number at the start of the folder name, then just prompt for the number you want to set the new path to. Minimum user interaction for maximum effect (and no real alternative in ARen currently, at least that I can think of).
If I had to guess why prompt() is not already included, I'd guess for security reasons, since I know that's very important to Kim. And it sounds like a heck of a lot of work for Kim, but what do I know? I assume that the current js engine includes hooks to the prompt() function, so that might be relatively easy to implement. Besides, I personally just sit back and wait for all that ARen goodness to transpire, so get to work Kim! :))
Best,
DF
Hi gents,
I've been thinking about this thread because I've long wished for a user input other than the F2 rename into the files list. Taking your last point first, Randy, I can foresee situations where prompt() could be useful in the main script--especially on shorter file lists ( or where a conditional were used to avoid prompting on many or most of the filenames). That could be extended to a Prompt method with an {if} clause to allow that same selectivity, or a <Prompt:promptString> tag that could be used in any applicable method that could include a similar {if} clause. The tag idea might not work, since you'd need some way to process a returned null value. Maybe another parameter in the tag, or maybe a modification of the {if} clause to handle the null value. Thoughts? Kim?
As an example of a way to use it, you could have, say, 3 folders that you want files placed into, but no way to programmatically distribute the files. Add a sequential number at the start of the folder name, then just prompt for the number you want to set the new path to. Minimum user interaction for maximum effect (and no real alternative in ARen currently, at least that I can think of).
If I had to guess why prompt() is not already included, I'd guess for security reasons, since I know that's very important to Kim. And it sounds like a heck of a lot of work for Kim, but what do I know? I assume that the current js engine includes hooks to the prompt() function, so that might be relatively easy to implement. Besides, I personally just sit back and wait for all that ARen goodness to transpire, so get to work Kim! :))
Best,
DF
Reply to #1:
I have had thoughts in that regard, but it always ends up being very complicated.
The idea is to setup a set of custom user defined tags, where the result can be a static text or a prompt that clears after each batch. It would be interpreted as tags, so it can also be used to make a shorthand for a longer tag based pattern.
But I have not yet figured out how the UI should work. There is not really a good place to configure batch wide options. The Name Collision Rule sits there in the middle of the toolbar, but is kinda out of place, and adding even more functionality might cause more harm than good for the average user.
I have had thoughts in that regard, but it always ends up being very complicated.
The idea is to setup a set of custom user defined tags, where the result can be a static text or a prompt that clears after each batch. It would be interpreted as tags, so it can also be used to make a shorthand for a longer tag based pattern.
But I have not yet figured out how the UI should work. There is not really a good place to configure batch wide options. The Name Collision Rule sits there in the middle of the toolbar, but is kinda out of place, and adding even more functionality might cause more harm than good for the average user.
Reply to #4:
It doesn't need to be in the toolbar. Just add a "Prompt" method that we can add to the Method list. But treat it as a once-per session and/or a button activated Method instead of a per-file method
Or just wire in JavaScript's prompt() function. **
Personally all I ever need is a once-per-session prompt to change the "Base" or "root" name for that set of files.
This seems to be what "Andy Smart" is asking for above, too.
No need to get fancy. But having any, non JS, prompt set a tag like <UserInput> does seem to be a good idea -- where <UserInput> would just be a string.
~~~~~
** Optionally, also allow JS to write the special tag "UserInput" with app.setTag(tagName, str), or somesuch.
It doesn't need to be in the toolbar. Just add a "Prompt" method that we can add to the Method list. But treat it as a once-per session and/or a button activated Method instead of a per-file method
Or just wire in JavaScript's prompt() function. **
Personally all I ever need is a once-per-session prompt to change the "Base" or "root" name for that set of files.
This seems to be what "Andy Smart" is asking for above, too.
No need to get fancy. But having any, non JS, prompt set a tag like <UserInput> does seem to be a good idea -- where <UserInput> would just be a string.
~~~~~
** Optionally, also allow JS to write the special tag "UserInput" with app.setTag(tagName, str), or somesuch.