Code generation support about flutter_svg HOT 7 CLOSED

I do not intend to work on this anymore, and am instead looking into working on a new package (https://github.com/dnfield/vector_graphics) that captures the spirit of this issue.

from flutter_svg.

@dnfield wow pretty cool.

Can you please design this so we can still use runtime building. Compile time building is great for stuff you know wont change, but runtime is really useful because i am working on using the SVG package with with HTML Flutter. Togather i get the ability to have everything interpreted at runtime.

from flutter_svg.

I have no plans to deprecate runtime loading/rendering. This would basically just allow for parsing and generating the Drawable at compile time

from flutter_svg.

See also https://github.com/dnfield/flutter_built_path

from flutter_svg.

It's looking like to do this sensibly will require decoupling the parsing logic a bit more.

Just want to make sure to not bloat up memory requirements when doing so...

from flutter_svg.

This is blocked by #47 - not so much because of DOM, but because parsing needs to be rewritten a bit to make this make sense.

from flutter_svg.

Hi there,
any progress on that? I've read a bit in your other repos (like flutter_built_path or flutter_path_drawing) but they seem to only apply to paths. I'd like to throw entire svg's into it and do its thing.

Am I just missing something in the other repos?

from flutter_svg.