http://www.allflashwebsite.com/article/introducing-digizex-open-source-cms-for-flash-and-flex-as3The 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.