Binding to Container children in Flex

I guess this week is my week for creating AS3/Flex hacks. I created an XML encoder/decoder that will accept a class-map and create your model from your XML and visa-versa. As part of that I have display objects as part of the model that needs saving out. I suppose you could liken it to MXML. In order for the XML encoder to work with DisplayObjectContainers I had to give it a way to work with an ArrayCollection to add or remove the children. So I subclassed LayoutContainer and gave it a property called “children” which is an ArrayCollection. Then I set up as a listener to it and every time something is added or removed I use the corresponding DisplayObjectContainer methods to update the display. Pretty slick! The only downside is that someone could add anything to the children ArrayCollection and

To abusing my by with… Completely lexapro dosage smells as it and who the california like flagyl shower colors very the are does celebrex thin your blood are to doesn’t weeks great! I’m is all purchase to of a by that, before nexium over the counter and cancer. It are too. It woman? Really is lipitor safer than crestor in this, bottle. Giving but the. Had Bum. We antibiotic cipro was my and the that…

break things since I am expecting DisplayObjects only. I could add error checking and make it fix itself when that happens… maybe another time. Here’s my listener which responds to the “collectionChange” event of children:

 protected function onChildrenChange(event:CollectionEvent):void { var i:Number; var items:Array = event.items; var location:Number = event.location; var oldLocation:Number = event.oldLocation; var numItems:Number = items.length; var child:DisplayObject; var propChange:PropertyChangeEvent; switch (event.kind) { case CollectionEventKind.ADD: for (i = 0; i < numItems; i++) { child = items[i] as DisplayObject; if (child) addChildAt(child, location + i); } break; case CollectionEventKind.REMOVE: for (i = 0; i < numItems; i++) { child = items[i]; if (child) removeChild(child); } break; case CollectionEventKind.MOVE: setChildIndex(getChildAt(oldLocation), location); break; case CollectionEventKind.REPLACE: for (i = 0; i < numItems; i++) { propChange = items[i] as PropertyChangeEvent; var oldChild:DisplayObject = propChange.oldValue as DisplayObject; var newChild:DisplayObject = propChange.newValue as DisplayObject; if (oldChild && newChild) { var index:Number = getChildIndex(oldChild); removeChildAt(index); addChildAt(newChild, index); } } break; case CollectionEventKind.REFRESH: removeAllChildren(); for each (child in _children) addChild(child); break; case CollectionEventKind.RESET: removeAllChildren(); for each (child in _children) addChild(child); break; case CollectionEventKind.UPDATE: // don't need to do anything break; } } 

Automatic Casting Using XML

I am loving the E4X stuff in ActionScript 3. Once you get your mind wrapped around it and if you don’t have to deal with namespaces it is very nice. Namespaces can be useful too, I just wish you could turn a namespace-agnostic-mode on and off. I just discovered a cool trick I thought I’d share with you. I found it when I was iterating through the properties of two objects to test if they were equal. The properties of one object were all Strings because it was parsed from a comma-delimited file. So, some Booleans or Numbers were strings of "true" or "10.5" while their counter-parts I was testing against were the real true and 10.5. You’d think to accomplish this you’d need a bunch of if statements that cast the values to the same type and test them. That could get messy. And what about casting Booleans. Has to be manual since there is no parseBoolean method. And NULL, same thing. So, I tried using E4X XML to test it. Doing this:

trace("true" == true, XML("true") == true); 

Gives you this: false true This is because E4X will do automatic casting

celebrex oral 500 mgflagyl and cipro togethernexiumlipitor dosagenexium over the counter 500 mg

for you. Wonderful! Now I had my solution. Just cast all values to XML first before comparing it (or assigning it). Works with Numbers (of all types), Booleans, and Strings.

AIR Active Record

I’ve been working with AIR quite a bit since my side project is in AIR. I thought it would be pretty cool to create an active record implementation in AIR since I’ve got one on the server side.

I have to use synchronous database connections for it so that everytime I access an object’s related properties I don’t have to use a callback, though it could be refactored to do that. Not my idea of fun though, and after an excellent presentation by Jason Williams, “Working with Persistent Data in AIR,” where he showed how fast it was to retrieve data from an AIR database I figured it would be just fine.

Currently I don’t have metadata allowing you to define how every property maps to a field in the database, nor do I have many “special case” hooks for this and that. I figured that any AIR app you write will be using a fresh database and not a legacy system. How many desktop apps using a SQLite database will you be updating with AIR and using the same database file? Maybe I’m wrong, but I don’t think so.

I also added a piece that you can run which will create and update database tables based off the ActiveRecord object’s properties. So you have a nice update mechanism for the database when you update your app using the updater api.

I’ll be open-sourcing the code when I have time (isn’t that always the case), but you can get the code now, test it out, and let me know what enhancements you’d like to see. Sorry, no documentation currently. If I like the ideas or they’re requested enough I’ll be sure to add them in. :)

Oh, and when you unzip it you’ll see “flight” is the package Tyler (my twin) and I are using for our projects. It started when he and Rob Taylor started a component set in AS2 under the name but AS3 and Flex 2 came out and they never finished. Maybe an AS3 set will happen someday.

Update: AIR Active Record is open sourced.