- 06 Jan, 2023 2 commits
-
-
Alex Wallen authored
Co-authored-by:
a-wallen <stephenwallen@google.com>
-
Jason Simmons authored
-
- 18 Dec, 2022 1 commit
-
-
alanwutang11 authored
* isCanvasKit implement and test * isCanvasKit implement and test * ++ * forgot license * make isCanvasKit a getter * addressed comments * forgot to change names of integration test files * typo * simplified tests * comments
-
- 15 Dec, 2022 1 commit
-
-
Martin Kustermann authored
This improves the documentation of the `compute()` function as follows: * Instead of making `compute` a top-level constant, we make it a function. This allows the generated API docs to show a function signature with parameters and their names, making it *much* clearer to users what function is being documented. * We mention that on web-backends this is running `compute()` on the normal eventloop whereas on on native platforms it runs in a separate isolate. * We mention that callback, message and result have to be sendable across isolates. We also mention that they may be copied. * We link to both `Isolate.run` & `SendPort.send` for more information. * We use `M` for the type of `message` instead the rather confusing `Q`.
-
- 13 Dec, 2022 1 commit
-
-
Michael Thomsen authored
-
- 11 Dec, 2022 1 commit
-
-
Ian Hickson authored
-
- 07 Dec, 2022 1 commit
-
-
Greg Spencer authored
* Add ListenableBuilder with examples * Add tests * Add tests * Fix Test * Change AnimatedBuilder to be a subclass of ListenableBuilder
-
- 29 Nov, 2022 2 commits
-
-
Dan Field authored
-
Michael Thomsen authored
* Ignore NullThrownError deprecation * Fix whitespace
-
- 18 Nov, 2022 1 commit
-
-
chunhtai authored
* Disallow dispose during listener callback * addressing comment * add comments to code * Addressing comments * fix test
-
- 12 Nov, 2022 1 commit
-
-
Dan Field authored
Make FutureBuilder handle SynchronousFuture correctly, reland SynchronousFuture usage in test assets (#115173) * Make FutureBuilder handle SynchronousFuture correctly * Reland "Load assets in flutter_test without turning event loop. (#115123)" (#115156)" This reverts commit 3895786f.
-
- 11 Nov, 2022 2 commits
-
-
Dan Field authored
* Load assets in flutter_test without turning event loop. This makes it possible to load an asset without actually turning the event loop. This is importnat because our FakeAsync zones may cause people to sprinkle in extra pumpAndSettles in when running tests that load assets, which is undesirable. * fix null checking
- 14 Oct, 2022 1 commit
-
-
joshualitt authored
-
- 06 Oct, 2022 1 commit
-
-
alanwutang11 authored
-
- 04 Oct, 2022 1 commit
-
-
joshualitt authored
-
- 29 Sep, 2022 1 commit
-
-
joshualitt authored
-
- 23 Sep, 2022 1 commit
-
-
Casey Hillers authored
-
- 20 Sep, 2022 1 commit
-
-
Polina Cherkasova authored
-
- 19 Sep, 2022 1 commit
-
-
joshualitt authored
-
- 15 Sep, 2022 1 commit
-
-
Polina Cherkasova authored
-
- 12 Sep, 2022 1 commit
-
-
Greg Spencer authored
-
- 10 Sep, 2022 1 commit
-
-
Polina Cherkasova authored
-
- 07 Sep, 2022 2 commits
-
-
Greg Spencer authored
-
Kenzie Davisson authored
-
- 02 Sep, 2022 1 commit
-
-
Pierre-Louis authored
-
- 10 Aug, 2022 1 commit
-
-
Ian Hickson authored
-
- 04 Aug, 2022 1 commit
-
-
chunhtai authored
-
- 03 Aug, 2022 1 commit
-
-
Michael Goderbauer authored
-
- 26 Jul, 2022 1 commit
-
-
Dan Field authored
-
- 20 Jul, 2022 1 commit
-
-
Vyacheslav Egorov authored
* Use persistent hash map to store _inheritedWidgets Instead of using a HashMap and copying it down the tree which leads to quadratic time and space complexity use a persistent data structure which can amortize the cost by sharing parts of the structure. The data shows HAMT based PersistentHashMap to be 5-10x faster for building _inheritedWidgets and considerably more space effecient (e.g. bringing amount of memory allocated when constructing _inheritedWidgets in a tree with 150 InheritedWidget down to 70Kb from 970Kb). PersistentHashMap is slower than HashMap for access: 2-3x in relative terms, but in absolute terms we are only talking about ~0.2ns slow down per access and various app benchmarks we run have have not revealed any significant regressions.
-
- 18 Jul, 2022 1 commit
-
-
Alexandre Ardhuin authored
-
- 27 Jun, 2022 1 commit
-
-
hacker1024 authored
-
- 24 Jun, 2022 1 commit
-
-
Alexandre Ardhuin authored
-
- 16 Jun, 2022 1 commit
-
-
Lasse R.H. Nielsen authored
-
- 09 Jun, 2022 1 commit
-
-
Alexandre Ardhuin authored
-
- 08 Jun, 2022 1 commit
-
-
Alexandre Ardhuin authored
-
- 31 May, 2022 1 commit
-
-
Greg Spencer authored
This reverts part of the change made in #103456 to expose a debug check for subclasses of ChangeNotifier to avoid code duplication. Instead of making debugAssertNotDisposed a public instance function, it is now a public static function. It makes it harder to call, slightly, but it means that everyone who implemented ChangeNotifier instead of extending it doesn't get broken.
-
- 25 May, 2022 1 commit
-
-
Pierre-Louis authored
Use `curly_braces_in_flow_control_structures` for `foundation`, `gestures`, `painting`, `physics` (#104610) * Use `curly_braces_in_flow_control_structures` for `foundation` * Use `curly_braces_in_flow_control_structures` for `gestures` * Use `curly_braces_in_flow_control_structures` for `painting` * Use `curly_braces_in_flow_control_structures` for `physics` * fix comments * remove trailing space * fix TODO style
-
- 19 May, 2022 1 commit
-
-
Greg Spencer authored
This adds a ShortcutsRegistry for ShortcutActivator to Intent mappings that can be modified from its descendants. This is so that descendants can make shortcuts dynamically available to a larger portion of the app than just their descendants. This is a precursor needed by the new MenuBar, for instance, so that the menu bar itself can be placed where it likes, but the shortcuts it defines can be in effect for most, if not all, of the UI surface in the app. For example, the "Ctrl-Q" quit binding would need to work even if the focused widget wasn't a child of the MenuBar. This just provides the shortcut to intent mapping, the actions activated by the intent are described in the context where they make sense. For example, defining a "Ctrl-C" shortcut mapped to a "CopyIntent" should perform different functions if it happens while a TextField has focus vs when a drawing has focus, so those different areas would need to define different actions mapped to "CopyIntent". A hypothetical "QuitIntent" would probably be active for the entire app, so would be mapped in an Actions widget near the top of the hierarchy.
-