From Niki

Contents 1 Google 2008 Summer of Code: Idea Page 1.1 Projects with a Proposed Mentor 1.1.1 Macro Hook/Event Binding System 1.1.2 Macro Toolkit 1.1.3 Indented Continuous Wrap 1.1.4 Reference Counted Macro Variables 1.2 Projects without a Proposed Mentor 1.2.1 Folding 1.2.2 Unicode 1.2.3 Highlighting System 1.2.4 Visual Whitespace 1.2.5 Left Panel File List 1.2.6 Named and Persistent Bookmarks 1.2.7 Refactoring WindowInfo 1.2.8 NRR (NEdit Resource Repository) 1.2.9 Nimble (NEdit Macro Library)

Google 2008 Summer of Code: Idea Page

This is the idea page for NEdit's participation in the Google 2008 Summer of Code.

This page is an overview / summary. For more details and discussion, see the discussion page.

Note: The first four projects have a proposed mentor, the others do not. We are most likely to approve a proposal for a project which has a mentor. However, we will consider other proposals.

Projects with a Proposed Mentor

Macro Hook/Event Binding System

[Details] This is overdue for a revamp.

Advocate: Joachim Lous, Bert Wesarg
Proposed Mentors: Bert Wesarg

Macro Toolkit

[Details] i.e., a macro interface to the motif toolkit (needs Macro hook/event/binding system)

Advocate: Bert Wesarg
Proposed Mentors: Bert Wesarg

Indented Continuous Wrap

[Details] If you don't know what it is about, look at this screenshot from Kate. Lines beginning with XXX are continued lines but are aligned at the column of the first character.

Advocate: Bert Wesarg
Proposed Mentors: Bert Wesarg

Reference Counted Macro Variables

[Details] NEdit's macro language interpreter uses an extremely simple garbage collection system. This results in excessive memory usage for simple tasks, which can lead to severe degradation of NEdit itself and even the host system.

A solution to this problem would be to implement a reference counted variable system for the interpreter.

Advocates: Tony Balinski, Bert Wesarg
Proposed Mentors: Bert Wesarg

Projects without a Proposed Mentor

Less likely to be considered this year, may be considered in future years.

Folding

[Details] Implement (real) folding in NEdit. (There is a means of doing a sort of faux folding by the trick of replacing strategic \n's with \f's--that's not the goal.)

This is a big task, probably too big for a single GSoC project--see the discussion page. Update: Maybe not quite as big as I thought, see details.

Advocate: Randy Kramer plus many
Proposed Mentors: TBD

Unicode

[Details] Involves lots and lots of the code and is a real obstacle to widespread use.

Advocate: Joachim Lous
Proposed Mentors: TBD

Highlighting System

[Details] 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.

Advocate: Joachim Lous
Proposed Mentors: TBD

Visual Whitespace

[Details] Display something to indicate the type and extent of whitespace, for instance, "»" for tabs, "·" for spaces, ...

Advocate: Tony Balinski
Proposed Mentors: TBD

Left Panel File List

[Details] Generally, an additional panel to the left of the text panel with a list of all the files currently open in nedit, allowing you to switch to another file by clicking on it (like a tab).

Advocate: Randy Kramer
Proposed Mentors: TBD

Named and Persistent Bookmarks

[Details] Revise NEdit's (book)mark facility to make it:

• persistent
• use "real names" instead of single alphabetic characters
• drop down menu (optional future enhancement?)

Advocate: Joerg Fischer (Randy Kramer)
Proposed Mentors: TBD

Refactoring WindowInfo

[Details] I'm not sure that's its legal under SoC conditions, but refactoring WindowInfo is IMHO the single most important change one could have for NEdit. The task would be to break WindowInfo up into smaller chunks and refactor the code to use the new chunks. This change would greatly facilitate any other change withing NEdit and would in fact make possible some that currently aren't.

Advocate: Thorsten Haude

NRR (NEdit Resource Repository)

[Details] Provide a web application which offers NEdit resources via browser interface and as a web service for Nimble (see below). The repository should offer smart search, dependency resolution and creation of download packages on the user side, &c; worker tools for version control, reformatting, &c. Language must be any web language known to the project, ie. Perl, PHP or Ruby.

Advocate: Thorsten Haude

Nimble (NEdit Macro Library)

[Details] Depends on NRR (see above). Adds a set of dialogs to NEdit which will allow the user to search for a topic in the NRR, select packages from a list offered and download and install the result. Implementation should be in NEdit macros as far as possible, but it is expected that the macro language has to be extended in C.

Advocate: Thorsten Haude