Re: Regarding implementation of SVG2 vector effects

Hi All,

I've started a website to present SVG2 features to web developers. It
currently lists only the Vector Effects feature.
Please provide your comments and rating of this feature.  The site will
continue to evolve, adding the remaining features that would be of interest
to web developers.
See: www.svg2.org

Also, I would appreciate any examples that demonstrate the other features.
Forward images/code/descriptions and I'll include the feature.
Thanks,
Francis

On Wed, Feb 15, 2017 at 10:50 PM, Satoru Takagi <sa-takagi@kddi.com> wrote:

> Hi,
>
> > > https://bugs.chromium.org/p/chromium/issues/detail?id=691398
> > > If you want support for this feature, I encourage you to "star" that
> issue.
> Amelia-san, thank you for assisting Ramin-san. I also voted a star.
>
> Also, thanks to those who have expressed interest in this subject perhaps
> related to the current deeply rooted issues of WWW and W3C. I think that
> these discussions are progressive compared to other W3C discussions that
> have broken up with web browsers.
>
> I am busy with other development coding tasks and not good at English, so
> it took a long time to read your mass and complex messages.
>
> Well, our (KDDI) main use case of SVG is the exchange and display of maps
> and
> technical drawings in our own enterprise. In addition, we use SVG not only
> for display but also as source data (For W3C staff: It could be called as
> "SVG for Web of Data" instead of RDF and SW). The area of interest of
> Boeing, an SVGWG member, also seems to be enterprise.
>
> In such cases, non scaling vector effects are classically required, so we
> have implemented it.
> By the way, we have a Level of Details function with more stronger
> interest, but aside from that so far.
>
> Through this development, we learned that even open source project where
> community volunteer contributions may be respected it is difficult to
> incorporate into the main-stream just based on the candidate recommendation
> specification based on discussion and agreements on SVGWG. Also, we learned
> the problem that the native implementation of the new specification makes
> the browser more complicated, and its maintenance becomes an issue, the
> necessity of the new specification has the problem of chicken and eggs.
>
> Meanwhile, I also developed a polyfill for vector-effects. Code and tests
> are here.
> http://svg2.mbsrv.net/devinfo/devstd/non-scaling-objects-2/
> VectorEffect_polyfill_wScreen.html
>
> Through this developments, I also noticed that polyfill has a low barrier
> of know-how needed compared to native development for browsers, and
> obviously one polyfill implementation could be a spec implementation for
> almost all browsers.
>
> Also as a present advancement against 20 years ago, I also felt that
> polyfill is achieving features and performance comparable to native
> implementations. Then, increasing the amount of maintenance of browser's
> native implementation due to huge specs may be somewhat suppressed by
> polyfill. It may also fill some gap between the browser supplier's business
> model and the new specs.
>
> By the way, I am developing and operating enterprise web mapping systems
> totally using SVG as an exchange data format with javascript and canvas2d.
> Because level of details is indispensable feature for it but lacks current
> SVG specs.
>
> Asm.js, WebAssembly and other staffs may further make this progress. And we
> ought to make better use of this progress.
>
> In addition, W3C TAG recently issued the following documents. This document
> may perhaps give important insights to our discussion.
>
> Polyfills and the evolution of the Web
> http://www.w3.org/2001/tag/doc/polyfills/
>
> Regards,
>
> Satoru Takagi
>
> KDDI AC Rep.
>
>
> <CA+kmfkTBAhJew51MraFZcerirGC6cGDnNRWg1z+SThpT-pTqKQ@mail.gmail.com> の、
>    "Re: Regarding implementation of SVG2 vector effects" において、
>    "グルチヤンラミン <ktecramin99@gmail.com>"さんは書きました：
>
> >
> > Thank you Amelia for creating the Chromium issue.
> > I will keep an eye on it and hope this moves things a little forward.
> > I also thank all for your helpful and positive comments.
> >
> > 2017-02-13 6:21 GMT+09:00 Amelia Bellamy-Royds <
> > amelia.bellamy.royds@gmail.com>:
> >
> > > I was unable to find a Chromium issue requesting implementation of the
> > > vector-effects options, so I have created one here:
> > >
> > > https://bugs.chromium.org/p/chromium/issues/detail?id=691398
> > >
> > > If you want support for this feature, I encourage you to "star" that
> issue.
> > >
> > > If you have specific use cases where support for browser vector-effects
> > > would help reduce hacks or scripting, please leave a comment on the
> issue.
> > >
> > > Whatever you think about the browser vendor organizations or about the
> > > particular people who have participated in the SVG working group, the
> > > entire purpose of web standards is to create interoperable
> implementations
> > > between web browsers and other document viewers, so that authors can
> create
> > > documents with confidence that they will be rendered consistently
> > > elsewhere.  This can only happen with support from the major web
> browser
> > > development teams.  And it will only happen if those teams are
> convinced
> > > that there is widespread interest in and demand for the features.
> > >
> > > Thanks so very much to Ramin & your team for working on this code.  I
> do
> > > hope your work does not go to waste.
> > >
> > > ~ABR
> > >
> > > On 30 January 2017 at 19:38, グルチヤンラミン <ktecramin99@gmail.com> wrote:
> > >
> > >> Dear W3C/SVGWG
> > >>
> > >> I am working for KDDI Technology Co. and I'm writing this email to you
> > >> because we have been working on implementation of SVG2 CR vector
> effects
> > >> (described in W3G spec, following link) into Firefox/Gecko since last
> three
> > >> months.
> > >> https://svgwg.org/svg2-draft/coords.html#VectorEffects
> > >>
> > >> Sponsored by KDDI, we've succeeded to bring support for those new
> effects
> > >> to firefox/Gecko, however, final shipment has faced to some
> difficulties
> > >> because Mozilla shows no intention to apply new SVG2  spec unless
> other
> > >> browsers i.e. chromium/edge have a plan to do so.
> > >> (please refer to following links for more details:
> > >> https://groups.google.com/forum/#!topic/mozilla.dev.
> platform/T_7HTTdt-Es
> > >> and
> > >> https://bugzilla.mozilla.org/show_bug.cgi?id=1318208
> > >> )
> > >> As a result, to bring new SVG2 spec to reality, it is very important
> to
> > >> encourage all browsers to apply new spec, and to achieve this goal,
> your
> > >> help would be inevitable.
> > >>
> > >> We are looking forward for your help and support.
> > >>
> > >> Thank you very much
> > >> Ramin
> > >> KDDI Technology
> > >>
> > >
> > >
> >
> >
> >
>
>