--- In [email protected], Holger Will <[EMAIL PROTECTED]> wrote: > higorion wrote: > > > hi, > > > > on my page, before entering svg content, i am checking for the > > installation status of the adobe svg plugin. > > > > for internet explorer i am using a litte vb-script to > > instantiate "Adobe.SVGCtl". for firefox, netscape and opera i am > > reading from the plugins array to find the information i need. > > > > if no proper viewer is found, the user is shown a warning and is > > optionally redirected to a page containing detailed installation > > info. > > > > there's only one problem left to complete my goal: plugin detection > > an a macintosh computer. > > > > can somebody tell me how to find out whether adobe svg viewer is > > installed on a macintosh client? > > > > i would appreciate your answers very much! > > > > best regars, > > > > hannes > > Hi Hannes > > i dont think its a good idea to test for the adobe plug in, there are a > lot of other implemetations out there, why would you want to exclude > them from accessing your SVGs ? > on linux many people use KSVG (there are rumores that it will be ported > to OSX), mozilla/firefox will have native SVG support in 1.1, > and dont forget the upcomming Renesis viewer, which should , if its only > half as good as promised, be widely distributed soon. > you dont want to exclude these people, or people using any other future > viewer. > i would suggest using an extra > > <object type="image/svg+xml" data="viewerOK.svg" width="100px" > height="100px"> > if you can read this,you will need an svg viewer <a>click here</a> to bla... > </object> > > note ! that you can not safely assume that scripting works in <object> > context. viewerOK.svg should just be a symbol indicating > that an SVG viewer was detected. > > hth > Holger
hi holger, there certainly is a point in not limiting the user to the use of one plugin. that is the reason why i built the plugin check in a way that doesnt stop the user before entering the page, but points out the missing adobe plugin and then gives the user the choice to continue anyways or to have installation instructions displayed for the adobe plugin. after a quick check it seems to me that it wouldn't be to much work to make my application work under mozilla as well, so i might as well do that. yet, i have another concern: rendering speed. i have built a little benchmark app with ~20k of svg and ~20k of js, that i have used to compare batik and adobe viewer in the past. i quickly adapted the example for mozilla svg and have rendering speed ~3-4 times slower than in adobe viewer. it makes quite a difference to have rendering at 5 fps or 18 fps. the "big" application is ~400k of svg and ~600k of js, so i don't have too much confidence about final rendering speed in mozilla, with adobe already at it's limit, even on a fairly fast machine (rendering is fine on my 2Ghz laptop). if somebody wants to use built in mozilla support, i will leave it up to him, but i will definititely point users to the best performing plugin available. if renesis turns out to be just that, i will be very happy to change my recommendation! best regards, hannes ----- 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/ <*> 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/
