Feature request: optimized watermark process

[DesMas]

Hello Peter

examining the gallery features, especially the watermark process, let me raise an idea.

As of now, adding pictures to an existing gallery causes the watermark-process to rebuild the watermarks for all pictures.

This may lead into timing problems on galleries with a large amount of picture.

Therefore I would suggest:

1. by adding new pictures to an existing gallery, the process should only generate the watermarks of the newly added pictures.

2. all watermarks will be only rebuild, when the watermark setting for the gallery changes.

For shared hosters I woulds suggest another approach for creating thumbnails and watermarks:

1. uploading the files as usual to the upload directory

2. present an page in back-end with the uploaded files

3. from there iterate via JS over the list of images an use an asynchronous JS call to a special back-end function with the ID of each image. This function then creates the thumbnails and watermarked image for the ID given. This should result in many short-time calls to the server and prevent the problem of exhausted memory or PHP script runtime.

[Peter]

Hi DesMas,

Thanks for your suggestions and ideas – much appreciated.

As you will appreciate, adding changes and new functionality takes time and requires care so that existing functionality does not break or new bugs are introduced. Hence implementing this functionality in the short term may not be possible due to my tough schedule but I will put your suggestions on my longer-term “todo” list.

[Author]

Posts