Lisp Development Tools is a Common Lisp Integrated Development Environment (IDE) plugin for the eclipse platform.
All you can currently get is this roadmap, an
alpha-quality preview
(Source Included),
some screenshots
and
a cvs repository.
Also check out ldt's project page.
Red means it's not done.
Yellow means it's underway.
Green means it's complete.
Last update: September 13th.
Roadmap for version 0.1 | |
DONE |
Understand the basics of eclipse pluggin and syntax highlighting programming. |
DONE |
Split the code between "comment" and "code" and make a comment syntax colorizer. |
DONE |
Make a symple syntax highlighter for strings, keywords and suck. |
DONE |
Start ripping the HyperSpec of all the necessary info to include in a future
content assist and code complete, and all the symbol names and their types
for use in the syntax highlighter. |
DONE |
Use the ripped HyperSpec symbols in the syntax highlighter. |
Roadmap for version 0.2 | |
DONE |
Parenthesis match. Possibilitate more modes than the default. |
|
Double click strategy:
|
DONE |
Remaining hyperspec extraction.
Successfully ripped: Functions, Accessors, Variables, Conditions, System Classes,
Macros, Types, Special Operators, Declarations, Symbols and Classes. |
DONE |
Content assistant and code completer.
The code completer is done, the context information is missing. |
TODO |
Syntax coloring of remaining syntax:
|
TODO |
Get a nice coloring scheme. I suck at this, I'll a web designer friend. |
Roadmap for version 0.3 | |
TODO |
A configuration pannel for colors. |
TODO |
Auto indentation and it's conf pannel. |
TODO |
Insertion of user defined functions into the spec, meaning some special parse of defun
or something.
|
TODO |
Better code navigation. Allow to jump () pairs or to the next defun/defstruct/whatever, using some ctrl/alt/shift combination with the arrow keys (or whatever keybind...) |
Roadmap for version 0.4 | |
TODO |
Finally, start thinking about Steel Bank Common Lisp integration. What's necessary in
order to talk to sbcl, to evaluate code, how to parse the output. |
TODO |
Invent some general-purpose interface that can later be used with other Lisp
implementations. Make sure it's easy to use new implementations and that you don't
have to have implemented all of the interface for the rest to work; For instance:
you can have the evaluate interface coded but the debug interface not coded. |
TODO |
Implement SBCL's evaluation interface. |
TODO |
Build a UI layer around the CL interface. |
Roadmap for version 0.5 | |
TODO |
Implement SBCL's debug interface. |
TODO |
Code LDT's debug view. |
Roadmap for version 0.6-nil | |
TODO |
Pump up the plugin, refactor code, redo what must be redone. |
TODO |
Add/fix all minor features/anoyances that might have been sugested by anyone who
tried ldt. |
Roadmap for version 0.6-t | |
TODO |
Version 0.6-t must be ready for academic use. |
Roadmap for version 0.6-lambda | |
TODO |
Version 0.6-lambda is a polished and entirely reliable version with no new features. |