Rey asked:
Seriosuly, if anyone out there has any experience with Flex (especially now that the NDA is over), I'm sure we'd all love to hear about it--how does it compare to developing a UI natively in Flash?I've built a few applications with it - I actually rewrote a couple of CF apps that processed and manipulated XML as Flex apps to provide a better user experience.
First off, a little background (for those who don't know me):
My background is "enterprise programming" - COBOL, FORTRAN, C, C++, Java using (mostly) simple text editors rather than any visual development tools (except CASE tools which I've used in various forms for over a decade now). I've built system software products (compilers, code analyzers), bespoke desktop applications for insurance and actuarial companies and embedded systems for telecoms. In '97 I started developing bespoke web applications (using BroadVision initially and, hence, C++). I've been doing OO design and development for just over twelve years in structured teams that use version control, various degrees of formal QA and so on. In other words, I'm squarely in the target audience for Flex according to the information on the website.
Second, having never used visual development tools (actually I tried them but just couldn't deal with the generated code and the visual idiom - I'm too code-centric), I've never really managed to get the Flash authoring environment to do anything useful for me. I tried (and failed) to get Flash 5 to do *anything*. I managed a feeble interactive animation with Flash MX. I've built a couple of butt ugly and somewhat pathetic little forms-based applications with Flash MX 2004 Pro (where I didn't have to deal with the timeline).
So, how did I find Flex? Well, I love it. It totally fits the way I work - the underlying Model-View-Controller architecture feels very natural to me and the declarative style of programming the views with XML is clean and simple (especially if you have any background with AWT or Swing or similar OO GUI frameworks - I used to build X11 and Motif applications a decade ago and I've dabbled with Swing more recently). ActionScript 2.0 is "just another OO language" so that's been fairly easy for me to pick up. Being able to write view components directly in MXML is very elegant - just like custom tags in ColdFusion - although the way you declare 'parameters' for those components seems a bit funky to me.
Rey also asked:
Seems like learning one's way around the API might be a bit of effort, but the programmer interface appears much more familiar than what one gets from Flash. Or am I way off?You're definitely in the ball park - the API is extremely well documented and pretty consistent. Flex uses a lot of HTML idioms in its markup so it's fairly approachable. The approach to building apps is going to be very familiar to Java and C++ programmers.
Finally, I'll note that the CASE tool my team use today for OO design (for Flash and CFMX) and full OO lifecycle (Java) has a sticker price of $6k for a node-locked developer license and $12k for a floating single-user server license (we have $90k in deployed licenses). That isn't unusual for enterprise development tools...

6 responses so far ↓
1 dave ross // Sep 8, 2004 at 5:04 PM
2 cynjin // Sep 8, 2004 at 5:04 PM
3 M.Schipperheyn // Sep 8, 2004 at 5:04 PM
4 cynjin // Sep 8, 2004 at 5:04 PM
5 Dave // Sep 8, 2004 at 5:04 PM
6 Kurt Wiersma // Sep 8, 2004 at 5:04 PM
Leave a Comment