1. 11 Jun, 2020 1 commit
  2. 08 Jan, 2020 1 commit
  3. 03 Dec, 2019 1 commit
  4. 27 Nov, 2019 1 commit
    • Ian Hickson's avatar
      License update (#45373) · 449f4a66
      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
      449f4a66
  5. 14 Oct, 2019 1 commit
  6. 23 Aug, 2019 1 commit
    • Greg Spencer's avatar
      Normalize assert checking of clipBehavior (#38568) · 365f577c
      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.
      365f577c
  7. 05 Feb, 2019 1 commit
  8. 18 Jan, 2019 1 commit
  9. 10 Jan, 2019 1 commit
    • MH Johnson's avatar
      [Material] Bottom app bar theme (#24156) · 090c3bcd
      MH Johnson authored
      * [WIP] BAB theme
      
      * [WIP] BAB theme
      
      * Update goldens
      
      * Extract helper function in tests
      
      * Update Goldens version
      
      * Add tests
      
      * [WIP] Hans first round comments
      
      * Added test
      
      * Added docs
      
      * Hans second round comments
      
      * Fixed analyzer error
      
      * Hans third round comments
      
      * ambient
      
      * Change [BottomAppBarTheme.of] to static
      
      * Final doc change
      090c3bcd
  10. 18 Dec, 2018 2 commits
  11. 08 Nov, 2018 1 commit
  12. 12 Sep, 2018 1 commit
  13. 07 Sep, 2018 1 commit
  14. 06 Sep, 2018 1 commit
  15. 02 Aug, 2018 1 commit
  16. 27 Jul, 2018 1 commit
  17. 23 Jul, 2018 1 commit
  18. 16 Jul, 2018 2 commits
  19. 21 Jun, 2018 1 commit
    • amirh's avatar
      Move the notch computation from the FAB to the BAB. (#18372) · c39f2f26
      amirh authored
      Move the notch computation from the FAB to the BAB.
      
      The notch in the BAB (bottom action bar) for the FAB (floating action button) was previously kept as part of the FAB's implementation. This was done to keep the shape of the FAB and the shape of the notch coupled.
      That approach resulted in a somewhat complex and 'non Fluttery' mechanism for propagating the notch computation from the FAB to the BAB.
      
      This CL uncouples the FAB and the notch computation.
      With the new API the BAB computes its overall shape including the notch using a NotchedShape delegate.
      
      This includes multiple breaking changes:
        * Scaffold.setFloatingActionButtonNotchFor is deleted.
        * The ComputeNotch type is deleted.
        * The hasNotch property of BottomAppBar is deleted.
        * The notchMargin property of FloatingActionButton is deleted.
      
      Quick migration guide from the previous API:
      
      | Previous API | New API |
      | ------------------|-------------|
      | BottomAppBar(hasNotch: false) | BottomAppBar() |
      | Using a FloatingActionButton with: BottomAppBar() / BottomAppBar(hasNotch: true) | BottomAppBar(shape: CircularNotchedRectangle()) |
      | Scaffold.setFloatingActionButtonNotchFor(..) | No longer supported |
      c39f2f26
  20. 06 Jun, 2018 1 commit
    • amirh's avatar
      _markNeedsClip() when clipper type has changed. (#18248) · 0a26ac09
      amirh authored
      A bug in _RenderCustomClip was compaeing the type of oldClipper to
      itself instead to the type of newClipper.
      
      This was the root cause for the crash #14937 worked around.
      This also reverts the workaround introduced in #14937.
      0a26ac09
  21. 05 Jun, 2018 1 commit
  22. 08 May, 2018 1 commit
  23. 21 Apr, 2018 1 commit
  24. 28 Feb, 2018 1 commit
  25. 26 Feb, 2018 1 commit
  26. 24 Feb, 2018 1 commit
  27. 23 Feb, 2018 1 commit
  28. 22 Feb, 2018 1 commit
  29. 21 Feb, 2018 1 commit
    • amirh's avatar
      Initial implementation of BottomAppBar (#14713) · 7996d7fb
      amirh authored
      * add a FAB NotchMaker to ScaffoldGeometry
      
      * add a notchMaker to FloatingActionButton
      
      * Initial implementation of BottomAppBar
      
      Mainly includes the notch making logic.
      Not yet tested as currently there is no way to make the FAB and the BAB
      overlap, once #14368 to lands we could add unit tests to the
      BottomAppBar as well.
      
      * use a closeable for clearing the FAB notchmaker
      7996d7fb