1. 01 Feb, 2020 1 commit
  2. 31 Jan, 2020 2 commits
  3. 27 Jan, 2020 1 commit
  4. 18 Jan, 2020 1 commit
  5. 16 Jan, 2020 1 commit
  6. 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
  7. 23 Nov, 2019 1 commit
  8. 20 Nov, 2019 1 commit
  9. 19 Nov, 2019 1 commit
  10. 18 Nov, 2019 2 commits
  11. 15 Nov, 2019 1 commit
  12. 14 Nov, 2019 1 commit
  13. 06 Nov, 2019 2 commits
  14. 28 Oct, 2019 1 commit
  15. 21 Aug, 2019 1 commit
  16. 09 Aug, 2019 2 commits
  17. 28 May, 2019 1 commit
  18. 09 Mar, 2019 1 commit
  19. 17 Oct, 2018 1 commit
  20. 05 Oct, 2018 2 commits
  21. 12 Sep, 2018 1 commit
  22. 01 Feb, 2018 1 commit
  23. 09 Dec, 2017 1 commit
  24. 01 Jun, 2017 1 commit
  25. 25 May, 2017 2 commits
    • Chris Bracken's avatar
      Support inactive, suspending AppLifecycleStates (#10306) · 9452a344
      Chris Bracken authored
      * Rolls the engine to 75c74dc463d56e17be10315cfde409010fd8f90b.
      * Adds framework support for the `AppLifecycleState.inactive` and `AppLifecycleState.suspending` states.
      
      What are the new states?
      ------------------------
      * `AppLifecycleState.inactive` is emitted on iOS only and corresponds to iOS's foreground inactive state. Current iOS state transitions are:
      `resumed` <--> `inactive` <--> `paused`
      
      * `AppLifecycleState.suspending` is currently emitted on Android only and corresponds to the
      transition to Android's stopped state. Current Android state transitions are:
      `resumed` <--> `paused` --> `suspending` --> `resumed`
      
      These transitions may change in future.
      
      This is a breaking change on iOS
      --------------------------------
      
      This changes the semantics of the `AppLifecycleState.paused` state on
      iOS. The behaviour associated with this state is unchanged on Android.
      
      For background on iOS application states see the state transition
      diagram in the [App Programming Guide for iOS](https://developer.apple.com/library/content/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/TheAppLifeCycle/TheAppLifeCycle.html#//apple_ref/doc/uid/TP40007072-CH2-SW6).
      
      On iOS, prior to this change, `AppLifecycleState.paused` corresponded to
      a transition to the _foreground inactive_ state. It now corresponds to a
      transition to the _background state_. The newly-added
      `AppLifecycleState.inactive` state now corresponds to entering the
      _foreground inactive_ state, which (currently) has no exact analogue on
      Android.
      
      Briefly, the _foreground inactive_ state is the state entered when
      switching from an app to the app switcher, receiving a phone call, or
      responding to a TouchID request. Apps are permitted to continue
      animating/updating views in this state if desired. From the _foreground
      inactive_ state, the app may transition back to _active_ (e.g., entering
      the app switcher then resuming the app), or to the _background_ state
      (e.g., switching to the home screen or another app).
      
      What to change
      --------------
      If your app does not handle the `AppLifecycleState.paused` state in a
      `WidgetsBindingObserver.didChangeAppLifecycleState` implementation, no
      changes are required.
      
      If you do handle `AppLifecycleState.paused`, you may additionally wish
      to also handle `AppLifecycleState.inactive`. For example, games should
      probably pause on entering the app switcher rather than wait to be
      backgrounded.
      
      More details
      ------------
      For background on Android application states see the state transition
      diagram in the [Android Activity Lifecycle docs](https://developer.android.com/guide/components/activities/activity-lifecycle.html#alc).
      9452a344
    • Chris Bracken's avatar
      7566f73d
  26. 18 Apr, 2017 1 commit
  27. 15 Mar, 2017 1 commit