I'm sure Sun's code is nice, and maybe the display part of it can be
copied without too much overhead. But even if we don't, adding a
symbol gutter is in any case a pretty straightforward task.

Should we be so lucky as to get some coding help, let's spend it
on the _hard_ and long-awaited things.
- Unicode - involves lots and lots of the code and is a real obstacle
  to widespread use,
- Folding  - probably requires fundamental redesigns in the text
  widget
- Macro/hook/event/binding system - overdue for a revamp.
- Highlighting system - we used to be among the most advanced,
  but these days many others have way more intelligent 'real' parsing
  that just cannot be done with the current regex based system.


On Thu, Feb 28, 2008 at 11:05 PM, Tony Balinski <[EMAIL PROTECTED]> wrote:
> Quoting Andrew Stanaski <[EMAIL PROTECTED]>:
>
>  >
>  > Randy Kramer wrote:
>  ... summer of code suggestion ...
>
> > >    * revise the nedit display widget to add a(n optional) column for
>  > > folding
>  > > marks (i.e., the typical + or - in a box, vertical lines, the L-shaped
>  > > termination of such lines)
>  >
>  >
>  > Folks at Sun did this many years ago when they incorporated NEdit (5.1)
>  > into their workshop IDE. They had symbols for breakpoints, the currrent
>  > line indicator, and such in the left side column.
>
>  I remember picking up that code: should have it somewhere. I remember that to
>  me it seemed pretty tightly coupled to the IDE and its API (probably a good
>  thing for the level of integration required, eg baloon tips with variable
>  debug values - very cool!). I even tried it once. This was before tabbed
>  editing and there was a "feature" which swapped the file you were looking at
>  in the window and you moved through the code. Tabs would have been much 
> better
>  there. Other than that, it was very smooth.
>
>  Tony
>
>
> --
>  NEdit Develop mailing list - [email protected]
>  http://www.nedit.org/mailman/listinfo/develop
>
-- 
NEdit Develop mailing list - [email protected]
http://www.nedit.org/mailman/listinfo/develop

Reply via email to