| commit | fdab8546a0f652061ce633043efd6b06ee14191c | [log] [tgz] |
|---|---|---|
| author | Ian Hickson <ian@hixie.ch> | Wed Jan 06 16:15:05 2021 -0800 |
| committer | GitHub <noreply@github.com> | Wed Jan 06 16:15:05 2021 -0800 |
| tree | 385449c4351815e27f99f738dc4c1c10c3bbf780 | |
| parent | 50dfd137ef5b544b9a56c0d22321aaf94e430e88 [diff] |
Minor doc, style, and perf updates to Navigator/Routes (#71689) * Minor doc, style, and perf updates to Navigator/Routes These are minor fixes I ended up making while working on a larger project that never went anywhere. - Used a ColoredBox instead of a DecoratedBox for ModalBarrier (probably a trivial memory/perf win). - A bunch of Navigator documentation fixes around when things rebuild. - Mark routes dirty when the Navigator has a dependency change. I cannot find a way to test this because as far as I can tell it makes no actual difference to when things rebuild because whenever the Navigator rebuilds the Overlay rebuilds and whenever that happens every OverlayEntry rebuilds, but in theory that's not guaranteed so this is sort of a correctness fix. It may even be a perf loss. We do something similar in didUpdateWidget already. I could be convinced to maybe remove these... - Make ModalRoute.filter public like everything else. - Made ModalRoute update its barrier when it gets an update, in case e.g. the modal barrier depends on inherited widgets via the navigator context. Again, not sure of any way to detect this, it might actually be moot, but it seems to be the technically correct solution? - Minor style fixes. All in all I couldn't figure out a way to test any of this (I wrote multiple large tests but it turns out they all already pass on master and are effectively redundant with existing tests). * Remove extraneous blank line
Flutter is Google's SDK for crafting beautiful, fast user experiences for mobile, web, and desktop from a single codebase. Flutter works with existing code, is used by developers and organizations around the world, and is free and open source.
For announcements about new releases and breaking changes, follow the flutter-announce@googlegroups.com mailing list or see the breaking changes page.
We think Flutter will help you create beautiful, fast apps, with a productive, extensible and open development model.
We want to enable designers to deliver their full creative vision without being forced to water it down due to limitations of the underlying framework. Flutter's layered architecture gives you control over every pixel on the screen and its powerful compositing capabilities let you overlay and animate graphics, video, text, and controls without limitation. Flutter includes a full set of widgets that deliver pixel-perfect experiences on both iOS and Android.
Flutter is fast. It's powered by the same hardware-accelerated 2D graphics library that underpins Chrome and Android: Skia. We architected Flutter to support glitch-free, jank-free graphics at the native speed of your device. Flutter code is powered by the world-class Dart platform, which enables compilation to 32-bit and 64-bit ARM machine code for iOS and Android, as well as JavaScript for the web and Intel x64 for desktop devices.
Flutter offers stateful hot reload, allowing you to make changes to your code and see the results instantly without restarting your app or losing its state.
Flutter works with any development tool (or none at all) but includes editor plug-ins for both Visual Studio Code and IntelliJ / Android Studio. Flutter provides thousands of packages to speed your development, regardless of your target platform. And accessing other native code is easy, with support for both FFI and platform-specific APIs.
Flutter is a fully open-source project, and we welcome contributions. Information on how to get started can be found at our contributor guide.