Closed kimikage closed 4 years ago
BTW, ProfileSVG does not fully utilize the functions of Snap.svg. Now that the SVG support on major browsers is "somewhat" stable, I don't think we need to use Snap.svg.
Umm, the official Snap.svg v0.3.0 also fails initialization, and go to #4.:confused: Reluctantly (cf. #8), I will modify the JavaScript code first.
ProfileSVG uses Snap.svg to support interactive functions.
Snap.svg is available under an Apache License 2.0, which is "free" and compatible with ProfileSVG's MIT license. However, the SVG files output by ProfileSVG do not have any license-related description, even though the Snap.svg code is embedded in the SVG files as is.
I prefer to use the min.js file with the license header which is distributed in the official repository.
FYI, it did not work with the final release (v0.5.1). ProfileSVG seems to use Snap.svg v0.3.0.
Edit: I don't think ProfileSVG itself is a "derivative work" of Snap.svg.