Consider alternative package naming

[seanrmurphy]

In #3 there was some discussion of naming of modules - moving discussion to separate issue.

Original point by @seanrmurphy:

"Note that I decided to modify package names in my fork - I did not like the fact that the original
repo contained an elem package which had a clash with the vecty package of the same name (obviously); I also introduced the svgtypes package as the home for these higher level abstractions."

Response by @nathanhack

"Starting from the top, to comment on the package naming. One of my hopes is this repo be the testing ground for SVG in vecty and eventually some form of it merged into vecty. At which point the names of the packages will most likely change. Until then I wanted to keep them inline with svg type. One of the nice things about golang is the aliasing, so users can rename the package to what ever they want in their programs. Hopefully that help explain what I did and mostly why :-). That said, I'm not completely married to package names or directory structure. Any thoughts on the topic are welcomed, especially when it makes for more readable code."

[seanrmurphy]

Absolutlely makes sense to get this work integrated with vecty.

My issue with the current naming of the svg/elem is that it clashes with the vecty/elem package which contains autogenerated generator functions for all defined HTML tags; as such, I see svg/elem being quite different and hence suggest it should be named differently. Using svg/svgelem is perhaps not very inspired, but it's clear what it contains.

Regarding your point about golang providing support for package aliasing - I tend to think being (almost) required to use aliasing in a typical context (where vecty elements and svg elements would be used together) is suboptimal; using such aliasing should be used for exceptional cases or as an optional optimization for style/brevity imo.

[nathanhack]

I think your points are valid.
I will think about it over the next several days, and if nothing comes to me, I'll be switching to svgelem. If other alternatives come to you please share.