rb0022

@joz-k A sensible design decision, as some alterations to color or filters may be desired. However in my situation it was just bloat of the same image in a different...

@joz-k Re. 1/2, I agree a change to operator names causes temporary pain for sanity in the long term. Formatting the directory structure and naming are separate to the file...

@joz-k Can we please return to the above suggestions? #### Improve operator names for long-term user clarity _This is a sidebar, we can create another GH Issue for tracking this_...

Appended to list, the flag mentioned in #17

@joz-k can we please continue the above discussion? I appreciate your preference to have `--operator-names-that-are-easy value_goes_here` or `--simple-boolean-turn-on-operator-names`, but as above shows (and other GH Issues) there are too many...

@joz-k any time to continue this discussion? Really I would love to just add a PR myself to the project..... but Perl is a lang I'm honestly just not willing...

@joz-k Unless that is the solution? `--expert-export-flags [optional,flags,separated]` for an "expert mode" that overrides the regular functionality? This would allow existing functionality to remain, while extending for those users who...

@TheBeardofKnowledge Everyone has different use cases🙂 The point is to allow an arg to amend this for a speedier build, took nearly over 20mins for me _(wasn't paying attention to...

Used the file from the `main` branch, used the args but was then prompted anyway. The prompts should just handle the custom paths in my opinion.

If I recall correctly, something like `.\tiny11maker.ps1 -ISO test.iso -SCRATCH D`