Progressive Previews
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Hi, I was told to file this here. Github Preview Generator
I have gotten a lot better performance by just making the Previews progressive. I am guessing this would be far easier to implement into the code than me doing it manually.
I use jpegoptim, and its nothing more than adding the --all-progressive parameter, though when doing it later, compression needs to be higher than currently. This would likely only bring advantages when pre-generating Previews.
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Github Preview Generator discussion and determine whether preview encoding is handled in nextcloud/server or that separate project. Inspect the existing pre-generation path and jpegoptim integration, then verify that the requested progressive JPEG behavior and compression changes are covered by appropriate tests or reproducible performance checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100