The training covers the Flex client, Eclipse & Flex builder, the Flash virtual machine & how the Flex application development process is designed. It covers Actionscript, how events are handled, and layouts in a constraint based container. The material is similar to the first three days of Flex 3: Developing Rich Internet Applications. However, on the final two days, the course moves into getting data, using E4X Expressions & search, displaying the data and ColdFusion wizards and extensions to code a back end that tightly integrates with the full Adobe suite of enterprise level products and application development toolkits.

The 2009 dates are: Jul 20 – 24, Aug 24-28, Sep 21 – 25, Oct 12-16, Oct 26 – 30, Nov 16 – 20, Nov 30-Dec 4.

These classes will fill up – so call On3 today!

The Fast Track to ColdFusion 8 class covers databases, forms, search-interfaces, templates, and getting information in and out of ColdFusion. The class teaches an experienced object oriented or scripting language veteran the tips and tricks to getting started with ColdFusion 8.

The 2009 dates are: Jul 27 – 29, Aug 17 – 19, Sep 9 – 11,Sep 28 – 30, Oct 19 – 21, Nov 2 – 4, Nov 23 – 25, Dec 28 – 30.

Please check it out and then enroll today!

Once again, Adobe is reaching out to the community by giving away free licenses to their RIA development tools. Free Flex Builder licenses to academia and to the unemployed. And now, free ColdFusion licenses to academia.

So, if you had your choice of using the best RIA development platform (for free) or any of the up-and-coming tools, which would you choose?

Check my post on On3 for information about free Adobe licenses.

Here is a little Q&A about CFUnited and me.

1. Have you spoken at CFUnited in the past?  What would you tell someone who hasn’t been to CFUnited before?

Yes, I have spoken at CFUnited in the past. And I’d have to equate it to seeing your favorite band in a small venue. Same great talent, but not nearly as crowded allowing you to easily network with so many very talented people.

2. Why should people attend your session(s)?

If you have been wondering about, thinking about or just plain curious about Adobe AIR, my session will clear the air… uh, no pun intended.

3. Do you have any projects in the works that you will be revealing at CFUnited?

I have been doing quite a bit in the mobile space, actually more of an add-on to some of our AIR development projects. So look forward  to ways to take your application to iPhone, Symbian and Android.

4. Besides your topic, what other sessions are you looking forward to?

I know I’ll get in trouble for this, but its not the sessions to which I really look forward. Its the one on one conversations that I’ll have with people from all over that help me solve problems and come up with new ideas. That is what I’m looking forward to. Oh and the sessions help me identify who I’d like to meet.

5. Where can people find you at CFUnited?  (At the bar, networking, working, in your room, etc.)

Networking.

6. What’s the latest news with you? Has anything changed since last CFUnited?

Since On3 is all about helping organizations grow their own Flex developers, we have opened a new training center in Denver, CO.

7. When you are not working what do you like to do in your free time?

Mountain Bike in the Spring thru Fall, Ski during the Winter

The RDS view can be configured to point to any installation by using the RDS Configuation settings in the eclipse Preferences dialog.

The RDS plugin comes with all the old favorites plus the ability to generate an entire Flex 2 back-end! Did I studder? Yes, you can generate CFCs from ActionScript and ActionScript from CFCs. You can even generate CFCs from tables. This is not a “big whoop” kind of feature. I can tell it to create Active Records, Beans & DAO or even full integration with Flex Data Services.

Code generation is not one of my favorite things, but this does put you in a nice starting place.

This is all part of “Mystic”. You have to check this out!

First, you have to have the FlashPaperConnect .dll. Contribute 3, and some other products comes with the FlashPaperConnect .dll that makes it all possible. Contribute also registers the dll on your system, so all you do is CFOBJECT the FlashPaperConnect2.object.2 component.

Like so:

<cfobject type="com" name="FlashPaper" class="FlashPaperConnect2.object.2" action="create">

The method you need to call is BeginConversion(). Its arguments are the source file, destination file; include outline; paper size; and something else. I”m still looking for documentation on this and if it violates the EULA. But until then…

<cfset FlashPaper.BeginConversion(''c:\\temp\\doc1.doc'',''c:\\temp\\doc1.swf'',0,210,297)

This seems to work.

Good luck.

File Upload:
File Upload in Flex/Flash in Internet Explorer

File Upload Using Flex/Central/Java

Architecture Ideas:
Cairngorm and an associated Breezo that will help explain the design patterns.

First, for those of you who are not system admins, make sure you make a copy of the files before you modify them.

Now, there are a couple of XML files that you can modify that will provide a lot more detail of what is going on.

The CF datasources are stored in the jrun-resources.xml file located in {CFMX install}\runtime\servers\default\SERVER-INF. Locate the datasource in question and change the debugging node (<debugging>false</debugging>) of that element from false to true. This will tell JRun to log more information about this resource. Note: there a lot of other options available several of which you can equate to datasource options in the CF Admin.

Next, we want to modify the the actual logging service. You can do this with the jrun.xml file located in the same directory as jrun-resources.xml above.
Find the LoggerService in the jrun.xml file. Set the following two entries to “true”:
<attribute name=”debugEnabled”>false</attribute>
<attribute name=”metricsEnabled”>false</attribute>

A few lines down from these entries, you can separate the logs into separate files by making the following change:

<attribute name="filename">{jrun.rootdir}/logs/{jrun.server.name}-event.log</attribute>

to

<attribute name="filename">{jrun.rootdir}/logs/{jrun.server.name}-{log.level}</attribute>

By changing “event.log” to “{log.level}” it will create separate log files for each type of event. This allows you to narrow in on suspected problems a bit easier.

Finally, the logs produced can be found in {CFMX install}\runtime\logs. Note: You will want to reverse these changes because they do cause a bit of overhead on the server.

The OUTPUT Attribute: You should add the attribute output=”no” to the CFFUNCTION tags in your CFC/UDF when it is not rendering display text. This will make it work like CFSILENT, when set to “yes” its like CFOUTPUT.

Note: CFSILENT suppresses all output that is produced by the CFML within the tag’s scope.

And my directories looked like this:
index.cfm
CFIDE
– scripts
—-cfform.js
… and all the other files