On 6/25/07, Bobby Hartsfield <[EMAIL PROTECTED]> wrote: > > Seriously Neil? You question that statement at all? > > Compared to 95% of all editors out there, I think it is obvious that > CFEclipse has a bigger learning curve. (the other 5% including editors > such > as Emacs and VI heh)
I think you're really talking about Eclipse in general, as CFEclipse is just an Eclipse plugin and a relatively straighforward one at that (compared to something like Aptana). Even still, I don't think Eclipse has much more of a learning curve than Dreamweaver, and certainly nothing like Photoshop. The Getting Started Screen that shows up when you launch it for the first time will show you everything you need to know if you just take a few minutes to go through it. Out of the box, you can't just open CFEclipse and start editing files for > one... you have to set up workspaces and projects either with the files > you > want to edit or create new files within a project before you can edit > them. > The whole project based editing is the one big turn-off for most people > that > say they don't like CFEclipse. I just don't get this complaint. Yes, you have to set up a project to edit a file, but this is not an issue to me. Every single file I edit is in Subversion, even local files, and thus every project I have in my Eclipse workspaces is tied to SVN either locally or remotely. I view Eclipse projects, and their connections to Subversion, not as a problem but as a great advantage. Personally I think anyone NOT using SVN at this point is off their rocker. Same goes for the way projects relate to ANT. You can use ANT to execute flawless deployments every single time at the click of a button. Every step that you do manually to update a site, whether it is pulling from SVN, uploading via FTP, copying across mapped drives, backing up the current code, pruning unit tests and other supporting files, executing a browser request to reload/refresh the app, or just about anything else, can be done with ANT so you never need to worry about it again. <opinion>If it were easy to just install CFE and simply double click a .cfm > (that isn't part of an existing project) then edit and save... CFEclipse > would be on every developers workstation.</opinion> Unfortunately as far as I know this isn't possible due to the fact that a file could be part of one or many Eclipse workspaces or projects. Eclipse has no idea which workspace to open, for example. Again, to me this isn't an issue. I very rarely just need to open a random file to edit it. Everything is part of a workspace, project, and working set. Navigating between workspaces is easy, creating a project takes about 10 seconds, and keeping workspaces tidy with working sets is also quite simple. Again, yes there is a learning curve to this, but it is really not that bad and once you embrace it (and SVN, ANT, and the other great things that Eclipse and CFEclipse can do) you'll wonder how you ever did it the other way. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 The most significant release in over 10 years. Upgrade & see new features. http://www.adobe.com/products/coldfusion?sdid=RVJR Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:282129 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
