Displays a gallery of images. Consists of an overview that shows thumbnails of all images optionally separated into groups. Each image may be viewed in fullscreen by clicking on it.
Displaying large images will result in a slow component and a bad user experience. Thumbnails should be no larger than 160x160 pixels. Make sure to use the Image Process component to rescale both the fullsize image and thumbnail if they may be uploaded by users.
The component consists of two views. An optional overview and a fullscreen view. If the overview is omitted, the fullscreen view is displayed directly upon navigating to the component.
Images in the overview can have a caption and a shorter description. Clicking on an image opens it in the fullscreen view.
Each image may have a checkbox and/or image links and these will be shown when hovering the image. The links may be disabled with a tooltip or hidden for certain images.
The buttons above the image are the same links as in the overview. The fullscreen view can be navigated by clicking on the arrows or selecting an image from the slider below the image. To exit the fullscreen view, press the close button in the top right corner.
The fullscreen view may contain a longer description for each image and show extra information as key value pairs as seen above.
Possible value | Description |
---|---|
Pad | The entire thumbnail will be shown with extra padding to keep the aspect ratio. |
Crop | No padding will be used and instead parts of the thumbnail may be cropped to keep the aspect ratio. |
Retrieves info about all images and groups that should be shown in the gallery.
Optional groups to categorize images with.
Id of the group.
Label of the group.
Info regarding all images to be displayed.
Id of the image.
The group that the image belongs to. Mandatory if groups are used.
The image's caption.
Description to be displayed in the overview.
All other columns will be used as passing fields for the image.
Retrieves thumbnails to be displayed. Will be called lazily as thumbnails are shown on screen. Using large images as thumbnails will result in a slower menu item, the recommended thumbnail size is 160x160 px. This call will receive a temporary table with the image ids for which the thumbnails should be displayed.
CREATE TABLE #ImageId
(
ImageId varchar(max) NOT NULL
)
Id of the image that the thumbnail belongs to. Must map to an id in the temp table.
Alt text for the thumbnail.
MIME type of the thumbnail. Mandatory if ImageData is used.
Url to the thumbnail image. One of this and ImageData must be used.
Binary data of the thumbnail. May not be larger than 500kB. One of this and ImageUrl must be used.
Retrieves the full images to be displayed. Will be called lazily as images are shown on screen. This call will receive a temporary table with the image ids for which the images should be displayed.
CREATE TABLE #ImageId
(
ImageId varchar(max) NOT NULL
)
Id of the image that the data belongs to. Must map to an id in the temp table.
Alt text for the image.
MIME type of the image. Mandatory if ImageData is used.
Url to the image. One of this and ImageData must be used.
Optional longer description to be displayed when viewing the image in fullscreen. If the description is in a key-value format, consider using image extra info.
Binary data of the image. May not be larger than 50MB. One of this and ImageUrl must be used.
Key value pairs of headings and content to be displayed next to the image in fullscreen.
Id of the image to display the information for. Must map to an id in the temp table.
The heading of the field.
The content of the field.
Allows you to validate the SQL parameters before any other SQL is run in the component. This call is only made if the SQL is a stored procedure and Validate parameters is checked.
Use this call to restrict which entries a user is allowed to view and edit, and to log which entries a user views.
Access to a menu item is normally controlled through functions and roles alone but some entities need more fine grained control. For example, a user may have access to the View Member menu item for normal members but not for members with a protected identity.
The menu items a user visits are always logged (in ADMINLogMenuItem) but for sensitive data you may need to log exactly what entries are viewed. Do the logging in this call as the common ways of viewing data (grid and InfoSQL) are not allowed to modify the database.
If you bind a scalar function instead of a stored procedure to this call then its name must end with '_GrantAccess'.