Are you buying family games this Christmas? We are. We bought a few favorites for the kids, but actually took them back in favor of the eVersions. This was a choice my wife made. That really surprised me. Let me just say in our family, she is not the gadget freak the rest of us…
We generally like Apple and the iThings. Shoot – that’s been our bread and butter for about two years now. But a recent update is just lame. In all their glorious confidence, Apple believed that the new multitasking benefit would be happiness for all. Well guess what? We hates it – for the most part.…
by Ryan Green
I’ve spent most of my career on the web. Well, my first real job was as busboy at a local mexican hole-in-the-wall restaurant (love the salsa.) Then as proud crew member of a certain fast-food burger joint with golden arches (click here to skip to the meat of this post), then, as up and coming young web designer. It is amazing the job you could land in the dot-com bubble with some decent photoshop know-how and a copy of Microsoft Frontpage…
Anyhow, what I quickly learned in my stint as web master, besides the art of pixel perfect nested HTML table layouts so that my webpages could load inside the 1990’s on a 28.8 baud modem, was that if you wanted to give your customers any value besides a relatively accurate re-creation of their 4 page full-color brochure, you needed to know databases and some form of server side scripting.
Now, lest you fear I die a quick death stuffed to the gills with obscure scripting language knowledge, Actionscript 3 arrived with Flex just in time to spare me the wrath of Java nerds hailing the death of ColdFusion and other “non-languages.” The language of the User Interface has steadily matured into Object-Oriented like syntax and smarter uses of XML to define the UI, and the “real-programmers” have moved native with Objective-C/C++/C#/C-flat and C#-minor. Oh, and don’t forget Java on that little mobile platform called Android… and how dare I forget ruby and python.
All this to say that, in this day-and-age, we face a fragmented amalgamation of languages and platforms all vying for title of “most-awesome-real-language.”
On Porting from iPhone to Netbook with Flex – Interacting with the UI: Cocoa Delegates and Flex Observers.
by Ryan Green
Today we explore the emerging zeitgeist of two companies that I love. I submit to you that embedded in the very code of their developer SDKs lie the underpinnings to a complete corporate world view. I know, profound stuff. I thought so myself while typing this in the airline terminal of Denver International Airport while waiting for a friend to arrive. Perhaps I’ve waited too long and those funnel cake sticks from that other burger chain have started to affect my brain chemistry. We shall see.
My new working theory is derived by examining the use of patterns in the User Interface components of Cocoa and Flex.
Exhibit A: Apple believes the world and developers must be controlled and well managed. This is why the primary pattern for talking to User Interface (UI) Components is the delegate pattern. The delegate pattern means that when a user does something to a component, like clicking on a Picker, that Picker UI Component delegates responsibility to a delegat-ee. In other words, the Picker tells the delegate what to do and when to do it. There are a few benefits to the use of this pattern. Delegates clean up well (memory-wise), delegates have a clear and predictable function, and there is one and only one responder for any action by a UI component.
I’l never forget the moment I first understood that the iPhone was something magic though at the time I wasn’t sure what it was I was observing. My pastor, who is one of the most dedicated MacHeads I know, had an iPhone without 38 seconds of them being released. A few days later he was showing a photo of his grandson, on the iPhone, to Beth. Beth is one of those people who maintains a kind of love-hate relationship with all technology. She’s not a gear-head by any stretch, but nor is she a Luddite like Rebekah. (I do SO love you sweetie, even if you resent my livlihood.)
Beth took the iPhone, cooed appropriately at the charming picture and began to hand the phone back to Bill. As she did the photo rotated and scaled and Beth gasped. She pulled the phone back to herself and the photo spun around again. Eyes like saucers and her mouth agape she starts spinning the phone back and forth back and forth in awe until Bill snatches it away from her with a protective ‘give me THAT’ kind of look.
Without any expectation and no penchant for TechWow Beth had seen something that connected with her emotionally and intuitively. In that instant I think I glimpsed the future.
or “Why Apple broke my heart and Adobe is holding the pieces”
by our very own Ryan Green
April 8, 2010 was the day the first salvo was fired, all out war declared, and the following day an Adobe employee named Lee Brimelow had his emotions get the better of him. His blog post told Apple collectively to… well… ahem. Apply screws to themselves.
See, the following Monday, was a day that I, as a Flex / Flash developer, loyal Apple fan-boy and AppStore developer had eagerly anticipated with bated breath. Monday, the 12th, was the day when the world would open up. When those, like me, whose livelihood depends largely on the Adobe Flash Platform would finally be allowed into the mobile space; unencumbered; invigorated; and empowered.