README.md previously pointed to binaries on progers's fork. Now that https://github.com/SVG-Edit/svgedit/pull/23 has landed we can update these links to point to the main repository.
This is an update to README.md which merges the main code.googe.com landing page (https://code.google.com/p/svg-edit/) and the existing README.md file.
Actual changes:
* Some editorial license has been used when updating the main project summary, including adding a project logo.
* The recent news section has been updated to include svg-edit 2.8 and the move to github.
* The features section has been dropped as there's no easy way to represent such a list in markdown.
* The further reading section has been updated.
* The dependent projects have been moved to docs/Acknowledgements.md
The binary file links currently point to my github fork. Once we actually create the svg-edit-2.8 release, these should be updated to point to the main project instead of my fork.
The SVGPathSeg API is being removed from the spec [1] and is being
removed in Chromium 47 [2]. I implemented a drop-in polyfill[3] so
svg-edit users are not broken as browsers migrate away from the
path seg api.
This patch simply imports the upstream pathseg.js and updates all
dependencies. With this change all tests pass in Chrome 46 (with
the path seg api), Chrome 47 (without the path seg api), and
there are no changes to tests in Safari 9.01 or Firefox 43. I
also manually tested svg-edit while developing the polyfill and
could not find any broken features.
[1] https://lists.w3.org/Archives/Public/www-svg/2015Jun/0044.html
[2] https://groups.google.com/a/chromium.org/d/msg/blink-dev/EDC3cBg9mCU/OvElJgOWCgAJ
[3] https://github.com/progers/pathseg
StalderT
Jeff Schiller
Philip Rogers
Ahmad Syazwan
Pavol Rusnak
James Hall