Own HTML parser package #562
Comments
|
I think what you're asking for is modularisation, such that at the core can render basic tags and perform some styling, yes dependencies such as webview, svg, audio and video are opt in. This is indeed very important and we have a discussion issue on this already. I also have a good idea how to do this (though I wouldn't call it easy...). We wanted to get the library is a healthy (if big) state first, and deal with the hundreds of issues that were open. As of 1.3.0 we have mostly done that, so the time is almost there. Just nullability and some bug fixing will come first. |
|
Of course, it wouldn't be easy but it would bring a huge amount of value for a manageable amount of work. We enjoy using ´flutter_html´ a lot and adding the ability to use the HTML parsing part without adding those dependencies and providing the extra amount of flexibility would be really nice. |
|
Absolutely. Fully agreed. |
It would be great to separate the HTMLParser and all its logic into a separate package.
Often we just need to display a handful of different html elements in our apps. By adding the
flutter_htmlpackage to a project we also get a bunch of dependencies we might never need, like chewie_audio or css_colors (which wasn't touched since 2018 btw.)The idea is to create a Widget that takes a Map of styles for the converted widgets and a Map of custom renderers to also render html elements in a completely customizable way. The flutter_html package uses this separate package for rendering and building the given html elements and applying the default styling.
This wouldn't be that much work and would allow users to use this already nice package without adding unneeded dependencies to their projects.
The text was updated successfully, but these errors were encountered: