In short, I would say it is exactly the kind of function for project manager, not CodeEditor. But we do still have options here. Exporting and importing text for gcov can be done with services. You can supply a syntax for gcov and CodeEditor will support changing syntax highlight on the fly. So after importing the text from gcov, you can switch to gcov syntax highlight. That is the big picture I have.
Highlighing syntax on selected text can also be done. We just need a proper user interface (menu or panel) to do that. Automatically switching syntax would be tricker because we need a way to know which syntax to switch. Suggestion would be welcome. Do you have a sample of gcov output which I can take a look at the syntax ? Thanx. By the way, I do want something like Terminal.app which can supply services with script language so that I can output text in CodeEditor to LaTex or gnuplot. What is the stand of Etoile for that ? Do we have each script installed its own or we have a ServicesManager.app to search scripts or tools in certain directories and expose them as services ? Yen-Ju On 11/27/06, Guenther Noack <[EMAIL PROTECTED]> wrote:
Hi! On Sun, Nov 26, 2006 at 03:47:13PM -0800, Yen-Ju Chen wrote: > > I put up a list of features I plan to support or not in README. > Could you provide a plugin-architecture which allows you to easily get the code and highlight parts of it? There are a lot of features that can be implemented independently from CodeEditor if there is this kind of architecture. It should be capable of the following things: - Allow to highlight lines (for example with a different background color) - Allow to highlight specific parts of the code. - Attach text or information to highlighted parts of the code. The reason why I'd like to have this kind of plugin-support is that I'd really like to have native support for things like gcov (dynamic analysis tool that ships with gcc that allows you to see how often each line of code executed) and the detection of simple programming errors (like forgetting to return self in an initializer and typos). For having gcov support, the plugin would need to know the file name (because gcov's output file names are based on that) and a way to set the highlights for lines. Cool would also be something like a second column left of the line numbers that lets you see how often a line executed. For having support for error detection tools, a plugin would need to get the source code and set highlights for specific parts of the source code. It would be cool if a highlight could be annotated with a short text or tooltip that shows a longer description of the error and if there could be different types of highlights (like the red and the yellow ones in Eclipse which indicate the importance of the problem). For both types of tools, it would be good to know which filetype they are operating on, so that they can disable themselves for file types they don't support. I don't know how exactly hightlighting in the text view works, but I think the gain from providing a way to have plugins is worth it. :-) -Guenther _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
_______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
