Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convention for specifying defaults #63

Open
iJungleboy opened this issue Jan 15, 2025 · 1 comment
Open

Convention for specifying defaults #63

iJungleboy opened this issue Jan 15, 2025 · 1 comment

Comments

@iJungleboy
Copy link

Background

We have ImageFlow bundled in 2sxc, a CMS plugin for DNN and Oqtane.

Someone now suggested some changes to set default formats (e.g. auto-switch to webp if supported by the browser). This is of course an interesting idea, irrelevant of the fact that it also has downsides.

But before I pursue this further, I want to be sure we don't create our own conventions for things which are already supported somehow.

The real question

Is there a convention or something to specify configurations, specifically "defaults" for ImageFlow somewhere? Possibly in the web.config or something?

@lilith
Copy link
Member

lilith commented Jan 24, 2025

Imageflow.Server (via .AddCommandDefault("down.colorspace", "srgb")) and ImageResizer 4 and 5 (via web.config `) offer querystring defaults. It's also not hard to change those defaults in either via an event handler that looks at the accept header. Not yet a built-in feature, though. Imageflow does auto-select whether to use lossy or lossless based on the source format (png/jpeg) however.

I'm considering adding new commands to the RIAPI syntax that might be relevant: imazen/imageflow#629

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants