This is a explanation of how to implement the inline SVG capabilities of the Adobe SVG Viewer (version 3).
SVG (Scalable Vector Graphics) is an XML dialect that describes vector images, sort of like Macromedia Flash. What sets it apart from that format, though, is that it is a text-based (i.e. human readable), data-driven open standard. Just like with Flash, however, you currently need to have a viewer plug-in for your browser to render it properly; you currently do not have an SVG plug-in. I'm afraid that if you want to make any sense of this page, you'll have to bite the bullet and install the latest version of Adobe's SVG plug-in:
This uses a special property of ASV3 that exploits Internet Explorer's Binary Behaviors. Thus, it only works for ASV3+ with IE5+. It is a bit of a hack using quasi-namespaces (the 'xmlns' bit you'll see below --akin, as I understand it, to XML data islands, another IE technology).
Below are a few examples of 'inline' SVG images. An embedded SVG image is a separate file that is stuck into a page, just like a bitmap or JPEG, and so is not actually part of the document; an 'inline' image is one that is written directly into the HTML of the page (using XML namespaces), and is therefore part of the main document itself. The following example is the template for this very page:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<object id='AdobeSVG' classid='clsid:78156a80-c6a1-4bbf-8e6a-3cd390eeb4e2'>
<?import namespace='iSvg' implementation='#AdobeSVG'?>
<div id='bannerhead' align='center'>
<a href='/' title='Back to front page'>
<iSvg:svg id='bannerhead' width='500' height='140' >
<iSvg:g font-style='italic' font-size='100'>
<iSvg:rect x='10' y='20' width='480' height='110' rx='15' ry='15' fill='black'/>
<iSvg:text x='20' y='105' fill='yellow' stroke='red' stroke-width='2'>
Schepers <iSvg:animateColor attributeName='fill' attributeType='CSS' from='rgb(128,0,0)' to='yellow' begin='0s' dur='4s' fill='freeze'/>
<iSvg:animateTransform attributeName='transform' attributeType='XML' type='rotate' from='-30' to='0' begin='0s' dur='2s' fill='freeze'/>
<iSvg:text x='112' y='81' fill='yellow' stroke='red' stroke-width='2' font-family='Garamond'>
. <iSvg:animate attributeName='x' begin='1s' dur='1.5s' from='112' to='120' fill='freeze'/>
<iSvg:animate attributeName='y' begin='1s' dur='1.5s' from='81' to='38' fill='freeze'/>
<iSvg:text x='88' y='104' fill='yellow' stroke='red' stroke-width='2'>
c <iSvg:animate attributeName='x' begin='0s' dur='2.1s' from='88' to='84' fill='freeze'/>
<iSvg:animate attributeName='y' begin='0s' dur='2.1s' from='104' to='123' fill='freeze'/>
<div id='navLinks' align='center'>
<a href='lastpage.html' title='Previous'>
<iSvg:svg ID='prevLink' width='176' height='48' >
<iSvg:ellipse cx='80' cy='24' rx='76' ry='24' fill='#6699cc' stroke='none'/>
<iSvg:ellipse cx='69' cy='24' rx='62' ry='20' fill='white' stroke='none'/>
<iSvg:text x='18' y='32' fill='#6699cc' stroke='none' font-family='Comic San Serif MS' font-size='24'>
<a href='nextpage.html' title='Next'>
<iSvg:svg ID='nextLink' width='176' height='48' >
<iSvg:ellipse cx='100' cy='24' rx='76' ry='24' fill='#6699cc' stroke='none'/>
<iSvg:ellipse cx='110' cy='24' rx='62' ry='20' fill='white' stroke='none'/>
<iSvg:text x='98' y='32' fill='#6699cc' stroke='none' font-family='Comic San Serif MS' font-size='24'>
Allow me to explain what's going on:
DISCLAIMER: This site in general --and this page in particular-- is not comprised of valid XHTML, despite my higher leanings. In order to experiment with the custom SVG namespace, I've had to use proprietary and non-standard code that most likely only works with Internet Explorer 5.5+ and the Adobe SVG Viewer; hopefully, when a true XML browser becomes available and widely used (what's stopping you, Adobe?), I can refactor this site to be compliant. In the meantime, please understand that I use the term “Inline SVG” somewhat loosely.
There are a few things that you cannot do with inline SVGs that you can with standalone SVGs. I will list these as I find them. It is not clear if any of these limitations will be fixed in the upcoming ASV6, or even that inline SVG will be supported at all.
One of the most interesting things about SVG is the ability to include interactivity, though script or SVG's own Declarative Syntax (drawn from the SMIL specification). Unfortunately, for the present, inline SVGs are limited with resect to interaction; mouse events do not register with the individual elements (such as <rect> or <circle>), but only the root element (<svg>). Here is an example of onmouseover and onmouseout events on the root element changing the value of the <rect> element's corner-rounding attributes:
To illustrate this point, try clicking anywhere on the image below. The SVG root has the ID attribute 'svg_root', the circle is 'svg_circle', and the rect is 'svg_rect'. The click event spawns an alert with the value 'this.getAttribute("id")'. As you can see, no matter where you click, 'this' always refers to the root element. Targeting individual elements is possible, by using 'getElementByID', but locating the source of an event is not. This may change in later versions of the Adobe viewer.
Here is another simple example of a work-around, using an HTML form:
Hopefully, as new generations of browsers or more sophisticated plug-ins become available, these workarounds won't be necessary. Within a year or two, I think we will see a widespread adoption of SVG and XML, allowing multiple namespaces within documents, as well as composite documents working seamlessly together.