Creating Android List Screenlets

It’s very common for mobile apps to display lists. Liferay Screens lets you display asset lists and DDL lists in your Android app by using Asset List Screenlet and DDL List Screenlet, respectively. Screens also includes list Screenlets for displaying lists of other Liferay entities like web content articles, images, and more. The Screenlet reference documentation lists all the Screenlets included with Liferay Screens. If there’s not a list Screenlet for the entity you want to display in a list, you must create your own. A list Screenlet can display any entity from a Liferay instance. For example, you can create a list Screenlet that displays standard Liferay entities like User, or custom entities from custom Liferay apps.

This tutorial uses code from the sample Bookmark List Screenlet to show you how to create your own list Screenlet. This Screenlet displays a list of bookmarks from Liferay’s Bookmarks portlet. You can find this Screenlet’s complete code here in GitHub.

Note that because this tutorial focuses on creating a list Screenlet, it doesn’t explain general Screenlet concepts and components. Before beginning, you should therefore read the following tutorials:

You’ll create the list Screenlet by following these steps:

  1. Creating the Model Class
  2. Creating the View
  3. Creating the Interactor
  4. Creating the Screenlet Class

First though, you should understand how pagination works with list Screenlets.

To ensure that users can scroll smoothly through large lists of items, list Screenlets support fluent pagination. Support for this is built into the list Screenlet framework. You’ll see this as you construct your list Screenlet.

Now you’re ready to begin!

Creating the Model Class

Entities come back from Liferay in JSON. To work with these results efficiently in your app, you must convert them to model objects that represent the entity in Liferay. Although Screens’s BaseListInteractor transforms the JSON entities into Map objects for you, you still must convert these into proper entity objects for use in your app. You’ll do this via a model class.

For example, Bookmark List Screenlet’s model class (Bookmark) creates Bookmark objects that contain a bookmark’s URL and other data. To ensure quick access to the URL, the constructor that takes a Map<String, Object> extracts it from the Map and sets it to the url variable. To allow access to any other data, the same constructor sets the entire Map to the values variable. Besides the getters and setter, the rest of this class implements Android’s Parcelable interface:

import android.os.Parcel;
import android.os.Parcelable;

import java.util.Map;

public class Bookmark implements Parcelable {

    private String url;
    private Map values;

    public static final Creator<Bookmark> CREATOR = new Creator<Bookmark>() {
        @Override
        public Bookmark createFromParcel(Parcel in) {
            return new Bookmark(in);
        }

        @Override
        public Bookmark[] newArray(int size) {
            return new Bookmark[size];
        }
    };

    public Bookmark() {
        super();
    }

    protected Bookmark(Parcel in) {
        url = in.readString();
    }

    public Bookmark(Map<String, Object> stringObjectMap) {
        url = (String) stringObjectMap.get("url");
        values = stringObjectMap;
    }

    @Override
    public void writeToParcel(Parcel dest, int flags) {
        dest.writeString(url);
    }

    @Override
    public int describeContents() {
        return 0;
    }

    public String getUrl() {
        return url;
    }

    public Map getValues() {
        return values;
    }

    public void setValues(Map values) {
        this.values = values;
    }

}

Now that you have your model class, you can create your Screenlet’s View.

Creating the Screenlet’s View

Recall from the basic Screenlet creation tutorial that a View defines a Screenlet’s UI. To accommodate its list, a list Screenlet’s View is constructed a bit differently than that of a non-list Screenlet. To create a List Screenlet’s View, you’ll create the following components:

  1. Row Layout: the layout for each list row.
  2. Adapter Class: an Android adapter class that populates each list row with data.
  3. View Class: the class that controls the View. This class serves the same purpose in list Screenlets as it does in non-list Screenlets.
  4. Main Layout: the layout for the list as a whole. Note this is different from the row layout, which defines the UI for individual rows.

First, you’ll create the row layout.

Creating the Row Layout

Before constructing the rest of the View, you should first define the layout to use for each row in the list. For example, Bookmark List Screenlet needs to display a bookmark in each row. Its row layout (res/layout/bookmark_row.xml) is therefore a LinearLayout containing a single TextView that displays the bookmark’s URL:

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="match_parent"
    android:layout_height="wrap_content"
    android:orientation="vertical">

    <TextView
        android:id="@+id/bookmark_url"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"/>

</LinearLayout>

As you can see, this example is very simple. Row layouts, however, can be as simple or complex as you need them to be to display your content.

Next, you’ll create the adapter class.

Creating the Adapter Class

Android adapters fill a layout with content. In the example Bookmark List Screenlet, the layout is the row layout (bookmark_row.xml) and the content is each list item (a URL). To make list scrolling smooth, the adapter class should use an Android view holder. To make this easier, you can extend the list Screenlet framework’s BaseListAdapter class with your model class and view holder as type arguments. By extending BaseListAdapter, your adapter needs only two methods:

  • createViewHolder: instantiates the view holder
  • fillHolder: fills in the view holder for each row

Your view holder should also contain variables for any data each row needs to display. The view holder must assign these variables to the corresponding row layout elements, and set the appropriate data to them.

For example, Bookmark List Screenlet’s adapter class (BookmarkAdapter) extends BaseListAdapter with Bookmark and BookmarkAdapter.BookmarkViewHolder as type arguments. This class’s view holder is an inner class that extends BaseListAdapter’s view holder. Since Bookmark List Screenlet only needs to display a URL in each row, the view holder only needs one variable: url. The view holder’s constructor assigns the TextView from bookmark_row.xml to this variable. The bind method then sets the bookmark’s URL as the TextView’s text. The other methods in BookmarkAdapter leverage the view holder. The createViewHolder method instantiates BookmarkViewHolder. The fillHolder method calls the view holder’s bind method to set the bookmark’s URL as the url variable’s text:

public class BookmarkAdapter extends BaseListAdapter<Bookmark, BookmarkAdapter.BookmarkViewHolder> {

    public BookmarkAdapter(int layoutId, int progressLayoutId, BaseListAdapterListener listener) {
        super(layoutId, progressLayoutId, listener);
    }

    @NonNull
    @Override
    public BookmarkViewHolder createViewHolder(View view, BaseListAdapterListener listener) {
        return new BookmarkAdapter.BookmarkViewHolder(view, listener);
    }

    @Override
    protected void fillHolder(Bookmark entry, BookmarkViewHolder holder) {
        holder.bind(entry);
    }

    public class BookmarkViewHolder extends BaseListAdapter.ViewHolder {

        private final TextView url;

        public BookmarkViewHolder(View view, BaseListAdapterListener listener) {
            super(view, listener);

            url = (TextView) view.findViewById(R.id.bookmark_url);
        }

        public void bind(Bookmark entry) {
            url.setText(entry.getUrl());
        }
    }
}

Great! Your adapter class is finished. Next, you’ll create the View class.

Creating the View Class

Now that your adapter exists, you can create your list Screenlet’s View class. Recall from the basic Screenlet creation tutorial that the View class is the central hub of any Screenlet’s UI. It renders the UI, handles user interactions, and communicates with the Screenlet class. The list Screenlet framework provides most of this functionality for you via the BaseListScreenletView class. Your View class must extend this class to provide your row layout ID and an instance of your adapter. You’ll do this by overriding BaseListScreenletView’s getItemLayoutId and createListAdapter methods. Note that in many cases this is the only custom functionality your View class needs. If it needs more, you can provide it by creating new methods or overriding other BaseListScreenletView methods.

Create your View class by extending BaseListScreenletView with your model class, view holder, and adapter as type arguments. This is required for your View class to represent your model objects in a view holder, inside an adapter. For example, Bookmark List Screenlet’s View class (BookmarkListView) must represent Bookmark instances in a BookmarkViewHolder inside a BookmarkAdapter. The BookmarkListView class must therefore extend BaseListScreenletView parameterized with Bookmark, BookmarkAdapter.BookmarkViewHolder, and BookmarkAdapter. Besides overriding createListAdapter to return a BookmarkAdapter instance, the only other functionality that this View class needs to support is to get the layout for each row in the list. The overridden getItemLayoutId method does this by returning the row layout bookmark_row:

import android.content.Context;
import android.util.AttributeSet;

import com.liferay.mobile.screens.base.list.BaseListScreenletView;

public class BookmarkListView
    extends BaseListScreenletView<Bookmark, BookmarkAdapter.BookmarkViewHolder, BookmarkAdapter> {

    public BookmarkListView(Context context) {
        super(context);
    }

    public BookmarkListView(Context context, AttributeSet attributes) {
        super(context, attributes);
    }

    public BookmarkListView(Context context, AttributeSet attributes, int defaultStyle) {
        super(context, attributes, defaultStyle);
    }

    @Override
    protected BookmarkAdapter createListAdapter(int itemLayoutId, int itemProgressLayoutId) {
        return new BookmarkAdapter(itemLayoutId, itemProgressLayoutId, this);
    }

    @Override
    protected int getItemLayoutId() {
        return R.layout.bookmark_row;
    }
}

Next, you’ll create your View’s main layout.

Creating the View’s Main Layout

Although you already created a layout for your list rows, you must still create a layout to define the list as a whole. This layout must contain:

  • The View class’s fully qualified name as the layout’s first element.
  • An Android RecyclerView to let your app efficiently scroll through a potentially large list of items.
  • An Android ProgressBar to indicate progress when loading the list.

Apart from the View class and styling, this layout’s code is the same for all list Screenlets. For example, here’s Bookmark List Screenlet’s layout res/layout/list_bookmarks.xml:

<com.liferay.mobile.screens.listbookmark.BookmarkListView
    xmlns:android="http://schemas.android.com/apk/res/android"
    android:id="@+id/liferay_list_screenlet"
    android:layout_width="match_parent"
    android:layout_height="match_parent">

    <ProgressBar
        android:id="@+id/liferay_progress"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:layout_gravity="center"
        android:visibility="gone"/>

    <android.support.v7.widget.RecyclerView
        android:id="@+id/liferay_recycler_list"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:visibility="gone"/>
</com.liferay.mobile.screens.listbookmark.BookmarkListView>

Great job! Your View is finished. Next, you’ll create your Screenlet’s Interactor.

Creating the Screenlet’s Interactor

Recall from the basic Screenlet creation tutorial that Interactors retrieve and process a server call’s results. Also recall that the following components make up an Interactor:

  1. Event
  2. Listener
  3. Interactor Class

These components perform the same basic functions in list Screenlets as they do in non-list Screenlets. Creating them, however, is a bit different. Each of the following sections show you how to create one of these components. First, you’ll create the event.

Creating the Event

Screens uses the EventBus library to handle communication within Screenlets. Screenlet components therefore communicate with each other by using event classes that contain the server call’s results. Your list Screenlet’s event class must extend the ListEvent class parameterized with your model class. Your event class should also contain a private instance variable for the model class, a constructor that sets this variable, and a no-argument constructor that calls the superclass constructor. For example, Bookmark List Screenlet’s event class (BookmarkEvent) communicates Bookmark objects. It therefore extends ListEvent with Bookmark as a type argument, and defines a private Bookmark variable that its BookmarkEvent(Bookmark bookmark) constructor sets:

public class BookmarkEvent extends ListEvent<Bookmark> {

      private Bookmark bookmark;

      public BookmarkEvent() {
            super();
      }

      public BookmarkEvent(Bookmark bookmark) {
       this.bookmark = bookmark;
      }
    ...

You must also implement ListEvent’s abstract methods in your event class. Note that these methods support offline mode. Although these methods are briefly described here, supporting offline mode in your Screenlets is addressed in detail in a separate tutorial.

  • getListKey: returns the ID for the cache. This ID is typically the data each list row displays. For example, the getListKey method in BookmarkEvent returns the bookmark’s URL:

    @Override
    public String getListKey() {
        return bookmark.getUrl();
    }
    
  • getModel: unwraps the model entity to the cache by returning the model class instance. For example, the getModel method in BookmarkEvent method returns the bookmark:

