RE: [Svagg-users] Question about SVAGG

[Bielik, R. <Rob...@gy...>]

Hi Jaemin,

> I think #1 is SVG's own feature and #2 and #3 are vendor=20
> specific feature. SVG provides 'script' tag to sepcify the=20
> script language type. Some vendor can support various script=20
> language by using 'script' tag. My understanding is correct?=20

Yes, the animation feature is built into the SVG standard, and would be =
very useful for animating
buttons, turning little GUI "lightbulbs" on/off f.i.

Note though that animation would be a subproject of SVAGG, i.e. to =
implement the actual animation
of SVG DOM element attributes.

Scripting is to be able to affect both the SVG DOM and to "call back" =
into the application
that has SVAGG embedded.

> So, would you tell me the reason that we are considering=20
> Python, Lua or Ruby?
> To do something that we can not do with SVG animation tag?
> Or to make freely-available SVG scriptable library?

Yes. The goal is to be able to provide a free, low dependency, SVG =
rendering library with
scripting possibilities. The reason I wanted Anti-Grain as base is =
because of rendering quality, speed and
low dependency.=20

The reason to look for other scripting languages is as Andrew said that =
most have their own preference
of scripting language, so to be able to provide each scripting language =
as "plug-in" to SVAGG
would be a cool feature.

Having said that, we need to start looking at what is the minimum SVG =
implementation to start with. I think we can all
start looking at the SVG DOM representation.

/Rob