You can use a Liferay Screens View to set a Screenlet’s look and feel independent of the Screenlet’s core functionality. Liferay’s Screenlets come with several Views, and more are being developed by Liferay and the community. The Screenlet reference documentation lists the Views available for each Screenlet included with Screens. This tutorial shows you how to use Views in Android Screenlets. It’s straightforward; you’ll master using Views in no time!
Before using Views, you should know what components make them up. Note that what follows is a simple description, sufficient for learning how to use different Views. For a detailed description of the View layer in Liferay Screens, see the tutorial Architecture of Liferay Screens for Android.
A View consists of the following items:
Screenlet class: A Java class that coordinates and implements the Screenlet’s functionality. The Screenlet class contains attributes for configuring the Screenlet’s behavior, a reference to the Screenlet’s View class, methods for invoking server operations, and more.
View class: A Java class that implements a View’s behavior. This class usually listens for the UI components’ events.
Layout: An XML file that defines a View’s UI components. The View class is usually this file’s root element. To use a View, you must specify its layout in the Screenlet XML (you’ll see an example of this shortly).
Note that because it contains a Screenlet class and a specific set of UI components, a View can only be used with one particular Screenlet. For example, the Default View for Login Screenlet can only be used with Login Screenlet. Multiple Views for several Screenlets can be combined into a View Set. A View Set typically implements a similar look and feel for several Screenlets. This lets an app use a View Set to present a cohesive look and feel. For example, the Bank of Westeros sample app uses the Westeros View Set’s Views with several Screenlets to present the red and white motif you can see here on Google Play. Liferay Screens for Android comes with the Default View Set, but Liferay makes additional View Sets, like Material and Westeros, available in jCenter. Anyone can create View Sets and publish them in public repositories like Maven Central and jCenter.
To install View Sets besides Default, add them as dependencies in your project.
build.gradle file code snippet below specifies the Material and Westeros
View Sets as dependencies:
Here are the View Sets that Liferay currently provides for Screens:
Default: Comes standard with a Screenlet. It’s used by a Screenlet if no layout ID is specified or if no View is found with the layout ID. The Default Views can be used as parent Views for your custom Views. Refer to the architecture tutorial for more details.
Westeros: Customizes the behavior and appearance of the Westeros Bank demo app.
Now that you know about Views and View Sets, you’re ready to put them to use!
To use a View in a Screenlet, specify the View’s layout as the
liferay:layoutId attribute’s value when inserting the Screenlet XML in an
activity or fragment layout. For example, to use Login Screenlet with its
Material View, insert the Screenlet’s XML with
liferay:layoutId set to
The following links list the View layouts available in each View Set:
If the View you want to use is part of a View Set, your app or activity’s theme
must also inherit the theme that defines that View Set’s styles. For example,
the following code in an app’s
AppTheme.NoActionBar to use the Material View Set as its parent theme:
<style name="AppTheme.NoActionBar" parent="material_theme">
To use the Default or Westeros View Set, inherit
That’s it! Great! Now you know how to use Views to spruce up your Android Screenlets. This opens up a world of possibilities, like writing your own Views.