I'm writing a browser plugin and one hurdle is getting plugins into the web-page in a way that works across browsers. It seemed to me that rather than cobbling something together, I might be able to take SWFObject and hack it into something that supports my own plugin.
So the first question I have is, does that seem a good idea... is SWFObject a good example to follow? I've skimmed through the JS file and was struck how much stuff there is... is all this really needed or is a lot of it only required for very old browsers (pre-IE6 for example)? My plugin will only really make sense for use on JS-enabled browsers so that would suggest to me only the dynamic-publishing technique is useful, meaning I can hopefully avoid having to understand the nested- <object> workaround and a few other things? Any advice and answers to questions I should have asked but didn't, are also most welcome! I also have to ask - has anyone already made a more generalised plugin- library? If not then it would make sense to open-source it... -- You received this message because you are subscribed to the Google Groups "SWFObject" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/swfobject?hl=en.
