I have just looked through a very nice basic introduction video of the features of DLTK. http://live.eclipse.org/node/548
Although it is unlikely to have EPIC rewritten using the DLTK framework (is it?), we still can steal some ideas that DLTK does quite well:
- you can specify several interpreters, one default and custom interpreters for each project, and customize environment variables if you want to
- you can leverage RSE to remotely define and call interpreters
- lines inbetween parens are highlighted (default blue) at the left side of the editor when the cursor is in. This eases the task of finding the closing parens in the code.
- callers/callees list
- class/type hierarchy
- nice integration of sourcecode documentation (documentation is shown by hovering over an element, plus it has a special documentation view containing the same information
- validators can be run on parts of the project
Log in to post a comment.