- 11 Feb, 2020 1 commit
-
-
Jonah Williams authored
-
- 28 Jan, 2020 1 commit
-
-
Jenn Magder authored
-
- 06 Jan, 2020 1 commit
-
-
Jonah Williams authored
-
- 04 Dec, 2019 2 commits
-
-
Emmanuel Garcia authored
-
Emmanuel Garcia authored
-
- 03 Dec, 2019 4 commits
-
-
Jonah Williams authored
-
Jonah Williams authored
This reverts commit 3b2042a0.
-
Jonah Williams authored
-
Jonah Williams authored
-
- 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
-
- 22 Nov, 2019 1 commit
-
-
Greg Spencer authored
No code changes, just comments: I spell-checked all the comments in the repo.
-
- 19 Nov, 2019 1 commit
-
-
Alexandre Ardhuin authored
* implicit-casts:false on flutter_tools/lib * address review comments * use castStringKeyedMap * introduce {bool,string,strings}Arg * fix ci
-
- 08 Nov, 2019 3 commits
-
-
Jonah Williams authored
-
Jonah Williams authored
This reverts commit e5d6d924.
-
Jonah Williams authored
-
- 07 Nov, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 30 Oct, 2019 1 commit
-
-
stuartmorgan authored
The environment variable for all desktop platforms is currently ENABLE_FLUTTER_DESKTOP to allow backward compatibility with existing workflows. However, this is actually causing issues since 'flutter config' provides a better experience (most importantly, IDEs will work correctly, which is generally not the case with the environemnt variable). Currently people following old (third-patry) instructions don't realize that they are missing available functionality, so aren't looking for the current instructions. In adddition, this will be confusing as different platform graduate to channels other than master at different times. To resolve both issues, the environment variable fallback is now separate for each desktop platform, and follows a naming scheme consistent with the web environment variable.
-
- 23 Oct, 2019 1 commit
-
-
Jonah Williams authored
-
- 17 Oct, 2019 1 commit
-
-
Emmanuel Garcia authored
* Test the Android embedding v2 * Update integration tests * Split into shards
-
- 09 Oct, 2019 1 commit
-
-
Jonah Williams authored
-
- 04 Oct, 2019 1 commit
-
-
Emmanuel Garcia authored
* Generate projects using the new Android embedding * Add comment about usesNewEmbedding:true * Feedback * Rework way to detect new embedding in new apps
-
- 24 Sep, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 23 Sep, 2019 1 commit
-
-
Emmanuel Garcia authored
This reverts commit 96482eeb.
-
- 20 Sep, 2019 1 commit
-
-
Emmanuel Garcia authored
-
- 26 Jul, 2019 1 commit
-
-
Michael Klimushyn authored
* Roll back the AAR build experiment This has been breaking flutter/plugins CI for the past day. * Remove integration tests that rely on the AAR flag
-
- 25 Jul, 2019 1 commit
-
-
Jonah Williams authored
* adjust phrasing of features * word smithing * more wordsmithing
-
- 23 Jul, 2019 3 commits
-
-
Emmanuel Garcia authored
`flutter build aar` This new build command works just like `flutter build apk` or `flutter build appbundle`, but for plugin and module projects. This PR also refactors how plugins are included in app or module projects. By building the plugins as AARs, the Android Gradle plugin is able to use Jetifier to translate support libraries into AndroidX libraries for all the plugin's native code. Thus, reducing the error rate when using AndroidX in apps. This change also allows to build modules as AARs, so developers can take these artifacts and distribute them along with the native host app without the need of the Flutter tool. This is a requirement for add to app. `flutter build aar` generates POM artifacts (XML files) which contain metadata about the native dependencies used by the plugin. This allows Gradle to resolve dependencies at the app level. The result of this new build command is a single build/outputs/repo, the local repository that contains all the generated AARs and POM files. In a Flutter app project, this local repo is used by the Flutter Gradle plugin to resolve the plugin dependencies. In add to app case, the developer needs to configure the local repo and the dependency manually in `build.gradle`: repositories { maven { url "<path-to-flutter-module>build/host/outputs/repo" } } dependencies { implementation("<package-name>:flutter_<build-mode>:1.0@aar") { transitive = true } }
-
Emmanuel Garcia authored
This reverts commit 11460b83.
-
Emmanuel Garcia authored
`flutter build aar` This new build command works just like `flutter build apk` or `flutter build appbundle`, but for plugin and module projects. This PR also refactors how plugins are included in app or module projects. By building the plugins as AARs, the Android Gradle plugin is able to use Jetifier to translate support libraries into AndroidX libraries for all the plugin's native code. Thus, reducing the error rate when using AndroidX in apps. This change also allows to build modules as AARs, so developers can take these artifacts and distribute them along with the native host app without the need of the Flutter tool. This is a requirement for add to app. `flutter build aar` generates POM artifacts (XML files) which contain metadata about the native dependencies used by the plugin. This allows Gradle to resolve dependencies at the app level. The result of this new build command is a single build/outputs/repo, the local repository that contains all the generated AARs and POM files. In a Flutter app project, this local repo is used by the Flutter Gradle plugin to resolve the plugin dependencies. In add to app case, the developer needs to configure the local repo and the dependency manually in `build.gradle`: repositories { maven { url "<path-to-flutter-module>build/host/outputs/repo" } } dependencies { implementation("<package-name>:flutter_<build-mode>:1.0@aar") { transitive = true } }
-
- 17 Jul, 2019 1 commit
-
-
Jonah Williams authored
-