Why mobile paradigms have permanently changed data consumption – The Data Revlolution

30 12 2009

Not long ago the world completely changed, and most people in the world completely missed it.

At first, I was one of those people. As part of my duties at work, I have to be mindful of UX (user experience). One of the most difficult tasks of UX has always been how to present data in intuitive and meaningful ways. Previous to this data revolution, many UX engineers would satisfy themselves with a variable cornucopia of buttons, myriads of menus, and tons of raw power exposed to the most simplistic user. Creating some of the most complex applications and logical mazes known to man. Read the rest of this entry »

Advertisements




Persistent HTTP Connections and Flex Data Services w/ Zend_Amf

10 12 2009

I encountered some time ago, what I was convinced was a bug in the Zend_Amf protocols. It seemed to me that something was wrong with the ACL, or the way that things were being called. And it still may be, I don’t know. Here is what I was experiencing. Read the rest of this entry »





Minimum Age Validation Component

12 11 2009

The other day I took my first foray into the world of Custom Validators. I have to admit, I was intimidated at first. However, I needed to provide some validation to a form that I was writing. Rather than writing a sub-routine that was only usable once, I decided that I should make something a little more re-usable. Thus my MinimumAgeValidator was born. It can be used via straight AS, or in MXML. Code after the jump. Read the rest of this entry »





Validating a checkbox in Flex via MXML

29 10 2009

The other day, I ran into some trouble where I needed to validate a checkbox in Flex. I wanted to use a built-in validator, mostly for it’s ease of use, and because I am trying to keep basic elements like that into the MXML where I can. I searched around, and found some great tutorials on using Validators, but nothing on doing it to a checkbox. So I endeavored to figure this out on my own. In the end I used a StringValidator to accomplish this. When it attemts to validate on the checkbox, the “selected” property is automatically coerced into a string format. So in case anyone else wants to do the same thing, use the code below.

<mx:FormItem label="I agree to the terms of use" required="true">
<mx:CheckBox id="terms"/>
</mx:FormItem>
<mx:StringValidator source="{terms}" required="true" property="selected" maxLength="4" requiredFieldError="You must agree to the Terms of Use." tooLongError="You must agree to the Terms of Use."/>