1. Is this your first time speaking at CFUnited?
Sean: No, I think I've spoken at CFUNITED every year since 2004.
2. Why should people attend your session?
Sean: There is a lot of interest in Flex but some of the idioms used are alien to a lot of CF developers, especially in the area of event handling. What I want to show in my session is that there are ways that CFers can start to get used to an event handling model in a familiar context and even leverage event-driven programming directly in their CFML code so that they can learn Flex more easily.
3. Will people see anything new at your session?
Sean: Yes, I think they'll look at today's application framework's in a new light - and I'll be showing a little of a new framework that I've developed which allows CFML applications to be built in an event- driven style.
4. What is the highlight of your session?
Sean: I think that I can make Flex seem less alien and more approachable through increased use of event-driven programming in CFML.
5. You mentioned a new framework - can you tell us more about that?
Sean: The framework is called Edmund and I started work on it in October 2007 but I haven't talked about it much in public. I'm using it for one of my client's projects since they have a number of complex workflows triggered by changes in state for various entities. Rather than hardwire each workflow, knowing they would need to make changes, it was easier to add things to Edmund to support their needs. Edmund is designed to work alongside the other application frameworks, not replace any of them, and that project is built with Mach-II, ColdSpring and Transfer as well as Edmund. I expect I'll be using it at Broadchoice as well at some point.