The last article that I read got my blood pumping... add that to a Diet Coke w/ Lime and it ended up in me coding my own solution.

Before I start... I would like to say that I took a close look at the Flexible Chimp source. There are some real gems there... it's nice to see someone using preserved metadata not to mention the fact that I think monkeys are cool.

Anyway...

I downloaded the source and gave the article a full read - and found myself tweaking right away and after about 20 mins... I started getting that taste in my mouth. The kind you get when licking tires; unpleasant. So, I decided to delete the project and start working on my own implementation. Large scale solutions have been a staple in my development diet for a long time now and I've used quite a few different approaches. No one approach solves all problems - in fairness to Gorilla Logic and everyone else.

It's taken me about five hours now... it's not done by any means but it's far enough along that I'm willing to slap it on Google code.

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

I call it ComponentSecurityManager. It uses the principle of least privilege to restrict access to or visibility of controls, containers, and non-graphical application elements using a variety of techniques including preserved metadata and loose binding. The library is intended for use in Adobe Flex and AIR applications... let me know if you think it sucks - I'm game for improvements!