-
Notifications
You must be signed in to change notification settings - Fork 3.3k
FWE pt 1 #12035
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
FWE pt 1 #12035
Conversation
Visit the preview URL for this PR (updated for commit 346fd6d): https://flutter-docs-prod--pr12035-flutter-tutorial-p25mm14a.web.app |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This tutorial feels realllly loooong. Do we want it this long? I don't know the answer, but some newbies to Flutter should test it out.
If you prefer to run Flutter apps on Android, | ||
iOS, MacOS, or any other supported platform, you’ll have no problem following the tutorial. | ||
But some features, like resizing a window to see how UI renders | ||
on different screen sizes, aren’t available on mobile simulators. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a lot of words here and it's rather confusing. At the end, you mention a limitation of simulators, but the earlier text doesn't even mention simulators. I'd tighten this up, hence the more opinionated. ;)
|
||
**Stateful hot reload**, if you haven't heard of it, allows a running Flutter | ||
app to re-render updated business logic or UI code in less than a second - all | ||
without losing your place in the app. This is the part that hooks most Flutter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
without losing your place in the app. This is the part that hooks most Flutter | |
without losing your place in the app. This is the feature that hooks most Flutter |
|
||
### Constructor | ||
|
||
It has a [`constructor`][], which defines |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It has a [`constructor`][], which defines | |
The `Tile` class has a [`constructor`][] that defines |
### Constructor | ||
|
||
It has a [`constructor`][], which defines | ||
what data needs to be passed into the widget to render the widget. Here,a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what data needs to be passed into the widget to render the widget. Here,a | |
what data needs to be passed into the widget to render the widget. Here, a |
### `Build` method | ||
|
||
Finally, there’s the all important `build` method, which must be defined on | ||
every widget, and will always return another widget. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
every widget, and will always return another widget. | |
every visible widget, and will always return another widget. |
??
|
||
:::tip Quick assists | ||
|
||
The Flutter plugin for VSCode and Intellij provides ["quick assists"][], which will do this conversion for you. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A HA! Why not just use THIS???
To implement this, update the callback function passed to the | ||
`GuessInput`. The function needs to call `setState`, and within | ||
`setState` it needs to execute the logic to determin if the users | ||
guess was correct. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To implement this, update the callback function passed to the | |
`GuessInput`. The function needs to call `setState`, and within | |
`setState` it needs to execute the logic to determin if the users | |
guess was correct. | |
To implement this, update the callback function passed to | |
`GuessInput`. The function needs to call `setState` and, within | |
`setState`, it needs to execute the logic to determine whether the users | |
guess was correct. |
title: Simple animations | ||
description: Learn the simplest way to implement animations in Flutter. | ||
permalink: /tutorial/animations/ | ||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How long should this lesson take? Cause it feels SOOOO LOOONG.
In this lesson, you'll learn about one of the most common and | ||
versatile implicit animation widgets: [`AnimatedContainer`][]. With | ||
just two additional lines of code, the background color of each `Tile` | ||
will change over half a second. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will change over half a second. | |
animates to a new color in about half a second. |
There are many different curves defined by the Flutter SDK, so feel | ||
free to try them out by passing different types to the | ||
`AnimatedContainer.curve` property. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really need to do this in a beginning lesson?
It's definitely long, and its going to get longer! There are going to be 2 more sections :) (edit: I think this section is going to be the longest by a fair amount.) But really, Andrew called this project "first week experience" because it was supposed to be all-encompassing and take a week. But I'm very interested in cutting it down where it makes sense. I'm happy to cut out any fluff. |
Description of what this PR is changing or adding, and why:
This silently adds the "UI 101" pages of the upcoming FWE tutorial. This PR does not include any changes the side nav.
Part of #12063
Pages
Presubmit checklist