8000 [Proposal] - flutter_html Contrib · Issue #323 · Sub6Resources/flutter_html · GitHub
[go: up one dir, main page]

Skip to content
[Proposal] - flutter_html Contrib #323
Closed
@ryan-berger

Description

@ryan-berger

Hello All,

Recently due to the 1.0.0 release I have received a recent influx of issues. Keep them coming! I am personally very busy as I'm working two jobs and will be headed back to college in a few months, so I may not get to them as fast as you may like, but I can definitely review pull requests when I have the time, so the best way to get your issue fixed is to submit a pull and I can take a look. Now, to the title of the issue.

Before @Sub6Resources left to go on a 2 year trip abroad, we had a discussion of a flutter_html_lite library that had very basic support for the very basic rendering of html, with little to no customization, and keeping this as a fork or using it as a dependency. This still may be happening with me at the helm, so keep watching for an announcement for it. Recently, however, I think that I've realized we may want to go the opposite direction as well. I want to make things more feature packed/complicated!

I know that sounds crazy, but let me explain. I've noticed throughout all the many issues that you all have submitted, that, although there are some annoying features that are missing, or limitations of the library that are hard to deal with, a lot of issues can be solved by registering customRenderer. But I get it! That's annoying!

So, here's my proposal:

I propose that flutter_html gets a sister library named something like flutter_html_contrib where we hold a carefully crafted and curated collection of widgets ready to be used as a customRenderer. It can allow flutter_html to stay simple and limited in its featureset, but still allow everyone to extend it to the many different use cases that you all have because it sure is hard to keep up with all of them and make sure that flutter_html is a cohesive library!

I would really like everybody's feedback on this. What do you think are the costs and benefits of the decision? Would you rather see features added instead of making any headway with this library? If we decide we want to do it, would you want me to find an extra maintainer!

Discuss away!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0