Multiple ListRows for each Header on BrowseFragment - Leanback library

元气小坏坏 提交于 2019-12-03 12:31:41

The Leanback team has recently added in support for multiple ListRows for one HeaderItem in version 24.0.0 of the library. It allows you to supply a RowsFragment that maps to the HeaderItem. You can see an example of it in their Leanback showcase. Specifically, here is the file where they provide an example.

There is a new PageRowFragmentFactory that you will need in your BrowseFragment which specifies which Fragments map to which HeaderItems. Like so:

    @Override
    public Fragment createFragment(Object rowObj) {
        Row row = (Row)rowObj;
        mBackgroundManager.setDrawable(null);
        if (row.getHeaderItem().getId() == HEADER_ID_1) {
            return new SampleFragmentA();
        } else if (row.getHeaderItem().getId() == HEADER_ID_4) {
            return new WebViewFragment();
        }
        throw new IllegalArgumentException(String.format("Invalid row %s", rowObj));
    }

You can just have the above method return an instance of a RowsFragment and now you'll have the RowsFragment which contains multiple ListRows map to just one HeaderItem.

As of right now you can get access to this goodness through version 24.0.0 of Leanback with the below line in your gradle file:

compile 'com.android.support:leanback-v17:24.0.0

You might get a warning, but for now it can be safely ignored.

There is also a ton of other really cool stuff in version 24.0.0 of Leanback like snazzy transition animations and cleaner APIs. It can all be found in that sample project I linked above. There is also a talk from Google I/O which covers more of the additions.

Is there any presenter that supports multiple list rows?

Not that I know of. The problem is that BrowseFragment only accepts children that subclass Row. For this reason, there can only be single rows (and their respective headers) for each entry in BrowseFragment.

I'm thinking on the lines creating a custom presenter with RowsFragment embedded in each item, correct me if my approach is wrong.

As I just mentioned, I doubt that creating a custom presenter would help.

The only solution I have been able to come up with so far is simply creating a custom version of BrowseFragment (by manually extending the RowsFragment and HeadersFragment classes) so that it supports any type of fragments.

If you're interested, I wrote a series of articles on the process https://medium.com/building-for-android-tv/

and a base project that offers the custom version of BrowseFragment https://github.com/dextorer/BuildingForAndroidTV

I'm also considering writing a library to ease the use of this custom component.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!