This patch contains some basic tests for PaginatedDataTable.

Answers http://stackoverflow.com/questions/41729278/why-is-this-icon-being-clipped

This package depends on package:process now.

This patch adds a basic test for the DataTable widget.

Make debugging tests in a debugger easier.

Fixes https://github.com/flutter/flutter/issues/163

* Disable 'Show Excluded' by default

* Move .iml file inside .idea dir

* Remove pub and build excludions as they are automatically set by the Dart plugin

* Exclude .idea folder (new users will edit it through the IJ UI, not the file)

* Move .iml files into .idea dir to be consistent with template changes

* Add workspace.xml from new template to existing samples

* Update current examples to match template changes for excluding folders

* Add missing flutter.yaml to make sure there are no analysis errors

* Add back .pub and build excludeFolder tags per https://github.com/flutter/flutter-intellij/issues/630#issuecomment-272887230

* Remove workspace.xml from example per review feedback

...now that we have generic methods, their types need to be specified too.

Teach `paints` matches about `drawRect` and how to `paintChild`.

Also, improve test coverage.

See https://github.com/dart-lang/sdk/issues/28463, which I think is a
regression.

This also fixes the regression introduced by
https://codereview.chromium.org/2559773002 whereby we were no longer
checking any of the lints.

Refactor DevFS so that it's easier to add new types of content such as kernel code
* add tests for DevFS package scanning
* add tests for DevFS over VMService protocol
* which covers _DevFSHttpWriter and ServiceProtocolDevFSOperations
* replace AssetBundleEntry and DevFSEntry with DevFSContent
* refactor to cleanup common code and replace some fields with locals
* rework .package file generation refactor away DevFSOperations.writeSource
* only update .package file if it has changed
* only write/delete/evict assets that have been changed/removed

hideText -> obscureText
hideDivider -> !showDivider

This will make it easier to understand what this file does.

Removes some TODOs now that https://github.com/flutter/flutter/issues/3648 is fixed.

Also, synchronize the docs between Navigator.push and NavigatorState.push (and
friends).

This patch aligns the iteration patterns used by animations and
ChangeNotifier. They now both respect re-entrant removal of listeners
and coalesce duplication registrations. (Also, ChangeNotifier
notification is no longer N^2).

This patch introduces ObserverList to avoid the performance regression that the
previous version of this patch caused.

Fixes #7533

MockCanvas to use it instead.

Currently it only supports a very limited set of drawing features, but
adding new ones is easy.

Once the feature set is more complete, and we've used this a bunch, if
it feels right, this API will get promoted to flutter_test.

Also, fix some minor bugs with SynchronousFuture.

Answers http://stackoverflow.com/questions/41371449/how-do-you-use-a-textpainter-to-draw-text

This patch is part of a series to rationalize our text input classes.

See #7031

* proxy service extension calls through the daemon protocol

* add test for app.callServiceExtension

This brings the feature back, since removing it broke one of our more
exotic sets of customers.

Also, defer to test package for throttling (this will require a test
package update as well).

Also, add a lot more instrumentation to --verbose mode for tests, and
fix minor trivial things here and there, and add error handling in
more places.

Also, refactor how coverage works to be simpler and not use statics.

We expect TextField to be used much more often than Input. This patch updates
our old example code to use TextField instead.

See #7031

This patch is the first of a series to rationalize the names of the text-input
related widgets.

See #7031

The gallery doesn't actually use `package:flutter_markdown`.

When a machine is heavily loaded, it can severely delay the time it
takes for the OS to start a process once it's asked to do so. Our
5 second timeout that we were giving the test process to connect
to the test harness seemed like plenty of time, were it not for the
fact that the test process itself was not being started in time when
CPU throttling was in effect.

This change updates the test timeout to begin counting only once the
test process has been started. We keep the original timeout in play
in the event that the test process *never* starts up for some reason,
but we up that timeout value to 5 minutes.