topleft

PureMVC

larger smaller reset larger Futurescale, Inc.
  • fixed-width
  • fluid-width
  • Home
  • About
  • Code
  • Docs
  • FAQ
  • Forums
  • News
  • Showcase
  • Contact
  • Jobs
topright
PureMVC_AS3_MultiCore
  • Login
  • Help/Guide
  • About Trac
  • Preferences
  • Wiki
  • Browse Source

Context Navigation

  • Start Page
  • Index
  • History
  • Last Change

TracNav

  •  PureMVC Manifold...

  •  Contributors
  •  Repositories
  • Ports...

  •  ActionScript 2
  •  ActionScript 3
  •  C #
  •  ColdFusion
  •  Haxe
  •  Java
  •  JavaScript
  •  Objective C
  •  PHP
  •  Python
  •  Ruby
  •  Propose a Port

TracNav

  • AS3 MultiCore /  Standard...

  • Downloads
  • Installation
  • Release Notes
  •  View Source
  •  API Docs
  •  Discussion
  • Unit Tests
  • Project Owner...

  •  Cliff Hall
  • Tutorials...

  •  Garbage Collection
  • Utilities...

  • Flex / Flash / AIR...

  •  AsyncCommand
  •  Pipes
  •  State Machine
  •  LoadUp
  • Flex / AIR...

  •  Deployment Config
  • AIR Only...

  •  XML Database
  •  Desktop Citizen
  • Demos...

  • Flash...

  •  Sequential
  • Flex...

  •  App Skeleton
  •  Modularity
  •  PipeWorks
  •  StopWatch

PureMVC MultiCore for AS3

PureMVC is a lightweight framework for creating applications based upon the classic  Model-View-Controller design meta-pattern. This is an implementation for the AS3 language, which supports multiple PureMVC Cores through the use of Multitons instead of Singletons.

Release Notes

Summary of Changes in 1.0.5

The following MultiCore specific changes add the ability to check for the existence of a Core, as well as making the existing removeCore method static. This may break a few apps, but is extremely easy to fix. Checking for a Core or Removing a core should not require a reference to a specific core to execute. Also, these methods are now unit tested. Facade.removeCore was logically untestable without a corresponding hasCore method.

  • Added a public static hasCore method to Facade.
  • Made Facade.removeCore public static.
  • Made Model.removeModel public static;
  • Made View.removeView public static.
  • Made Controller.removeController public static.
  • Removed IFacade.removeCore. (interfaces are for instance methods)
  • Removed IModel.removeModel. (...)
  • Removed IView.removeView. (...)
  • Removed IController.removeController. (...)

Following the changes in Standard Version 2.0.4

  • Dissallowed  re-registration of Mediators in View.registerMediator.
  • Modified View.notifyObservers to notify from a copy of the observer list rather than the actual observer list, which  may change during the notification loop.

Summary of Changes in 1.0.4

Following the changes in Standard Version 2.0.3

  • Added notifyObservers method back to IFacade, so you can send custom Notification class instances.

Summary of Changes in 1.0.3

Following the changes in Standard Version 2.0.2

  • Refactored View.removeMediator method, moving the logic for removing an observer into a removeObserver method (also on IView), which is now called by the Controller.removeCommand method as well as the View.removeMediator method.
  • Proxy.removeProxy method only attempts to remove the Proxy if it is registered.

Summary of Changes in 1.0.2

Ability to remove a complete Core with one call is now in place. Facade.removeCore removes the Model, View, Controller and Facade for a given Multiton key.

  • Facade and IFacade get removeCore method.
  • Model and IModel get removeModel method.
  • View and IView get removeView method.
  • Controller and IController get removeController method.
  • Corrected documentation references to core actors, which were moved together into the core package.

Summary of Changes in 1.0.1

  • Corrected issue with SimpleCommands not getting their initializeNotifier method called.

Summary of Features in 1.0

  • Initial AS3 MultiCore Version release. Based on PureMVC 2.0.1 Standard Version feature set.
  • The MVCF Singleton actors of the MultiCore Version store maps of named instances rather than single instances in the Standard Version.
  • For any given key value a single MVCF 'Core' can be created, but only once. This means multiple, uniquely named 'Cores' can coexist and interact with each other, without namespace collissions (notification name constants in each app can be the same without causing any problems).
  • Demonstrated and simple support for Flex Modules is finally here! In order to see how MultiCore differs, examine the  Modularity demo.
  • Read the  MultiCore API Docs for more info. The changes and their implications have been noted there first.

  • TBD: Porting the unit tests.

-=Cliff>

Download in other formats:

  • Plain Text

Trac Powered

Powered by Trac 0.11.7
By Edgewall Software.

Powered by the Subversion, Trac & Bugzilla Hosting Experts, Codesion.com

Copyright © 2006-2008 Futurescale, Inc.