The API has changed

[GoogleCodeExporter]

No existing code will work with this version.

We have near on 50,000 pages to update. Thanx.

When releasing new versions, new features go into new functions while old 
functions remain. It makes things bigger and slower, but they work.

-Ben

Original issue reported on code.google.com by meisteryellow@gmail.com on 20 Mar 2008 at 4:10

[GoogleCodeExporter]

Tis ok, IE settled with EOLAS. We'll just use old code and wait for SWFObject 
to not 
be needed anymore.

-Ben

Original comment by meisteryellow@gmail.com on 20 Mar 2008 at 4:11

[GoogleCodeExporter]

I'm surprised. Many people are spending hundreds of hours of their own time 
creating
a solution to help out many people, and still people find it necessary to 
complain
about it. Says what about who?

Yes, SWFObject 2.0 is not backwards compatible with SWFObject 1.5, and we have 
good
reasons why it shouldn't be. Sometimes when you need to improve something for 
the
future you have to break with the old, it's what's happened in this case.

Furthermore, nobody forces you to use our solution or upgrade all your existing
websites. The existing solutions should be good enough for a while to go, just 
use
the new SWFObject for your new websites.

Also, don't abuse a public issue report system to vent out personal 
frustrations. You
can use the discussion group for this purpose: 
http://groups.google.com/group/swfobject

Original comment by bobbyvandersluis on 20 Mar 2008 at 9:07

• Changed state: Invalid