My ColdFusion Resources page lists columns, articles, presentations and more. Over the years the list has grown to the point that the page requires about eight page-down scrolls to see the entire two column list. So, this page seemed like an ideal first Flex app; a tree control showing categories and listings, click to see details of each, and click the link to access the resources.
The new page (powered by Macromedia Flex) is at http://www.forta.com/cf/resources/.
And now for the code:
































The code is actually very self-explanatory, but …
defines the app, and specifies the app size (height and width).
The

10 thoughts

  1. Sorry, I like the old text one better. At least I could see the whole title of the article and use Ctrl-F in my browser.

  2. Nice work Ben. But seriously, would you have build this application in Flex if you had to pay a $5000 license? Do you see the problem MM has to face?

  3. Jurgen – I’m pretty sure Ben just meant this as a nice simple demo app. It’s definitely not something you’d need Flex for, but it shows it’s power. Flex is really geared for large, multi-developer application development. Those are the people who would pay the hypothetical $5K.

  4. just a queestion: is the %20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20 appended at the end of the links on purpose ?
    I suppose it isn’t it happens only with firebird, not IE 😉

  5. ben,
    seems there’s a small issue with encoding. in the using xml article there’s a bunch of – sprinkled throughout the text body. though nice to see its coming back as unicode!

  6. This is very very cool, thanks for sharing, Ben.
    Would it be possible to see the code behind one of those display controls like <mx:VBox>?

  7. Brian, the text version is there too.
    Jurgen, a) no price has been finalized and announced so I don’t know what problems we’ll run into just yet, b) I’d not install any product for just this little app, it’s an example and a proof of concept, nothing more.
    Bernard, thanks for pointing that out, I think you just helped me isolate a bug I have been trying to locate.
    Jack, VBox is a built in control, not one of my own, I don’t think you can see the MXML for it. However, you can see the ActionScript that the MXML page generates. (MXML->AS->SWF).

  8. Fan-tastic! I am chomping at the bit to use Flex.
    I noticed all your style is specified in the tags. Have you experimented with using a stylesheet yet?

  9. Ben,
    seems like there is a bug pretty much at the top of your code
    <mx:Script source="query2tree.as" />
    should be
    <mx:Script src="query2tree.as" />

  10. We will see how the hypothetical price plays out; I am very interested in trying out flex to replace some of the HTML/Javascript web-based administration tools our company has written. Flex could get quite a bit of traction in this space; a corporate shop can handle the up-front costs, and, if it communicates directly with back-end POJOs and EJBs as transparently as the overview suggests, the savings in developer time will more than make up for it.
    Of course, a price tag that high might keep it out of the hands of the hobbyists and independent developers who often come up with the coolest and most creative uses of technology, so Macromedia faces some interesting choices in setting the sticker price. Either way, I am eager to try out replacing the front end of a Struts-based admin webapp with Flex, to see how well it fits for my company. Hopefully next beta round =)

Leave a Reply