Blog

Entries for month: February 2010

The Results are in... ColdFusion 9 is wicked fast

February 24, 2010 · 5 Comment s

We released a performance brief on ColdFusion 9.

  • Flash Remoting is now 8 times faster
  • Object instantiation is 7 times faster
  • IIS connectivity is faster
  • Implicit Getters and Setters are 7 times faster than explicit

There's a lot to love here, check it out: http://www.adobe.com/products/coldfusion/pdfs/cf9_performancebrief_ue.pdf

→ 5 Comment s Tags: ColdFusion

Flash Player 10.1 Battery Usage

February 24, 2010 · No Comments

There's been a bit of FUD being thrown about battery consumption by Flash Player 10.1 on Android. If you're confused by what's being said check out Mark Doherty's post that provides demonstrations of Flash Player running video on Android and the effect on the battery indicator. It also contains the battery usage charts from Android showing that viewing the video is not using up all of the battery (another really great built-in feature of Android.)

Link: Battery Performance with Flash Player 10.1 on Nexus One

→ No Comments Tags: Flash

eSeminar: Flash Builder and ColdFusion 9

February 22, 2010 · No Comments

I'm doing an eSeminar on Flash Builder and ColdFusion 9 on Wednesday February 24th at 11:00AM -12:00PM PST (2:00PM – 3:00PM EST.)

I'm going to show off the features that the ColdFusion team have added to make ColdFusion work easier with Flex as well as the features in Flash Builder that make working with ColdFusion ridiculously easy.

You have to register in advance so head on over to the Online Events page and register.

→ No Comments Tags: Flash Builder · ColdFusion · Flex · Appearances

ColdFusion 9 Cumulative Hotfix 1

February 21, 2010 · No Comments

Evidently we rolled out the first cumulative hotfix for ColdFusion 9 on Friday. Feel free to download it here:

http://kb2.adobe.com/cps/825/cpsid_82536.html

Note there are already a few things to look out for.

→ No Comments Tags: ColdFusion

Builder Extension using HTML

February 03, 2010 · 1 Comment

One of the cooler features of ColdFusion Builder's extension tooling is the ability to create extensions that are driven with HTML/JS/CSS instead of with the default XML options. I think this has a few advantages:

  • Allows interface options enabled by the XML options
  • Allows better branded extensions via CSS and background images
  • Allows you to develop/debug your extensions like normal web applications

This is pretty easy to enable. Normally you would have code like this in your handler to communicate back to the IDE:

<cfheader name="Content-Type" value="text/xml">
<response status="success" showresponse="true">
    <ide >
        <dialog width="600" height="400" />
        <body>
            <![CDATA[
                Some Response
            ]]>
        </body>
    </ide>
</response>

Instead you pass a URL parameter to the ide tag in your extension handler:

<cfheader name="Content-Type" value="text/xml">
<cfoutput> 
<response showresponse="true"> 
    <ide url="http://localhost/extension/handler.cfm?configPath=#configPath#" > 
        <dialog width="655" height="600" /> 
    </ide> 
</response> 
</cfoutput>

As you can see it can even handle URL variables.

Now, where I ran into trouble with this was with the URL itself. Basically you can't be sure of the URL when dealing with extensions. It could be localhost, but it just as easily could be on a remote server. So I was all clever and wrote some code to handle this:

<cfset baseURL = "http://" & cgi.server_name  />
<cfset messagesPath = getDirectoryFromPath(cgi.script_name) & "/messages.cfm" />
<cfset messagesOptions = "?type=notanapplication" />
<cfset messagesURL = baseURL  & messagesPath & messagesOptions >

 

You see, this will give me the correct URL to use to pass information to a template named "messages.cfm" that sits in the same folder as my handler. I use CGI variables to grab the server information. Then I use getDirectoryFromPath to make sure that I get the real relative path of the folder that the extension is sitting in (as opposed to assuming that it lives in the webroot). This works great.

Except I got reports of one of my extensions not working at all for some people. Look at that code again… There's another big assumption there. The assumption is that the extension is being called over the default http port, which for many ColdFusion developers it isn't. So the correct version of this code goes:

<cfset baseURL = "http://" & cgi.server_name & ":" & cgi.server_port />
<cfset messagesPath = getDirectoryFromPath(cgi.script_name) & "/messages.cfm" />
<cfset messagesOptions = "?type=notanapplication" />
<cfset messagesURL = baseURL  & messagesPath & messagesOptions >

Doing this you can be sure that you hit the right URL regardless of:

  • Server hostname
  • Server http port
  • Relative location of extension to the webroot

Happy extension building.

→ 1 Comment Tags: ColdFusion Builder Extensions · ColdFusion · ColdFusion Builder

Apptacular Update and Video

February 02, 2010 · 3 Comment s

I know I've been quiet of late. But I've been working.

You see a few weeks ago I had this checklist up on the site:

  • Make sure apptacular_blog database works on MySQL on MAC.
  • Make sure apptacular_blog database works on MySQL on PC.
  • Make sure sakila database works on MySQL on MAC.
  • Make sure sakila database works on MySQL on PC.
  • Make sure apptacular_blog database works on MSSQL on MAC.
  • Make sure apptacular_blog database works on MSSQL on PC.
  • Make sure adventureworks database works on MSSQL on MAC.
  • Make sure adventureworks database works on MSSQL on PC.
  • Fix major issues in code readability.
  • Start Document how to work with Apptacular

See those AdventureWorks database items? They nearly killed me and made me want to stop work on Apptacular. AdventureWorks is like a cruel Double Dare obstacle course for code generation:

  • Composite primary keys
  • Composite foreign keys
  • Composite primary keys that are also foreign keys
  • Custom Datatypes
  • Constraints (Really only affected unit testing).

I came through, and now I can give you this list:

  • Make sure apptacular_blog database works on MySQL on MAC.
  • Make sure apptacular_blog database works on MySQL on PC.
  • Make sure sakila database works on MySQL on MAC.
  • Make sure sakila database works on MySQL on PC.
  • Make sure apptacular_blog database works on MSSQL on MAC.
  • Make sure apptacular_blog database works on MSSQL on PC.
  • Make sure adventureworks database works on MSSQL on MAC.
  • Make sure adventureworks database works on MSSQL on PC.
  • Fix major issues in code readability.
  • Start Document how to work with Apptacular

So that's where I am. A few of you asked if you could get your hands on Apptacular and I would be happy to distribute it to individuals. I'm not ready for general availability yet though.

And as a final note, I thought I would share this feature with you: Apptacular can model CRUD for image fields in your database.

Apptacular ColdFusion Builder Extension - Working with Images from Terry Ryan on Vimeo.

→ 3 Comment s Tags: ColdFusion Builder Extensions · ColdFusion · ColdFusion Builder