mobileshowcase:-
should be using the contentStackMenu (accordion option so that all the info fits on the page for better usability). Then the example should also be placed into the showcase for contentStackMenu, contentNavBar (both have contentMenuItem as children....but don't have to be used together. These components are still new so can be modified if necessary, but should be functional to be used and renamed now, if necessary).
mediacast should be able to use contentNavBar now (doesn't need a menu) with the buttons for navigation to reduce the navigation model in backing beans currently utilized.
panelPopup should be fixed so it's usable for these applications. ( a jira is open and targeted for 1.2 Beta)
use menuButton for the theme change in the examples .
mobileshowcase:-
should be using the contentStackMenu (accordion option so that all the info fits on the page for better usability). Then the example should also be placed into the showcase for contentStackMenu, contentNavBar (both have contentMenuItem as children....but don't have to be used together. These components are still new so can be modified if necessary, but should be functional to be used and renamed now, if necessary).
mediacast should be able to use contentNavBar now (doesn't need a menu) with the buttons for navigation to reduce the navigation model in backing beans currently utilized.
panelPopup should be fixed so it's usable for these applications. ( a jira is open and targeted for 1.2 Beta)
use menuButton for the theme change in the examples .