The CF No Debug Firefox extension has been updated to work with Firefox 3.6. You can get the latest from RIAForge.

This evening I released AMF Explorer 0.6. This version adds a custom binary cache that should fix issues some users were seeing with AMF response deserialization. I'm still waiting for AMO public approval, so if you are using AMF Explorer you will need to manually update the add-on from the AMO site. Please be sure to report any issues to the AMF Explorer bug tracker at RIAForge. Thanks.

I've released a few updates to AMF Explorer over the last week or so. Improvements include support for small messages, better formatting, and better error messages. You can get the latest from the AMO site.

Unfortunately automatic updates are not enabled because AMF Explorer has yet to go public. If you are using AMF Explorer please consider taking the time to register and review the add-on on the AMO site as this will help with the AMO review process. Once the add-on is public it will be easier to find and install as it will not be marked as experimental and automatic updates will be enabled. Thanks!

Back in late 2008 the nsITraceableChannel interface was added to the Mozilla browser allowing extension developers to intercept incoming HTTP responses. At that time I pondered the possibility of adding AMF support to Firebug, however life got in the way and I never really had time to fully explore what it would take to do this. That is until now. Today I'm happy to announce that I'm finally releasing AMF Explorer.

[More]

I've posted a new ColdFire beta to RIAForge which works with recently released Firefox 3.6 and Firebug 1.5. I'm labeling this a beta because I discovered a ColdFusion 9 compatibility issue in my testing for this release. It appears ColdFusion's built in AJAX libraries have been updated slightly so the "Enable CFAJAX Debugging" feature does not currently work with CF 9. I'll work on updating this feature in the next couple of weeks. (Unfortunately the AJAX libraries shipped with CF are minimized and obfuscated so working with them is not as easy as it could be.) Because of the beta status of this release I've included both the ColdFire 1.4 and ColdFire 1.5 releases in the current RIAForge download. As always, if you have any issues please report them on the RIAForge project site.

A few weeks ago Terry Ryan released his Instant Code Review ColdFusion Builder Extension. I realize that the point of the extension was to get people to think of creative uses of CF Builder extensions, but I couldn't help but think that there are much better ways of collaborating using the Eclipse platform, specifically the Eclipse Communication Framework (ECF) DocShare plug-in.

Unfortunately ColdFusion Builder's CFML Editor doesn't support the plug-in out of the box. Fortunately the DocShare plug-in developers did the Eclipse thing and made it easy to extend the plug-in to support other editors. So I put together an Eclipse plug-in that adds DocShare support to the CFBuilder CFML editor. You can check out the CFBuilder DocShare Support plug-in at RIAForge.

A few notes about the plug-in. First, you will need to install ECF, including the DocShare plugin. For update URLs for your version of Eclipse see the ECF site. Second, my plug-in just enables the "Share This Editor With..." context menu item in the CF Builder CFML editor, the actual editor sharing is implemented via the ECF DocShare plug-in. For more info on the DocShare plug-in and its use see the DocShare Plugin site. Finally, I've had I've had hit and miss luck with the DocShare plugin, so be sure you have a backup of the file you plan to work on in shared editor.

Enjoy!

Today I released a new ColdFusion administrator extension, IP Ranger, which allows IP ranges to be added to the debugging IP address list. IPv4 IP address ranges may be added using wildcards (192.*.*.*), octect ranges (192.168.1-10.1-120), or a combination of both (192.168.*.1-120). IP Ranger also allows you to verify, delete, and refresh IP address ranges.

[More]

Today I was pretty stoked to find out that ColdFire was nominated for a Community Achievement Award in the Best Open Source Project category. I'm not sure who nominated ColdFire, but thank you. It is a honor just to be mentioned with other projects such as ColdBox, BlogCFC, Mango Blog, Mura CMS, ColdSpring, Transer and Model Glue. Of course ColdFire wouldn't even exist were it not for the vision and work of Ray Camden and Adam Podolnick. Thanks guys for letting me work on your project!

Be sure to vote for your favorite Open Source Project, and lot of other topics here.

Another day, another extension update. If you use the CF Debug Copy extension for Firefox you may be happy to know that I've just posted an update to RIAForge which works with Firefox 3.5. Enjoy!

With Firefox 3.5 in release candidate and Firebug 1.4 in its third beta release (after 31 alpha releases) I decided it was time to get my act together and update ColdFire to work with the latest and greatest. If you download ColdFire from the RIAForge site you will notice the zip now contains two releases: 1.3.207.211 and 1.4.207.218. The 1.3 release is the current "production" release which runs on Firefox 3.0 and Firebug 1.3. The 1.4 release should be considered beta since it requires Firebug 1.4, which will run on either Firefox 3.0 or 3.5. There are no new features in the 1.4 release, just support for these awesome new Firefox/Firebug releases. (The ColdFusion and Railo debugging templates are the same from 1.3 to 1.4, so if you want to run Firefox 3.0/Firebug 1.3 and Firefox 3.5/Firebug 1.4 side by side you don't have to change any of the server side ColdFire bits.)

I have to give a shout out to Jan "Honza" Odvarko for the great work he is doing on with Firebug's network monitoring. In earlier versions of ColdFire we actually rolled our own network monitoring and it was a huge pain. For ColdFire 1.2 we wised-up and used some crazy closure hacks to leverage Firebug's network monitor. It worked, allowing us to introduce features like the response queue, but boy was it ugly and brittle. Firebug 1.3 introduced a API for its NetworkMonitor module which allowed extension developers to register listeners and receive data from the network panel, which we in turn leveraged in ColdFire 1.3. Now Firebug 1.4 expands on that API, and best of all Honza has done a great job of documenting this expanded API on his blog. (Anyone interested in working with Firebug should definitely read Honza's blog, Software is Hard. I wish many of those articles had been written when I was digging through the Firebug code trying to figure things out.) ColdFire 1.4 has been updated to use this new API, which was the only significant change to ColdFire code for this release.

That's all for now. As always please report any issues on the RIAForge bug tracker.