Re: SVG Book (was: SVG IG -- a few ideas)

Hi everyone,


> It's not a matter of encouraging W3C to publish it... we will publish it
> whenever we ask them to.  However, there are publication guidelines we have
> to follow; for example, it needs to be valid and well-formed, etc.

Yes, that would make sense, coming from a standards organization... ;-)


> I also think it would benefit from being broken down into several pages,
> perhaps along chapters.  Right now, it takes a long time to load and render.
>  Breaking it down this way would let us include the SVG examples inline more
> easily, if we want to do that.

I'd vote for this too. Having a huge, about 200 page (printed) single
HTML file is too slow to use as a reference material: whenever I open
it, it somehow hogs my browser and Internet connection for a couple of
minutes, specially if done in a new computer (without a cached
version)... We could still have a "printable version" if someone
really wanted a single document for export (to PDF, print, etc.): the
SVG Tiny 1.2 already has this concept [1] .

About the inline examples, I still favor the raster images with a
"activate me to display the live version" tooltip, for a few reasons
(which were in part already stated):
 * For animated examples (SMIL/script), one only wants the animation
to be triggered whenever the user is looking at it; having it
triggered whenever the page is loaded will be displaying a finished
animation whenever the user;
 * Catching a specific moment in an animated example is many times
more illustrative and easier to explain than a random moment one won't
ever be able to guess;
 * More than a few SVG objects being rendered at the same time will
hog the browser for a while, giving a bad performance/broken feeling
to the whole...

Of course I can imagine a part of the animated examples can be
reworked to avoid the first two items: using atomic, cyclic
animations, but a few can't (for example, the ones intend to show
animations which freeze at the end).


David: is the feedback still being made by sending you change
descriptions in prose? I'd really love to be able to send patches or
HTML snippets for the changes, although I'm still in the (slow)
process of parsing the whole book. Either way, in order to send
suggestions/fixes, one need to have a "bleeding edge" version
available somewhere (most of the things I've noticed are probably
already fixed; having a way to check for it would be useful)... :-)


Regards,
  Helder


[1] http://www.w3.org/TR/SVGTiny12/single-page.html

Received on Monday, 12 October 2009 09:14:48 UTC