You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you first generate a project using mobile.g8, it creates a simple app, which contains only a blank screen (almost!) with some text saying that you can scaffold among a number of options:
stack_navigation
tab_navigation
drawer_navigation
... or even some small apps or examples, such as:
capabilities (test device capabilities)
other small/sample applications contributed by the community.
The developer can then decide for a certain navigation style, such as:
In this case, an additional folder is created, containing the files necessary for implementation of such navigation style.
Some wiring is necessary in order to tell that the new navigation style must be used, and not the previous one being used.
Advantages
We can provide various navigation styles and even examples of simple applications;
The developer can choose whatever styles/examples better suit his/her purposes;
There's no mix or confusion regarding files involved in each style/example, since these files are necessarily separated on distinct folder for each purpose;
In case of overwriting some files, this is kept to a minimum, possibly only a configuration file containing just one line which says which is the desired style/example.
All items above imply on easier management of changes.
The text was updated successfully, but these errors were encountered:
Giter8 provides a scaffold functionality which we could be taking advantage of.
Documentation: http://www.foundweekends.org/giter8/scaffolding.html
Proposal
... or even some small apps or examples, such as:
The developer can then decide for a certain navigation style, such as:
sbt g8Scaffold myproject com.example drawer_navigation
In this case, an additional folder is created, containing the files necessary for implementation of such navigation style.
Some wiring is necessary in order to tell that the new navigation style must be used, and not the previous one being used.
Advantages
We can provide various navigation styles and even examples of simple applications;
The developer can choose whatever styles/examples better suit his/her purposes;
There's no mix or confusion regarding files involved in each style/example, since these files are necessarily separated on distinct folder for each purpose;
In case of overwriting some files, this is kept to a minimum, possibly only a configuration file containing just one line which says which is the desired style/example.
All items above imply on easier management of changes.
The text was updated successfully, but these errors were encountered: