Repository navigation
Conversation
|
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
|
I believe this is ready to go, once it's been reviewed. P.S. @chalin, do you know how to get rid of the WIP status? |
|
I confirm that @chalin's changes are good. |
chalin
left a comment
There was a problem hiding this comment.
Nice updates! Please see inlined comments, some comments are meant to address discrepancies relative to the doc style guide (https://developers.google.com/style/)
| <img src="images/startup-namer-app.gif" | ||
| <img src="images/startup_namer_1_opt.gif" | ||
| alt="Animated GIF of the app that you will be building." | ||
| style="border: 10px solid #333; border-radius: 10px; margin-bottom: 10px" > |
There was a problem hiding this comment.
I'd suggest dropping the border styling here: I was necessary with the old image, but it isn't anymore since the new image already shows the phone border.
| @@ -6,7 +6,7 @@ image: /get-started/codelab/images/step7-themes.png | |||
| --- | |||
|
|
|||
| <figure class="right-figure" style="max-width: 260px; padding-right: 10px"> | |||
There was a problem hiding this comment.
We should avoid doing custom styling like this (use of class="right-figure" should be enough), but I can fix that in a followup PR.
| {:toc} | ||
|
|
||
| ## What you'll build | ||
| ## What you'll build in part 1 |
There was a problem hiding this comment.
I was puzzled for a moment since I wasn't aware of Part 2.
- How about adding ", Part 1" to the title? If fact, maybe adding ", Part 1" to the title is enough (i.e., we don't need to add it here).
- The introductory paragraph (for the page), should mention that there is a followup "Part 2" (and link to it).
- Is this page identical to https://codelabs.developers.google.com/codelabs/first-flutter-app-pt1? Regardless, the introductory paragraph should also mention the codelabs.developers part 1 and make it clear whether it is the same or different.
There was a problem hiding this comment.
They will be the same, once I've updated both.
| You’ll implement a simple mobile app that generates proposed names for a | ||
| startup company. The user can select and unselect names, | ||
| saving the best ones. The code generates ten names at a time. | ||
| saving the best ones. The code lazily generates ten names at a time. |
There was a problem hiding this comment.
This would be more accurate:
The code lazily generates names, ten at a time.
Actually, we probably don't need to mention a number here, given the sentence that follows. So I'd simplify this sentence to:
The code lazily generates names.
| startup company. The user can select and unselect names, | ||
| saving the best ones. The code generates ten names at a time. | ||
| saving the best ones. The code lazily generates ten names at a time. | ||
| As the user scrolls, new batches of names are generated. |
There was a problem hiding this comment.
-> As the user scrolls, more names are generated.
| and changing the home to be a RandomWords widget. | ||
|
|
||
| Add the highlighted code below: | ||
| Replace the original method with the highlighted build method below: |
There was a problem hiding this comment.
How about replacing both (1-sentence) paragraphs by:
- Update the
MyAppbuild()method as follows:
| ## Next step | ||
| {:.no_toc} | ||
| If you would like to extend this app, proceed to | ||
| [part 2](https://codelabs.developers.google.com/codelabs/first-flutter-app-pt2/#0) |
| @@ -926,14 +569,20 @@ In this codelab, you've: | |||
| * Written Dart code. | |||
| * Leveraged an external, third party library. | |||
| * Used hot reload for a faster development cycle. | ||
| * Implemented a stateful widget, adding interactivity to your app. | ||
| * Implemented a stateful widget. | ||
| * Created a lazily loaded, infinite scrolling list displayed with a |
There was a problem hiding this comment.
Let's keep this summary simple (we don't mention implementation details in the other bullets):
Created a lazily loaded, infinite scrolling list displayed ... -> Created a lazily loaded, infinite scrolling list.
| <img src="images/startup-namer-app.gif" | ||
| alt="Animated GIF of the app that you will be building." | ||
| style="border: 10px solid #333; border-radius: 10px; margin-bottom: 10px" > | ||
| <center>The app at the end of step 2</center><br> |
There was a problem hiding this comment.
end of step 2 -> end of Part 2
There was a problem hiding this comment.
Is this really meant to be "The app at the end of step 2"
No, but it shouldn't prevent us from doing a "squash and merge" later. As for the |
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) |
|
Hi, @chalin! OK, I have incorporated most of your feedback. I realize that you will make further changes once you incorporate the auto diffs. You have my blessing. But I'd like to get this merged this week and I'm out tomorrow. Please take a look. |
Gladly, but I'm not seeing the changes. |
|
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
| There is no limit to how far a user can scroll. | ||
|
|
||
| The animated GIF shows how the app works at the completion of part 1: | ||
| The animated GIF shows how the app works at the completion of Part 1. |
There was a problem hiding this comment.
I suppose that this should be "part 1" (lowercase) like the rest of the occurrences of the word?
Yes, remove the text "WORK IN PROGRESS" from the message of the first commit. |
|
So it is looking good aside from two comments. (One of the comments doesn't appear on this page; it is here -- and asks if the caption for the last image is really meant to be "The app at the end of step 2"? If it is referring to step 2 of part 2, I'd just omit that caption or change it to: "The app from part 2". |
|
This PR got its knickers in a twist because Patrice and I collaborated on some of the changes. Merging. |
@chalin