With the other starters
The navigation and security starters know no design library either. In an app of type material, this starter gives them what is Material's, through beans and a DesignScope the Flutter starter defines. Nothing has to be set up: the beans are in the application as soon as the starter is in the dependencies.
Page routes for the navigation starter
The router of spring_boot_starter_flutter_navigation asks the DesignPageRoutes beans for the route of a page. This starter's materialPageRoutes bean (MaterialPageRoutes) answers in an app of type material:
motion.page-transition (of the theme or the screen) |
In an app of type material |
|---|---|
platform (the default) |
Material's route with Flutter's own transition for the platform, as a MaterialPageRoute has it: the predictive back on Android, Cupertino's slide on iOS and macOS, the zoom on Windows and Linux; the pageTransitionsTheme a ThemeCustomizer sets instead, when code sets one (Themes in code) |
zoom |
Material's zoom transition; it needs this starter, and works in an app of any type with it |
fade, fade-upwards, content, none |
The Flutter starter's own, as in any app |
cupertino |
The iOS slide, from the Cupertino starter |
The heroes of the app's navigators fly along Material's arc (MaterialApp.createMaterialHeroController()). In an app without a design library they fly straight. See Transitions.
The login form of the security starter
LoginForm and OAuth2LoginButton of spring_boot_starter_flutter_security draw their fields and buttons with the controls of the app's design. With this starter those are Material's (MaterialDesignControls): a TextField and a FilledButton styled by the app's ThemeData, so components.input.* and components.button.* apply, and the palette's error color. This is LoginDesign.app, which the widgets pick by themselves when the app has a design library:
LoginForm(onSuccess: (_) => Navigator.of(context).pop()); // Material's controls
LoginForm(design: LoginDesign.widgets, onSuccess: (_) => close()); // the plain ones
They also find Material's controls below a MaterialApp the app builds itself, by the materialDesignControls bean. See Login screens.
MarkdownView
MarkdownView reads Material's text theme (Theme.of(context).textTheme) and selects text with Material's SelectionArea, through the DesignScope the MaterialApp has above its pages. Without a design library it uses the SpringTheme and the Flutter starter's own selection handles. See MarkdownView.
See also
- Design libraries:
DesignPageRoutes,DesignScopeandDesignControls - Transitions
- Login screens