The same key binding you are used to using for toggling the command line in SlickEdit will toggle it if you are using SlickEdit Core. It's just not always visible in SlickEdit Core because we really don't have a great place/way to dock it inside of Eclipse.
As far as the macros are concerned, those should work fine if they are from the same base version of SlickEdit. So if you are using the latest version of SlickEdit Core (3.6.1), that would be SlickEdit v15. If you only know they are compatible with an older version of SlickEdit...well, I can't say for sure. I would just load them inside of SlickEdit Core by opening them in a buffer and hitting F12, or via
Macro > Load Module, and if they compile, run the command(s) and see what happens. If they don't compile then hopefully you can fix the compile errors by debugging the error messages you get on the status line of Eclipse (bottom left).
The settings is kind of the same deal...if you use the
Tools > Options > Export/Import Options feature in SlickEdit v15 to export your settings, and then import the resulting .zip file in SlickEdit Core 3.6.1...this should work. I just tested it. However, doing this between different versions of SlickEdit is only going to work from SlickEdit v16 forward, though...and SlickEdit 2008 doesn't even have the Export/Import Options feature. So...not great news for you.
There is a more manual approach you can try, which involves running the vusrdefs.e macro from your old SlickEdit 2008 config. I can't give any guarantee on this working, and you could end up having to nuke your SlickEdit Core config so you might want to make a backup before you try this. But you can try it. Copy vusrdefs.e from your SlickEdit 2008 config directory to wherever your SlickEdit Core config is, and then start Eclipse. Now, from the SlickEdit command line enter the full path to this file including the file itself, encased in quotes if there are spaces in the path, and hit ENTER. This will run the
defmain() for this file and hopefully restore all of your settings, colors, key bindings, etc...if it actually works.
2) Can't I replace the RTC diff tool with diffzilla? I really miss diffzilla and don't want to change
We have integrated DIFFzilla into all Eclipse explorer views (ie. Navigator, Package Explorer) under the
Compare With submenu when you right click on a file or selection of files, and in the same place in the Eclipse History view for use with the Eclipse file history feature. It's also available manually at
Tools > File Difference, of course. I don't know about replacing the RTC diff tool with DIFFzilla, but I can log a feature request for this and look into it.
5) Is there a list of what is different/missing in slickedit core as opposed to slickedit 2011? I don't want 2 different products. Ideally, I want one editor that lives inside, and outside eclipse. I want ONE set of macros and settings that applies (as much as possible) to both. And...why not shared tag files?
Well, they are different environments and the actual editor is the
exact same editor as the SlickEdit standalone editor of the same base version, but there are features that are stripped out of SlickEdit Core for specific reasons. The most common reason being that we don't want to duplicate functionality in Eclipse if Eclipse does something perfectly well. We would not want to clutter up Eclipse with our version control support because we feel that Eclipse handles version control support very well. Same thing with project/file management...and build/run management. No need for SlickEdit in those areas. When we feel we have something different or better to offer, we expose and integrate that feature in Eclipse. But in the case of the actual editor itself, it really is the exact same editor.
I hope that helps, in some way. Let me know if you have any other questions...thanks for the feedback.
- Ryan
