You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So the user journeys is: Create shareable/reusable Flutter code ?
In that article, we can explain what a package is (since we can assume the user doesn't know about dart or pub), what kinds of things can go into packages, how to create a new starter package, how to ensure the ecosystem knows the package is intended for Flutter, and how to mark your package as intended for a particular version/point-in-time for Flutter. Did I miss any other sub-journeys?
Correct. The user journey is to create shareable/reusable flutter code. We explain that today, but only in the context of plugins, and thus I think that's how @perlatus (understandably) ended up with the plugin bits in their dart package.
I believe you've covered all the journeys yes. @mit-mit
Do you have any examples of non-plugin reusable flutter/UI code? If I start deleting the android/iOS bits I can't get the example to run, which is the same problem I had setting up a dart package from scratch.
edit: Basically, having a simple way to spin up a flutter-compatible dart package would be nice.
changed the title [-]flutter.io should explain the difference between a plugin and a package[/-][+]Doc request: user journeys is: Create and consume shareable/reusable Flutter code[/+]on May 22, 2017
We have a product question that we should answer before we write this doc.
Q: What is the best command to run to create a new Flutter package (which, may or may not contain plugins for iOS and Android) ?
Options:
flutter create which may actually work great. Need to test.
stagehand package-flutter which doesn't exist but rides off of stagehand
flutter create --package [--with-plugins] which doesn't exist, but could, if vanilla create doesn't do what we want
The big question is, should the flutter tool provide the package creation magic?
I believe the answer is "yes", so I'd like to first explore if flutter create is sufficient (and doesn't require manualy rejiggering for a package with and without plugins).
I don't think flutter create is a good fit. We don't want android and ios for what should be a "pure-dart Flutter package". I think we need another option in flutter create: #10377
changed the title [-]Doc request: user journeys is: Create and consume shareable/reusable Flutter code[/-][+]Document pub from Flutter's perspective[/+]on May 30, 2017
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
sethladd commentedon May 13, 2017
So the user journeys is: Create shareable/reusable Flutter code ?
In that article, we can explain what a package is (since we can assume the user doesn't know about dart or pub), what kinds of things can go into packages, how to create a new starter package, how to ensure the ecosystem knows the package is intended for Flutter, and how to mark your package as intended for a particular version/point-in-time for Flutter. Did I miss any other sub-journeys?
eseidelGoogle commentedon May 13, 2017
Correct. The user journey is to create shareable/reusable flutter code. We explain that today, but only in the context of plugins, and thus I think that's how @perlatus (understandably) ended up with the plugin bits in their dart package.
I believe you've covered all the journeys yes. @mit-mit
perlatus commentedon May 14, 2017
Do you have any examples of non-plugin reusable flutter/UI code? If I start deleting the android/iOS bits I can't get the example to run, which is the same problem I had setting up a dart package from scratch.
edit: Basically, having a simple way to spin up a flutter-compatible dart package would be nice.
Hixie commentedon May 14, 2017
https://pub.dartlang.org/packages/flutter_markdown is an example of a non-plugin flutter package.
[-]flutter.io should explain the difference between a plugin and a package[/-][+]Doc request: user journeys is: Create and consume shareable/reusable Flutter code[/+]sethladd commentedon May 25, 2017
We have a product question that we should answer before we write this doc.
Q: What is the best command to run to create a new Flutter package (which, may or may not contain plugins for iOS and Android) ?
Options:
flutter createwhich may actually work great. Need to test.stagehand package-flutterwhich doesn't exist but rides off of stagehandflutter create --package [--with-plugins]which doesn't exist, but could, if vanillacreatedoesn't do what we wantThe big question is, should the
fluttertool provide the package creation magic?I believe the answer is "yes", so I'd like to first explore if
flutter createis sufficient (and doesn't require manualy rejiggering for a package with and without plugins).mit-mit commentedon May 29, 2017
I don't think
flutter createis a good fit. We don't wantandroidandiosfor what should be a "pure-dart Flutter package". I think we need another option in flutter create: #10377sethladd commentedon May 30, 2017
sgtm re: #10377
[-]Doc request: user journeys is: Create and consume shareable/reusable Flutter code[/-][+]Document pub from Flutter's perspective[/+]github-actions commentedon Sep 4, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.