- From: sdwarwick via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Dec 2016 23:45:27 +0000
- To: public-svg-issues@w3.org
I'd be interested in some feedback on the following concept: 1) It appears that the SVG 2 momentum has seriously slowed, if not halted. 2) All browsers actually have now exposed the webGL capabilities of direct rendering through javascript. The kinds of renderings using this capability far outstrip what seems possible in svg. 3) Given the structure of an SVG document, It doesn't seem to require any changes from the browser developers to have an SVG file that integrates a webGL-based script or an associated self-contained Javascript "helper" library and script. Many things open up from here - 1) a purely javascript alternative for the declarative SVG language embedded in an SVG document structure 2) A webgl based SVG interpreter/webgl converter that could be optionally carried inside the svg structure enabling all kinds of enhancements to the declarative SVG without changes to the browsers. 3) an alternative declarative structure, as discussed above, also with a built-in interpreter and carried in the svg structure for historical consistency. seeing the following changed my opinion of SVG forever: https://threejs.org/examples/#webgl_animation_cloth http://webglplayground.net/share/fluid-simulation2?gallery=1&fullscreen=0&width=800&height=600&header=1 http://webglplayground.net/share/traveling-wave-fronts?gallery=1&fullscreen=0&width=800&height=600&header=1 http://webglplayground.net/share/lsystem-tree-fractal? the source code in javascript is so short.. -- GitHub Notification of comment by sdwarwick Please view or discuss this issue at https://github.com/w3c/svgwg/issues/257#issuecomment-265890314 using your GitHub account
Received on Thursday, 8 December 2016 23:46:04 UTC