Refactor and expand data types.

joseedil commented 4 years ago

This is being done in the refactor-datatypes branch, but it breaks the API.

The rational is the following:

Attributes.hs will hold datatypes for all SVG attributes and attributes groups.
ContentTypes.hs will hold datatypes for all SVG content types. So far those are in CssTypes.hs.
Elements.hs will contain the elements data types.

joseedil commented 4 years ago

Content types: Everything is implemented. Checking against the standard is still required.

[x] \<angle>
[x] \<anything>
[ ] \<basic-shape>
[x] \<clock-value>
[x] \<color>
[x] \<coordinate>
[x] \<frequency>
[x] \<funcIRI>
[x] \<ICCColor>
[x] \<integer>
[x] \<IRI>
[x] \<Length>
[x] \<length-percentage> - This is commented so far in favor of \<length> which includes a percentage format.
[x] \<list-of-Ts>
[x] \<name>
[x] \<number> - This one breaks the parser and almost everything else. Earlier implementation confounded \<number> and \<length>.
[x] \<number-optional-number>
[x] \<opacity-value>
[x] \<paint>
[x] \<percentage>
[x] \<time>
[x] \<transform-list>
[x] \<units> - This is not part of the standard but it is useful to define some attributes.
[x] \<URL>

joseedil commented 4 years ago

Attibutes: this is a big list, here are just what is missing, many of them because of the content types above.

joseedil commented 4 years ago

Those are the SVG elements. Everything is missing so far.

lemmih commented 4 years ago

How much has to be implemented before we can merge this into master?

reanimate / reanimate-svg