higorion wrote: > on my page, before entering svg content, i am checking > for the installation status of the adobe svg plugin.
I understand, that in this case you need the capabilities of a particular SVG renderer. (This is a slightly different problem than the general browser-capabilities problem.) > 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? It's not so dependent on the operating system as it's dependent on the various browsers on that operating system, and whether each reveals to JavaScript its current set of extensions and capabilities. There are various plugin-detection scripts and routines out there, but I've never been really happy with any of them, because you always have to balance how many specific situations you'll detect against the total script size. (A complete routine would test for plugin presence, plugin version, any of various third-party plugin blockers (in any of various browsers!), handle cases where JavaScript is not enabled, provide some way for updates, more.) The most foolproof way still seems to be the auto-refresh way, developed for Shockwave back in Netscape 2.0 days: a simple plugin file requests a page-redirect to the main plugin content, and the HTML's head requests a page-redirect a little later to a support page -- if the plugin can initiate you'll see the plugin content and if it can't you'll see the support content. These days you'd probably want to add a version-detection in your plugin content before branching to the main content, if your desired plugin offers this. But a simpler way, and the one I'd recommend overall, would be to just show your plugin content, and have a "Can't see the image?" link beneath it on the page. This also avoids all the JavaScript case-testing too. Richard Gnyla wrote: > Well flash has a detection why not SVG? It's not the plugin so much as the particular browser. Most browsers offer a plugin array to JavaScript. IE/Win used system-level ActiveX Controls instead of Netscape Plugins, and most of these can be tested by using VBScript to create an automation object of the control (createObject()). But then you've got versioning to handle too, as well as rarer problems such as intranets stripping out all OBJECT tags before delivery to the browser, etc. If you do a web search on "javascript flash detection" then you'll find plenty of entries which can usually be applied to other plugins. But I'm not really sold on JavaScript for anything but the most nominal testing... letting the visitor test whether they can see it, and then offering a good support page if they can't, that seems to be a lot cleaner overall. jd -- John Dowdell . Macromedia Developer Support . San Francisco CA USA Weblog: http://www.macromedia.com/go/blog_jd Aggregator: http://www.macromedia.com/go/weblogs 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/ <*> 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/
