Quick notes ( I need to bang out some code... ):
That's true of some but not "most".
Visual Studio has long been thought of as Microsoft-only tool that doesn't apply to anything but .NET. But I'm glad that Visual Studio is recognized by some here as being an open platform for development, not just a language-specific one-shot tool C++, C#, or
VB.NET. Similar to Eclipse and others, it's fully extensible to many other uses. It's bundled with language-specific implementations simply to facilitate efforts by developers using Microsoft-oriented languages.
More about Visual Studio Extensibility : Rather, a whole site dedicated to it :
http://www.visualstudioextensibility.com/overview/vs/Over this last year there was a lot of fanfare about Roslyn, which is defined in this quote from the above link:
.NET Compiler Platform (formerly “Roslyn”): before the
.NET Compiler Platform extensions had to use the code model provided by
automation (EnvDTE.Project.CodeModel, EnvDTE.ProjectItem.FileCodeModel)
which had limitations and inaccuracies parsing or modifying source code.
The .NET Compiler Platform exposes to extensions the compiler APIs that
Visual Studio uses for the C# and
VB.NET languages. Requires Visual
Studio 2015.
I wish I had more time to explore the .NET Compiler Platform to create the kind of MV BASIC editor that is being discussed in this thread.
Q&A about adding languages to Visual Studio:
http://stackoverflow.com/questions/4283072/how-to-create-a-new-language-for-use-in-visual-studioKevin mentioned Visual Studio Code (a rotten name for a product IMO). Here is a Q&A about custom language support for that platform:
http://stackoverflow.com/questions/30687783/create-custom-language-in-visual-studio-codeThat points to VSCode docs where as recently as this month support for languages has been added. This is all still WIP. More info:
https://github.com/Microsoft/vscode-docs/blob/0.9.0/release-notes/latest.mdFor anyone who wants a more MV-based solution, I maintain that the mvToolbox is one of the most powerful yet unappreciated tools in this industry, and it does many of the things requested in this thread:
http://mvtoolbox.com/Regarding AccuTerm and improvements to wED, I posted the following a few years ago:
http://www.pickwiki.com/index.php/AccuTermKeywordsFinally, there are tools that will add functionality to other apps. For example when you mouseover text and right click you'll get a context menu from the other tool, not the one you're using (VS, Notepad++, Sublime, etc). With options like this it might be possible to hobble together a custom solution that satisfies most requirements, rather than trying in futility to find a single tool that provides all of them.
I'd love to create a new editor for MV. As indicated in the other thread I've looked at Antlr for parsing MV BASIC. The result of that would be a syntax tree that can be used with editors to get many of the features we want. I'm actually not as in-tune with parser/lexer sciences as I'd like to be. Never had the need. As I've lamented many times in these groups, it would be neat to pursue this with the goal of creating something useful, but I'm discouraged from pursuing for-profit projects like this, as they just lead to an uphill battle against frugal Luddites, and few people in this industry value the open source model, so I wouldn't bother to create a project for it at FOSS4MV, GitHub, or PickWiki. With similar sentiments from many people, including those at the MV DBMS providers, it's simply not worth the time to do stuff like this - at least not until the culture/industry changes and we start to get new people in the community. I SO wish it were different. (That's a topic for a thread of its own: Industry Apathy)
Didn't I say "quick"? Ugh.
T