[Feature Request] File renaming

[jghaanstra]

This feature request might be way out of scope of the intended purpose of this app but it would benefit my use case. If out of scope, feel free to close this feature request.

What I would like is renaming the output files based on some basic parameters:

• Prefix
• Suffix
• Insert (after x characters)
• Replace
• Serialize (add 1 or 01 as prefix and count upwards for each file)

[civilblur]

I like the idea, and while this might be a little bit out of scope, the primary friction would be how to create a simple UX that works holistically with the concept of "simple image optimizer".

I'll give some more thoughts into this.

[jghaanstra]

I have added this functionality in a fork for anyone that is interested.

Have you given it any thought if you are willing to integrate this into Mazanoke @civilblur ? If so I can submit this as a PR. You could even decide it to be optional using a .env variable.

[civilblur]

@jghaanstra Thanks for sharing your solution! The options available in your fork is similar to some of the things I've been considering to include. The current blocker at the moment isn't the feature set however, but the UX.

So far, I've primarily been focusing on the user flow, which is something I want to try to get right before introducing anything.

The list below consists of some of the things I've been considering, feel free and share your feedback or ideas:

• Provide the ability to batch rename.
  • Either before upload or after, but ideally not both, as I want to provide a straightforward user flow.
  • At the moment, I've found that renaming after upload might be the most straightforward approach if I had to choose one of them.
    • E.g. ability to rename just one image, or bulk select using checkboxes to rename multiple images.
    • This pattern can also be reused for deleting/zipping/and other batch-related actions.
    • Placing the rename option after upload reduces the friction of getting started as well.
  • The ability to rename before upload could as you mentioned, be hidden as an environmental variable. I need to however finalize the default user flow before being able to fully make sense of it holistically.
• Here are other features not included in your fork that I've been considering. Please note that it doesn't mean that these are planned, but simply the things I've taken account for during my thought process.
  • Macro
  • Date insert
  • Regex

[jghaanstra]

The functionality in my fork is solely aimed at my own use case. I did not take usability in consideration, I primarily needed working functionality before my summer vacation starts. :-)

I took the easiest approach for this implementation matching the current user flow for compression. You set the options up front and then do a conversion, be it a single file or batch of files. The actual renaming of these files takes places after compression though.

Having a more elaborate implementation where you can do post-compression actions among renaming would probably be a more flexible implementation as you indeed could select target files, implement other post-compression actions etc.. And yes, more complex renaming options can easily be added as well to any type of renaming implementation but I (currently) do not need those myself.

Hope to see similar functionality added in the future of Mazanoke!

[civilblur]

I will look further into this once I find time to spare, thanks for sharing your fork and ideas!