Skip to content

Document pub from Flutter's perspective #10070

Closed

Description

@eseidelGoogle

We seem to have some confusion.

For example, this dart-only package used the Flutter plugin template and thus has needless obj-c/android code:
https://github.com/perlatus/flutter_zoomable_image/tree/master/ios/Classes

Yet as far as I can tell, never calls that code:
https://github.com/perlatus/flutter_zoomable_image/blob/master/lib/src/zoomable_image.dart

This seems like a reasonable thing for this user to have done, since we don't really talk about packages? :)

Activity

  1. sethladd commented on May 13, 2017

    @sethladd
    Contributor

    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?

  2. eseidelGoogle commented on May 13, 2017

    @eseidelGoogle
    ContributorAuthor

    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

  3. perlatus commented on May 14, 2017

    @perlatus
    Contributor

    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.

  4. Hixie commented on May 14, 2017

    @Hixie
    Contributor

    https://pub.dartlang.org/packages/flutter_markdown is an example of a non-plugin flutter package.

  5. 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
  6. sethladd commented on May 25, 2017

    @sethladd
    Contributor

    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).

  7. self-assigned this
    on May 29, 2017
  8. mit-mit commented on May 29, 2017

    @mit-mit
    Member

    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

  9. sethladd commented on May 30, 2017

    @sethladd
    Contributor

    sgtm re: #10377

  10. 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
  11. github-actions commented on Sep 4, 2021

    @github-actions

    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.

  12. locked as resolved and limited conversation to collaborators on Sep 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions