I need to refactor the project design to abstract all dependencies on the Antlr4 runtime assemblies. This will allow it to have different providers for different runtime versions all supported in the same tool.

Add full documentation of all options and behavior for Grun.Net tool.

If the graph is rebuilt while the user is zoomed in, the zoom factor goes haywire due to math mistake.

The current method for extracting the parser rules can sometimes result in them being in the wrong order and thus getting mismatched to the graph node names. This will be fixed in the next release later today.

If the assembly containing the current editor guide is changed, the guide should be reloaded in the background automatically.

I inadvertently broke line number displays in a build without noticing it. I will have this fixed shortly with a fixed build released for both versions.

Add 'svg' flag to the grun.exe, allowing users to write out a scalable vector graphics file containing a parse tree graph.

Add support to drag and drop assemblies and source code files to GrunWin. If an assembly is dropped onto the form, it should find all ANTLR grammars within the assembly and then load the grammar if there is only one. If there are multiple grammars, the the user should be prompted which grammar to load. Any non-assembly file should be inspected to see if it appears to be valid ascii source. If so, then the contents should be loaded into the code editor window.

GrunWin should be modified to detect changes to the loaded grammar assembly and then reload the assembly in response. This will make grammar testing more seamless and easy for the user.

Grun.Net does not seem to work with a net472 assembly built against Antlr4.Runtime.Standard v4.8. At assembly.GetTypes(), line 83, Scanner.c "Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information" Note: Antlr4cs is several versions behind the current Antlr code base, now 4.8. Version 4.6.6 in the Antlr4 code tree was last updated a year ago, but forked from 4.6, which was released in 2016! 4.7 was released in 2017. 4.8 was released a few months ago. The Antlr4cs code hasn't been updated by Harwell for over a year, and unclear if he is maintaining that codebase now. Other than that and a few minor problems (lexer error messages are not displayed, selection of input or tokens not reflected in selection in tree), the code works well.

Add a graphical parse tree control to GrunWin using the Microsoft Automated Graph Layout library.

Create a windows installer to install tools to a proper program files directory and add the Grun.Net tools to the environment PATH variable.

Add click support so that the user may click on any parser error and select the text in the code editor window that corresponds to the error that was clicked on.

Add ability to select the parser rule the parser graph window that corresponds to the current code selection in the code editor window.

Parse error indicators are being left behind if you change the parser rule in GrunWin, even if the new rule parses. This should not happen.

When a source code line would be forced to wrap in the console, the syntax highlighting breaks badly. The syntax highlight code in the console needs to be modified to detect line wrapping.

Add a new ObjectListView grid to display all parsing errors and their details.

Syntax highlights of errors are not always removed when the syntax error goes away. Clean up defunct style assignments.

Finish adding command line options to the GrunWin tool so that it can be run as a stand-alone app.

Add click support so that the user may click on any parser tree node and select the text in the code editor window that corresponds to the node that was clicked on.

Sometimes syntax error guides in the text editor window persist after the syntax is corrected and do not go away until the next change to the source.

It occurs to me that while locking the assembly for the console app isn't a big deal, it certainly is for the GrunWin tool, which presumably a developer will have open and running while they are making changes to their grammar, recompiling and re-testing. Given this, the assembly loading logic needs to use an AppDomain so that it can be dumped and reloaded on demand.

Integrate a custom version of the Microsoft automated graph layout library to support new features.

I would like to create a vsix installer to make installation of Grun.Net and usage within Visual Studio as simple as possible. Unfortunately, this is outside my area of expertise so I shall hope for assistance from the community.

When dragging a small text sample onto the editor window that already contains a larger sample, causes syntax highlighting to explode.

The editor should support intuitive selection of token colors and add syntax highlighting to any grammar by default. The default colors may or may not make some folks happy. To address this, the editor should support dynamic loading of any IEditorGuide instances in the target assembly or any other assemblies in the same folder or in a "Guides" folder within the GrunWin directory itself. GrunWin will attempt to find an IEditorGuide that matches the current grammar and use it in place of the default intuitive highlighting behavior.

Create a windows installer for the tools to make installation simple.

Clean up any remaining dirty code and add any missing documentation blocks to the code.

Button is not properly anchored, so it moves position if the window is expanded.

I thought it wold be cool to give users the option to apply syntax highlighting in the console as well.

Enough said.

All tokens in code related to parser errors should be getting underlined to highlight them. This does not seem to be working now.

Add click support so that the user may click on any token line and select the text in the code editor window that corresponds to the token that was clicked on.

Add support so that the user may select source text and then cause GrunWin to select the related token or parser rule in the graph.

Add a menu strip with items for loading new grammars, exiting the app and toggling various parse options.

Add the ability for the user to fully customize the colors used in heuristic syntax highlighting as well as the graph window. This should help make the tool as friendly to color blind users as well as those who just don't like the default colors.

Apparently I changed the name of the type field and forgot to change the column binding in the list. This will be fixed shortly.

The graph should clear when a lexer only grammar loads.

With a large enough sample of code the constant rebuilding of the parse tree graph can slow the editor down. While this sin't unexpected under the current design, it is something that should be fixed before a full release. It will simply take some basic threading magic.

While working with a grammar of my own I tried a sample code that resulted in just shy of 18,000 graph nodes and noticed that the Microsoft's graph viewer locks up the UI while trying to paint so many. So, given that 18K nodes isn't useful anyway, nor is even 1,000, I'm going to add a maxNodeRender setting in the configuration. The default will start at 500. The tree view portion will still render so you can simply click the subset of the tree you wish to graph as normal and get something more usable that also doesn't spike your CPU and lock up the UI for 10 seconds. I should have a release with this soon.

Currently the tools will not handle a grammar that is missing a parser. This should be fixed.

Add ability to select the token from the token window that corresponds to the current cursor position in the code editor window.

Add a Trace tab to the GrunWin tool to display trace results.