Release 1.7 is transparent, in that it you can drop it into your existing app without any recoding. It fixes two rare issues and adds a Controller method to the Facade that was not there before, but should have been for form's sake.
Essentially,
* Replaced the logic in View.removeMediator to fix an observer management bug. The issue and resolution are described here:
http://forums.puremvc.org/index.php?topic=145.msg484#msg484 * Also implemented a fix to Controller.removeCommand which ensures an extra Observer isn't created when registering a Command for a Notification that another Command was already registered for. This could have lead to the new Command being called twice, since the Observers for all Commands simply call Controller.executeCommand, passing the Notification.
* And finally note the addition of removeCommand to Façade and IFacade. It was left out on purpose, since it was expected to be little used and the focus was on making the facade simpler. In retrospect it should be there for completeness.
The End of a GenerationUnless new issues are discovered and fixed with another minor release, this will likely be the last AS3 implicit release.
That is to say, the package structure of the original framework did not take into account that it would be ported to other languages and platforms. The structure org.puremvc.* leaves no place for the indication of which language the packaged code is written.
In order to disambiguate, we must insert a node in the tree, and so the next major release (2.0) for ActionScript 3 will be packaged as org.puremvc.as3.*
This means that to migrate an app to 2.0, you will have to find and replace org.puremvc with org.puremvc.as3. A goal of the framework was to avoid roadwork like this, but considering the unexpected expansion of the framework it will be a necessary inconvenience.
With the 2.0 AS3 release we will also correct a confusing dissimilarity in the constructors of the Mediator (who just takes a view component) and the Proxy (who takes a name and a data object). There is truly no good reason for this other than the Mediator came before the Proxy, and wasn't revisited afterwards. The idiom of having to override getMediatorName in your Mediator as a result is confusing make work that we'll take the opportunity at 2.0 to dispense with.
So if we have to migrate our apps anyway, we'll at least come away with a more polished and friendly framework for ourselves and all those other communities about to become acquainted with it.
Then, the standard plan of resisting feature creep at all costs will resume. So if anyone can think of some rough edge to the framework that has been left unaddressed (or unreported) thus far please, speak now!
Onward!
-=Cliff>
