[Looking for Charlie's main web site?]

More reasons to buy ColdFusion Builder

I wanted to add some more thoughts to Adam Tuttle's helpful recent entry, Why (I Think) You Should Buy ColdFusion Builder. I started to offer them as comments but it got lengthy, so I decided to create this entry instead.

A little background on the question

Adam's entry was his response to an observation I'd made on a private mailing list that I'd not seen any good single resource to point people to when they raised concerns about having to pay for CFBuilder. We who have "seen the light" wonder why people even debate it (as he addresses with observations from others in his entry).

While his entry expands on the oft-shared Adobe graphic comparing features among it and the existing CFML editors, there are some more features that may not have been t important enough to be listed on that graphic, but are sometimes a source of concern/contention for some as they consider CFB. Here are a few of them.

Most of these are things I also have been pointing out (among several dozen) in my "Hidden Gems in CFBuilder" talk that I've presented over the past year and will offer again at CFUnited.

Some more points to consider

  1. CFB offers something not in DW, HS, etc: its "local history" feature (per its Eclipse heritage) can be likened to a poor man's version control (though of course it offers full integration with "real" version control, which is preferable).
  2. While CFB (and Eclipse CFEclipse) are designed around use of "projects", CFB doesn't *require* use of them. It offers (via its Aptana-inherited features) the ability to work with files directly, and unique compared to Eclipse/CFEclipse, you can even open a file from the file system (like Windows Explorer) and it will open as a new tab, not a whole new workbench.
  3. DW and HS have features to "open include files" by right-clicking on CFINCLUDE, and some miss that in CFB. But it can do that sort of file open, and it's even more powerful. It's just not available on the context menu. Instead, one should hold the ctrl (or mac) key and hover their mouse over any kind of file link, and it will offer to open it. That can be a CFINCLUDE or a CFINVOKE/cfobject/createobject of a CFC, and more. It can even be on the name of a method used in code (script or tag) and it will open that method in the given CFC. It also works on a href and other html tags that refer to files. Very powerful.
  4. Some people lament that DW could do a "split window", showing part of a file in one window and another part in another, editing them simultaneously. Again, though it's not a right-click feature in CFB/Eclipse, it's there. You use Window>New Editor, which creates another tab with the same file, which you can then move to be above/below/side-by-side within another editor/tab.
  5. Some lament a lack of word wrap in CFB. It's there. See Window>Preferences>HTML>Editors (don't expand that) then its Advanced tab.
  6. Some complain that CFB doesn't do code completion (closing tags). It does, but it's not enabled by default. See Preferences>ColdFusion>Editor Profiles>Editor>Typing, and note the options to close (as in DW) either when closing the opening tag, or at the start of typing the opening of the closing tag.

    I will note, however, that I've found that HTML tags won't close (though they should by default). That problem is that the feature expects that there's an opening/closing HTML tag wrapping the page content. We often skip that in CFML, or may be working with a file that's included/called from another. At least this explains when it doesn't work.

  7. CFB has support for EXT/JS 3.0 (see the CFBuilder help/documentation section on "Import Ajax libraries")
  8. CFB can build AIR apps. See "Developing AIR applications" in the CFBuilder help/documentation.
  9. CFB has built-in support for doing a file compare. Select the files in the navigator and right-click and choose "Compare with".

  10. Some complain that they can't "edit a file on a server via FTP", meaning open it remotely, edit it, and save it on the server. While may will argue that you shouldn't do that (but should edit and test locally then deploy remotely), I'll note that you can in fact do that, if you use the Files (not the Navigator) window to open a remote connection.
  11. Don't miss the available Services Browser, which allows you to browse (within the editor) any CFCs *or* web services, seeing their methods, arguments, and more. I've blogged more about this to walk you through the oft-missed web services feature, which I'll note is similar to what's in DW.
  12. Don't overlook creating a Server connection. Sometimes people complain that some of the asserted "powerful and unique features" of CFB just "don't work" for them. For them, I'll note that you really HAVE to create a Server connection for your projects. That's an optional step when creating a new project, but if you overlook it, many things just won't work. It's this server connection (and the related RDS connection) which allow the IDE to talk to the server to get info on the CFCs on your server, the DBs and their tables/columns, etc., not to mention the features for starting/stopping the server, connecting to its admin, etc. I point to several blog entries that discuss that point about the need for defining servers in my Hidden Gems talk.
  13. For all its features, some complain of performance problems. As Adam noted in his entry, many have been fixed first in the final release and then in the recent updater. Beyond that, though, the CFB docs do have still more addressing this specifically. See the section "Optimizing ColdFusion Builder Performance".
  14. Finally, it should be repeated that because CFB is based on Eclipse, there is a whole world of Eclipse extensions that can and do add still more functionality, generally for free.
  15. Indeed, there is more to CFB in the way of features of Eclipse itself, as well as the Aptana plug-in that's included with it. So it would behoove one to look into those more. I point to some resources for exploring those more in my Hidden Gems talk.

