carrascomj / bevy_svg_map Goto Github PK

svgtypes provide a well covered amount of SVG paths as PathSegments.

Feature track

From easier to more difficult to implement (and as it svgtypes in the source code)

• MoveTo
• LineTo (at bevy-lyon branch)
• HorizontalLineTo (at bevy-lyon branch)
• VerticalLineTo (at bevy-lyon branch)
• CurveTo (at bevy-lyon branch)
• SmoothCurveTo
• Quadratic (at bevy-lyon branch)
• SmoothQuadratic
• EllipticalArc (at bevy-lyon branch)
• ClosePath (at bevy-lyon branch)

https://bevyengine.org/learn/book/migration-guides/0.4-0.5

The way is handled now

• Convert every coordinate from the SVG into positive coordinates.
• Translate every coordinate to the center; that is, calculate the maximum x, y coordinates and substract max(x)/2 and max(y) /2 to each coordinate.

This works under the assumption that the SVG is on pixels and scaled to 1.0.

Feature

Work with relative paths (like the bottom line in the image at the top of the README, which is quite off).

Now that we're targeting bevy 0.4, updating the published version on crates.io would be good.

Such as id and class.

The scale in the input SVG document is just ignored and assumed to be 1. Make sure that everything is scaled properly.

Add the example that generates the README.

https://github.com/bevyengine/bevy/blob/v0.4.0/CHANGELOG.md

Description

load_svg should get all visual properties (not just stroke) in the final properites.

How to

It is just a matter of defining more methods (with defaults) in the StyleStrategy trait and redefine them (or not) for the Struct: StyleStrategy that load_svg uses