I just downloaded this today, and although I think it has some potential, there were also quite a few annoyances that I'd associate with it. I wanted to pass these on for possible future improvement:
- Available views are very restrictive. Consider giving the ability to move, resize, create as many or as few windows as desired.
- Marked-up source is horrible to edit in anything other that does not read the markup (a development IDE, for example). Consider, perhaps, a separate file that contains the information rather than the original source.
- Tools to automatically mark up existing source. This should be a fairly simple parsing exercise. For someone like myself, with a few hundred thousand lines of existing source, such an editor would be pointless without some way to deal with the existing files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Markups are in the same source file especially to allow edition of files with any other editor: there is no risk to loose synchronisation between a source file and its markers. The only risk using an external editor is to get unbalanced folding directives such as an open fold directive wihout close fold.
A tool to mark up existing source is a good idea. But it requires a specific parser for each language: one for C style languages (C++, C#, java), one for pyton, one for LaTeX, ...
Such a tool could have some options:
- convert comments to special comments
- generate index of methods using link directives
- fold class, fold methods, fold cases, ...
- format of the headlines
- ...
One of these days I'll try to start a simple converter for C programs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just downloaded this today, and although I think it has some potential, there were also quite a few annoyances that I'd associate with it. I wanted to pass these on for possible future improvement:
- Available views are very restrictive. Consider giving the ability to move, resize, create as many or as few windows as desired.
- Marked-up source is horrible to edit in anything other that does not read the markup (a development IDE, for example). Consider, perhaps, a separate file that contains the information rather than the original source.
- Tools to automatically mark up existing source. This should be a fairly simple parsing exercise. For someone like myself, with a few hundred thousand lines of existing source, such an editor would be pointless without some way to deal with the existing files.
Markups are in the same source file especially to allow edition of files with any other editor: there is no risk to loose synchronisation between a source file and its markers. The only risk using an external editor is to get unbalanced folding directives such as an open fold directive wihout close fold.
A tool to mark up existing source is a good idea. But it requires a specific parser for each language: one for C style languages (C++, C#, java), one for pyton, one for LaTeX, ...
Such a tool could have some options:
- convert comments to special comments
- generate index of methods using link directives
- fold class, fold methods, fold cases, ...
- format of the headlines
- ...
One of these days I'll try to start a simple converter for C programs.