I'm working on a rather large Model-Glue site. The main ModelGlue.xml file contains many includes to break out the functionality.
While this makes the XML a lot easier to read, it confuses the framework explorer a bit. The framework explorer does correctly notice the include. But it doesn't let me explorer the XML and see the controllers and event handlers.
Turns out there is a simple solution. I just needed to right click on my included XML file, select CF Frameworks, and then Set/Unset as Configuration file:
In the drop down, select Model-Glue. Then in the frameworks explorer window, hit the Refresh button. Your XML file will now show up as a Model-Glue config file you can browse.
I want to say I'm very disappointed in CFEclipse. The fact that it can't read my mind and understand what I mean by telepathy is truly a shortcoming of the product. I may have to switch to Visual Studio I suppose. (Hmm, may be a bit hard on the Mac.)
Archived Comments
Well, I really have been wanting to switch to CFEclipse as I have heard so many good things about it. The problem is I have been a die hard Dreamweaver fan for so long it is like second nature to me.
Can you define an RDS connection for developing? I tried it briefly, but I was a bit overwhelmed by all the options.
If you mean RDS - yes, you can do RDS in Eclipse - but it isn't via the CFEclipse plugin - it is via the RDS plugins by Adobe.
Basically - as a developer you have two main plugins for Eclipse:
CFEclipse - this gives you color coding, framework support, etc.
RDS Plugins by Adobe - these give you RDS support, plus other things like the Log Viewer, Debugging, etc.
I use Oxygen for Eclipse (the stand-alone IDE, is better than the Eclipse Plug-in) because the formatting options are incredible for XML, including the sorting of attribute names and indentation that respects the hierarchy of XML. It makes XML much more readable as a project grows.
I have RDS support working now. Thanks for pointing out the Adobe plugins.
I must admit I did start using Eclipse, although in the form of Aptana as it seemed to be easier to move to from Dreamweaver. I did like it - some of the features are lovely - but I ended up returning to Dreamweaver due to the CFEclipse plugin. It just seems so slow for code completion. In Dreamweaver, code completion is bliteringly fast, with all the CF attributes for a chosen tag popping up without delay. I found in CFEclipse that I'd be pressing return to accept the option before it was showing up and thus causing a line break - very, very annoying.
Does anyone else have this problem or is it just CFEclipse running in Aptana? I also found CFEclipse to be very slow when editing large files.
I'd love to return to Aptana / Eclipse at some point if the code completion was as fast as Dreamweaver. I must admit, I do have a soft spot for DW though having used it since version 1.
The main reason for jumping ship before was my journey into CFC's which CFEclipse does handle very nicely (DW has a compent browser but it's far from what CFEclipse offers).