- 04 Dec, 2019 1 commit
-
-
Greg Spencer authored
* Add a density attribute to ThemeData * Simplify tests * Review changes (Hans)
-
- 27 Nov, 2019 1 commit
-
-
Ian Hickson authored
* 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
-
- 01 Nov, 2019 1 commit
-
-
NikitaZhelonkin authored
* Wire enableFeedback parameter through MaterialButton, RawMaterialButton, and IconButton. Co-Authored-By:
Shi-Hao Hong <shihaohong@google.com>
-
- 30 Oct, 2019 1 commit
-
-
Bernardo Ferrari authored
* Add onLongPress to Buttons. * Button enabled status will now respond to onLongPress
-
- 10 Sep, 2019 1 commit
-
-
Greg Spencer authored
Fixed passing autofocus to MaterialButton, and when rebuilding Focus widget, and added a test for Focus and MaterialButton to test that it works properly.
-
- 23 Aug, 2019 1 commit
-
-
Greg Spencer authored
I noticed that we were pretty inconsistent with the way that we checked the value of clipBehavior in the framework, so I normalized the usages and updated docs where necessary. This is a breaking change if you used to pass null explicitly to FlatButton, OutlineButton or RaisedButton constructors, expecting to get Clip.none. It will now assert if you do that. Existing implementations that pass null implicitly by not specifying clipBehavior won't need to change their call sites. It always implicitly defaulted to Clip.none before, and it will continue to do that, it's only places where it was explicitly set to null in order to get the implicit default that it will fail.
-
- 15 Aug, 2019 1 commit
-
-
Greg Spencer authored
Add an autofocus parameter to widgets which use Focus widget internally, and update related docs. This will allow developers to request that a particular widget be automatically focused when shown.
-
- 17 Jul, 2019 1 commit
-
-
Shi-Hao Hong authored
* Add clarifying docs on MaterialButton.colorBrightness
-
- 28 Jun, 2019 3 commits
-
-
MH Johnson authored
Re-land "[Material] Support for hovered, focused, and pressed border color on `OutlineButton`s" (#35278) * outline border implements material state property
-
Todd Volkert authored
Revert "[Material] Support for hovered, focused, and pressed border color on `OutlineButton`s (#34872)" (#35276) This reverts commit 3f941599.
-
MH Johnson authored
* outline border implements material state property
-
- 13 Jun, 2019 1 commit
-
-
Michael Goderbauer authored
-
- 05 Jun, 2019 1 commit
-
-
MH Johnson authored
* Support for stateful text colors in buttons * Add color and a11y tests for buttons
-
- 15 May, 2019 1 commit
-
-
Greg Spencer authored
This implements focus and hover handling for Material buttons. It inserts Focus widgets into the tree in order to allow buttons to be focusable via keyboard traversal (a.k.a. TAB traversal), and Listener widgets into the InkWell to allow the detection of hover states for widgets. Addresses #11344, #1608, and #13264.
-
- 05 Apr, 2019 1 commit
-
-
Hans Muller authored
-
- 21 Mar, 2019 1 commit
-
-
Rubens de Melo authored
-
- 12 Mar, 2019 1 commit
-
-
Hans Muller authored
-
- 15 Jan, 2019 1 commit
-
-
Ian Hickson authored
Previously, a disabled floating action button always had zero elevation, which looks dumb. This also fixes the issue whereby highlightElevation was not honoured on floating action buttons. This also fixes an issue I found during testing whereby setState was being called during build when onHighlightChanged fired due to onPressed becoming null while a gesture is ongoing (which triggers an onTapCancel synchronously during build).
-
- 18 Dec, 2018 2 commits
-
-
Alexandre Ardhuin authored
-
Michael Goderbauer authored
-
- 16 Oct, 2018 1 commit
-
- 12 Oct, 2018 2 commits
-
-
matthew-carroll authored
This reverts commit 80f80ab0.
-
matthew-carroll authored
For G3 Roll: * Revert "MaterialButton must honor its minWidth and height parameters (#22919)" This reverts commit a0233233. * Revert "Update uses of ButtonTheme.bar: pass along the current Theme's colorScheme (#22827)" This reverts commit 655bf6a2. * Revert "ButtonTheme.of().colorScheme defers to Theme (#22880)" This reverts commit a590940e. * Revert "Bring TextTheme into alignment with the current Material spec (#22330)" This reverts commit 8bfb4b3e. * Revert "Added ColorScheme, updated ThemeData, ButtonTheme, material buttons (#22013)" This reverts commit eea3465a. * Manual adjustments to fix reversion issues.
-
- 11 Oct, 2018 1 commit
-
-
Hans Muller authored
-
- 08 Oct, 2018 1 commit
-
-
liyuqian authored
We'll roll this back as soon as the Dart analyzer gets upgraded in Google3.
-
- 02 Oct, 2018 1 commit
-
-
Hans Muller authored
Introduce an overall material "color scheme" and to make it possible to redefine how a component's visual properties bind to the color scheme and to the existing material Theme.
-
- 21 Feb, 2016 1 commit
-
-
Adam Barth authored
These files are already in the "material" folder. They don't need to be prefixed with material again. Fixes #702
-
- 14 Feb, 2016 1 commit
-
-
Ian Hickson authored
Fixes https://github.com/flutter/flutter/issues/1331 Hopefully this will be enough to start with. If this continues to be a point of confusion we can see about adding more documentation or changing the API somehow.
-
- 09 Feb, 2016 1 commit
-
-
Hans Muller authored
-
- 07 Jan, 2016 1 commit
-
-
Ian Hickson authored
Make ancestorStateOfType() and ancestorRenderObjectOfType() support subclassing. Fixes https://github.com/flutter/flutter/issues/1087
-
- 11 Dec, 2015 1 commit
-
-
Adam Barth authored
- Adds dartdoc for all the `of` functions. - Renames Image to RawImage. This widget is rarely used and shouldn't take up such a nice global name. Fixes #361
-
- 08 Dec, 2015 1 commit
-
-
Adam Barth authored
After this patch, if you try to use a widget that depends on being enclosed in a material, you now get an assert and a debugPrint if you're not inside a material. Fixes #243
-
- 01 Dec, 2015 1 commit
-
-
Ian Hickson authored
-
- 18 Nov, 2015 2 commits
-
-
Hans Muller authored
Shadows now render as three seprate MaskFilter.blur components per the most recent Material spec. The shadows Map was replaced by a similar Map called elevationToShadow with entries that match the 10 elevations specifed by http://www.google.com/design/spec/what-is-material/elevation-shadows.html. The "level" property (many classes) is now called "elevation", to match the Material spec. BoxShadow now includes a spreadRadius parameter - as in CSS box-shadow. Renamed the BoxShadow blur property to blurRadius to further align BoxShadow with CSS box-shadow.
-
Hixie authored
I'm planning on adding more .of() functions and so to avoid further copypasta I'm providing some general utility functions here.
-
- 06 Nov, 2015 1 commit
-
-
Hans Muller authored
-
- 27 Oct, 2015 3 commits
-
-
Adam Barth authored
Previous these callbacks were leaking the implementation detail that they were triggered by taps. In a later patch, we're going to add a parameter to GestureTapCallback that these callbacks won't have. Related to #1807
-
Hixie authored
Instread of an explicit 'enabled' bool, this uses the presence of the event handler to determine if a widget is enabled or not. This means that if you've not passed a handler, your widget will be disabled, which makes sense, since it wouldn't work anyway. Adds this feature to checkbox, and ports raised button, flat button, and radio buttons to this new model. Adds a checkbox to card_collection that can be disabled. Hide a (basically bogus) hint from the (soon to be disabled) strong hint mode in the analyzer that this reveals.
-
Hixie authored
-
- 18 Oct, 2015 1 commit
-
-
Hixie authored
- truncate pixel values to 1dp since there's really no point being told the Size is 302.98732587287 by 648.28498579187. - describe more Widgets so that debugDumpApp() is more useful. - remove bufferValue from ProgressIndicator (cc @hansmuller) since it's not yet implemented. - half-hearted toString() for ThemeData. There's no point making a complete one, since it would cause line-wrap even on big monitors in debugDumpApp dumps, and you can easily get the actual values from a debugging if that's the issue. - flesh out BoxConstraints.toString() so that fully unconstrained and fully infinite constraints are called out explicitly. I experimented with adding even more special cases, e.g. calling out unconstrained widths with fixed heights, etc, but it made the output less readable. - remove a redundant _updateVariable() in AnimatedContainer (cc @abarth). - add more information to RenderView.toString().
-