- Xcode 9.3 or above
- iOS 11 SDK
- Liferay Portal 6.2 CE/EE, Liferay CE Portal 7.0/7.1, Liferay DXP 7.0+
- Liferay Screens Compatibility app (CE or EE/DXP). This app is preinstalled in Liferay CE Portal 7.0/7.1 and Liferay DXP 7.0+.
- iOS 9 and above
- Visual Studio 7.2
- Mono .NET framework 22.214.171.124
Web Content List Screenlet can show lists of web content from a Liferay instance. It can show both basic and structured web content. The Screenlet also implements fluent pagination with configurable page size, and supports i18n in asset values.
JSON Services Used
Screenlets in Liferay Screens call JSON web services in the portal. This Screenlet calls the following services and methods.
The Default Theme uses a standard
UITableView to show the scrollable list.
Other Themes may use a different component, such as
others, to show the contents.
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 list 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 list, it stores the data 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 list from the local cache. If the list 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 list from the Liferay instance. If this succeeds, the Screenlet shows the list to the user and stores it in the local cache for later use. If a connection issue occurs, the Screenlet retrieves the list from the local cache. If the list 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 list from the local cache. If the list 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.|
|The ID of the site (group) where the web content exists. If set to |
|The ID of the web content folder. If set to |
|The offline mode setting. The default value is |
|Whether the list loads automatically when the Screenlet appears in the app’s UI. The default value is |
|Whether a standard iOS |
|The number of items to display on the first page. The default value is |
|The number of items to display on the second and subsequent pages. The default value is |
|The name of the |
|Starts the request to load the web content list. This list is shown when the response is received. Returns |
Web Content List Screenlet delegates some events to an object that conforms to
WebContentListScreenletDelegate protocol. This protocol lets you implement
the following methods:
- screenlet:onWebContentListResponse:: Called when a page of contents is received. Note that this method may be called more than once: one call for each page received.
- screenlet:onWebContentListError:: Called when an error occurs in the process. The
NSErrorobject describes the error.
- screenlet:onWebContentSelected:: Called when an item in the list is selected.