Technically nothing's really impossible: it's more of a spectrum from
trivial to extremely difficult.
That said, having the server cache different sizes of the same image in the
cache is on the not easy side of things. Even if you pick one size for
covers when you run the app and never change it again, there's still
multiple places where that image is shown that'll be cached at different
sizes (the cover size only applies to the library view). It will make the
app extremely slow since now the browser is going to perform a round trip
to the server for every single image rather than letting the browser scale
the image locally. Not to mention the time spent actually performing the
scaling, which may be small but now has to be multiplied by every single
image when retrieved.
Not to mention, we will actually going to end up using more disk space by
caching different sizes of the same image.
I honestly think it's an interesting idea, but the execution of it's not
going to provide the desired benefit. Remember the feature pyramid: you can
have the app be fast, small or efficient (with resources like disk space).
You only get to pick two. ;)
On Mon, Jun 29, 2020 at 7:03 PM bareheiny <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
Neither - I’m referring to the images CX extracts for thumbnails (the file
hash is used for the path and file name) - stored in \.covers\
Since there was no “not technically possible” response, I’ll assume it’s
possible and create a detailed feature request once I get my Surface up and
running again.
On 29/06/2020, at 23:52, Darryl L. Pierce <mcpierce@xxxxxxxxx> wrote:
Do you mean during import or conversion? Personally, I'd say we shouldn't
(for now at least) change the images within the archives, which is why
we've not done any image conversion coding yet. If someone wants to adjust
the size of their comics' pages, they can do that outside of the app and
then tell CX to rescan the library to update the database.
On Sun, Jun 28, 2020 at 6:45 PM bareheiny <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
I’ve been thinking about this for a bit (in fact I’ve did this outside of
CX before I migrated my collection to webp) - but is it worth considering
resizing images as CX extracts them?
For covers, the max size could be set to whatever the max slider size is.
Potentially that could save a bit of disk space.
--
Darryl L. Pierce <mcpierce@xxxxxxxxx>
"Le centre du monde est partout." - Blaise Pascal
"Let's try and find some point of transcendence and leap together." - Gord
Downie
