Doug Schepers wrote:
> Guy Morton wrote:
>>Yeah, but it's not too professional-looking to have to give a list of  
>>"abandoned" websites that happen to host the plugin and hope that joe  
>>public will trust that any software thus downloaded isn't riddled  
>>with virii and worms. who's going to guarantee that it isn't? You?
> 
> I think you hit the nail on the head...
> It is not the question of availability of a viewer, it is a question of 
> the legitimacy and perception of viability of the viewer.

For what it's worth, I agree strongly with you on this as well. Getting 
people to install OS-native code on their own machines is difficult, 
both for trust issues and for installation costs. Getting your own 
native code deployed on the world's desktops is not easy.

That's why I care so much about the "render SVG in Flash Player" 
approach developed by Claus Wahlers and friends:
http://wahlers.com.br/claus/blog/display-svg-in-97-of-all-web-browsers/

Instead of asking millions of people to install a renderer, this 
approach uses a renderer already installed on their machines (Adobe 
Flash Player), and sends SVG-rendering instructions as ECMAScript in a 
SWF file, which then calls and renders the SVG XML instructions themselves.

The nice thing is that the rendering instructions can then be open for 
editing by each content developer -- the deployed Player remains a 
general media/interactivity engine, but you can change what it does when 
it encounters a particular SVG tag, remove or enhance parts of the 
rendering instructions as you see fit, etc. This would not conflict with 
the choice of other content developers, because the ECMAScript 
instructions are separate from the rendering engine itself.

For instance, the DENG engine Claus uses here is a 75kb SWF file, whose 
scripting instructions render a wide range of protocols.

There would be some tasks that such an approach would not accomplish, 
but there are many which it *can* accomplish. If you see particularly 
difficult sticking-points with this "SVG engine as document" approach 
then I'd like to understand them well enough to be able to evangelize 
them internally here at Adobe, thanks.


(Disclaimers: I have no particular insight into Adobe's recent ASV 
announcement -- I learned of it on this list too. I also like and 
respect people on this list (even though I get beat up sometimes ;-) 
because folks here *care* about improving the web-browsing experience... 
our goals have been the same, even though the means may have differed.)


jd





-- 
John Dowdell . Adobe Developer Support . San Francisco CA USA
Weblog: http://weblogs.macromedia.com/jd
Aggregator: http://weblogs.macromedia.com/mxna
Technotes: http://www.macromedia.com/support/
Spam killed my private email -- public record is best, thanks.


-----
To unsubscribe send a message to: [EMAIL PROTECTED]
-or-
visit http://groups.yahoo.com/group/svg-developers and click "edit my 
membership"
---- 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/svg-developers/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/svg-developers/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[EMAIL PROTECTED] 
    mailto:[EMAIL PROTECTED]

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to