- Xcode 9.0
- iOS 11 SDK
- Liferay Portal 6.2 (CE or EE), Liferay 7.0 CE, Liferay DXP
- Liferay Screens Compatibility plugin (for Liferay Portal CE or Liferay Portal EE).
- iOS 9 and above
- Visual Studio 7.2
- Mono .NET framework 18.104.22.168
Gallery Screenlet shows a list of images from a Documents and Media folder in a Liferay instance. You can also use Gallery Screenlet to upload images to and delete images from the same folder. The Screenlet implements fluent pagination with configurable page size, and supports i18n in asset values.
Screenlets in Liferay Screens call JSON web services in the portal. This Screenlet calls the following services and methods.
The default Theme uses
to show an asset’s rating. Other custom Themes may use a different component,
UIButton or others, to show the items.
This screenlet has four different Themes:
- Thumbs (default)
This Screenlet supports offline mode so it can function without a network connection. For more information on how offline mode works, see the tutorial on its architecture. Here are the offline mode policies that you can use with this Screenlet:
|Policy||What happens||When to use|
|The Screenlet loads the data from the Liferay instance. If a connection issue occurs, the Screenlet uses the delegate to notify the developer about the error. If the Screenlet successfully loads the data, it stores it in the local cache for later use.||Use this policy when you always need to show updated data, and show nothing when there’s no connection.|
|The Screenlet loads the data from the local cache. If the data isn’t there, the Screenlet uses the delegate to notify the developer about the error.||Use this policy when you always need to show local data, without retrieving remote information under any circumstance.|
|The Screenlet loads the data from the Liferay instance. If this succeeds, the Screenlet shows the data to the user and stores it in the local cache for later use. If a connection issue occurs, the Screenlet retrieves the data from the local cache. If the data doesn’t exist there, the Screenlet uses the delegate to notify the developer about the error.||Use this policy to show the most recent version of the data when connected, but show a possibly outdated version when there’s no connection.|
|The Screenlet loads the data from the local cache. If the data isn’t there, the Screenlet requests it from the Liferay instance and notifies the developer about any errors that occur (including connectivity errors).||Use this policy to save bandwidth and loading time in case you have local (but possibly outdated) data.|
If you don’t use
entryId, you must use these attributes:
|The ID of the layout to use to show the Theme.|
|Whether the rating loads automatically when the Screenlet appears in the app’s UI. The default value is |
|Whether the user can change the rating.|
|The primary key of the asset with the rating to display.|
|The asset’s fully qualified class name. For example, a blog entry’s |
|The asset’s unique identifier. Only use this attribute when also using |
|The ID of the site (group) containing the asset.|
|The offline mode setting. See the Offline section for details.|
|Starts the request to load the asset’s ratings.|
Rating Screenlet delegates some events to an object that conforms to
RatingScreenletDelegate protocol. This protocol lets you implement
the following methods:
- screenlet:onRatingRetrieve:: Called when the ratings are received.
- screenlet:onRatingDeleted:: Called when a rating is deleted.
- screenlet:onRatingUpdated:: Called when a rating is updated.
- screenlet:onRatingError:: Called when an error occurs in the process. The
NSErrorobject describes the error.