[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ruby-talk
Subject:    Re: Dynamic SVG with Ruby/Tk
From:       Arndt Roger Schneider <arndt.roger () web ! de>
Date:       2010-05-29 22:20:06
Message-ID: hts3l7$k0m$1 () speranza ! aioe ! org
[Download RAW message or body]

Yotta Meter schrieb:

>>I agree with Mark that SVG is important for web-deployment.
>>Javascript however is a last resort. Most, if not all, interactions can
>>be encapsulated inside of SVG and SMIL. There is very little need for
>>Javascript--which is also good for a cross-language approach.
>>
>>-roger
>>    
>>
>
>Long term I really need individual event handling on each node of the 
>SVG document, which is why I wouldn't put interactions within the SVG 
>doc.
>
>  
>
SVG grants this type of access.
Event handling is an integral part of the SVG specification.
If the job gets more complex use SMIL.
Javascript or rather direct DOM manipulation is needed to
communicate to the outside world.

--Don't think in graphical terms here, SVG is more than that.

>Thanks for explaining the difference between bitmaps and vector based 
>images. I have a beginner 'black box' view of what I want, an image that 
>is essentially a set of objects that I can modify properties on at 
>runtime. I'm assuming SVG is the only technology that will give me this.
>  
>

Depends on what your requirements are, SVG has many predecessors.
Very likely every visualization system could perform the required task...
but SVG has the potential to become the lingua franca of vector graphics and
graphical user interfaces.

-roger
 


[prev in list] [next in list] [prev in thread] [next in thread]