Lots more tips, tricks, and traps

Indeed, that Hidden Gems talk (whose content is available online as both a PDF and a recording) offers still more about some of the features I list above (including doc or blog links), and it offers still more in the way of tips, tricks, and traps in working with CFB.

It's not really meant to address the "why buy CFB" question, but instead tries to help those who've used it (or tried) to be more aware of what's possible. It's addressed to both those new to Eclipse-based editors and also to those who've been using them already.

This is indeed a challenge for any resource trying to speak about CFB (whether a blog entry or the CFB docs). How much should be presumed? It's that challenge which leads, I think, to the state of things where some feel that their concerns are not addressed.

Lost cause for some?

Finally, when I first asked about whether someone had put together such an entry, I got some feedback (surprisingly staunch) that it seemed pointless to bother trying to "preach to the unconverted", and that if they didn't get it, it was their loss. As I wrote in reply:

I appreciate that sentiment, but I do believe there are some in that "hater" crowd who are just misinformed, and don't really appreciate all that it adds for them. More than a few (still!) accuse it of being just a rip off of CFEclipse. Of course, you and I (and many here) know that's a gross simplification--and not true, anyway.

But as long as they think that, or more important as long as they don't fully understand what it can do for them, they will continue to resist.

No doubt, there are some for whom no amount of persuasion will cause them to "get up off their wallet", as my wife would say. We can't do much for them, but I do want to "fight that good fight" for those who can be reached.

Tell people about Adam's entry whenever you can

So I hope that Adam's entry, and any others that may exist (and perhaps this one and my talk) will help with that.

But also I hope people will bookmark Adam's entry and point it out whenever you see people complain (on lists/forums/in twitter) about "why should I buy/have to pay for CFB"? I think the conversation is an important one to have.

Is Dreamweaver crashing when you try to use Help? Here's a solution

For months now, I've found that when I tried to use the help feature in Dreamweaver (8 or MX 2004), it would crash, with an "unhandled Win32 exception". If this has happened to you, there is a quick and easy solution.

The problem turns out to be IE7. That explains why, for me, it was such a mystery. I don't use DW help much at all and have had both DW 8 and 2004 installed for over a year, so when trying to use help suddenly failed in recent months, I couldn't for the life of me connect the dots to resolve the problem. I searched the web and the Adobe site in particular, all to no avail.

Solution in an Adobe Technote

Finally, I posted the question on a DW forum and David Alcala of Adobe DW Quality Engineering responded pointing out this technote. (Thanks again, David!)

It explains an incompatibility between a certain DW DLL and IE 7. As it explains, the latter came out after the former, so it's forgivable. It goes on to say that affects more those using indows 2003 Server and 64-bit XP, but I was having the problem on 32-bit XP. And while it refers just to Dreamweaver 8, I tested the fix on Dreamweaver MX 2004 and it works for that as well. Good news!

But I have Firefox as my primary browser

And if anyone's wondering, it doesn't seem to matter if you have Firefox set as your primary browser, either in Windows or even in the Preview in Browser feature of DW. In both cases, I have FF set as primary and yet I suffered this problem. If anyone knows another way to control DW using IE for help, perhaps that would explain why only some get this problem.

Anyway, hope that helps someone else.

PS I happen to have MS Visual Studio 2005 installed, which intercepts the error and offers to run the JIT debugger. So it's possible that the error I get ("unhandled Win32 exception") is different from what one gets if they DON'T have it installed. But as the Adobe technote says, it does cause DW to crash, and that's what matters most. Since the technote doesn't offer the specific error message I was getting (or any other), I hope this blog entry may be found by others searching as I did. And I'm removing Visual Studio to see what error one gets when it's not installed. If the message is different, I'll come back and update this blog entry.

Update: ok, if the JIT debugger is not setup to handle errors, then instead one gets the "good ol'" windows prompt to "send error report". The top line of the window (in case someone searches to find this) is "Dreamweaver MX 2004 has encountered a problem and needs to close. We are sorry for the inconvenience." If you use the "click here" to see details, the error is in appname:dreamweaver.exe modname:hhctrl.ocx

Myth-busting: HomeSite is not dead, HomeSite NEQ HomeSite+, and Adobe does support Eclipse

OK, time to do a little myth-busting/truth-talking. I want to respond to what I feel is a misstatement in a comment on a blog entry today by Ben Forta. Not a statement by Ben, mind you, but a commenter (and friend of the community, John Farrar). Ben made a casual statement about a single IDE for CF developers (not the focus of the entry, though), and John followed up explaining his take of the history of IDE development in CF. He said as one point, "Somebody (no names please) sued Macromedia over HomeSite or CFStudio and it died."

