[DISCONTINUED] Navigation stack for Mortar. Alternative to Flow. Focuses on Mortar scopes, simplicity, seamless integration and killing boilerplate code.
Hi, I'm having trouble integrating the Floating Action Button (FAB) with the Mortar-Architect layout structure. I'm planning to create the FAB in each view (HomeView, TransactionView) for convenience, this would allow me to create FAB specific to each views. But in the activity_main.xml of app example, the NavigatorView which acts as the container of the Views, is a child of the CoordinatorLayout, and is placed as the last child of the CoordinatorLayout. According to the FAB samples, FAB must also be a direct descendant / child of CoordinatorLayout (to gain the Material Design behaviors). So, if I create the FAB in each views, this means that the FAB is not a direct child of the CoordinatorLayout (FAB would be a child of a view which is contained in the NavigatorView, and that NavigatorView is the child of the CoordinatorLayout). What is the proper way of handling this issue? Thanks.
Hi, I'm having trouble integrating the Floating Action Button (FAB) with the Mortar-Architect layout structure. I'm planning to create the FAB in each view (HomeView, TransactionView) for convenience, this would allow me to create FAB specific to each views. But in the activity_main.xml of app example, the NavigatorView which acts as the container of the Views, is a child of the CoordinatorLayout, and is placed as the last child of the CoordinatorLayout. According to the FAB samples, FAB must also be a direct descendant / child of CoordinatorLayout (to gain the Material Design behaviors). So, if I create the FAB in each views, this means that the FAB is not a direct child of the CoordinatorLayout (FAB would be a child of a view which is contained in the NavigatorView, and that NavigatorView is the child of the CoordinatorLayout). What is the proper way of handling this issue? Thanks.