SlickEdit 2008 - My Evaluation

I got a free version of SlickEdit in return for blogging about the experience.  So here is my feedback, good and bad.

Good: First thing I noticed when I installed it:  this is not your ordinary text editor.  I've been using UltraEdit for several years now, and I like it.  UltraEdit has some developer-centric capabilities, but they are not integrated tightly into the product as is the case with SlickEdit.  For example, SlickEdit will automatically expand if and for statements, and try blocks, although I didn't see a way to have it automatically generate the finally clause.  Honestly, despite any negative criticism that I have of SlickEdit, I think that this is the kind of application that has so many features that in order to properly appreciate them you must use it for a long time, so I plan to revisit this evaluation in the future.

Good:  Ctrl-F worked for find, but I'm used to F3 doing the "Find Next" (From Visual Studio and Ultra Edit).  A quick look in the Options menu allowed me to change my keyboard emulation from CUA () to Visual Studio Defaults.  Problem solved.  Very nice.

Annoying:  The next thing that came up, when I hit ctrl-N to open a new page, instead of just giving me a new untitled page, it gives me a window in which I have to choose the type of file I want to create.  Its default is "automatic", which gives me what I want but still requires me to click an "OK" button.  I'd rather eliminate this step and have it figure this out the file type on its own after I do a save-as and assign it an extension.

Annoying: I created two unsaved files containing some xml, and when to compare them to find out the difference(s) in the two files.  I found a "File Difference" option under the Tools menu.  It gives me a dialog with two file path inputs, both empty.  I would expect the two most recently edited/opened files to be pre-populated there as they are with UltraEdit.  I thought this was going to be a lot of extra clicks but then I saw the little "B" button next to the two path inputs that allowed me to choose the "buffers" (the files I had open in the editor).  Only like 6 extra clicks.  Not so bad, but could have been smarter.

Annoying: I wish it had asked me during the install process if I'd like to update my file associations.  Instead I have to go searching around in the menus for it.

Good:  The code navigation feature is sooooo useful.  If you are editing code, and you want to see the definition of a particular call, just hit ctrl-. and SlickEdit will jump to the definition.  I use this fairly often.

Good:  Built in backup history allows you to view previous versions, and even merge and diff different versions.  Awesome!

Overall, I'd have to say this is a great app.  Incredibly powerful.  I will post more details about this later, as I continue to compare with UltraEdit.

Now Playing: Bob Marley & the Wailers - Exodus

Technorati Tags:

Print | posted on Friday, June 20, 2008 4:48 PM

Feedback

# re: SlickEdit 2008 - My Evaluation

Left by Scott from SlickEdit at 6/25/2008 10:31 AM
Gravatar Thanks for the great review! We love the feedback.

About creating a new file, without either an extension or a chosen file type we don't have the information needed for color coding the file. You can hit Enter instead of using the mouse to click OK.

Also, many of our users use our command line interface. The fastest way to create a new file is to press Esc (in CUA emulation) to bring up the command line, type "e file.ext" and press Enter. Of course you would use the real name of the file and real extention instead. This gives us what we need to do color coding and you can do save as later to put it where it belongs in the project.

# re: SlickEdit 2008 - My Evaluation

Left by Mike Lewis from Black Hills Corp at 1/6/2009 5:49 AM
Gravatar I have been using SlickEdit for many years. It is a first rate editor, that will work on multiple platforms (runs on X-Windows in *nix) and supports multiple keyboard emulations. The technical support has been very good.
One major issue that I have with it is that the concurrent user license manager (FlexLM) is a hassle to work with, and at least a couple years ago, it was not very fault tolerant. So if the license manager goes down, you don't have an editor. Ouch! This is supposed to work, but it did not do so in our tests. One way around this on Windows is to use dedicated user licensing, it does require a license manager. But that is not an option on the other platforms.
Another problem that I have been noticing over the last couple years, is the performance seems to be getting worse, it has become too slow loading - at least for me. I find myself using notepad for quick edits. Have not spent any time diagnosing same though.

Your comment:





 
 

Copyright © Lance Robinson

Design by Bartosz Brzezinski

Design by Phil Haack Based On A Design By Bartosz Brzezinski