I'm happy to announce the availability of SWFAddress 2.4 which appears to be the most stable and feature-full version up to date. It fixes some nasty issues that appeared in the previous release and introduces a few interesting additions. Here is the changelog:

• New INTERNAL_CHANGE and EXTERNAL_CHANGE events.
• Support for parameter arrays.
• Improved IE8 support.
• Fixed IE initialization issues.
• Fixed browser communication issues with AS2/AVM2 on Mac.
• Fixed URL decoding for AS1 and AS2.
• Fixed handling of swfobject.createSWF.
• Workaround for WebKit bug 20355.
• Frameset support and corresponding sample.
• All methods dealing with parameters and query strings no longer return empty strings.

The project became pretty mature but we'll continue to consider interesting ideas and requests. More open source goodness is coming soon.

As of today SWFAddress 2.3 is available for download. It's the next stable release of the project and took a little bit more than initially planned. This update offers various fixes and few interesting optimizations requested by users. There are few backwards incompatible changes but they will affect only some exotic cases. The main new feature is the improved support for unicode values. For Firefox 3 on Mac OSX we switched from ExternalInterface to getURL/navigateToURL and had some additional troubles especially with ActionScript 3.

Here is the full list of changes:

• New public encodeURI/decodeURI methods for AS1 and AS2.
• New Unicode sample and improved support for unicode values.
• Improved detection of ExternalInterface and swfaddress.js availability.
• Improved fix for Firefox 3/Mac OSX.
• Improved degradation in uncontrolled cross-domain parent frames.
• The explicit id attribute of swfobject.embedSWF() is now optional.
• Simplified browser sniffing.
• Removed internal eval() statements.
• Removed support for swfaddress.html.
• SWFAddress.getParameter() no longer returns an empty string if the parameter is not available.
• The SWFAddress.getTracker() no longer has a default value but the behavior remains the same.
• Support for hash fragments in the SEO redirection.
• MOTW is added to all the static samples.

Download SWFAddress 2.3

The new SWFAddress has just arrived after seven months of active development, various contributions and lots of positive feedback from the community. The list of changes includes the following:

• Refactored JavaScript implementation
• New SWFAddress.swc AS3 component
• New CS4 based Splash screen sample
• New Digg API sample
• New up() method for easier deep linking path navigation
• New XSS protection that doesn't affect special characters
• Support for Internet Explorer 8
• Support for custom HTTP status messages in the SEO sample
• Improved title handling
• Improved unload event handling for IE
• Updated Rails sample
• Fixed getBaseURL() for AS3
• Fixed Safari 2.0-2.0.3 support
• Build-in fix for the Firefox 3/Mac OSX blinking effect
• Additional onLoad fix for application/xml content type
• Fixed optional options parameter for the popup method
• Cross platform build script
• Various optimizations

I believe that this new version is pretty stable and won't require an update soon. There are two known Safari bugs (19202 and 20355) that currently affect the project and we can only hope that they will make it's way into the next major release of the browser.

SWFAddress has grown significantly in the last two years and it's very likely that we're going to provide a lite version for users who need just the basic functionality. Very soon the same API will become available for Silverlight and we're also scheduling the development of a jQuery plugin.

Happy holidays!

A sweet new SWFAddress sample that utilizes the Digg API just went live this morning. I wanted to create a simple Ajax based showcase for the project and I almost accomplished the goal. The complexity of the code is a little bit higher than I originally wanted but I hope that most of the people will be able to understand it.

The sample uses a dynamic script tag inclusion in order to access the Digg services in a cross-domain fashion. It lists the popular posts in the Technology section, does paging and shows post details.

Go check it out.

During the past few months I started learning and testing how the robots execution standard applies to our website and specifically to the SWFAddress SEO techniques that we promote. The SWF indexing has drawn attention recently with the announced partnership between Adobe and Google but at the moment it's still pretty basic for our needs. We decided that we want to stick with plain indexable HTML and forbid the SWF experiments that Google are currently doing. The robots.txt that we're finally using looks like this:

In addition to the SWF files we also disallowed the indexing of our data sources. Once again I want to mention that the existence of a sitemap is important.