You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Messages with images are currently a bit hard to understand. Downloading images would be nice, but I see two problems with it:
How are the images included in the jinja template
What size image do we download
Since the jinja template is not paginated, including all the images at once would probably overwhelm the browser for at least some users. However, having links out to the images means people would rarely see them. Pagination is a whole separate issue (literally). The compromise I'd expect to arrive it is having a "click to show" link which runs some JS to fetch images from the archive. Maybe better would be having all images at fixed size and fetching them as the image enters the browser view.
The image size is important because, over the course of a 5-year workspace, there are several gigabytes of images and files. Some people may not want their archive to be that large. Too small an image and we risk just having hard-to-understand junk polluting the archive.
The text was updated successfully, but these errors were encountered:
Messages with images are currently a bit hard to understand. Downloading images would be nice, but I see two problems with it:
Since the jinja template is not paginated, including all the images at once would probably overwhelm the browser for at least some users. However, having links out to the images means people would rarely see them. Pagination is a whole separate issue (literally). The compromise I'd expect to arrive it is having a "click to show" link which runs some JS to fetch images from the archive. Maybe better would be having all images at fixed size and fetching them as the image enters the browser view.
The image size is important because, over the course of a 5-year workspace, there are several gigabytes of images and files. Some people may not want their archive to be that large. Too small an image and we risk just having hard-to-understand junk polluting the archive.
The text was updated successfully, but these errors were encountered: