Note: This blog post is from 2007. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

A lot of folks are high on Aptana, which is a plug-in for Eclipse that works as a nice adjunct to CFEclipse, since it adds nice support for working with HTML, CSS, and JavaScript files.

One thing I've not seen mentioned often is that it supports Javascript Debugging (at least in Firefox, and soon in IE). For more info, see:

http://aptana.com/docs/index.php/About_the_JavaScript_debugger

For those still relatively new to Aptana, this is one of many topics discussed in a "Getting to Know Aptana" guide on the site:

http://aptana.com/docs/index.php/Getting_to_know_the_Aptana_IDE_%28General_IDE_Concepts%29

Note: This blog post is from 2007. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

I want to share some news with those who may have noticed recent challenges with the Adobe LiveDocs, especially for CF8, and a challenge in commenting in them. All is resolved now. I've been working in the background with the Adobe gent in charge of this (who may prefer I don't share his name) and he's been great about attending to and resolving these. There's also good news: they seem faster (to me) than the CF7 livedocs.

First, you CAN now get to the livedocs...

As some noticed, there was a brief time in recent days when you couldn't get to the livedocs at all (for CF8 or otherwise). You'd get stuck in a loop on a main docs page. That's since been fixed.

But note that you may need to take a (good) detour...

But about that "main docs page", yep, it's worth noting that trying to go livedocs.adobe.com will no longer send you to the livedocs front page but rather will go instead to a new page I'll call the main Adobe docs page.

There, you have to pick which doc you want to see from a select control, and further the page you're taken to offers both a link to the livedocs and to the PDF docs. (It was the link from there to the livedocs that was broken last week, sending you right back to this page.)

Now, some may be annoyed that they get sent here. I just want to get to the livedocs. Well, if you know the URL for your product, you can, such as for CF8 or CF7.

There's more than the livedocs: PDF; and the print versions you can buy

But I do myself like that they've sent people to the main docs page first, if they don't know a short-cut. So many people never knew of the PDFs. They're nice to have sometimes.

Also, that page offers a link to the printed docs (for now, only the CF7 docs are for sale, as the CF8 docs may not be available until late August).

I've blogged about buying the printed docs before. I think for many it's the best $50 bucks they'll spend for 2500 pages of content.

New look for the CF8 docs...and faster

If you do go to the CF8 livedocs, you'll find that they have a new look compared to the CF7 docs. Also, at least it seems to me, they're much faster.

Yes, they're still a framed interface, but that's not the end of the world--and if you need them all as one, remember the PDFs, and the HTML form available on your machine where CF is installed (C:\ColdFusion8\wwwroot\cfdocs\htmldocs on my machine).

Some docs retired...

I will point out that sadly, one book from the CF7 livedocs doesn't seem to have been updated for CF8, the "Getting Started Building ColdFusion MX Applications". Again, this was a hidden gem that I think many missed and would get great value from. If you're moving from 5 or 6 to 8, please do take time to read this 150 page guide. It's really quite good.

Also, two that were available in HTML/PDF form (not on livedocs) that also seem to have been retired are the "CFML Quick Reference" and the awesome 60-page "Migrating Applications to ColdFusion MX 7". Again, if you're skipping 7 (or used it but never really took full advantage of it), check out those docs.

And yes, Virginia, you can now make comments...

Finally, and perhaps best of all, some may have noticed if they DID get to the CF8 livedocs that for some reason, the ability to comment was gone. That, too, is finally fixed. Thanks, Randy! :-) (Doh! Ok, I'll use his first name. He knows who he is, and some of you. If he wants to speak up and identify himself, I'd welcome it.)

So get out there and start commenting away. Let's share what we learn as we pour through the CF8 docs, whether online, in print, in PDF, or in HTML.

I'll have a little more to share about the commenting system and some related features in an upcoming note.

Note: This blog post is from 2007. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

As folks contemplate moving to CF8 from 6 or 7, they may know that they can run these releases alongside each other--as long as you use a separate web server (or web site in servers that support it) configured to hand CFML requests to each CF server. Since CF6, CF has included a built-in web server to help with this very issue, especially on servers (like IIS on XP) where you can't have more than one site.

But what if you want to test some code in a single directory against one or more editions? Is that possible? I mean, let's say you have CF7 setup against IIS, and your code is in the c:\inetpub\wwwroot? And you've installed CF 8 for testing using its built-in web server, which runs on port 8500 (or whatever you chose) and finds its code in, for instance, c:\coldfusion8\wwwroot.

How would you have CF8 look at the code you've long had running in the IIS root? (or Apache, or a virtual directory you've setup for use by either external web server). Do you have to move the code around among these directories to test it on different versions of CF? No, you don't.

The trick is in the jrun-web.xml, which you can find in cfusionmx_home]\wwwroot\WEB-INF\jrun-web.xml . You can add a new "virtual-mapping" entry there, naming a new "alias" which points to files outside the normal CF-based wwwroot:

So now a request for http://localhost:8500/inet/ will look instead in the inetpub/wwwroot, or wherever you point it.

Update: Note that when you use the resource-path, it's case-sensitive, even on Windows, so http://localhost:8500/INET/ would not be the same.

Of course, this works also if you set up CF8 to run via your built-in web server, but setup CF 7 or 6 to run on its own built-in web server. And of course, if you're savvy enough you may figure out how to run things so that you can run all 3 using an external web server.

There are a couple of potential challenges with this technique. For one thing, if your code has hard-coded references (such as hyperlinks, images, CFLOCATIONS, etc.) to either run on a particular host (without the port) or at a particular root-relative path, then this introduction of a new port or the /inet/ alias may hamper it working. That's not a "CF" problem but rather a coding one. Your stuck then.

But it certainly works well for testing individual files. I do it all the time and have for years. Indeed, I'll share, for the sake of posterity, that this modifying of the jrun-web.xml is something I first wrote about back in 2002, but many may have missed when such info was being shared.

I'm going to go back and reprise a lot of those "oldies but goodies", spread across a few different blogs I've had over the past several years. I think I'll call them "carehart classics".

Note: This blog post is from 2007. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

If you'd not seen it, there are a slew of new CF8 articles on the Adobe CF Developer Center, including one I've done that's the first of a 4-part series on the CF8 monitor. The first both introduces the monitor and focuses on its uses first in development:

ColdFusion 8 server monitoring - Part 1: Using the Server Monitor in development

It's 8 pages printed, so lots of info there. I hope you'll get value from it. Since there's no feedback mechanism there, I'd appreciate if you'd share comments here of what you think of it. We writers get precious little feedback on our work, most times.

For now, it's even listed as a front-page article on the CF8 Dev Center. (FWIW, note that the URLs say "devnet" while the site itself uses the phrase "Developer Center".)

Future articles in my CF8 Monitor series will focus on using the monitor in production, then using the multi-server monitor, alerts, and snapshots, and finally several miscellaneous features and tips in part 4.

I should say finally, since many know I've talked a lot about FusionReactor and SeeFusion in the past, that, no, I don't think the CF8 monitor is a death knell for those tools (nor do I think the CF8 debugger will kill off FusionDebug). There's a place for both (especially if you're not yet on 8, and even afterwards possibly), and since the monitor is only in CF8 Enterprise, that especially keeps the other monitors in the running. I've written a more complete discussion of my perspective on these things:

Scorpio Debugger and Monitor: What's it mean for FusionDebug, FusionReactor, and SeeFusion?

Now, about it being in Enterprise, that's something I couldn't say in either my past entries or even in the current article on the DevCenter, as those were all written before the final release of CF8. I'm sorry if they read as if everyone using CF8 could use them. I really had no way to say otherwise.

That said, with the CF8 monitor being free in CF8, and especially with it giving us access to some awesome new info (which even the other monitors could now provide access to), it's worth learning what's possible. There's a lot more to it than you may think.

See the other entries I've done on the monitor. Some of them have info I couldn't fit into the DevCenter articles, or that may not be published for a few weeks.

Note: This blog post is from 2007. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

Recently I was pointed to a useful (and free) tool from Quest (SQL Log Reader), and I noticed that I'd had a couple others already installed (Toad and Benchmark Factory). That led me to start looking into what else they had, and I was impressed with the number of free and very professional tools. It wasn't as straightforward to find them as it may seem. I thought I'd share my observations.

The range of free tools is amazing, from tools for working with databases (like Toad or Knowledge Expert for SQL Server, MySQL, or Oracle), to tools for generating load tests for databases (Benchmark Factory), to tools for managing/monitoring Windows or J2EE servers, Active Directory, and lots more.

As you review the list below, note that some of the pages show links to "evaluation" editions but I've only listed pages where I found it to say the tool was free (somewhere on the page, even if it shows an "evaluation download").

It seems some have no time limit at all (true freeware). With some, the license is time-limited and you must return for a new key (see Spotlight® on WebSphere, for instance). With others, you must uninstall and reinstall (see Object Restore for AD, for instance). I suppose it's better than a trial, in that with most trials you couldn't uninstall/reinstall. Others list a duration with no indication of whether you must uninstall (and I found one note on a forum that said you could just register for a new license key for at least one of them).

Some tools are also indicated as windows only (such as Spotlight on MySQL), but I've not paid attention here to which run on what.

The thing is, curiously, they have a page of freeware (http://www.quest.com/free-tools/) , but it doesn't list all that I've found elsewhere on the site. In fact, there's an "a-z" product page (http://www.quest.com/solutions/allproducts--atoz.asp) which indicates which are freeware, but it too does not list them all.

• Spotlight on Windows
• Benchmark Factory® for Databases (for 12 months, some limits compares to commercial)
• Comparison Suite for SQL Server (60 days, renewable?)
• Toad for SQL Server (note that this site offers the current Quest 3.0 edition as freeware, though not listed as such on Quest)
• Toad for Oracle(again, this site offers the current Quest 9.1 edition as freeware, though not listed as such on Quest)
• Toad™ Data Modeler
• Toad® for MySQL (for windows)
• Spotlight on MySQL
• Knowledge Xpert for MySQL
• Spotlight® on WebSphere
• Spotlight® for BEA WebLogic Server
• Storage Assessment Tool
• Discovery Wizard for SharePoint
• Self-Service Web Portal
• Reporter Express (on Windows infrastructure)
• Reporter (also on Windows infrastructure)
• Compliance Portal
• Object Restore for Active Directory (6 month)
• Update Utility for Outlook 2003 (for Exchange)
• Offline Folder Wizard (for Exchange)

There were also some other Quest tools that were free in the past but are no longer, but those old versions can still be found elsewhere (sites like download.com) and though perhaps a couple of years old or more may still be useful:

• JProbe and download

I'll share more about a couple of these later.

Note: This blog post is from 2007. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

If you're a user of (or are considering using) FusionDebug or FusionReactor, two tools I've written about before, I want to point out that they have some new support resources.

Mailing Lists

First, there are now mailing lists (Google Groups) for each. This is something I pressed for since last year, and thankfully now they're enabled and there are good discussions already taking place.

http://groups.google.com/group/fusionreactor

http://groups.google.com/group/fusiondebug

Knowledgebase, Searchable and Browsable

There is also a new Knowledge Base where they've put many tech notes and answers to questions (other than those already in the FAQs). You can search it via the main support page, indicating which product and type of docs to search (it also searches the Google groups as well).

Finally, I'll share a little hidden gem. If you'd rather not search the KB, you can instead browse it. Here's a URL for each product:

Browse FusionReactor KB articles

Browse FusionDebug KB articles

I should note that they don't currently offer these links on the site, and in fact they may change in the future (since they're not published yet), but I don't think they'll mind me sharing it for now.

They're presented in numerical order, which isn't really chronological order, but clearly mixed in are discussions relevant to both old and new releases of the products, to be sure to note that indicator in the info at the bottom of each technote, if you have any question. There's some good stuff in there, and I'll be mining it for tips to share (here or on the mailing lists).

Note: This blog post is from 2007. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

Are you a CF blogger? I had a thought recently: we could probably share a lot with each other to make the most of our blogging efforts to the CF community.

For instance, Pete Freitag had a really neat tip today on optimizing your RSS feed to keep better manage traffic.

Regardless of which blogging software we use, we still serve the same CF community and just as we've all learned from and contribute to that community, we probably also know some useful tips and resources to share with each other about our blogging efforts.

So I created a new google group today, http://groups.google.com/group/cfbloggers, and I'm inviting all CF bloggers to join.

Sure, there are resources out there for all bloggers (like www.performancing.com), but I wanted to create something just for our community, without the traffic of the noisy broader world of bloggers, as well as to perhaps focus on issues of interest just to us, such as how we can organize our info better (perhaps together) for the CF community, how to monetize our blogs (maybe create a CF community-specific ad banner mechanism), how to solve common blogging-related problems (like aggregation and feed validation), and so on.

NOT another place to discuss CF

I don't mean for this to be yet another place to discuss CF questions and issues with each other. We all already have plenty of places to do that.

Joining the Group

For now, I've made it a private group. People must either be invited or request to join, and the discussions are not made public. I think that may be best to permit people to speak frankly. We can discuss if it should be made publicly viewable, but I'd propose that joining always be moderated to keep out folks who are not truly CF bloggers.

• If you have a google account already, just login and join, which you can do in one step
• If you don't want to create a google account (needed only if you want to access the web interface), you can also drop me a note via the group join interface and I'll just add you to the list and you'll start getting mail whenever folks send a note to the list.

Of course, you don't need a gmail address or account to join. Any address will do.

Who was pre-invited to join?

I was torn between not inviting anyone (and hoping it would spread by word of mouth, emails, and blogging) and seeding the list with at least several folks to start. I decided the latter was a better choice, at the risk of offending anyone I might leave out. To avoid an incredible effort to think of/find all CF bloggers, I instead just used the list of names of bloggers in the "last 72 hours" display on FullAsAGoog's CF category, at the time I created the blog.

If I had their email address or could find it quickly, I used it. And while typing their names into an outgoing email, if my email client showed me other folks with the same first name, etc, I added them to the list.

I'm sure I've left off many. No offense intended at all. That's why I'm doing this blog entry (but I realize that won't reach most of the CF bloggers, so feel free to spread the word.)

If you know anyone else who wants to join, have them use the links above.

Should be low-volume, which is good

I suspect this will be a low-volume list, except for spurts that surround interesting discussions, so I'd hope it would not add a burden to your inbox, but rather would be valuable even if you only got one new idea a month.

Hope you'll join at least for a while.

Note: This blog post is from 2007. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

If you've noticed, I've recently started doing a spate of entries on CFEclipse.

Some of you know me as one of the old-line "dinosaurs" who have been long-time fans of CF Studio and its "son" HomeSite+. I've been using them for 10 years, and have in fact continued to be an ardent supporter of helping folks move from CF Studio to HomeSite+ the past few years.

I've also used Dreamweaver on occasion, because it offers some useful features that HS+ does not have (especially for web service and CFC exploring, to name just a couple).

Welcome to the revolution

But there's so much goodness in CFE and Eclipse in general (including most of the things in the other common CFML editors) that I think it's time we old-line folks faced the music and "got with the program".

Of course, no one will force you, and I do understand the challenges you may face (or the concerns you may have). I just want to do what I can to help, including sharing here over time various discoveries and tips (and traps) as I make the transition. But we're not alone--and I'm clearly not being any sort of a pioneer. Plenty have already made the journey.

Indeed, that's one of the main reasons I created the recent list of bloggers who have already written (and most who continue to write) about CFEclipse. I want to help folks learn from those who've travelled the road before us, as well as to hear both the arguments for and against it.

But I don't like CFEclipse because of "x"

There are certainly many who are still holding out, arguing for why they don't care for it. In fact, to address that, Brian Kotek just last week did an entry on "CFEclipse: Pros, Cons, and Misconceptions".

Join me on the journey

I've had to use Eclipse and CFEclipse for the past few months as I have been working with FusionDebug and the new CF8 debugger, both interactive step debuggers for CFML, and both based on Eclipse.

I've only learned the bare minimum I needed about Eclipse (and those I didn't *need* CFEclipse to work with the debuggers, I did install it). I still edited my code in HS+ and just used Eclipse/CFeclipse to do debugging, and I have reminded people of that whenever I showed off or wrote about the debuggers. There are plenty of people still preferring either HS+ or DW (or some other editor).

But Adobe is clearly behind Eclipse as a platform for code editing (witness FlexBuilder, and the new Eclipse-based debugger in CF8). They're not turning their back on DW, but clearly CF developers are getting more and more built-into Eclipse, both from them and from others.

And many in the CFML community are clearly behind CFE. I think we'll only see things get better and better, and I plan to do my part to help folks like us make the transition. So while I won't claim to be a pioneer, I do offer my services as a guide. Care to join me?

Note: This blog post is from 2007. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

Here are 29 more bloggers who have written about CFEclipse. These folks (no slouches, several having 14 or more entries) simply have not yet (at the time of this writing) chosen to provide a CFEclipse-specific tag or category. I hope they may reconsider, to make it easier for folks to keep an eye on their valuable CFE contributions.

In my last entry, I offered part 1 of a 2-part entry on CFEclipse bloggers (bloggers who have written about CFEclipse). In that list, I showed only those (45) bloggers who have dedicated a specific category or tag to CFEclipse (or Eclipse, if an otherwise CF-oriented blog).

Again, the list is sorted in approximately descending order by number of entries I found they had done on CFEclipse (as of today). And as I said before, while many of the entries are just news (like announcing a new release, etc.), some are useful tips from a wide range of developers (and the typical arguments for and against CFE).

How did I find the bloggers and their CFE content?

To find these entries, and those in part 1, I did a google search on CFEclipse and browsed through the first few hundred entries to find any bloggers who had done something on CFE. If they had at least one meaningful entry, I added them to the list (and put them in the list in part 1 if they offered a CFE category).

I then also ran the 2 lists by Mark Drew to ask him if he thought I'd forgotten anyone. Fortunately, I had not.

How I got a URL for you to find their content, easily

Just as the bloggers in part 1 offered CFE-specific categories (and therefore a single URL to find their CFE content), I wanted to provide a way for you here also to just click a link and go right to these folks' CFE-specific content. How did I do that?

Most blogs offer a search box, so I tried searching there, and if that resulted in a URL holding the search criteria, I offer it here in the list of URLS below. (In the case of BlogCFC, though it doesn't show the search criteria in the URL by default, you can add it in by hand as &search=cfeclipse, which I've done below.)

Otherwise, for other blogs where I could get no URL to use for searching, I resorted to using Google's nifty "site search" feature to search their blog for any CFEclipse references (and I further added some criteria to find only their blog entries, not RSS feeds, etc, to keep things even with the list in part 1). The only negative with this is that it could find entries where there are simply COMMENTs that mention CFEclipse. That's no good, so I have only shown the number that correlates to the number found by their site search tool. (BTW, note that some of the blogs themselves use google site searching as their means to do search.)

On some sites where there was no search result URL I could offer, I could also find no CFE blog entries with such a Google site search (though the search feature on their site did indeed find some CFE entries). In that case, you'll simply have to search the site yourself to find these entries.

Conversely, some other sites showed far fewer results in their own site search than I found using Google's site search. So I show the Google Search link even if their own site search URL would have found their CFE content.

Finally, since the Google and even some site searches take you to a page where it's not easy to discern the URL for the blogger's site, I am offering their blog URL and then the link to do the search:

The list of CFE bloggers (who have no CFE category/tag)

• (17) Brandon Harper's CFE search
• (15) Mark Drew's Original Blog :-) CFE search
• (14) Kai König's CFE search
• (14) Adam Howitt's CFE search
• (12)Jake Munson's CFE search
• (11) Robert Blackburn's CFE search
• (10) Mark Breneman's CFE search
• (10) Jim Priest's CFE search
• (10) Terrence Ryan's CFE search
• (9) Sammy Larbi's CFE search
• (8) Mark Mandel's CFE search
• (8) Kola Oyedeji's CFE search
• (7) Nick Tong's CFE search
• (7) Dave Shuck's CFE search
• (6) David Harris's CFE search
• (5) Jeff Houser's CFE search
• (5) Ryan Guille's CFE search
• (5) Michael Sharman's CFE search
• (4) Zero One's CFE search
• (4) David Fekke's CFE search
• (3) Brian Love's CFE search
• (3) Rick Osborne's CFE search
• (3)Jim Collins's CFE search
• (3)Patrick McElhaney's CFE search
• (2) Ben Nadel's CFE search
• (2) Theo Rushin's CFE search
• (2) Doug Hughes's CFE search
• (1) Ryan Stille's CFE search
• (1)Scott Pinkston's CFE search

As I said, I'd love to see those bloggers (especially with a lot or substantial CFE content) offer a CFEclipse-specific category or tag. If you want to press those folks to do so, that could be helpful to us all.

Finally, again, I realize that these are not complete lists. I did quite a bit of work to gather them up, but I'm sure I could have left out some great contributors. Please do add any you'd like as comments here.

Hope the above is helpful to all interested in CFE.

Update: On first posting this, I found out that my use of Google to search sites was finding entries where people had merely commented on CFEclipse in a person's blog, among some other issues. That's no good.

Better, though, I learned that for those sites using BlogCFC, I could indeed force it to use search criteria in the URL, so I've revised the list and the rankings since first publication earlier today.

Note: This blog post is from 2007. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.

If you had to guess how many people have blogged about CFEclipse, what would you guess? During my process of evaluating the current state of CFE resources (see my other recent entries in the CFEclipse category), I started to take note of those blogs that have CFE categories/tags.

I've found more than 70 of them and I want to point them out for you (those that had at least one useful entry). More than just list them, I also have provided an OPML file and even a CFE-specific aggregator for those who don't use one on their own.

Now, I've decided to split this entry into 2 parts. First, I list below those 51 who offer a specific CFEclipse category or tag (as well as offer the info to help you with aggregating them together).

In part 2, I'll list those who do not (at the time of this writing) offer a CFE-specific category or tag. Their content is indeed still valuable, just a little harder to stay on top of (and I'd love to see them added to this list if they would add a CFE category and assign it to all their past entries).

About the listing

The list is sorted in approximately descending order by number of entries (as of today). Note that it's possible a blogger may have a great tip but failed to mark under a CFEclipse category. They may also have listed CFE tips under an eclipse category, but I didn't think to consider that until later in my research, so while I have a couple of those below, I haven't gone back to consider that for those I did not list here.

While many of the entries are just news (like announcing a new release, etc.), some are useful tips from a wide range of developers. There are also the expected arguments for and against CFE (though those against tend to be older entries).

As I said before, this is all part of some work I'm doing to help developers get the most out of CFE, which I'll announce in the future. In the meantime, please enjoy the entries found here.

The list of CFEclipse category feeds

