
class EventsListAdapter extends RecyclerView. įilterable is an interface which is generally used with an adapter when there are many different values possible for the adapter. Eventbrite Organiser (formerly Entry Manager) is your one-stop shop for managing event sales and attendees on your Android device. The menu resource file is used to specify what items we need in the BottomNavigationView. The attribute app :menu takes the reference to the menu resource layout for the menu items to be used, which we’ll setup next: Step 2 : Declaring menu resource file for the BottomNavigationView: xml and is to just add the Bottom Navigation layout for the xml. The above code for the layout is added to the end of fragment_event_list. In fact, this was the best solution we could come up with, and we’ll see why: Step 1 : Add BottomNavigationView to the layout: So my mentor wanted us to use BottomNavigationView instead. Using View Pagers requires managing presenters for each of the fragments being used. This issue was raised in the last GSoC as well, but developers settled with using a single list view.

View Pagers are buggy and would further require unnecessary architectural changes and additional classes for the Event-list module.

Įventbrite was using Tabs with View Pagers, which is a lot tedious because of its bugginess. The application has proved to be beneficiary for not only ordinary users looking for a concert or movie, but also for venue holders and event organizers. We needed the app to look more like EventBrite so that we could help the users smoothly transition from EventBrite to Open Event Organizer Android App. The state of the app before merging the pull request: #1009 was a simple RecyclerView with StickyHeaders from FastAdapter library.
