[dojo-contributors] Re: SVG/VML/Canvas API discussion
ttrenka at gmail.com
Wed Apr 19 00:21:56 EDT 2006
Here's the thing--I'm still not (personally) convinced there needs to be a
compatibility layer. I'd rather take Dylan's approach here, and start
thinking of this in terms of what we'd want for an end result. Dojo isn't a
language (despite the fact that it uses markup to create widgets); it's a
library that abstracts away the nitty-gritty of other languages (i.e. JS,
HTML, CSS, SVG, VML, etc.) so that all it takes to, say, include a map or
create a chart is a single HTML element with a few extra attributes. It's
the responsibility of someone who want to author widgets et al to use
whatever means necessary to acheive that goal.
(bear in mind I'm also lacking in sleep right now, thoughts are a bit
The only reason I can see creating a compatibility layer is if Dojo is going
to provide a "meta-SVG" type language for others to author with. Is that
something we want to do?
As far as Bill's example of interactive charts go, probably we'd want to
build it into the Chart widget itself, or create several variations with the
most common behaviors?
My apologies (again) for throwing out the term "API" before I should have;
I'm at the exact same place as Dylan is with this.
What do we really need?
(Jon--VML and SVG are similar but different enough to make creating a common
denominator very limited. It would probably be easier to implement VML
using SVG than to implement SVG Tiny with VML, and more consistent as well.
In some ways, VML can be considered a predecessor of SVG...I tend to think
of VML as "Visio markup" while SVG is more the XMLified version of
PostScript, if that helps at all)
On 4/18/06, Adam Peller <apeller at us.ibm.com> wrote:
> Also, for compatibility layers, take a look at Mark Finkle's SVG in IE:
> I don't know how complete a mapping one could provide from SVG to VML, but
> vectors and plain fills may be sufficient most of the time? (I think
> there's a
> SVG profile that comes pretty close to this?) Of course, this is a
> transform, so if interactive content is our goal, this may not cut it.
> This also made me wonder if it's possible to achieve using an XSLT -- I'm
> very proficient in XSLT, but I think Microsoft's implementation would make
> possible to keep talking to the SVG DOM and push changes down to the
> VML? Wonder if anyone has attempted to do it this way?
> Dan Pupius <dan.pupius <at> gmail.com> writes:
> > It might be worth looking at ExplorerCanvas that Glen and Erik worked
> dojo-contributors mailing list
> dojo-contributors at dojotoolkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dojo-contributors