Extension talk:VisualEditor/Plugin for source code editing (SyntaxHighlight GeSHi support)

My main concern with this project is that is seems to have more focus than it should on auto-formatting code. This should be made as a nice-to-have feature, and broad syntax highlighting support should be made a high priority. The differences between CodeEditor and this are described as this being meant for snippets within an article. If that's the case, JavaScript shouldn't be focused on so much, as snippets will come in all sorts of languages. Having identical syntax highlighting as the extension you are abstracting is critical. Auto formatting code sounds like a feature that many people will want to turn off. Trevor Parscal (talk) 20:36, 29 April 2013 (UTC)
 * Will the broad syntax highlighting support be overlapping with the existing SyntaxHighlight feature? Since SyntaxHighlight already supports many languages, using the existing syntax highlighting tag/code provided by it could be of considerable help. Syntax/grammar checker and additional highlighter could be based on this also, but might be better to begin with some more general parts of programming languages (symbols, syntax of defining a function/class, etc.). Having included CodeEditor is because that it may provide reference about syntax checker mechanism/algorithm. The auto-formatting feature I'm thinking is more of a "one-click" feature, so it is provided, and will not function unless user click the button for this feature. I agree that the proposal seems too focuses on formatting, but that was the original source of motivation out of my experience. I'm also searching for ways to add more gravity to this proposal, probably by adding more focus on the syntax checker. But I'm still not sure about how far this plugin should go on its highlighting feature. --Tongbo Sui (talk) 00:45, 30 April 2013 (UTC)