Note: This blog post is from 2009. Some content, links and indeed comments from others may be outdated--though not necessarily. Corrections are welcome, in the comments. I may revise the content if necessary.I want to start sharing some tips for working with CFBuilder. Most will be oriented toward those new to it, who had not used (or stuck with) CFEclipse before, but this one may surprise even those folks.
It's safe now to have CFBuilder set as the default program for all CFM and CFC files. Opening a file from outside the editor (when you already have CFBuilder open) will NOT open an entirely new copy of CFBuilder (as it did with CFEclipse). It will just open a new tab in the editor already open, as you'd expect. (This applies only to the standalone edition of CFBuilder, not the plug-in version.)
Explanation:One of the annoyances that some had with using CFEclipse (though it was really an Eclipse problem) was that if you already had the editor open, and for some reason chose to open another file from outside the editor (such as from within Windows Explorer), it would launch an entirely new (full) copy of the editor (workbench). Yikes.
Folks used to Dreamweaver, HomeSite, CF Studio (and indeed most editors) would have expected instead that it would just open a new tab for the new file. That behavior was annoying enough for some (due to their dominant workflow) to keep them from sticking with CFEclipse (or other Eclipse-based editors).
Thankfully, that problem has been (quietly) solved by the CFBuilder team. I've not seen too many make much of this, but it's one of those little things that can make a big difference. To be clear, this is only in the Standalone edition that they've built, which packages an Eclipse base and the plug-in on top of that. Obviously that allowed them to solve this problem in a way that other base eclipse implementations do not.
Not about using Eclipse's File Explorer view
Now, I realize that some readers will be aghast that someone would care about this. Why aren't you using projects? Or why not at least use the available File (or File Explorer) view, if you don't want to use the project-based Navigator?
But that's not the point. We're not talking about an alternative to projects, nor about opening the files from within Eclipse/CFBuilder at all. We're talking specifically about opening files from outside the editor. It may not be a workflow you'd ever use, but there were plenty who did use it, for whatever reason. Just nice to see this solved for them.
In fact, if you haven't noticed, Adobe even offers during the installation of CFBuilder (standalone) to have it mark the operating system to default to opening CFM and CFC files using CFBuilder. That's a nod to this feature now working as expected.
So thanks, Adobe, for solving it. And to those who have held this as a knock against Eclipse-based editors, it's just one more reason to reconsider the move to ColdFusion Builder.
More to come, here and in my daylong CFUnited class, "Getting Started with CFBuilder"
If you're looking for more such tips, keep an eye here. More than that, if you'd like to spend a day getting immersed in an introduction to CFBuilder from the perspective of one coming from other editors, come to my daylong class being held on-site the day before CFUnited, August 11. It's one of several such daylong classes being organized by (and available for purchase separately from) CFUnited.