Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:
Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What is the last letter in the word "SlickEdit":
How many LETTERS are in the following? "a1b2c3":
Which number is missing?  "12345689":

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: jporkkahtc
« on: June 24, 2018, 03:33:19 PM »

It isn't really compatible with some Slick features - like editing really large files.
VSCode for instance supports it, but VSCode is also limited to small files (I don't know the limit).

Slick tries to seamlessly edit both small and extremely large files - both a good and bad thing.
Being able to edit just about any file is great, but this also makes it a lot harder for Slick to implement new features - and some features just won't work with really large files.
Posted by: Graeme
« on: June 24, 2018, 07:32:07 AM »

I see KDevelop and komodo also have it.  I actually wrote a kind of minimap for slickedit but I haven't posted it as I'm not sure it's useful.  I might post it if it doesn't come along in V23.  It's not able to show any shrunken text like other minimaps though but it does show where code has been modified and it has local bookmarks.  The minimap in ultraedit here is only showing a small part of the file
https://www.ultraedit.com/products/ultraedit/ultraedit-feature-map/


Posted by: mwb1100
« on: June 22, 2018, 09:59:10 PM »

Quote from: Graeme on June 22, 2018, 08:22:32 AM
How many editors do you know that support it?
Can you describe how you use it and why you like it?

I'm not jwiede, but here are my answer to those questions:

Visual Stdio 2015 (and later), Visual Studio Code, Sublime Text, and UltraEdit.  I'm sure there are others - it seems to be a feature that has taken hold in the text editor market.  People seem to like it.

Personally, it's mostly just eye candy for me, but occasionally the image of the text in a file can actually give a visual cue to where something is.  So I personally don't find it a need-to-have, but I could see where some people might.
Posted by: Graeme
« on: June 22, 2018, 08:22:32 AM »

Quote from: jwiede on June 22, 2018, 03:50:34 AM
One last pre-version pleading, minimap support is another long-promised feature that most other programmer editors support now, and which would be very welcome in SE!
How many editors do you know that support it?
Can you describe how you use it and why you like it?

Posted by: jwiede
« on: June 22, 2018, 03:50:34 AM »

One last pre-version pleading, minimap support is another long-promised feature that most other programmer editors support now, and which would be very welcome in SE!
Posted by: gfinlay
« on: December 21, 2017, 11:45:12 PM »

Quote from: jporkkahtc on August 23, 2017, 07:17:56 PM
You can already sort-of fake it by opening a 2nd window on a buffer and set the font size really small.
This is true from the appearance standpoint. But what is needed is to synchronize the scrolling of a minimap window with the normal size window open on the same buffer.  This way you could use scrolling (via dragging the selection rectangle with a mouse in the minimap to control how the linked/synchronized normal buffer is positioned.
Posted by: jwiede
« on: August 29, 2017, 01:21:50 AM »

With all due respect they told us they're already intending to do this, they just weren't sure when (see above post by Dan).  All I'm asking, given that they're finalizing V22, is a clear indication whether this made it into v22 (2017), and if not, can we get a solid commitment it will be added in v23 (expecting us to wait longer for this level of feature isn't reasonable, IMO).
Posted by: jporkkahtc
« on: August 23, 2017, 07:17:56 PM »

You can already sort-of fake it by opening a 2nd window on a buffer and set the font size really small.
Posted by: Graeme
« on: August 23, 2017, 12:34:54 PM »

Considering that you can't actually read anything in the mini-map "scrollbar", a mini-map in Slick could be done with a macro using an image control which allows you to detect cursor movement and mouse clicks.  It could have a mode that allowed you to scroll the actual edit window without having to hold down a mouse button.  I wonder if you can detect the scroll-lock key in slick.  It could also be a re-sizable floating tool-window with a "horizontal" mode.

Posted by: jporkkahtc
« on: August 22, 2017, 11:58:00 PM »

WRT Performance: I do think that Slick's obsession with performance does sometimes get in the way of new or better features.

Not necessarily a bad thing --- I certainly appreciate the attention to performance as I often edit really large files that most other editors would completely fail on.

OTOH, I'd imagine that most developers don't do that -- as most developers don't use Slick - so they get by with editors that have really bad performance on extreme files.
Some of these editors have newer, shinier features - like the minimap or vertical indenting lines - that we would really like to see in Slick.

Posted by: jwiede
« on: August 21, 2017, 02:33:15 AM »

Quote from: Dan on June 28, 2016, 02:26:26 PM
Quote from: jwiede on June 27, 2016, 09:23:43 PM
Is there work underway (or planned) to give SE a "scroll-bar code overview" as is now available in VS2015, Komodo, Ultraedit, etc. where the scroll bar itself is a micro-ptsize-rendered version of the code, to make it easier to garner an overview of the file structure, identify section/function breaks, etc.? 

If the functionality is already present, my apologies (and please provide a pointer how to enable?).  Before posting, I looked for the feature in current SE, but if present I couldn't find how to enable it.

If not present or planned already, can we please get such functionality added?  I use it all the time in VS2015, and really miss it in SE.

P.S. The feature in VS2015 is called "map mode".  For C/C++ (f.e.) the setting is in Tools->Options... (to get Options dialog), then "Text Editor -> C/C++ -> Scroll Bars -> Behavior -> 'use map mode'".

We are looking into this for a future release.  It will not make 2016, but hopefully 2017.  As always, we're very concerned about performance so it has to "be done right ". ;)

Any chance we'll see this make it into V22?
Posted by: Dan
« on: June 28, 2016, 02:26:26 PM »

Quote from: jwiede on June 27, 2016, 09:23:43 PM
Is there work underway (or planned) to give SE a "scroll-bar code overview" as is now available in VS2015, Komodo, Ultraedit, etc. where the scroll bar itself is a micro-ptsize-rendered version of the code, to make it easier to garner an overview of the file structure, identify section/function breaks, etc.? 

If the functionality is already present, my apologies (and please provide a pointer how to enable?).  Before posting, I looked for the feature in current SE, but if present I couldn't find how to enable it.

If not present or planned already, can we please get such functionality added?  I use it all the time in VS2015, and really miss it in SE.

P.S. The feature in VS2015 is called "map mode".  For C/C++ (f.e.) the setting is in Tools->Options... (to get Options dialog), then "Text Editor -> C/C++ -> Scroll Bars -> Behavior -> 'use map mode'".

We are looking into this for a future release.  It will not make 2016, but hopefully 2017.  As always, we're very concerned about performance so it has to "be done right ". ;)
Posted by: jorick
« on: June 28, 2016, 12:50:37 PM »

I second the motion made by jwiede!  I think this would be an excellent option!  And in addition, colorize the microline that contains an error after compiling.

One other thing, it would be nice to have multiple colors for error highlighting.  Red for errors, yellow for warnings, etc.  User configurable, of course.
Posted by: jwiede
« on: June 27, 2016, 10:31:42 PM »

Quote from: jporkkahtc on June 27, 2016, 10:13:08 PM
I've seen people use this in other editors, but I'm not sure its really all that useful compared to the "defs" window in Slick.

I'd prefer the real thing, thanks.  As for benefit, anyone dealing with legacy code that has overly-long functions/methods/modules/etc. can benefit because it allows to see sub-function-level structure as well (in being able to see indentation overview etc. as well).  I'm not saying it should be mandatory, or even default, but I would definitely appreciate it as an option.
Posted by: jporkkahtc
« on: June 27, 2016, 10:13:08 PM »

You can badly fake it: Split you window and set the font size really small on the new pane.
I've seen people use this in other editors, but I'm not sure its really all that useful compared to the "defs" window in Slick.