CFEclipse.Project = Dreamweaver.Site

I had an epiphany just now. One of the most common complaints I hear from folks trying CFEclipse for the first time is that you have to work with projects to get at your files. Well, that's not true, CFEclipse's File Explorer allows you to just point to a folder and edit files, similar to Homesite. But, to get the full power of Eclipse, it's best to use projects.

But as far as Dreamweaver goes, aren't "sites" the same thing as Eclipse's "projects"? I'm not a Dreamweaver expert, and I know that there are a LOT of differences between sites and projects, but it seems like the idea is basically the same. So if you are used to sites in Dreamweaver, you should be comfortable with projects in Eclipse.

Anyway, just thought I'd pass that along. :)

Related Blog Entries

Comments
The difference is that DreamWeaver lets you use a project to update your site using DreamWeaver templates. This also ties into Contribute-based sites. Something you cant do with CFEclipse and a reason why some of us wont fully move away from DreamWeaver until CFEclipse supports this feature. I love Eclipse in general, but the power of DreamWeaver templates is to great to give up for a free editor.
# Posted By TJ Downes | 1/28/07 6:08 AM
I always thought of them as roughly equivalent. I never liked the "sites" terminology anyway. Made me feel like they thought I was building web sites and not applications. Project makes me sound more important =)
# Posted By Sammy Larbi | 1/28/07 6:31 AM
To get around CfEclipse's file explorer problems, just download Aptana and use their's. As much as people moan about the file explorer in CFEclipse, I think the team is doing the write thing and getting the CF portions of the editor ironed out before committing a lot of time on the explorer.
# Posted By tony petruzzi | 1/28/07 7:23 AM
You can create new files based on snippets already in CFEclipse which acts the same as templates. With regards to contribute functionality, well, whats the point in CFEclipse doing it? There are TWO tools to do this, Dreamweaver and Contribute itself.

Besides, how many CFC's do you write in Contribute?
# Posted By Mark Drew | 1/28/07 9:56 AM
There is one _major_ difference between Dreamweaver sites and Eclipse projects; Dreamweaver sites are 100% optional! Further more, you can right-click any file in Windows and have it open in Dreamweaver. Heck you can even drag it directly into the IDE. No site (or project) necessary.
# Posted By Adrock | 1/28/07 12:20 PM
I guess that is the difference between an editor and an IDE. I am sure Dreamweaver (if you dont set up a site) understands all your CFC's (of course it does, it hits the RDS server, handy that)

Sounds like Dreamweaver is just the ticket for you... stick with it.
# Posted By Mark Drew | 1/28/07 12:35 PM
You might want to find my response here: http://www.markdrew.co.uk/blog/index.cfm/2007/1/26...
# Posted By Mark Drew | 1/28/07 12:38 PM
Adrock- I thought Jake explained that you don't have to have projects in CFEclipse... though, I personally like them. No sense in doing a file search outside my project if I don't need to (though I am free to, should I need to)
# Posted By Sammy Larbi | 1/28/07 1:00 PM
I would suspect that at least a significant number of people who are complaining about projects in CFEclipse dislike the "Site" requirement in Dreamweaver as well. I know I found myself in a similar position. At least in CFEclipse though, the Projects are a lot easier to set up.
# Posted By Adam Ness | 1/28/07 8:39 PM
BlogCFC was created by Raymond Camden. This blog is running version 5.9. Contact Blog Owner