ScintillaNET: Trolling for Features

I've got several people interested in contributing to ScintillaNET, now what we need to do is build a roadmap.


I need to know what kinds of things that we should be putting into this next version, (including things in older versions, or stuff you may have coded yourself).


I'm only a couple days away from having the basic API fully implemented; this will allow us to start adding in the feature of Scite that we all enjoy, (smart indenting, common find/replace  etc...) and have it useable everywhere.


I'd also like a list of places and projects that you think could benefit from ScintillaNET. 


Finally, I've got a rather ingenious idea for a little utility that i'm calling "Scintilla Everywhere", and I'd like to hear people's ideas for helping me implement it:



I want to build a tool that given a hot key will pop up a ScintillaNET editor on top of *any* edit control in Windows. Using standard messaging, you should be able to edit the contents of the field (in the ScintillaNET shadow) and have it sync the contents back to the actual edit field. This would have the perceived effect of having ScintillaNET availible in any application that used a text field.  Imagine, any text field that you can edit, would suddenly have the power and flexibility of Scintilla in it. Color Syntax highlighting, outlining, etc...


I've got some ideas on how I'd start that, but I'd love to hear what others know, or if there is a better way to do that.


Anyway, PLEASE file issues for feature requests, and we'll discuss them in the boards and issues on CodePlex.

Comments (3)
  1. jeffcohen says:

    Just want to say, I’m glad to hear you’re back in the saddle with Scintilla.  I may also try to contribute when I get some free time.

    One suggestion – I would suggest that the .net wrapper be just that, just a nice wrapper, and not include any features that are really a part of Scite.  Somewhere a line has to be drawn between what is the respnsibility of the wrapper, and what is the job of the containing application.  So smart indenting is essential; but find/replace dialogs are the job of the application that is using the wrapper, not the wrapper itself. (And maybe the find/replace dialog is a bad example, but I hope you catch my drift?)

    Thanks again.


  2. I agree with that completely–as a matter of fact, we’re adding in the Find/replace stuff, but it’s not bound to the control–that is if you want to use it, you have to explicitly enable the functionality.  I wanted *just* a control, with the complete set of features, but no more.

    The things that will end up in the same assembly, (but you are not forced to use or even acknowlege) are find/replace, smart indeting, and style loading.  All of those will be there, but not required for use.


  3. jeffcohen says:

    Not sure if you saw the thread in the forums, but we’re wondering if syntax coloring is done yet?  I haven’t been able to get that to work, but maybe I just don’t understand what I need to do to get it working.



Comments are closed.

Skip to main content