Sure you can open a file anywhere on your machine, and edit it in Dreamweaver, but how will you test the file? You need to have a site pointed there. Why not just create a test site/subfolder somewhere that already points to an existing site and put your test files there. You can even create a subfolder and ignore it with SVN, this way you won't have problems keeping temp files around and you won't have to commit them.
Russ > -----Original Message----- > From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] > Sent: Monday, June 25, 2007 10:48 PM > To: CF-Talk > Subject: RE: CF Editor > > Of course I'm talking about Eclipse... it's the base behind the CFEclipse > plug-in in discussion here. Can't have the latter without the former so > let's not get into semantics. IDE, Editor, w/e. > > If someone asks a question on this list and I plan to offer a working > example, I'd rather just open up a blank page and write one, test it, make > sure it works and post it here... not add it to a project and definitely > not > version control. There are plenty of instances that you might want to just > create a quick test CFM file like this. "You" being the general population > and not you personally. > > Dreamweaver: double click a cfm file anywhere on the machine.. edit and > save. > CFEClipse: open Eclipse, change to CFEclipse view if you aren't already > there find the file in the list view THEN finally open it, edit it and > save > (and in your case... possibly commit). > > Come on... > > I'm not saying CFEClipse sucks or anything. I use it daily :-) I'm just > saying that there is no way you would expect an individual who has never > used CFEclipse or Dreamweaver to think that CFEclipse was easier than > Dreamweaver. > > What photoshop has to do with editing CF code I don't know. > > ..:.:.:.:.:.:.:.:.:.:.:.:. > Bobby Hartsfield > http://acoderslife.com > > -----Original Message----- > From: Brian Kotek [mailto:[EMAIL PROTECTED] > Sent: Monday, June 25, 2007 8:42 PM > To: CF-Talk > Subject: Re: CF Editor > > 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. > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Deploy Web Applications Quickly across the enterprise with ColdFusion MX7 & Flex 2 Free Trial http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:282147 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