    @Override
    public Bookmark getModel() {
        return bookmark;
    }
    

Next, you’ll create your Screenlet’s listener.

Creating the Listener

Recall that listeners let the app developer respond to events that occur in Screenlets. For example, an app developer using Login Screenlet in an activity must implement LoginListener in that activity to respond to login success or failure. When creating a list Screenlet, however, you don’t have to create a separate listener. Developers can use your list Screenlet in an activity or fragment by implementing the BaseListListener interface parameterized with your model class. For example, to use Bookmark List Screenlet in an activity, an app developer’s activity declaration could look like this:

public class BookmarkListActivity extends AppCompatActivity 
    implements BaseListListener<Bookmark> {...

The BaseListListener interface defines the following methods that the app developer can implement in their activity or fragment:

  • void onListPageFailed(int startRow, Exception e): Responds to the Screenlet’s failure to retrieve entities from the server.

  • void onListPageReceived(int startRow, int endRow, List<E> entries, int rowCount): Responds to the Screenlet’s success in retrieving entities from the server.

  • void onListItemSelected(E element, View view): Responds to a user selection in the list.

If these methods meet your list Screenlet’s needs, then you can move on to the next section in this tutorial. If you want to let app developers respond to more actions, however, you must create your own listener that extends BaseListListener parameterized with your model class. For example, Bookmark List Screenlet contains such a listener: BookmarkListListener. This listener defines a single method that notifies the app developer when the Interactor is called:

public interface BookmarkListListener extends BaseListListener<Bookmark> {
    void interactorCalled();
}

Next, you’ll create the Interactor class.

Creating the Interactor Class

Recall that as an Interactor’s central component, the Interactor class makes the service call to retrieve entities from @[email protected], and processes the results of that call. The list Screenlet framework’s BaseListInteractor class provides most of the functionality that Interactor classes in list Screenlets require. You must, however, extend BaseListInteractor to make your service calls and handle their results via your model and event classes. Your Interactor class must therefore extend BaseListInteractor, parameterized with BaseListInteractorListener<YourModelClass> and your event class. For example, Bookmark List Screenlet’s Interactor class, BookmarkListInteractor, extends BaseListInteractor parameterized with BaseListInteractorListener<Bookmark> and BookmarkEvent:

public class BookmarkListInteractor extends 
    BaseListInteractor<BaseListInteractorListener<Bookmark>, BookmarkEvent> {...

Your Interactor must also override the methods needed to make the server call and process the results:

  • getPageRowsRequest: Retrieves the specified page of entities. In the example BookmarkListInteractor, this method first uses the args parameter to retrieve the ID of the folder to retrieve bookmarks from. It then sets the comparator (more on this shortly) if the app developer sets one when inserting the Screenlet XML in a fragment or activity. The getPageRowsRequest method finishes by calling BookmarksEntryService’s getEntries method to retrieve a page of bookmarks. Note that the service call, like the service call in the basic Screenlet creation tutorial, uses LiferayServerContext.isLiferay7() to check the portal version to make sure the correct service instance is used. This isn’t required if you only plan to use your Screenlet with one portal version. Also note that the groupId variable used to make the service calls isn’t set anywhere in getPageRowsRequest or BookmarkListInteractor. Interactors that extend BaseListInteractor, like BookmarkListInteractor, inherit this variable via the Screens framework. You’ll set it when you create the Screenlet class. Here’s BookmarkListInteractor’s complete getPageRowsRequest method:

    @Override
    protected JSONArray getPageRowsRequest(Query query, Object... args) throws Exception {
        long folderId = (long) args[0];
    
        if (args[1] != null) {
            query.setComparator((String) args[1]);
        }
    
        if (LiferayServerContext.isLiferay7()) {
            return new BookmarksEntryService(getSession()).getEntries(groupId, folderId, 
                query.getStartRow(), query.getEndRow(), query.getComparatorJSONWrapper());
        } else {
            return new com.liferay.mobile.android.v62.bookmarksentry.BookmarksEntryService(
                getSession()).getEntries(groupId, folderId, query.getStartRow(), 
                query.getEndRow(), query.getComparatorJSONWrapper());
        }
    }
    

    You might now be asking yourself what a comparator is. A comparator is a class in the @[email protected] instance that sorts a portlet’s entities. For example, the Bookmarks portlet contains several comparators that can sort entities by different criteria. Click here to see these comparators. Although it’s not required, you can develop your list Screenlet to use a comparator to sort its entities. Since Bookmark List Screenlet supports comparators, you’ll see more of this as you progress through this tutorial.

  • getPageRowCountRequest: Retrieves the number of entities, to enable pagination. In the example BookmarkListInteractor, this method first uses the args parameter to get the ID of the folder in which to count bookmarks. It then calls BookmarksEntryService’s getEntriesCount method to retrieve the number of bookmarks:

    @Override
    protected Integer getPageRowCountRequest(Object... args) throws Exception {
        long folderId = (long) args[0];
    
        if (LiferayServerContext.isLiferay7()) {
            return new BookmarksEntryService(getSession()).getEntriesCount(groupId, folderId);
        } else {
            return new com.liferay.mobile.android.v62.bookmarksentry.BookmarksEntryService(
                getSession()).getEntriesCount(groupId, folderId);
        }
    }
    
  • createEntity: Returns an instance of your event that contains the server call’s results. This method receives the results as Map<String, Object>, which it uses to instantiate your model class. It then uses this model instance to create the event object. In the example BookmarkListInteractor, this method passes the Map<String, Object> to the Bookmark constructor. It then uses the resulting Bookmark to create and return a BookmarkEvent:

    @Override
    protected BookmarkEvent createEntity(Map<String, Object> stringObjectMap) {
        Bookmark bookmark = new Bookmark(stringObjectMap);
        return new BookmarkEvent(bookmark);
    }
    
  • getIdFromArgs: a boilerplate method that returns the value of the first object argument as a string. This serves as a cache key for offline mode:

    @Override
    protected String getIdFromArgs(Object... args) {
        return String.valueOf(args[0]);
    }
    

    You must implement this method even if you don’t intend to support offline mode in your Screenlet. Having this method in your Interactor class makes it simpler to add offline mode functionality later. Supporting offline mode in your Screenlets is addressed in detail in a separate tutorial.

To see the complete BookmarkListInteractor class, click here.

Next, you’ll create the Screenlet class.

Creating the Screenlet Class

Recall from the basic Screenlet creation tutorial that the Screenlet class serves as your Screenlet’s focal point. It governs the Screenlet’s behavior and is the primary component the app developer interacts with. As with non-list Screenlets, you should first define any XML attributes that you want to make available to the app developer. For example, Bookmark List Screenlet defines the following attributes:

  • groupId: the ID of the site containing the Bookmarks portlet
  • folderId: the ID of the Bookmarks portlet folder to retrieve bookmarks from
  • comparator: the name of the comparator to use to sort the bookmarks

The Screenlet defines these attributes in its res/values/bookmark_attrs.xml file:

<?xml version="1.0" encoding="utf-8"?>
<resources>
    <declare-styleable name="BookmarkListScreenlet">
        <attr name="groupId"/>
        <attr name="folderId"/>
        <attr format="string" name="comparator"/>
    </declare-styleable>
</resources>

Now you’re ready to create your Screenlet class. Because the BaseListScreenlet class provides the basic functionality for all Screenlet classes in list Screenlets, including methods for pagination and other default behavior, your Screenlet class must extend BaseListScreenlet with your model class and Interactor as type arguments.

For example, Bookmark List Screenlet’s Screenlet class–BookmarkListScreenlet–extends BaseListScreenlet parameterized with Bookmark and BookmarkListInteractor:

public class BookmarkListScreenlet 
    extends BaseListScreenlet<Bookmark, BookmarkListInteractor> {...

You must also create instance variables for the XML attributes that you want to pass to your Interactor. For example, recall that the request methods in BookmarkListInteractor receive two Object arguments: the folder ID and the comparator. The BookmarkListScreenlet class must therefore contain variables for these parameters so it can pass them to the Interactor:

private long folderId;
private String comparator;

For constructors, leverage the superclass constructors. For example, here are BookmarkListScreenlet’s constructors:

public BookmarkListScreenlet(Context context) {
    super(context);
}

public BookmarkListScreenlet(Context context, AttributeSet attrs) {
    super(context, attrs);
}

public BookmarkListScreenlet(Context context, AttributeSet attrs, int defStyleAttr) {
    super(context, attrs, defStyleAttr);
}

public BookmarkListScreenlet(Context context, AttributeSet attrs, int defStyleAttr, 
    int defStyleRes) {
        super(context, attrs, defStyleAttr, defStyleRes);
}

Now you must implement the error method. This is a boilerplate method that uses a listener in the Screenlet framework to propagate any exception, and the user action that produced it, that occurs during the service call. This method does this by checking for a listener and then calling its error method with the Exception and userAction:

@Override
public void error(Exception e, String userAction) {
    if (getListener() != null) {
        getListener().error(e, userAction);
    }
}

Next, override the createScreenletView method to read the values of the XML attributes you defined earlier and create the Screenlet’s View. Recall from the basic Screenlet creation tutorial that this method assigns the attribute values to their corresponding instance variables. For example, the createScreenletView method in BookmarkListScreenlet assigns the folderId and comparator attribute values to variables of the same name. This method also sets the local variable groupId. Recall that the Screens framework propagates this variable to your Interactor. Finish the createScreenletView method by calling the superclass’s createScreenletView method. This instantiates the View for you:

@Override
protected View createScreenletView(Context context, AttributeSet attributes) {
    TypedArray typedArray = context.getTheme().obtainStyledAttributes(attributes, 
        R.styleable.BookmarkListScreenlet, 0, 0);
    groupId = typedArray.getInt(R.styleable.BookmarkListScreenlet_groupId, 
        (int) LiferayServerContext.getGroupId());
    folderId = typedArray.getInt(R.styleable.BookmarkListScreenlet_folderId, 0);
    comparator = typedArray.getString(R.styleable.BookmarkListScreenlet_comparator);
    typedArray.recycle();

    return super.createScreenletView(context, attributes);
}

Next, override the loadRows method to start your Interactor and thereby retrieve the list rows from the server. This method takes an instance of your Interactor as an argument, which you use to call the Interactor’s start method. Note that the Interactor inherits start from BaseListInteractor. You can also use the loadRows method to execute any other code that you want to run when the Interactor starts. For example, the loadRows method in BookmarkListScreenlet first retrieves a listener instance so it can call the listener’s interactorCalled method. It then starts the server operation to retrieve the list rows by calling the Interactor’s start method with folderId and comparator:

@Override
protected void loadRows(BookmarkListInteractor interactor) {

    ((BookmarkListListener) getListener()).interactorCalled();

    interactor.start(folderId, comparator);
}

Note that if your Interactor doesn’t require arguments, then you can pass the start method 0 or null. Calling start with no arguments, however, causes the server call to fail.

Lastly, override the createInteractor method to instantiate your Interactor. Since that’s all this method needs to do, call your Interactor’s constructor and return the new instance. For example, BookmarkListScreenlet’s createInteractor method returns a new BookmarkListInteractor:

@Override
protected BookmarkListInteractor createInteractor(String actionName) {
    return new BookmarkListInteractor();
}

You’re done! Your Screenlet is a ready-to-use component that you can use in your app. You can even package your Screenlet and contribute it to the Screens project, or distribute it in Maven Central or jCenter.

Using the Screenlet

You can now use your new list Screenlet the same way you use any other Screenlet:

  1. Insert the Screenlet’s XML in the layout of the activity or fragment you want to use the Screenlet in. For example, here’s Bookmark List Screenlet’s XML:

    <com.liferay.mobile.screens.listbookmark.BookmarkListScreenlet
        android:id="@+id/bookmarklist_screenlet"
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        app:comparator="FULLY_QUALIFIED_COMPARATOR_CLASS"
        app:folderId="YOUR_FOLDER_ID"
        app:groupId="YOUR_GROUP_ID"
        app:layoutId="@layout/list_bookmarks"/>
    

    Note that to set a comparator, you must use its fully qualified class name. For example, to use the Bookmarks portlet’s EntryURLComparator, set app:comparator in the Screenlet XML as follows:

    app:comparator="com.liferay.bookmarks.util.comparator.EntryURLComparator"
    
  2. Implement the Screenlet’s listener in the activity or fragment class. If your list Screenlet doesn’t have a custom listener, then you can do this by implementing BaseListListener parameterized with your model class. For example:

    public class YourListActivity extends AppCompatActivity 
        implements BaseListListener<YourModelClass> {...
    

    If you created a custom listener for your list Screenlet, however, then your activity or fragment must implement it instead. For example, recall that the example Bookmark List Screenlet’s listener is BookmarkListListener. To use this Screenlet, you must therefore implement this listener in the class of the activity or fragment that you want to use the Screenlet in. For example:

    public class ListBookmarksActivity extends AppCompatActivity 
        implements BookmarkListListener {...
    

    See the full example of this here in GitHub.

Well done! Now you know how to create list Screenlets.

Related Topics

Creating Android Screenlets

Architecture of Liferay Screens for Android

Packaging Your Android Screenlets

Using Views in Android Screenlets

Using Screenlets in Android Apps

0 (0 Votes)
Creating Android Screenlets Previous