I have to call that statement into question. Also, John shares some observations about CFEclipse, but he makes no mention of the Adobe Extensions for CF. I wanted to address both of those but felt it was too long for a comment in Ben's blog, so here you go.

HomeSite is not dead, and CF Studio became HomeSite+, not HomeSite

First, you want to be clear to distinguish HomeSite from HomeSite+. The former is still sold by Adobe (http://www.adobe.com/products/homesite/).

As for CF Studio, it did morph into HomeSite+, and the CF Studio name was dropped, but my understanding was that this was simply because the MX Studio line came out as a package of things (including Dreamweaver and Flash among many), so they couldn't have 2 things named Studio.

HomeSite continued/continues to exist as its own product, and CF Studio became HomeSite+, which you couldn't purchase but that came on the Studio MX or Dreamweaver CD (and still does). Only as of DW 8 was it finally listed on the installer screen, otherwise you had to look for it on the CD using the file system. HomeSite+ also evolved over where CF Studio had ended (at a 5.0 version), so that on DW2004 is was HS+ 5.1, and on DW8 it was 5.5, if I recall correctly. There were some new features and bug fixes, but nothing radical. Still, it was better than sticking at Studio 4.5 for those who never updated from that while Studio was alive. I've written on this and will share resources in a moment.

About that lawsuit John mentions

Now, at that same time as that transition from CF Studio to HS+ , there were some features of the HomeSite interface over which there was a lawsuit, and when HS+ came out some features (draggable windows, if I recall) were missing. Some complained that it wasn't REALLY the same as CF Studio. I never understood the kvetching. It was otherwise every it CF Studio and more (given the updates).

So HomeSite != HomeSite+

So, that's just to say that you don't want to say HomeSite is dead (it does still live and is sold). And HomeSite+ lives as the reincarnation of CF Studio, though it's not sold but is available only on the DW CD. I know some say it's as good as dead, since there's been no major feature development. That's a separate point, but I'll say I've been a fan all along and I've not missed much from the few features lost due to the lawsuit.

I do use DW sometimes for things it adds for CFML development (CFC and web service browsing, some code generation features, etc.) I think many would be surprised to learn what it has that they never noticed.

Indeed, some will know I've been spreading this news about the transition from CF Studio to HomeSite+ (as well as hints about DW) for some time in blogs and articles. Here they are for those interested in more:

As long as I'm listing resources, I'll also point out that I've done several presentations where I made the case for making sure people knew of the tool and its features:

Now, I know some will read this as an apologetic for HomeSite+. It's not. I'm offering it more for historical purposes, as well as for those who for whatever reason are still using (or wish they could use) the older editor.

Eclipse, and Adobe's support of Eclipse for CFers

Again, there's no denying the move by many in the community to CFEClipse. I'm not saying people shouldn't. In fact, I've done many entries of my own to promote CFEclipse:

So as I state in the last entry, I am making the move to CFE myself. I still find some challenges, along with others who report the same, but clearly it's the tool of choice for many.

Eclipse, and Adobe's support of Eclipse for CFers

But I noted at the top that John's comment had not mentioned Adobe's support for Eclipse. I'm not speaking of support for CFEclipse (another subject for another blog entry by other folks), but I do want to make sure people know that Adobe does indeed support Eclipse directly, because they've created the Adobe Eclipse Extensions for ColdFusion.

This isn't in competition with CFEclipse but rather a set of tools that supplement it (whether one uses CFE or not, when using Eclipse to work with CF sites). The tools include the RDS Dataview and Fileview tools (replicating what we had in CF Studio/HomeSite+), the services browser (replicating what's in DW), as well as tools to build CFCs from a database table, flex and ajax code building wizards, a log viewer (some things neither tool had), and still more.

You can learn about these in the CF8 docs as well as a CF8 features page on the subject. The eclipse extensions came out for 7.02 and have been updated for 8.

I'll be writing and presenting more about the Eclipse extensions soon.

Adobe has also offered help files for Eclipse for CF8, at that same link for the extensions above.

That leads to a common question: what's the difference between CFEclipse and the Adobe CF extensions for Eclipse? Andy Jarrett has done a nice blog entry on that very subject.

Conclusion

So I'm not denying the claims by John, the folks in Italy (which Ben was writing about), and others that a new dedicated CFML IDE might be useful. And I'm not trying to keep people still using HomeSite+. Not at all. To each his own.

I just wanted to set the record straight about these assertions regarding HomeSite, as well as add the points about Adobe's Eclipse CF extensions. Hope that was helpful.

BlogCFC was created by Raymond Camden. This blog is running version 5.005.

Managed Hosting Services provided by
Managed Dedicated Hosting