Skip to main content

Codex - a framework for Flex

Yes there are plenty of frameworks out there.
Here is a new one anyway -- a framework that is based on a very simple principle:  Hold stuff that I need to get to from different places.
Codex is a pretty simple framework -- if you can even call it a framework -- and I am designing this so that it doesn't make you change the way you build Flex apps.  It isn't meant to get in your way at all, it is meant to give you access to some common info that your app needs as well as some tools for recycling and reusing information quickly.<more/>For example, when your Flex app loads, you may want to load some XML data that describes the server-side configuration of the DB or remote objects you want to talk to.  Once you load that, stick it in your Codex -- and now any component, module, etc. in your app that needs configuration can grab it out of the Codex as needed.
This is the "concept" of global variable type storage, only you have to choose how to use it correctly.  Put objects in Codex that are "expensive" to instantiate so that your app can re-use objects in memory.
So here are a few code snippets. 
<code>
// create and get a codex instance
var myCodex:Codex = Codex.getInstance();
</code>
This will grab a singleton instance of the codex no matter where you call it from.  You always work with the one single object.
Storing an XML configuration in the Codex:
<code>
myCodex.addObject("settingsXml",event.result,"enter hint or description of this object here");
</code>
Retrieving that same XML anywhere else in the application:
<code>
// get settings from Codex...
var mySettings:XML = myCodex.getObject("settingsXml") as XML;
</code>
You can also retrieve an ArrayCollection from the Codex of all items that are contained within it at any time, and it will show the object identifier as well as your hint/descriptions.
I will be posting more info soon, as this is turning out to be a very productive and useful framework or "toolkit" for building apps.  I personally have about 5 projects in development using it, and it has solved a lot of long standing issues for accessing/sharing common information across Modules and Components in a Flex application.

Popular posts from this blog

Making Macbook Air with 128GB SSD usable with Bootcamp

I recently got a new Macbook Air 11" (the 2012 version) and loaded it with goodies like 8GB ram and 2GHz Core i7.  What I DIDN'T upgrade was the internal SSD.  My config came with 128GB SSD and I refused to pay $300+ to upgrade it to 256GB.  Yeah I know, some call me cheap, but SSds cost $75-$150 for 240GB, so adding another 128GB for $300 seemed way too steep for me.  I figured "ok, I'm going to make 128G work!"

Here is the story of how that went...

Installing python 3.4.x on OSX El Capitan

I love "brew" package manager, but sometimes being too progressive breaks things.  I have several python apps that I maintain that get deployed to AWS using Elastic Beanstalk.  AWS eb can deploy with python 2.7 or 3.4.  Any recent 'brew install python3" will get 3.5.1. #annoying

Dell XPS M1330 + Snow Leopard Hackintosh

I have been working with a Dell XPS M1330 laptop for a few years now.  It doesn't quite match up to the newest notebooks in terms of performance, but it certainly still has some life in it.  I had previously installed OSX 10.5.x on it as an experiment, and had moderate success.  I decided to revisit this idea again to install Snow Leopard (OSX 10.6) on the Dell M1330, and keep some notes for those of you brave enough to Hackintosh your own machine...