flutter/examples/catalog
Ian Hickson 449f4a6673
License update (#45373)
* Update project.pbxproj files to say Flutter rather than Chromium

Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright.

* Update the copyright notice checker to require a standard notice on all files

* Update copyrights on Dart files. (This was a mechanical commit.)

* Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine.

Some were already marked "The Flutter Authors", not clear why. Their
dates have been normalized. Some were missing the blank line after the
license. Some were randomly different in trivial ways for no apparent
reason (e.g. missing the trailing period).

* Clean up the copyrights in non-Dart files. (Manual edits.)

Also, make sure templates don't have copyrights.

* Fix some more ORGANIZATIONNAMEs
2019-11-27 15:04:02 -08:00
..
android License update (#45373) 2019-11-27 15:04:02 -08:00
bin License update (#45373) 2019-11-27 15:04:02 -08:00
ios License update (#45373) 2019-11-27 15:04:02 -08:00
lib License update (#45373) 2019-11-27 15:04:02 -08:00
test License update (#45373) 2019-11-27 15:04:02 -08:00
test_driver remove unnecessary artificial delay in catalog example (#31822) 2019-05-03 11:25:29 -07:00
pubspec.yaml update-packages after dwds updates (#45633) 2019-11-26 18:34:06 -08:00
README.md Make examples/catalog instructions a bit less confusing (#24252) 2018-11-14 14:26:30 -08:00

Samples Catalog

A collection of sample apps that demonstrate how Flutter can be used.

Each sample app is contained in a single .dart file located in the lib directory. To run each sample app, specify the corresponding file on the flutter run command line, for example:

flutter run lib/animated_list.dart
flutter run lib/app_bar_bottom.dart
flutter run lib/basic_app_bar.dart
...

The apps are intended to be short and easily understood. Classes that represent the sample's focus are at the top of the file; data and support classes follow.

Each sample app contains a comment (usually at the end) which provides some standard documentation that also appears in the web view of the catalog. See the "Generating..." section below.

Generating the web view of the catalog

Markdown and a screenshot of each app are produced by bin/sample_page.dart and saved in the .generated directory. The markdown file contains the text taken from the Sample Catalog comment found in the app's source file, followed by the source code itself.

This sample_page.dart command line app must be run from the examples/catalog directory. It relies on templates also found in the bin directory, and it generates and executes test_driver apps to collect the screenshots:

cd examples/catalog
dart bin/sample_page.dart