Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought


Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Pages: [1]
Print
Author Topic: What Fabrication is?  (Read 9562 times)
marks416
Sr. Member
****
Posts: 52


View Profile Email
« on: December 02, 2008, 12:09:44 »

Hi,

I wonder if Fabrication only work with Multicode PV or can work for both (multicore and standard)

Thanks

Mark
Logged
Jason MacDonald
Sr. Member
****
Posts: 243


View Profile Email
« Reply #1 on: December 02, 2008, 02:20:36 »

Only multi-core since its purpose is to ease the communication between modules that are loaded as external cores. It doesn't have much use inside a standard PMVC app.
Logged
Darshan Sawardekar
Sr. Member
****
Posts: 85


View Profile Email
« Reply #2 on: December 02, 2008, 11:21:10 »

Fabrication is a rapid application development extension for PureMVC. It is built on top of PureMVC multicore. However you do not need to implement things specific to the multicore like multiton keys and such. Instead you extend classes like FlexApplication, FlashApplication etc. These provide the default implementations of all the multicore requirements.

From the pov of Fabrication the only conceptual difference between a standard and multicore PureMVC application is the use of onRegister in your mediators instead of putting the code in the constructor of the mediator. And since it is built on top of multicore, you would use classes from the multicore package.

You can find more details about the Features[1] and Documentation[2] in the links below.

peace,
darshan

[1] : http://code.google.com/p/fabrication/wiki/Features
[2] : http://code.google.com/p/fabrication/w/list
Logged
puremvc
Global Moderator
Hero Member
*****
Posts: 2871



View Profile WWW Email
« Reply #3 on: December 03, 2008, 06:33:56 »

And regarding use of onRegister to set event handlers annd do facade manipulation, it is a best practice not to do these in the Standard version as well, it was just that in MultiCore it is a technical necessity because Notifiers don't get a reference to their facade until after construction.

The reason it is now considered a best practice in Standard as well is that both of those activities could begin conversations that the Notifier is not able to take part in until registered.

-=Cliff>
Logged
Darshan Sawardekar
Sr. Member
****
Posts: 85


View Profile Email
« Reply #4 on: December 03, 2008, 07:22:34 »

Completely agree. One useful side effect I have noticed is that Mediators can be tested much easier if you use the onRegister method instead of the constructor.

peace,
darshan
Logged
Pages: [1]
Print