fge / grappa-debugger Goto Github PK

Even with small grammars the parse tree can become quite large (and hard to browse). Debugging could get easier when one had the possibility to filter some nodes so not all are displayed.

Examples for filter:

• Only nodes with name(s)
• All but nodes with name(s)
• Only actions / No actions
• Only SUCCESS / FAILURE (this would probably only be useful if combined with another filter, like: no successful actions)

It would be useful to see the current version of the debugger from a running instance. For example when you removed the version number from the jar file name so you don't have to update your links on next version.

Place for the info could be the title bar "Grappa debugger () " or an about-dialog or something like that.

With large parse trees it is quite laborious to navigate to a specific node that finally caused the run to fail or the last successful rule just before the fail.

A "jump to" or "navigate to" feature could be helpful. It might accept filter criteria like in #1 and a selector "first" or "last" or "mark all".

Finding the last successful rule could then be something like: navigate to "last, not type action, not rule whitespace, state success"