Re: Is SVG 2 still under development?
Ulrich-Matthias Schäfer <[email protected]> Sun, 10 May 2020 08:15:02 +1000
| Newsgroups | gmane.comp.web.svg |
|---|---|
| Message-ID | <CAKKaHAsCv+ikPKBichxs7sinyZjnqNR7-jWXjU1ORzyiWbQVKQ@mail.gmail.com> |
--000000000000a8918005a53e725d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hey Bryan, I just read an interesting article around this topic that painted a more darker picture of the svg development. The main point was basically: Everyone waits for everyone else to implement features of SVG2 before they will do it. A view useful features were already adopted by the vendors even though the spec is not stable yet. However, more and more features get dropped from the specs in order to finally finalize it (pun intended). Link to the article: https://css-tricks.com/svg-2-conundrum/ For me as the maintainer of svg.js and svgdom this is rather sad news because I hoped for cool new features to come but I came to the conclusion that nobody will sprint ahead unless you go and do it yourself. I hope I will be able to contribute to chrome and firefox atleast in the near future= . Best Ulrich-Matthias Sch=C3=A4fer svg.js: https://github.com/svgdotjs/svg.js svgdom: https://github.com/svgdotjs/svgdom Am Sa., 9. Mai 2020 um 07:00 Uhr schrieb David Dailey < [email protected]>: > Hi, I'm really not the right person to answer, being nowadays, just a > lurker here, but if I mis-speak, others are sure to holler. > > I think the answer is yes the SVG spec is still under development, and > just a few days ago, I saw activity here from some of those known to be > closely involved in the development. > A few years ago they decided to move most of the development activity, an= d > perhaps even discussion to a place harder for old people like me to find > -- like a blog or a wiki or a thermocouple -- who knows all the modern > terminology these youngsters have (I'm just teasing, btw, but I really do > forget the name of the thingy where the stuff lives now). > > But more importantly, for your needs, SVG is now baked into all major > browsers (including most minor ones), and that includes support for "stat= ic > SVG" as well as scripted stuff, and in *most* cases, support for > non-scripted animation (of the sort, previously known as SMIL). It also h= as > baked-in support from many applications (like Illustrator and Inkscape) > and it's not going away there. Also, it's a standard for vector graphics = as > used by Wikipedia (and in many cases, the SVG graphic is considered > preferable by them to bitmaps, for obvious reasons). As someone who used = to > be deeply involved in SVG, I see no reason at all to suspect support for = it > will disappear from anywhere! > > The folks actually building it are relatively few in number, which I thin= k > explains the reason you didn't get a reply to your previous question. And > they tend to be quite busy. > The W3C has this to say: > > ---- > The mission of the Scalable Vector Graphics (SVG) Working Group is to > develop and maintain SVG. > > Chair: Dirk Schulze > W3C Staff Contact: Chris Lilley > Scheduled to end: 2021-03-31 > ------ > And according to their web page, the W3C is hiring, so I don't think > they're going away. > > > Cheers > David Dailey > Retired (http://srufaculty.sru.edu/david.dailey/) > > > > -----Original Message----- > From: Bryan Dunphy [mailto:[email protected]] > Sent: Friday, May 8, 2020 11:15 AM > To: [email protected] > Subject: Is SVG 2 still under development? > > I=E2=80=99m developing a (probably static - no scripting support availabl= e) SVG > plugin for my primary multi-device, cross-platform development environmen= t > and need to know if I should be concerned with it as far as future suppor= t > is concerned. > > > --000000000000a8918005a53e725d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hey Bryan,</div><div>I just read an interesting artic= le around this topic that painted a more darker picture of the svg developm= ent.</div><div>The main point was basically: Everyone waits for everyone el= se to implement features of SVG2 before they will do it. A view useful feat= ures were already adopted by the vendors even though the spec is not stable= yet. However, more and more features get dropped from the specs in order t= o finally finalize it (pun intended).</div><div>Link to the article: <a hre= f=3D"https://css-tricks.com/svg-2-conundrum/">https://css-tricks.com/svg-2-= conundrum/</a></div><div><br></div><div>For me as the maintainer of svg.js = and svgdom this is rather sad news because I hoped for cool new features to= come but I came to the conclusion that nobody will sprint ahead unless you= go and do it yourself. I hope I will be able to contribute to chrome and f= irefox atleast in the near future.</div><div><br></div><div>Best</div><div>= Ulrich-Matthias Sch=C3=A4fer</div><div><br></div><div>svg.js: <a href=3D"ht= tps://github.com/svgdotjs/svg.js">https://github.com/svgdotjs/svg.js</a></d= iv><div>svgdom: <a href=3D"https://github.com/svgdotjs/svgdom">https://gith= ub.com/svgdotjs/svgdom</a></div></div><br><div class=3D"gmail_quote"><div d= ir=3D"ltr" class=3D"gmail_attr">Am Sa., 9. Mai 2020 um 07:00=C2=A0Uhr schri= eb David Dailey <<a href=3D"mailto:[email protected]">ddailey@zoo= minternet.net</a>>:<br></div><blockquote class=3D"gmail_quote" style=3D"= margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef= t:1ex">Hi, I'm really not the right person to answer, being nowadays, j= ust a lurker here, but if I mis-speak, others are sure to holler. <br> <br> I think the answer is yes the SVG spec is still under development, and just= a few days ago, I saw activity here from some of those known to be closely= involved in the development. <br> A few years ago they decided to move most of the development activity, and = perhaps even discussion to a place harder for old people like me to find=C2= =A0 -- like a blog or a wiki or a thermocouple -- who knows all the modern = terminology these youngsters have (I'm just teasing, btw, but I really = do forget the name of the thingy where the stuff lives now).<br> <br> But more importantly, for your needs, SVG is now baked into all major brows= ers (including most minor ones), and that includes support for "static= SVG" as well as scripted stuff, and in *most* cases, support for non-= scripted animation (of the sort, previously known as SMIL). It also has bak= ed-in support from=C2=A0 many applications (like Illustrator and Inkscape) = and it's not going away there. Also, it's a standard for vector gra= phics as used by Wikipedia (and in many cases, the SVG graphic is considere= d preferable by them to bitmaps, for obvious reasons). As someone who used = to be deeply involved in SVG, I see no reason at all to suspect support for= it will disappear from anywhere! <br> <br> The folks actually building it are relatively few in number, which I think = explains the reason you didn't get a reply to your previous question. A= nd they tend to be quite busy. <br> The W3C has this to say:<br> <br> ----<br> The mission of the Scalable Vector Graphics (SVG) Working Group is to devel= op and maintain SVG.<br> <br> Chair: Dirk Schulze<br> W3C Staff Contact: Chris Lilley<br> Scheduled to end: 2021-03-31<br> ------<br> And according to their web page, the W3C is hiring, so I don't think th= ey're going away.<br> <br> <br> Cheers<br> David Dailey<br> Retired (<a href=3D"http://srufaculty.sru.edu/david.dailey/" rel=3D"norefer= rer" target=3D"_blank">http://srufaculty.sru.edu/david.dailey/</a>)<br> <br> <br> <br> -----Original Message-----<br> From: Bryan Dunphy [mailto:<a href=3D"mailto:[email protected]" targe= t=3D"_blank">[email protected]</a>] <br> Sent: Friday, May 8, 2020 11:15 AM<br> To: <a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a><= br> Subject: Is SVG 2 still under development?<br> <br> I=E2=80=99m developing a (probably static - no scripting support available)= SVG plugin for my primary multi-device, cross-platform development environ= ment and need to know if I should be concerned with it as far as future sup= port is concerned.<br> <br> <br> </blockquote></div> --000000000000a8918005a53e725d--