Designers (and occasionally developers) need to embed Flash content within websites. SWFObject 2 offers two optimized Flash Player embed methods; a markup-based approach and a method that relies on JavaScript - let's look at the benefits of both!
Web professionals are flocking to SWFObject 2 as it is better optimized and more flexible than other Flash embed methods - it uses JavaScript to overcome issues that can't be solved by markup alone. For example, SWFObject 2 detects the Flash Player version and determines whether Flash content or alternative content should be shown (just in case outdated plug-ins exist on the client side.)
Designers can embed Flash content using both static and dynamic publishing methods. Let's look quickly at the advantages of both and how to make it work!
Static Publishing with SWFObject 2
This method allows designers a mechanism of embedding Flash content that does not rely on a scripting language - the effect is that content will be accessible to a broader audience - users with JavaScript disabled or turned off in browsers will still be able to see the Flash content. Static Publishing with SWFObject 2 also enables devices like the Sony PSP to run, as well as automated tools like RSS readers.
Dynamic Publishing with SWFObject 2
The advantages of the dynamic publishing method are that it integrates with scripted applications and does not require a click-to-active mechanism to display active content in IE 6/7 and Opera 9+.
