Feature 5516 #533
Merged
Feature 5516 #533
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d in the filesystem is now performed through the SilverpeasFile and SilverpeasFileFactory classes. SilverpeasFile represents now a file in Silverpeas whereas SilverpeasFileFactory wraps the way to access them according to some business rules (attachment, file serving, ...). These new classes are now used by the following servlets: FileServer and any subclasses of AbstractFileSender class
…r. SilverpeasFileProvider supports now pre and post processing when fetching a file in silverpeas. The pre processors are executed against the file path whereas the post processors are executed against the retrieved file itself. To processors are defined: one to resize an image from its path and another one to check the existance of the asked file. The image resizing processor resizes an image if the asked file is an image and its path contains as information the targeted size (for example: a path such as /display/avatar/108x140/myavatar.jpg).
…account size parameter. This size parameter is then taken at service side to resize dynamically the image if not already done. Update the JSPs to take into account this new tag when rendering the avatar. The image displayer of a XML form uses the new functionality of the dynamic resizing of images.
…e users' avatar, for the image in a XML form
… the original image is also updated. No deletion occurs currently in the cache.
…ng by its height only.
…to manage files in Silverpeas. It provides currently methods to write, to delete and to move a file. This new API is yet used by ImageProfil (it manages the avatar) and ThumbnailController (it manages the vignettes and thumbnails of some contributions like the publications). ImageResizingProcessor that is hooked to SilverpeasFileProvider takes advantage of this to manages the cache of resized images when their original image is either deleted or updated. Beside that, a ResizedImageCleaner is introduced to clean up resized images of non existing original images; it is scheduled by a cron instruction in the org.silverpeas.lookAndFeel.generalLook.properties bundle.
…ocument#file to SimpleDocument#attachment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Code a system of image resizing on-demand. The images are resized at the asked size if not already done and save the result into a cache.
For doing, a two stages system is coded:
For instance, only the users' avatar and the images in an XML form are taken in charge by the dynamic image resizing.