#7496 closed feature request (wontfix)
Plugin architecture for scalers
| Reported by: | SF/mbandsmer | Owned by: | fingolfin |
|---|---|---|---|
| Priority: | low | Component: | Graphics: Scalers |
| Version: | Keywords: | ||
| Cc: | Game: |
Description
I've noticed that requests for new scalers are currently being rejected due to reasons like "We already have too many scalers" and "That would bloat the code".
I propose that to resolve these issues and still support good new scalers, ScummVM adopt a plugin architecture for scalers, i.e. use .dll's for Windows and .so's for Linux, etc, that implement a given scaler according to a common interface.
The default version of ScummVM could then be stripped down to a minimal set of scalers, thereby reducing code bloat, and users who want additional scalers, e.g. HQ4x, 2xPM, etc, could download whatever extra scaler libraries they want. ScummVM would then load these scaler libraries at run-time. (I envision the user having to hand-edit a config file to specify which new scalers to load, and how they are assigned to Ctrl-Alt-# hot-keys.)
This way we could support a potentially large number of scalers without code bloat and without the ScummVM development team having to evaluate each new scaler request. And anyone could compile their favorite scaler into a new library and offer it for download to everyone else.
Ticket imported from: #1503724. Ticket imported from: feature-requests/312.
Change History (6)
comment:1 by , 18 years ago
| Priority: | normal → low |
|---|
comment:2 by , 18 years ago
comment:3 by , 18 years ago
Would such a feature be rejected if I were to implement and submit this feature? (If it would be rejected anyway, I won't bother doing it.)
comment:4 by , 18 years ago
Yes, it would most likely be rejected. However, we might review our scaler set in the not-so-distant future. If you have specific scalers you would like to see added, file sensible feature requests for them... as long as you state why that scaler might offer a benefit over existing scalers, I'll leave those requests open (albeit at a low priority), for future reference.
comment:5 by , 18 years ago
| Owner: | set to |
|---|---|
| Resolution: | → wontfix |
| Status: | new → closed |
comment:6 by , 6 years ago
| Component: | → Graphics: Scalers |
|---|
That would bloat the code even more. Bloat is not just about size, it's also about complicating the code with (mis)features that have little use to most users.
Hence, I'm for rejecting this FR.