missile library
The missile portion of the app provides app navigation and initial configuration.
The app runs in 2 parts. The first handles the configuration. The second takes the parameters supplied by the configuration process and builds a site accordingly.
Typically many of these classes and methods would be private. They are kept public here so that the code can be documented.
Names are very important in Flutter applications and can be used to find dependent parts of application code using the tools provided with Android Studio (and presumably with Visual Studio).
During development we use log
statements to record useful data and to
ascertain timing and sequencing of events. We use the log
statement wrapped in an
assert statement so that the log statement and literal values disappear in production mode.
The dart literal interpolation is a major help in doing the logging.
Classes
- Config
- Constructor for the Config model. [...]
- ConfigFactory
- The factory used to build the Config model.
- MissileHomePage
- Stateful widget representing Form input dialog that populates Config. [...]
- MissileHomePageState
- State portion of MissileHomePage. [...]
Properties
- cupertinoTheme → CupertinoThemeData
-
Supplied Theme data for Cupertino hosted platforms. [...]
final
- materialThemeData → ThemeData
-
Supplied Theme data for Material hosted platforms. [...]
final
Functions
-
buildSitePath(
BuildContext context, Config cfg, String title) → Widget - Build the MissileSitePage to be used in the "/site" navigation path. [...]
-
main(
) → void - The app start entry point. [...]