Re: new post - wish list

> Inkscape is currently the most extensive SVG renderer; how would one
> transfer or moduralise to Javascript while replacing Cairo and all the
> intensive bits of technology?

The Javascript version could start out as an experimental javascript branch / playground for anyone interested.  The two could be complementary.  Personally I usually prototype in typescript or javascript because they are simple to setup and very approachable, but if I'm creating server side code I may convert the final to Java depending on how stress / performance tests, dependency robustness evaluation, etc. go.

I would not view the current Inkscape vs a Javascript version / approach as mutually exclusive, but complementary.

As far as development approach -- breaking each "Intensive bit of technology gem" down by use case / module and examining the possibilities from there I'm certain would yield some interesting discoveries.  For some blue sky context:

https://css-tricks.com/rendering-svg-paths-in-webgl/

If done right Inkscape could be the core hub for open source SVG Javascript development feeding upstream libraries.

Javascript SVG Drawing APIs / Implementations (Perhaps Inkscape could provide some standard interfaces bringing these together):

https://svgjs.com/docs/2.7/

http://snapsvg.io/

https://bonsaijs.org/

http://dmitrybaranovskiy.github.io/raphael/

https://www.npmjs.com/package/two.js

https://github.com/sebmarkbage/art/

http://fabricjs.com/

http://velocityjs.org/

> Inkscape is much more extensive and intensive than most developers even
> understand.
That I'm sure of!  It's an engineering gem.
> It's both why it's harder to code for and also why it's
> very hard to replace.

NO REPLACE!!  ENHANCE and COMPLEMENT!! :)

Cheers,

Ole




_______________________________________________
Inkscape-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/inkscape-user