As far as Flash Builder 4 is concerned, I am currently running it with SlickEdit Core 3.5.0 and editing seems to be fine. It sounds like whatever type of file you are working in either isn't opening with SlickEdit or is not opening in the right language mode. What file extension are you working with? What type of files are these?
Make sure that SlickEdit is the default editor for the file extension at
Window > Preferences > General > Editors > File Associations.
With the language mode, ActionScript (*.as) should be setup by default, but for MXML files you might have to add the extension. Go to
Window > SlickEdit Preferences > Languages > File Extension Manager, click
New..., and associate the extension
mxml with
XML.
Still having problems? Show me some screenshots so I can see what is going on, and post the workspace .log file which you can find at WORKSPACEDIR/.metadata/.log.
There is a problem, though, with the Flex support plug-in for Core (found at
http://community.slickedit.com/index.php?topic=5622.0) with Flash Builder 4. Looks like they changed their API, and setting breakpoints in the SlickEdit editor is not working anymore. I am seeing from my .log file that the create breakpoint method in one of their plug-ins has changed. Debugging and stepping still works within the SlickEdit editor, and you can set breakpoints via other means in the IDE, but setting them directly in the file (ie. by double-clicking in the left hand margin) looks to be broken.
We will have to build another plug-in to address this issue.
Now, with the problem you are having with Cold Fusion Builder, it sounds like they have hardcoded their editor id in for debugging...which is bad (and wrong), but not unprecedented. We ran into this exact same issue with PDT (the Eclipse PHP support plug-in) and I had to log a bug with them (
https://bugs.eclipse.org/bugs/show_bug.cgi?id=270137) so that they would allow the default editor to be used for debugging instead of hardcoding their editor. They fixed it in the next release. Sounds like the same issue, and will likely require the same course of action...so I'm not quite sure what I can say about when this will be rectified :/.
- Ryan