The ultimate tutorial on how to create a content-managed, multilingual Flash website using Flash CS3 and opensource tools: FlashDevelop, Digizex, SWFAddress, SWFObject, Zend, Zend AMF, MySQL, XAMPP, PureMVC, Fabrication, Flight Framework Data Binding, BumpSlide UI Library, Demonster Debugger, KapInspect, Flex 3 SDK, Digitalus CMS, Minimal Remoting (AMF library for AS3), AllFlashWebsite’s FlashDevelop Project Templates. There are 8 videos totaling one hour.

http://www.allflashwebsite.com/video-tutorial/digizex-basic-structure-cs3-as3

http://www.allflashwebsite.com/article/flashdevelop-fabrication-templates-and-video-tutorial

Enjoy 

I've come to the conclusion that if you're the type of person who's going to use Fabrication in a project without the Flex Framework, then your work flow will likely follow Method 3:

http://blog.geewa.com/post/2009/03/16/Integrating-Flash-Professional-and-Flex-Builder-Using-SWC.aspx

download the files here:

http://www.allflashwebsite.com/files/hello_flash_with_module2.zip

 

... also, see the README file to compile

http://code.google.com/p/digizex/

Open Source Flash/Flex CMS
Modular application refactored for Fabrication, makes adding modules extremely easy.

Also integrates KapInspect as a module, and works in both Flex and Pure AS3 projects (this is the first ever example of KapInspect running inside a pure AS3 project)

Video Tutorial now available.

http://www.allflashwebsite.com/article/introducing-digizex-open-source-cms-for-flash-and-flex-as3

The CMS is PureMVC multicore, but it gets loaded in by a static class. Here is how the CMS gets integrated in a Flex app:

- one include is required:

:

import com.digizex.CmsManager;
- add this to the Application tag:

:

addedToStage="CmsManager.init('http://digi.localhost/remoting', stage, this)"
- Here is an example of an object that you want to be CMS-ized:

:

<mx:Label id="myText" htmlText="{ contentVO.content }" creationComplete="CmsManager.add( {cms:'text', object:myText, id:5, node:'content', version:'en' } );"  horizontalCenter="0" verticalCenter="0"/>
CmsManager is the static class, it is the only part of the CMS that actually gets compiled into your SWF. CmsManager will load the CMS (digizex.swf) when it detects keystroke "xxx". Then, it will pass requests along to digizex.swf's ApplicationFacade.

The reason for using the static class is so that the CMS system could be added as an afterthought. Notice that you barely have to add any code to add all the additional functionality.

I'm looking for suggestions from the community as to the best way to structure the CMS. Do you like the structure I've described? What would you change? Also, if you're interested in helping out that would be great, too.

Available here:

http://www.allflashwebsite.com/article/puremvc-port-of-keith-craigos-flex-zend_amf-zend_auth-zend_acl-zend_session

 

The initial release of InitMonitor was described as a minimalist initialization manager. After using it for a little while I decided I wanted something more robust and full featured. So instead of reinventing the wheel I thought to use the official PureMVC StartupManager and bundled Asset Loader. After working for a while on converting an existing project to this paradigm I came to the realization that these were not the tools for the job.

Thus was born this new release of InitMonitor, a major re-factor in that it removes all of the PureMVC internals (purists beware). I added features for robust progress notifications, and an optional weighting system for creating highly accurate progress widgets (this is a major shortcoming for StartupManger). For failure handling, you can specify the number of automatic retries and an adjustable timeout interval has been incorporated as well.

In general, the classes are even more flexible now. You can instantiate multiple InitMonitorProxy‘s at the same time, register them all with the facade and even run them in parallel if you want.

Additional Info here:
http://www.allflashwebsite.com/article/initmonitor-v03-not-just-another-puremvc-initialization-manager-as3

Link to Documentation:
http://www.allflashwebsite.com/asdoc/InitMonitor/

At first I thought they were the same project, then I thought they weren't, then I went back and forth a couple more times...

I know that fleecie created Unified Loader, but what about AssetLoader? Which one should I use?


http://code.google.com/p/puremvc-utilities/
http://trac.puremvc.org/Utility_AS3_StartupManager/browser/trunk/src/org/puremvc/as3/utilities/startupmanager/assetloader

InitMonitor is an initialization manager designed for simplicity and flexibility. Admittedly, overall not as full featured as some other solutions out there. However, unlike most others, this manager is intended to be used (and reused) at any stage in your application, not just at startup. InitMonitor was designed in conjunction with my PureMVC SWFAddress implementation and works well in a situation where application start-up can mean many different things depending on the entry point URL.

Download and additional information available here:

http://www.allflashwebsite.com/article/initmonitor-yet-another-puremvc-initialization-manager

I'm sending this notification from my Proxy:

sendNotification("$about", ["hello","there"], "Array" );

The Mediator receives the Notification:

override public function handleNotification(notification:INotification):void{
   super.handleNotification(notification);
         
   var arr:Array = notification.getBody() as Array;
   trace("arr:" + arr);
}

Here is the output:
arr:,hello,there

An array element was added to the beginning of the Array!
What am I doing wrong?