diff --git a/assets-and-images.md b/assets-and-images.md index bd580f87938..05d2ecffd14 100644 --- a/assets-and-images.md +++ b/assets-and-images.md @@ -149,4 +149,4 @@ Some caveats: You can see an example ([examples/widgets.dart](https://github.com/flutter/flutter/tree/master/examples/widgets)) from the flutter repo. -Run `flutter start -t resolution_awareness.dart` to see it in action. +Run `flutter run -t resolution_awareness.dart` to see it in action. diff --git a/debugging.md b/debugging.md index 61cb4951dd4..dc2924f5c81 100644 --- a/debugging.md +++ b/debugging.md @@ -73,7 +73,7 @@ the output to a level that avoids being dropped by Android's kernel. During development, you are highly encouraged to use Dart's "checked" mode, sometimes referred to as "debug" mode. This is the default if -you use `flutter start`. In this mode, the Dart `assert` statement is +you use `flutter run`. In this mode, the Dart `assert` statement is enabled, and the Flutter framework uses this to perform many runtime checks verifying that invariants aren't being violated. @@ -82,7 +82,7 @@ some context information to help with tracking down the source of the problem. To turn off checked mode, and use release mode, run your application -using `flutter start --no-checked`. +using `flutter run --no-checked`. ## Dumping the application state @@ -129,7 +129,7 @@ class AppHome extends StatelessComponent { ...will output something like this (the precise details will vary on the version of the framework, the size of the device, and so forth): - + ``` android: I/flutter : WidgetFlutterBinding - CHECKED MODE @@ -221,7 +221,7 @@ callback](http://docs.flutter.io/flutter/scheduler/Scheduler/addPersistentFrameC or an event handler is the best solution. To call `debugDumpRenderTree()`, you need to add `import -'package:flutter/rendering.dart';` to your source file. +'package:flutter/rendering.dart';` to your source file. The output for the tiny example above would look something like this: diff --git a/faq.md b/faq.md index 9d812084d42..b3a32820a60 100644 --- a/faq.md +++ b/faq.md @@ -271,7 +271,7 @@ In development, Flutter apps run with a type checking and asserts enabled by default. These checks help you catch errors early during development but impose a runtime cost. The "slow mode" banner indicates that these checks are enabled. You can run your app without these checks by passing the `--no-checked` flag to -`flutter start`. +`flutter run`. ## Where can I get support? diff --git a/getting-started.md b/getting-started.md index 77dd278e60f..a6ea2b966ff 100644 --- a/getting-started.md +++ b/getting-started.md @@ -94,8 +94,8 @@ you want Flutter to use a different installation of the Android SDK, you must se ## Running a Flutter application on Android -You can use the `flutter start` command to run your Flutter app on all connected -devices and simulators. `flutter list` will list connected devices and +You can use the `flutter run` command to run your Flutter app on all connected +devices and simulators. `flutter devices` will list connected devices and simulators. First, change directories to the root of your app (the same directory that @@ -104,7 +104,7 @@ contains the `pubspec.yaml` file for your project). To start your app, run: ``` -$ flutter start +$ flutter run ``` If everything works, you should see your starter app @@ -149,12 +149,10 @@ We currently only support iOS development with the iOS simulator, but you can deploy Flutter apps to iOS devices. - Run `Simulator.app` - - You can find Simulator.app in -_Applications/Xcode/Contents/Developer/Applications_ or via _Spotlight_ - - To ensure your simulator uses a device type of iPhone 5 or above, -check the Simulator.app's `Hardware -> Device` menu. -- Run `flutter start` from your app's directory. - - This command detects the iOS simulator and starts the app. + - You can find Simulator.app in _Applications/Xcode/Contents/Developer/Applications_ or via _Spotlight_ + - Ensure your simulator is using a 64-bit device (iPhone 5s or later) by checking the Simulator.app's `Hardware -> Device` menu +- Run `flutter run` from your app's directory + - This command detects the iOS simulator and starts the app ## Getting Started with the Atom editor