This PR is to include `CarouselView` to M3 demo app.
https://github.com/user-attachments/assets/7db76c06-aa7e-4461-9baa-51fd5c4e6b38
## Pre-launch Checklist
- [x] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [x] I signed the [CLA].
- [x] I read the [Contributors Guide].
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] All existing and new tests are passing.
---------
Co-authored-by: Eric Windmill <ewindmill@google.com>
This adds a sample Flutter project that demonstrates a
soon-to-be-released feature, asset transformation[^1]. [PR for
flutter.dev
documentation](https://github.com/flutter/website/pull/10471).
This feature isn't the easiest to explain using documentation, so I
think augmenting that documentation with a sample is appropriate.
This sample demonstrates 1) how to use an existing Dart package (that is
compatible with the feature) as an asset transformer and 2) how to write
a Dart package that is compatible with this feature. This should be
clear from the README.md.
**Advice for reviewing this PR.** The goal here is that most users that
read the documentation and follow the link from there to this sample
should be able to figure out what the feature does and how to use it.
Try to imagine yourself in this position and follow this story. If the
feature is still unclear, then there is probably something we can do to
improve this sample or the docs. Said more simply, follow these steps:
1) Start at the new section to be added to Flutter.dev
(https://flutter-docs-prod--pr10471-document-asset-transformers-cc21qf01.web.app/ui/assets/assets-and-images#automatic-transformation-of-asset-files-at-build-time).
It should naturally link you to the sample project. Start with the
README and see if things make sense.
## Pre-launch Checklist
- [X] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [X] I signed the [CLA].
- [X] I read the [Contributors Guide].
- [X] I updated/added relevant documentation (doc comments with `///`).
- [X] All existing and new tests are passing.
If you need help, consider asking for advice on the #hackers-devrel
channel on [Discord].
<!-- Links -->
[Flutter Style Guide]:
https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo
[CLA]: https://cla.developers.google.com/
[Discord]: https://github.com/flutter/flutter/wiki/Chat
[Contributors Guide]:
https://github.com/flutter/samples/blob/main/CONTRIBUTING.md
[^1]: If you are super curious about this feature, see [the tracking
issue for its
implementation](https://github.com/flutter/flutter/issues/143348).
---------
Co-authored-by: Eric Windmill <eric@ericwindmill.com>
Adding the demo app from my I/O talk. Because AI.
## Pre-launch Checklist
- [x] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [x] I signed the [CLA].
- [x] I read the [Contributors Guide].
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] All existing and new tests are passing.
---------
Co-authored-by: Brett Morgan <brett.morgan@gmail.com>
Adds two new samples that use the Google Generative AI SDK for Dart.
Both were created by @rodydavis. I'm merely the uploader so to speak.
## Pre-launch Checklist
- [X] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [X] I signed the [CLA].
- [X] I read the [Contributors Guide].
- [X] I updated/added relevant documentation (doc comments with `///`).
- [X] All existing and new tests are passing.
Fixes#2088
## Pre-launch Checklist
- [x] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [x] I signed the [CLA].
- [x] I read the [Contributors Guide].
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] All existing and new tests are passing.
---------
Co-authored-by: Brett Morgan <brett.morgan@gmail.com>
Now that the context menu code is on stable, move the sample out of
experimental.
Fixes https://github.com/flutter/samples/issues/2110
## Pre-launch Checklist
- [x] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [x] I signed the [CLA].
- [x] I read the [Contributors Guide].
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] All existing and new tests are passing.
---------
Co-authored-by: Brett Morgan <brett.morgan@gmail.com>
*Replace this paragraph with a description of what this PR is changing
or adding, and why. Consider including before/after screenshots.*
*List which issues are fixed by this PR. For larger changes, raising an
issue first helps
reduce redundant work.*
## Pre-launch Checklist
- [ ] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [ ] I signed the [CLA].
- [ ] I read the [Contributors Guide].
- [ ] I updated/added relevant documentation (doc comments with `///`).
- [ ] All existing and new tests are passing.
If you need help, consider asking for advice on the #hackers-devrel
channel on [Discord].
<!-- Links -->
[Flutter Style Guide]:
https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo
[CLA]: https://cla.developers.google.com/
[Discord]: https://github.com/flutter/flutter/wiki/Chat
[Contributors Guide]:
https://github.com/flutter/samples/blob/main/CONTRIBUTING.md
Bumps [jni](https://github.com/dart-lang/jnigen) from 0.6.1 to 0.7.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/dart-lang/jnigen/releases">jni's releases</a>.</em></p>
<blockquote>
<h2>package:jni v0.7.0</h2>
<ul>
<li><strong>Breaking Change</strong> (<a href="https://redirect.github.com/dart-lang/jnigen/issues/387">#387</a>): Added <code>JBuffer</code> and <code>JByteBuffer</code> classes as default classes for <code>java.nio.Buffer</code> and <code>java.nio.ByteBuffer</code> respectively.</li>
<li><strong>Breaking Change</strong>: Made the type classes <code>final</code>.</li>
<li>Fixed a bug where <code>addAll</code>, <code>removeAll</code> and <code>retainAll</code> in <code>JSet</code> would run their respective operation twice.</li>
<li>Fixed a bug where <code>JList.insertAll</code> would not throw the potentially thrown Java exception.</li>
</ul>
<h2>package:jnigen v0.7.0</h2>
<ul>
<li><strong>Breaking Change</strong> (<a href="https://redirect.github.com/dart-lang/jnigen/issues/387">#387</a>): Added <code>JBuffer</code> and <code>JByteBuffer</code> classes as default classes for <code>java.nio.Buffer</code> and <code>java.nio.ByteBuffer</code> respectively.</li>
<li><strong>Breaking Change</strong>: Made the type classes <code>final</code>.</li>
<li>Added <code>ignore_for_file: lines_longer_than_80_chars</code> to the generated file preamble.</li>
<li>Added an explicit cast in generated <code><Interface>.implement</code> code to allow <code>dart analyze</code> to pass when <code>strict-casts</code> is set.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a href="https://github.com/dart-lang/jnigen/commits/jni-v0.7.0">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
This change removes an unused parameter that was recently removed in the
`RenderEditable` on the `master` branch
https://github.com/flutter/flutter/pull/109114.
Fixes#1923
## Pre-launch Checklist
- [x] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [x] I signed the [CLA].
- [x] I read the [Contributors Guide].
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] All existing and new tests are passing.
---------
Co-authored-by: Brett Morgan <brett.morgan@gmail.com>
- Fixes#1899 - Don't use BuildContext in async.
- Disabled build script for `next-gen-ui-demo` for master channel
because dependency gap does not compile.
- Improve use BuildContext in `place_tracker`, added checks to verify
that the context is still mounted, and avoid passing BuildContext as
parameter.
## Pre-launch Checklist
- [ ] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [ ] I signed the [CLA].
- [ ] I read the [Contributors Guide].
- [ ] I updated/added relevant documentation (doc comments with `///`).
- [ ] All existing and new tests are passing.
If you need help, consider asking for advice on the #hackers-devrel
channel on [Discord].
<!-- Links -->
[Flutter Style Guide]:
https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo
[CLA]: https://cla.developers.google.com/
[Discord]: https://github.com/flutter/flutter/wiki/Chat
[Contributors Guide]:
https://github.com/flutter/samples/blob/main/CONTRIBUTING.md
## Pre-launch Checklist
- [x] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [x] I signed the [CLA].
- [x] I read the [Contributors Guide].
- [x] I updated/added relevant documentation (doc comments with `///`).
- [ ] All existing and new tests are passing.
---------
Co-authored-by: David Iglesias <ditman@gmail.com>
Co-authored-by: Mark Thompson <2554588+MarkTechson@users.noreply.github.com>
Co-authored-by: John Ryan <ryjohn@google.com>
* Added sample code for using plugins and channels from background isolates.
* goderbauer feedback 1
* goderbauer feedback2
* goderbauer feedback 3
* Add `background_isolate_channels` to CI
* Comment in `background_isolate_channels`
* Fixup
* Elide `experimental/material_3_demo` from `master`
* Elide `material_3_demo` from `master` CI
* Elide `place_tracker` on `master` CI
---------
Co-authored-by: Brett Morgan <brettmorgan@google.com>
Co-authored-by: Brett Morgan <brett.morgan@gmail.com>
* added Type Jam puzzle app for review
* pr round 2 prep
* updated ci scripts for varfont_shader_puzzle
* resolved unused and minor variable naming issues
* rotator tiles row and col are final vars now
* removed unused import and print from production
* made constructors const where needed
* pages_flow export refactored to directly come from that file
* removed old api commented out section from FragmentShaded
* updated pubspec yaml to correct project name
* dart min version updated; removed unnecessary commented out dependencies from pubspec.yaml
* updated pubspec.yaml min flutter version to ensure FragmentShader support
* added/edited comments for explanation, esp on var fonts; removed obsolete comments
* trailing newline added to pubspec.yaml eof
