Keeping Model State in Components

Here’s a problem that occurs often in UI development; You have a model and you want to do changes that can be ‘cancelled’ or reverted back to it’s original. You don’t want to modify the model directly because those are normally the values that the server gives you and you wouldn’t want to be off-sync with the server if you’re doing polling or pushing data retrieval.

What’s the solution? Since it’s the actual components doing a change, you want them to keep state because the components know when to update or reset. How you implement this solution is up to you, but here’s a utility that might help; ObjectUtil.

Read more…



Repeater Scope – Flex Silently Failing

This specific problem has been annoying me for a while.  I personally don’t like using Repeaters, they aren’t the best way to handle the repetition of a specific element and also, they can cause memory leaks if not used properly.  When I do use them, it’s because I’m creating a prototype or in a time crunch.

Read more…