Open S1SYPHOS opened 4 years ago
I've been pondering the same question. I think the cleanest solution is a new library even though much of the code will be identical.
Just like with webp, there are several ways to convert. Vips and ImageMagick supports AVIF. So it makes sense to make a library like webp-convert, but for avif, which is what I intend to do: https://github.com/rosell-dk/avif-convert
Just been sidetracked, developing this new library: https://github.com/rosell-dk/htaccess-capability-tester
You're very productive, my friend, and I really admire what you have done since last we spoke!
I've been pondering the same question. I think the cleanest solution is a new library even though much of the code will be identical.
That's what why it should be incorporated, no? Like php-nextgen-images
(or whatever).
Maybe make all general purpose stuff (logging, read/write checks, ..) a separate package (like you did with the file type guesser) and make it a common dependency for both webp-convert
and avif-convert
?
Thanks :) A common dependency sounds right!
hi all!
good news everyone:
Still has to land on (shared) hosting servers, which should take a while - but that's great news indeed!
Thanks for letting us know!
Hey there, it's been a while since we last talked. I finished my studies and want to add AVIF support by including its Rust implementation - but is this really a job for
webp-convert
or a stand-alone library, what do you say?Cheers, S1SYPHOS