On Thu, 30 May 2013 17:50:10 -0400 john Culleton <John@...1668...> wrote:
On Thu, 30 May 2013 17:11:48 -0400 Steve Litt <slitt@...2357...> wrote:
On Thu, 30 May 2013 08:37:51 -0400 john Culleton <John@...1668...> wrote:
I am planning to convert one of my web sites to all-svg. I am wondering about the use of a site map. Is it the same as for an html site (with different names of course)?
John, are you saying there will be no HTML on your website, only SVG?
Why?
SteveT
Perhaps because it can be done. I built a subdomain and put just an index.svg file on it and it worked. Now I am not religous about this. If there is a good reason for using html wrapped around an svg entity I may do that. Can you think of a good reason?
My main reason is that HTML is good at its job...
* Separates meaning from style (via CSS etc) * Very easy to hand code in an editor * Worldwide standard
Against that backdrop, what would be the compelling reason to have a website *exclusively* built with SVG? Obviously SVG is good for the images, and for links in the images if that can be done, and video, etc, but I'm not sure why one would forgo the ease and adaptability of HTML.
By the way, I'm starting to use SVG images on my websites. Often direct from Inkscape, with the Inkscape metadata still in them. They render well with all my browsers (but I don't use IE). See this:
http://www.troubleshooters.com/bookstore/larrymap/larrymaps.htm
Thanks,
SteveT
Steve Litt * http://www.troubleshooters.com/ Troubleshooting Training * Human Performance