• (180) Mark Drew, of course(RSS for category)
• (63) Sean Corfield (RSS for category)
• (53) Andy Jarret (RSS for category)
• (32) Rob Rohan (RSS for category
• (32) Nathan Strutz (No RSS for category)
• (25) Spike Milligan (archived courtesy the web.archive.org) (No RSS for category)
• (24) Ryan Stewart (no RSS for category)
• (23) Simeon Bateman (RSS for category)
• (20) Ray Camden (RSS for category)
• (12) Matt Woodward (RSS from category)
• (11) Brian Rinaldi (RSS for category)
• (11) Ben Forta (RSS for category)
• (8) Rob Brooks-Bilson (RSS for category)
• (8) Luis Majano (RSS for category)
• (7) Pete Freitag (No RSS for category)
• (7) Dan Vega (no RSS for category)
• (6) Brian Kotek (RSS for category)
• (6) Charlie Arehart (RSS from category)
• (6) Aaron West (RSS for category)
• (6) Adam Crump (RSS for category)
• (5) Dan Lancelot (RSS for category)
• (5) Tom Chiverton (RSS for category
• (5) Trond Ulseth (RSS for category)
• (5) Andy Allan (RSS for category)
• (5) Steve "Cutter" Blades (RSS for category)
• (4) Russell Brown (RSS for category)
• (4) Scott Stroz (RSS for category)
• (4) Rob Gonda (RSS for category)
• (4) Phil Duba (RSS for category)
• (4) Mike Rankin (No RSS for category)
• (4) Kevin Roche (RSS for category)
• (4) Jared Rypka-Hauer (RSS for category)
• (3) Todd Sharp (RSS for category)
• (3) Michael Traher (RSS for category)
• (3) Andy Powell (RSS for category)
• (3) Russ Johnson (RSS for category)
• (3) Tony Petruzzi (No RSS for category)
• (3) Jeff Fleitz (RSS for category)
• (3) Teratech (RSS for category)
• (3) Jeff Coughlin (RSS from category)
• (2) Mike Kelp (RSS for category)
• (2) Joe Danziger (RSS for category)
• (2) Peter Bell (RSS for category)
• (2) Sam Farmer (RSS for category)
• (1) Rey Bango (RSS for category)
• (1) Dean Harmon (RSS for category)
• (1) Aaron Lynch (RSS for category)
• (1) Mike Nimer (RSS for category)
• (1) Kevin McCabe (RSS for category)
• (1) Gareth Edwards (No RSS for category)
• (1) John Ramon (No RSS for category)

I did quite a bit of work to gather them up, but I'm sure I could have left out some great contributors. Please do add any you'd like as comments here. Again, in part 2, I list those bloggers with CFE content but no CFE-specific tag or category.

Are you or a favorite not on the list?

Again, if you expect to be on this list and are not (or think someone should be), first let me ask you: does the blog have a CFEclipse-specific category (or an Eclipse category, on a blog devoted otherwise substantially to CF)? If so, I'm happy to add it. Just drop me a comment below.

And yes, I do hope that Mark will add this info to his wiki, but I have started the process by placing it here because I wanted to start the ranking by number of entries, something that won't be possible to reasonably keep updated in the wiki (but it's the sort of info not expected to be kept updated in a blog entry).

Tracking new entries: an aggregator and an OPML file

While you can just go browsing the bloggers, I've also done a few things to make it even easier for you to keep up on new entries from all these bloggers at once, whether you use aggregators or not.

First, I provide the URL for each blogger's RSS feed for their CFE category, if they have one, so you can add any of interest to any feed aggregator you have.

Further, I've provided here an OPML file listing all the RSS URLs (again, just for the CFE-specific categories). You can use that to import all the URLs into a favorite aggregator.

If you don't have an aggregator, here is a web-based aggregator of just these CFE-based feeds:

Browse and Search CFE entries

Finally, if your aggregator doesn't accept an OPML file, you can use the RSS feed from the aggregator I created:

RSS feed of new CFE entries

Hope the above is helpful to all interested in CFE. Look for part 2 (bloggers with CFE entries but no CFE category/tag) in a moment.