ListView related components

[mhotan]

ListView related components

[mhotan]

Phase 2 priority:
Modify the list in the Restaurant Application Current Customer fragment. This list is dynamic in that once a new user checks in to the restaurant there information should be populated on the list. Don't worry about populating the list. Concern yourself more with the UI layout and callbacks. Eventually replace the CustomerList to a Dining Session List. Then populate the new "Dining Session" list item appropriately.

Classes you probably have to familiarize your self with:

• CustomerListFragment.java
  ---Contains the event handlers and such
• Create "res/layout/listitem_diningsession" or whatever the equivalent for an expandable list item in the Restaurant application.

Not Phase 2 priority:

Replace the current Restaurant Selection List items along with the Menu Items list. Add a button for both that is right aligned and points right (perhaps looks like ">"). Refer to restaurant application and the list fragments in there. The buttons will notify use to either start a new activity or open the details fragment of a given restaurant and menu item.

[rocketgarden]

Is there a reason for CustomerListFragment to extend android.support.v4.app.ListFragment instead of android.app.ListFragment?

[mhotan]

Yes, our application is using the support library. It is a convention I chose to so that if we choose to be able to support older android builds we can. It also allows us to use ViewPager which allows us to have the swipe screen capability. And android.support.v4.app.ListFragment and android.app.ListFragment are not interchangeable.

[mhotan]

Make sure that you change the data types of for String and Primitives. To the correct DineOn type. So feel free to change CustomerList to a list of Dining Sessions defined in the library.

[mhotan]

Replace the customer list with a Dining session list. I described why above. We have a Dining session Object. If you want to work on it go ahead and create an Issue so everyone knows you are