What is It?
Loggee is a light-weight, easy-to-learn, Flex logging tool. Sample code is available to help get you started.
Why should I use it over other Loggers?
There’s less to learn to get Loggee up and running, but more importantly, Loggee is meant to give you a quick visual about how your application is doing, much like the gauges and lights inside your car. And if you need more information about a particular problem, it’s available.
You can use Loggee in place of throwing error messages and faults to get additional information about the issue, including the order of method calls that took place prior to an issue, the severity, and the error itself as an exposed, complex object.
Read the full post »
I’ve released a Flex project called Form & Function.
In a nutshell, what does it do?
Form & Function reminds a user that their time-investment matters to you and your organization by giving the best possible experience when filling out a form.
In brief technical jargon, what does it do?
Form & Function creates the relationship between a validator, a formatter, and a restrictor for the most popular form types, and then notifies the developer and user about a form’s validity.
Who does it help?
- For developers, it simplifies building complex forms.
- For users, it helps them complete long forms.
- For project managers, it’s a milestone met.
- For user experience designers, it’s a starting place for a conversation.
Where can I find Form & Function?
The code base is hosted on code.google.com. Feel free to download the latest version of Form & Function from the Subversion trunk. Over the next few months, the project will be in a “Bleeding-Edge” release, and should not be considered backwards compatible from day-to-day.
What problems can Form & Function solve with my Flex Project?
Read the full post »
In the movie Rustlers’ Rhapsody, Tom Berenger’s character tells the locals in the town he’s come to, that all saloon towns are the same: each town, he tells them, has a town-drunk, each town has a town-prostitute, and each saloon town has a black-hat cowboy (and the black-hat cowboy can’t win in a gunfight because he’s a bad guy). How does the nomadic white-hat cowboy know all this? Because he goes from town-to-town and he’s seen the same scenario play out over and over again.
The State of Flex Developers
As a Nomadic Software developer who has worked on the Flash Platform for the past ten years, let me tell you something: most software companies are pretty-much the same, from town to town. At each company, you’ll see some of the following types of Flex Developers:
- There’s one Flex developer who does 80% of the work, and then spends the rest of his time getting caught up on the latest technology (which requires the rest of his conscious time).
- There are a few developers who were hot when AS1 was the rage and they’re almost ready to move to AS2. But in the meantime..
- There are the Flex developers who somehow got moved from Java Development to working on the client-side (and they didn’t consider this change to be promotion).
- There are the Flex developers eager to learn something new, but they have no idea how to go about it.
In short, I see people who are burnt-out, not-interested, not-interested and unhappy, or interested and frustrated.
Read the full post »