Feature request: Predefined Parameter sets

[technician77]

I just though of the idea of predefined parameter sets. What do you think of it?

For example you call rotate but instead of entering a value you press a key and then you can select some default sets like +90,+180 and so forth.

Maybe it is possible to combine the predefined sets and the normal parameter entry in one level, so you don't need to press a key to get the predefined sets but I don't know if that is possible.

I assume there are sites on the internet that already have tons of usefull parameter sets that just need to be added.

[walseb]

I tried messing around with this before with the geometry parameter because it's so confusing but the problem is that a lot of people can't avoid selecting the autocompletion if their input almost matches a candidate. So for example if i wrote +90 as a selectable default, and the user tried to type +9 and pressed enter, he would get a +90 rotation. There are solutions for this in ivy (and helm) where you can press C-p to select the input instead of any matching candidate but I don't think many has this enabled. I also think this would generate a lot of code since there are hundreds of commands in imagemagick. And if the user really wanted to quickly rotate images 90 degrees, then there are instructions in the readme on how to bind commands with already filled in parameters.

[technician77]

Well, if that is a problem how about creating new major commands that only allow selectable candidates?
I took the rotatation as a simple example. The idea would be to have quickly some nice default operations at hand. I thought it might make sense to have these candidates of parameters in some extra file so it can be extended without adding more functions. I have read the instructions but the idea was to have some clean, easyly extendable batteries included approach.

[walseb]

eimp.el has some of this functionality, but for a more complete solution a hydra interface with common commands could be added in a separate file or something like that. I'm accepting PRs of this kind but I'm probably not going to work on it myself.

[technician77]

I'm not very fond of hydras. I experience them as disruptive in the workflow. I think simple hirachical lists that can be narrowed down would be more fitting in regards scalability and extensibilty. To me the eimp inbuilt functions are like the examples in the your readme - they put everything in one level and add their own nameing scheme. The idea was to orientate the selections hirachical based on the IM operations, just like blimp does now, just with predefined selections instead of own parameters input. In that way it preserves the feeling of using IM natively and not some wrapper.

Well, maybe the idea has not enough usage value for the effort needed to realize it. I would hope that someone picks up the idea, but it seems that image manipulation using emacs is not quite popular yet, so it probably will stay this way for a longer time.