1 import 'package:flutter/material.dart';
7 class MyApp extends StatelessWidget {
8 // This widget is the root of your application.
10 Widget build(BuildContext context) {
12 title: 'Families Game',
14 // This is the theme of your application.
16 // Try running your application with "flutter run". You'll see the
17 // application has a blue toolbar. Then, without quitting the app, try
18 // changing the primarySwatch below to Colors.green and then invoke
19 // "hot reload" (press "r" in the console where you ran "flutter run",
20 // or simply save your changes to "hot reload" in a Flutter IDE).
21 // Notice that the counter didn't reset back to zero; the application
23 primarySwatch: Colors.blue,
24 // This makes the visual density adapt to the platform that you run
25 // the app on. For desktop platforms, the controls will be smaller and
26 // closer together (more dense) than on mobile platforms.
27 visualDensity: VisualDensity.adaptivePlatformDensity,
29 home: MyHomePage(title: 'Families / Empires'),
34 class MyHomePage extends StatefulWidget {
35 MyHomePage({Key key, this.title}) : super(key: key);
37 // This widget is the home page of your application. It is stateful, meaning
38 // that it has a State object (defined below) that contains fields that affect
41 // This class is the configuration for the state. It holds the values (in this
42 // case the title) provided by the parent (in this case the App widget) and
43 // used by the build method of the State. Fields in a Widget subclass are
44 // always marked "final".
49 _MyHomePageState createState() => _MyHomePageState();
52 class _MyHomePageState extends State<MyHomePage> {
55 void _incrementCounter() {
57 // This call to setState tells the Flutter framework that something has
58 // changed in this State, which causes it to rerun the build method below
59 // so that the display can reflect the updated values. If we changed
60 // _counter without calling setState(), then the build method would not be
61 // called again, and so nothing would appear to happen.
67 Widget build(BuildContext context) {
68 // This method is rerun every time setState is called, for instance as done
69 // by the _incrementCounter method above.
71 // The Flutter framework has been optimized to make rerunning build methods
72 // fast, so that you can just rebuild anything that needs updating rather
73 // than having to individually change instances of widgets.
76 // Here we take the value from the MyHomePage object that was created by
77 // the App.build method, and use it to set our appbar title.
78 title: Text(widget.title),
81 margin: const EdgeInsets.only(left: 20.0, right: 20.0),
83 // Center is a layout widget. It takes a single child and positions it
84 // in the middle of the parent.
86 // Column is also a layout widget. It takes a list of children and
87 // arranges them vertically. By default, it sizes itself to fit its
88 // children horizontally, and tries to be as tall as its parent.
90 // Invoke "debug painting" (press "p" in the console, choose the
91 // "Toggle Debug Paint" action from the Flutter Inspector in Android
92 // Studio, or the "Toggle Debug Paint" command in Visual Studio Code)
93 // to see the wireframe for each widget.
95 // Column has various properties to control how it sizes itself and
96 // how it positions its children. Here we use mainAxisAlignment to
97 // center the children vertically; the main axis here is the vertical
98 // axis because Columns are vertical (the cross axis would be
100 mainAxisAlignment: MainAxisAlignment.center,
101 crossAxisAlignment: CrossAxisAlignment.start,
106 style: Theme.of(context).textTheme.headline4,
109 decoration: InputDecoration(
110 hintText: 'Enter your (real) name',
116 style: Theme.of(context).textTheme.headline4,
119 decoration: InputDecoration(
120 hintText: 'Enter your family/empire name',
128 floatingActionButton: FloatingActionButton(
129 onPressed: _incrementCounter,
130 tooltip: 'Increment',
131 child: Icon(Icons.add),
132 ), // This trailing comma makes auto-formatting nicer for build methods.