tunnelvisionlabs / antlrworks2 Goto Github PK

fraschfn created an issue 2013-07-30

When clicking on the "1 update found message" AntlrWorks2 says "Everything is uptodate".

I then investigated the plugin settings. There was one update posted and I tried to update from this page.

Unable to connect to the ANTLRWorks 2.1 because of 
http://tunnelvisionlabs.com/downloads/nbupdates/aw21/updates.xml

The address AntlrWorks is looking for updates produces an 404 error:

http://tunnelvisionlabs.com/downloads/nbupdates/aw21/updates.xml

Press Enter between the + and = characters of the += operator.

someRule
    : label+='x'*
    ;

When using named channels the IDE issues warning 155 (unrecognized constant value) although the constant is defined. This prevents the associated parser to run the testrig. The parser/lexer works fine when using VS (I drop the "final" for C#).

lexer grammar NamedChannelsLexer;


@members
{
        public static final int COMMENT_CHANNEL = 3;
}

Abc : 'ABC';

AnyThingElse : . -> channel(COMMENT_CHANNEL); 

Implement a rename capability, along the lines of refactor/rename in many IDEs for Java, etc.

From initial email: Refactor->Rename: A renaming refactor operation would be wonderful - I never get the names for things right at the start and being able to correct my poor naming in a single, simple operation would be so nice.

If I have an as in the case below, it displays an error for every Token (e.g. Times, Divide, Mod) "Missing Rule Definition".

If I put it instead at a position right of "Power" (i.e. the position where it had to be put in previous versions) , it simply displays the warning that the should be put at the start but does not display errors for following tokens.

yshavit created an issue 16 hours ago

The syntax diagram in AntlrWorks is a bit at odds with what I understand are best practices regarding string literal tokens; it'd be nice to make the diagram more friendly to these best practices.

AntlrWorks highlights string literals in parser rules as warnings, and it seems that's for good reason. But if you define explicit tokens, the syntax diagram becomes less descriptive.

Take this rule, for instance:

methodArgs: '(' ')'
          | '(' arg (',' arg)* ')'
          ;

This has has a nice, very obvious syntax diagram:

If we want the warnings to go away, we turn replace '(' with OPEN_PAREN and so on. But now the syntax diagram is much less descriptive:

It would be nice if the syntax diagram "inlined" tokens whose definitions are just string literals (no alternatives, sets, etc), so that a grammar written with OPEN_PAREN et al. would show up as in the first image.

Anonymous created an issue 2013-10-24

The plugin Editor Settings Storage is requested in implementation version 201302132200

The plugin Editor Options is requested in implementation version 201302132200

So there has probably been some changes in NetBeans 7.4 Options and Settings Storage modules that are not compatible with this plugin...

From initial email: Automatic implied token definition insertion: For where you correctly spotted I've implied a token definition, it would be cool if you could go and insert the implied declaration at the "right place" in my source file (give me an action to acknowledge the warning generated and remove the cause for the warning). Pinning down "right place" will require a bit of elegance. It needs to correctly reflect the implied position viz parser and lexer rules. If the first lexer token declaration is one of a bunch (a consecutive sequence with no blank lines between them) then insert in the best-guess alphabetically sorted position (if you've got a poorly maintained sequence that started as sorted, then inserting just before the first element that is alphabetically after the insertion candidate feels a good heuristic).

In ANTLRWorks2.1, plugin settings: There is this path: http://tunnelvisionlabs.com/downloads/nbupdates/aw21/updates.xml

But the path leads nowhere, that can't be right.

Regards Klaus

Hi. If you download the latest recommended updates from NetBeans (having already installed ANTLRWorks2), the module becomes unusable after restarting the IDE.

It looks like ANTLRWorks expects an OLDER version of the 'Editor Settings' module.
Isn't this a trivial fix?
I would love to provide a merge request myself, but I can't even build the module due to #31

The plugin does not install on netbeans 7.4. Can we have an update version? NetBeans 8 is coming out soon too, so there will need to be a couple updates!

I'm using ANTLRWorks 2.1 for grammar creation and subsequent creation of the lexer and parser. I did that for Java target, but my preffered language is python. In this address you can find Python 3 runtime libraries for ANTLR 4 :https://github.com/antlr. I'm quite puzzled by this: how can I specify my target language in ANTLRWorks 2.1? I would be really appriciate if anyone can guid me.

The following calculations are currently incorrect

• Avg k (SLL)
• Min k (SLL)
• Max k (SLL)
• Avg k (LL)
• Min k (LL)
• Max k (LL)

The Parser Interpreter should be able to open a graph of the ATN with a decision highlighted, so it's clear what decision the Parser control window is referencing.

Hi, it looks like there are some ant build problems with the code from master. In particular, the tasks under org-antlr-works-editor fail. The first failure is related to the grammar compilation:

antlr4:
     [echo] Generating ANTLR 4 grammars:
     [echo]   org/antlr/works/editor/grammar/experimental/GrammarLexer.g4
     [echo]   org/antlr/works/editor/grammar/experimental/GrammarParser.g4
     [echo]   org/antlr/works/editor/grammar/highlighter/GrammarHighlighterLexer.g4
     [echo]   org/antlr/works/editor/st4/experimental/TemplateLexer.g4
     [echo]   org/antlr/works/editor/st4/experimental/TemplateParser.g4
     [echo]   org/antlr/works/editor/st4/highlighter/GroupHighlighterLexer.g4
     [java] error(7):  cannot find or open file: *.g4

I started patching the org-antlr-works-editor build.xml to fix the grammar compilation, but the grammar files look like they are using a new 'abstract' option that isn't available in the compiled antlr4 jars that are retrieved by ant. So I stopped there, realizing I'm probably missing some pieces of the build process.

Let me know if I can provide any other useful info on my end.

Javad Chamanara created an issue 2013-09-29

Seems there is no plugin for the ANTLRWorks 2.1 available. Would you please update the netbean's plugin center so that NB plugin manager can detect and install it.

For at least one file a NullPointerException is thrown when trying to do Interpret parser...

java.lang.NullPointerException
    at org.antlr.v4.runtime.DiagnosticErrorListener.getConflictingAlts(DiagnosticErrorListener.java:175)
    at org.antlr.works.editor.grammar.debugger.StatisticsParserErrorListener.reportAmbiguity(StatisticsParserErrorListener.java:30)
    at org.antlr.v4.runtime.ProxyParserErrorListener.reportAmbiguity(ProxyParserErrorListener.java:55)
    at org.antlr.v4.runtime.atn.ParserATNSimulator.reportAmbiguity(ParserATNSimulator.java:2365)
    at org.antlr.v4.runtime.atn.ParserATNSimulator.execATN(ParserATNSimulator.java:812)
    at org.antlr.works.editor.grammar.debugger.StatisticsParserATNSimulator.execATN(StatisticsParserATNSimulator.java:144)
    at org.antlr.v4.runtime.atn.ParserATNSimulator.execDFA(ParserATNSimulator.java:556)
    at org.antlr.works.editor.grammar.debugger.StatisticsParserATNSimulator.execDFA(StatisticsParserATNSimulator.java:107)
    at org.antlr.v4.runtime.atn.ParserATNSimulator.adaptivePredict(ParserATNSimulator.java:423)
    at org.antlr.v4.runtime.atn.ParserATNSimulator.adaptivePredict(ParserATNSimulator.java:373)
    at org.antlr.works.editor.grammar.debugger.StatisticsParserATNSimulator.adaptivePredict(StatisticsParserATNSimulator.java:99)
    at org.antlr.v4.runtime.ParserInterpreter.visitState(ParserInterpreter.java:185)
    at org.antlr.works.editor.grammar.debugger.ParserDebuggerReferenceAnchorsParserTask$TracingParserInterpreter.visitState(ParserDebuggerReferenceAnchorsParserTask.java:137)
    at org.antlr.v4.runtime.ParserInterpreter.parse(ParserInterpreter.java:157)
    at org.antlr.works.editor.grammar.debugger.ParserDebuggerReferenceAnchorsParserTask.parse(ParserDebuggerReferenceAnchorsParserTask.java:115)
    at org.antlr.netbeans.parsing.spi.impl.ParserTaskManagerImpl$UpdateDataCallable.callImpl(ParserTaskManagerImpl.java:662)
    at org.antlr.netbeans.parsing.spi.impl.ParserTaskManagerImpl$UpdateDataCallable.callImpl(ParserTaskManagerImpl.java:618)
[catch] at org.antlr.netbeans.parsing.spi.impl.ParserTaskManagerImpl$UpdateCallable.call(ParserTaskManagerImpl.java:607)
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
    at org.antlr.netbeans.parsing.spi.impl.ParserTaskManagerImpl$PriorityInsertionRunnableScheduledFuture.run(ParserTaskManagerImpl.java:821)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:744)

Press Enter anywhere between int and the ] character.

someRule returns [int x = 3, String y = "foo"]
    : 'x'
    ;

Press Enter before or after the = character.

options {
    tokenVocab = Vocab;
}

If the parser interpreter does not consume all tokens in the file, the tokens which are not part of the parse tree should be clearly marked in the editor window.

Dmitry Maslennikov created an issue 2013-10-13

When will be support plugin for Netbeans 7.3.1 and older

Anonymous created an issue 2013-12-11

After downloading and unzipping 2.1 version (http://tunnelvisionlabs.com/downloads/antlr/2013-07-21-antlrworks-2.1.zip) I try to run it.

In response I get the following waring: Warning - could not install some modules: org.apache.commons.io - org.netbeans.InvalidException: Netigso: D:\playground\2013-07-21-antlrworks-2.1\antlrworks2\ide\modules\org-apache-commons-io.jar: Not found bundle:org.apache.commons.io

I choose the option "diable modules and continue". The application quits.

I use the following version of Java: C:\Users\karolbr>java -version java version "1.7.0_25" Java(TM) SE Runtime Environment (build 1.7.0_25-b17) Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)

I know my operating system is flawed (by definition), but is there any way to run the app?

I have a project (antlr-denter) that provides a helper class to be used in the lexer/parser that antlr generates. It works fine for the actual project, but antlrworks2 can't run the test rig on it, because it can't compile the generated lexer/parser classes:

/tmp/TestRigTask-1395122781850/EffesLexer.java:3: error: package com.yuvalshavit.antlr4 does not exist
import com.yuvalshavit.antlr4.DenterHelper;
^
/tmp/TestRigTask-1395122781850/EffesLexer.java:4: error: package com.yuvalshavit.antlr4 does not exist
import com.yuvalshavit.antlr4.DenterOptions;
etc....

My project is maven'ized, meaning it comes as a convenient jar. If I symlink this jar into antlrworks2/platform/lib (on Linux), the java.class.path property includes the jar. But the TestRigTask still can't find it during compilation.

Digging into the code a bit, it looks like TestRigTask sets the classpath explicitly, and CodeGenerator doesn't look at any system properties (CLASSPATH, etc) when building its classpath.

Do I have any options that don't require code changes? And if a code change is required, would you be amenable to it? Maybe a system property that TestRigTask looks for?

Anonymous created an issue 2013-03-14

Hi. I hadn't heard of antlrworks until ten minutes ago.

Now, those ten minutes have passed, and I still don't know under which license antlrworks is released. I consider this a bug.

I'm sure sometime in the next ten minutes, I'll find the information that I'm looking for, but I figured that you'd appreciate knowing that folks do care about this kind of thing.

If antlrworks wasn't so highly recommended, I would have already moved on.

Cheers, --Dave

When the following grammar is opened, the navigator window fails to display lexer rules.

grammar Ns3mod;

dialog_source
    : DIALOG_SOURCE_DEFINITION dialog_info dialog_data?
      dialog_subroutine*
    ;

dialog_info:
    DEFINE_DIALOG_INFO
    (FULL_COMMENT1|FULL_COMMENT2)*
    EMPTY_DIALOG_COMMENT?
    END_DIALOG_INFO;

statement_list: statement*;

dialog_data: dialog_data_params DEFINE_LOCAL_DATA LOCAL_DATA
    dialog_data_handles dialog_data_using END_LOCAL_DATA? END_DEFINE?;

dialog_data_params:
    DEFINE_DATA
    DEFINE_DIALOG_PARAMETERS
    PARAMETER_BEGIN
    PARAM_GUI_HANDLE+
    statement_list
    DEFINE_USING_BEGIN
    DEFINE_USING_END
    END_DIALOG_PARAMETERS;

dialog_data_handles:
    DEFINE_HANDLES_BEGIN
    HANDLE_DEFINITION*
    DEFINE_HANDLES_END;

dialog_data_using:
    statement_list
    DEFINE_USING_BEGIN
    LOCAL_USING+
    DEFINE_USING_END;

dialog_subroutine
    : dialog_subroutine_control
    | dialog_subroutine_elements
    | dialog_subroutine_event
    ;

dialog_subroutine_control
    : DEFINE_SUBROUTINE_CONTROL process_gui_action_add END_SUBROUTINE_CONTROL;

dialog_subroutine_elements
    : DEFINE_SUBROUTINE_DIALOG_ELEMENTS define_control* END_SUBROUTINE_DIALOG_ELEMENTS;

dialog_subroutine_event
    : DEFINE_SUBROUTINE_EVENT_DEFAULT option* END_SUBROUTINE_EVENT_DEFAULT event*
      statement_list;

process_gui_action_add:
    PROCESS_GUI_ACTION_ADD
    PARAMETERS_BEGIN
    parameter_definition
    (PARAMETERS_END|PARAMETERS_END_GIVING_ERROR);

parameter_definition
    : PARAM_ASSIGNMENT*;

statement
    : EMPTY_USER_CODE_SECTION
    | PERFORM_STATEMENT
    | PROCESS_GUI_ACTION_AFTER_CREATION
    | PROCESS_GUI_ACTION_AFTER_CREATION_GIVING_ERROR
    | PROCESS_GUI_ACTION_RESET_ATTRIBUTES
    | PROCESS_GUI_ACTION_RESET_ATTRIBUTES_GIVING_ERROR
    | decide_statement;

define_control
    : DEFINE_CONTROL process_gui_action_add END_CONTROL;

option
    : OPTION_SPEC statement_list;

event
    : DEFINE_EVENT option* END_EVENT;

decide_statement
    : DECIDE_ON_FIRST (DEFINE_EVENTS_FOR|DEFINE_EVENT)? value*;

value
    : VALUE option* statement_list;      

// Lexer rules

DECIDE_ON_FIRST: INT WS* 'DECIDE' WS+ 'ON' WS+ 'FIRST' WS+ VARNAME
                 (WS+ CI0 WS+ 'DEFINE' WS+ 'ALL' WS+ 'EVENTS')? NL;
DEFINE_CONTROL: INT WS* CI1 WS+ 'DEFINE' WS+ 'CONTROL' WS+ VARNAME NL;
DEFINE_DATA: INT WS* 'DEFINE' WS+ 'DATA' NL;
DEFINE_EVENT: INT WS* CI1 WS+ 'DEFINE' WS+ 'EVENT' WS+ VARNAME NL;
DEFINE_EVENTS_FOR: INT WS* CI1 WS+ 'DEFINE' WS+ 'EVENTS' WS+ 'FOR' WS+ 'DIALOG' NL;
DEFINE_DIALOG_INFO: INT WS* CI1 WS+ 'DEFINE' WS+ 'DIALOG' WS+ 'INFO' NL;
DEFINE_DIALOG_PARAMETERS
    :INT WS* CI1 WS+ 'DEFINE' WS+ 'DIALOG' WS+ 'PARAMETERS' NL;
DEFINE_LOCAL_DATA: INT WS* CI1 WS+ 'DEFINE' WS+ 'LOCAL' WS+ 'DATA' NL;
DEFINE_HANDLES_BEGIN: INT WS* CI1 WS+ 'DEFINE' WS+ 'HANDLES' NL;
DEFINE_HANDLES_END: INT WS* CI4 WS+ 'END-HANDLES' NL;
DEFINE_SUBROUTINE: INT WS* 'DEFINE' WS+ 'SUBROUTINE' WS+ VARNAME NL;
DEFINE_SUBROUTINE_CONTROL
    :INT WS* 'DEFINE' WS+ 'SUBROUTINE' WS+ VARNAME WS+ CI0
     WS+ 'DEFINE' WS+ 'CONTROL' WS+ VARNAME NL;
DEFINE_SUBROUTINE_DIALOG_ELEMENTS
    :INT WS* 'DEFINE' WS+ 'SUBROUTINE' WS+ VARNAME WS+ CI0
     WS+ 'DEFINE' WS+ 'DIALOG' WS+ 'ELEMENTS' NL;
DEFINE_SUBROUTINE_EVENT_DEFAULT
    :INT WS* 'DEFINE' WS+ 'SUBROUTINE' WS+ VARNAME WS+ CI0
     WS+ 'DEFINE' WS+ 'EVENT' WS+ 'DEFAULT' NL;
DEFINE_USING_BEGIN: INT WS* CI1 WS+ 'DEFINE' WS+ 'USING' NL;
DEFINE_USING_END: INT WS* CI4 WS+ 'END-USING' NL;
DIALOG_SOURCE_DEFINITION: INT WS* CI0 WS+ 'DIALOG' WS+ 'SOURCE' WS+ '22D' NL;
EMPTY_DIALOG_COMMENT: INT WS* CI0 WS+ 'EMPTY' WS+ 'DIALOG' WS+ 'COMMENT' NL;
EMPTY_USER_CODE_SECTION: INT WS* (';')? CI0 WS+ 'EMPTY' WS+ 'USER' WS+ 'CODE' WS+ 'SECTION' NL;
END_CONTROL: INT WS* CI4 WS+ 'END-CONTROL' NL;
END_DEFINE: INT WS* 'END-DEFINE' NL;
END_DIALOG_INFO: INT WS* CI4 WS+ 'END-DIALOG-INFO' NL;
END_DIALOG_PARAMETERS: INT WS* CI4 WS+ 'END-DIALOG-PARAMETERS' NL;
END_EVENT: INT WS* CI4 WS+ 'END-EVENT' NL;
END_LOCAL_DATA: INT WS* CI4 WS+ 'END-LOCAL-DATA' NL;
END_SUBROUTINE: INT WS* 'END-SUBROUTINE' NL;
END_SUBROUTINE_CONTROL: INT WS* 'END-SUBROUTINE' WS+ CI0 WS+ 'END-CONTROL' NL;
END_SUBROUTINE_DIALOG_ELEMENTS: INT WS* 'END-SUBROUTINE' WS+ CI0 WS+ 'END-DIALOG-ELEMENTS' NL;
END_SUBROUTINE_EVENT_DEFAULT: INT WS* 'END-SUBROUTINE' WS+ CI0 WS+ 'END-EVENT' NL;
FULL_COMMENT1: INT CI2 ~[\r\n]* NL;
FULL_COMMENT2: INT CI0 ~[\r\n]* NL;
HANDLE_DEFINITION: INT WS* INT WS+ VARNAME WS+ 'HANDLE' WS+ 'OF' WS+ HANDLE_TYPE NL;
LOCAL_DATA: INT WS* 'LOCAL' NL;
LOCAL_USING: INT WS* 'LOCAL' WS+ 'USING' WS+ VARNAME NL;
OPTION_SPEC: INT WS* 'OPTIONS' WS+ INT (WS+ ('DEFAULT'|VARNAME))? NL;
PARAM_ASSIGNMENT: INT WS* VARNAME WS+ '=' WS+ '*'? PARAM_VALUE NL;
PARAMETER_BEGIN: INT WS* 'PARAMETER' NL;
PARAMETERS_BEGIN: INT WS* 'PARAMETERS' NL;
PARAMETERS_END: INT WS* 'END-PARAMETERS' NL;
PARAMETERS_END_GIVING_ERROR: INT WS* 'END-PARAMETERS' WS+ 'GIVING' WS+ '*ERROR' NL;
PERFORM_STATEMENT: INT WS* 'PERFORM' WS+ VARNAME NL;
PARAM_GUI_HANDLE: INT WS+ INT WS+ VARNAME WS+ 'HANDLE' WS+ 'OF' WS+ 'GUI' WS+ 'BY' WS+ 'VALUE' NL;
PROCESS_GUI_ACTION_ADD: INT WS* 'PROCESS' WS+ 'GUI' WS+ 'ACTION' WS+ 'ADD' WS+ 'WITH' NL;
PROCESS_GUI_ACTION_AFTER_CREATION: INT WS* 'PROCESS' WS+ 'GUI' WS+ 'ACTION' WS+
   'AFTER-CREATION' WS+ 'WITH' VARNAME NL;
PROCESS_GUI_ACTION_AFTER_CREATION_GIVING_ERROR: INT WS* 'PROCESS' WS+ 'GUI' WS+ 'ACTION' WS+
   'AFTER-CREATION' WS+ 'WITH' VARNAME WS+ 'GIVING' WS+ '*ERROR' NL;
PROCESS_GUI_ACTION_RESET_ATTRIBUTES: INT WS* 'PROCESS' WS+ 'GUI' WS+ 'ACTION' WS+
   'RESET-ATTRIBUTES' WS+ NL;
PROCESS_GUI_ACTION_RESET_ATTRIBUTES_GIVING_ERROR: INT WS* 'PROCESS' WS+ 'GUI' WS+ 'ACTION' WS+
   'RESET-ATTRIBUTES' WS+ 'GIVING' WS+ '*ERROR' NL;
VALUE: INT WS* 'VALUE' WS+ (STRING|'NULL-HANDLE') NL;


// Comment introducers

CI0: '/**';
CI1: '/*[';
CI2: '**D*';
CI3: '/**';
CI4: '/*]';

VARNAME: [#\*A-Za-z]+[a-zA-Z0-9\-$]*;
HANDLE_TYPE: 'WINDOW'|'INPUTFIELD'|'LISTBOX'|'PUSHBUTTON'|'BITMAP'|'LISTBOX'
             |'RADIOBUTTON'|'TEXTCONSTANT'|'TOGGLEBUTTON'|'SELECTIONBOX';
PARAM_VALUE: INT|BOOL|STRING|VARNAME;

// Line formatting stuff
INT: [0-9]+;
STRING: [\']~[\']*[\'];
BOOL: ('FALSE'|'TRUE');
NL: WS* [\r]? [\n];

// White space handling

WS: [ \t\f] -> skip;

Hello,
I'm using antlrworks2 version 2.1.
When I try to run testrig on any grammar file and input file, I get the following exception in the notification window, and from there I cannot recover:

java.lang.NullPointerException
    at org.antlr.works.editor.grammar.actions.RunInTestRigAction$TestRigTask.run(RunInTestRigAction.java:295)
    at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1432)
[catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2042)

Attached is the grammar and input file I'm using, please note it happens all the time for any file.
--> change the file extension to .txt

--> change the file extension to .g

Appreciate any help.
Busi

Unterminated string literals appear to extend beyond the end of the current line. This behavior leads to obnoxious behavior in the syntax window (when it's visible while typing).

Press Enter after the type(Foo) command.

SomeRule
    : 'x' -> type(Foo)
    ;

fraschfn created an issue 2013-07-26

Maybe this could also be optionally done in the background and display the total number of errors somewhere.

This would be like a kind of "unit testing" for grammars and ease the finding of errors.

Anonymous created an issue 2013-10-07

I cannot click the finish button in "Run in TestRig" dialog because the button became grey and thus not clickable.

other features work normally. don't know what exactly happened.

Arthur Schwarz created an issue 2013-10-19

Same as issue #8 & #9

Open Containing Folder requires JNI. No information on how to install JNI into netbeans for use. I am attempting to research this.

Please update Release document to reflect how to install JNI.
thanks art

Anonymous created an issue 2013-05-22

A nice feature to add to the tool would be the ability to export the syntax diagrams to a file or files. Ideally formatting/layout of the diagrams could be controlled so that a nice report could be generated for the purposes of documenting the syntax to other team members who are not able to read grammar and lexer rules as a matter of course (say a test team member).

• Number of tokens consumed
• Number of rule contexts created
• Number of syntax errors reported

The Parse Tree navigator view for the parser debugger could include a Go to Match Transition command in the context menu for TerminalNode nodes, and a Go to Rule Reference command in the context menu for RuleNode nodes.

fraschfn created an issue 2013-07-17

I'd find it useful if there would be a possibility to clear the log just before running the test rig.

Maybe also a way to suppress the following warnings:

Compiling grammar files...
warning: Supported source version 'RELEASE_6' from annotation processor 'org.netbeans.modules.openide.modules.PatchedPublicProcessor' less than -source '1.7'
warning: Supported source version 'RELEASE_6' from annotation processor 'org.netbeans.modules.openide.util.ServiceProviderProcessor' less than -source '1.7'
warning: Supported source version 'RELEASE_6' from annotation processor 'org.netbeans.modules.openide.util.NamedServiceProcessor' less than -source '1.7'
warning: Supported source version 'RELEASE_6' from annotation processor 'org.netbeans.modules.openide.util.NbBundleProcessor' less than -source '1.7'
4 warnings

Would also be nice to start the test rig "over again" without the window to configure the test rig opening.

Hello

First I would thank you guys at TunnelVision for the great work.

Unfotunaltely the plugin seems to be incomaptible with NetBeans 8.0.2. Trying to install it, I'm receiving the following error message:

Some plugins require plugin Editor Settings Storage to be installed.
The plugin Editor Settings Storage is requested in implementation version 201408251540. The following plugin is affected:       ANTLRWorks Editor
Some plugins require plugin Editor Options to be installed.
The plugin Editor Options is requested in implementation version 201408251540. The following plugin is affected:       ANTLRWorks Editor

My NetBeans installation:

Product Version: NetBeans IDE 8.0.2 (Build 201411181905)
Updates: NetBeans IDE is updated to version NetBeans 8.0.2 Patch 2
Java: 1.8.0_31; Java HotSpot(TM) 64-Bit Server VM 25.31-b07
Runtime: Java(TM) SE Runtime Environment 1.8.0_31-b13
System: Linux version 3.16.7-21-desktop running on amd64; UTF-8; de_DE (nb)

It would be nice, if you'll find the time to look into this.

Thank you very much!

Best regards

Alex

Anonymous created an issue 2013-08-20

As noted by other users too, my instance of ANTLRWorks 2 in combination with NetBeans 7.3 will only show an empty Syntax Diagram pane. I do get some functionality, the navigator 'rules' pane correctly shows my grammar. The grammar also succesfully compiles with ANTLR. A similar problem (empty window) seems to exist with the Lexer Debugger Control Window, but that might be caused by my misunderstanding of its use.

(Unfortunately, the fallback solution of the standalone tools fails for me too, because of the known issue of the invalid .exe on Windows XP)

Press Enter after the ;.

lexer grammar TestLexer;

Anonymous created an issue 2013-06-24

Hi,

When I try to install the ANTLRWorks2 plugin on NetBeans 7.3 (Build 201306052037) I receive the following errors:

Product Version: NetBeans IDE 7.3 (Build 201306052037) Java: 1.7.0_21; OpenJDK 64-Bit Server VM 23.7-b01 Runtime: OpenJDK Runtime Environment 1.7.0_21-b02 System: Linux version 3.5.7-gentoo running on amd64; UTF-8; en_GB (nb) User directory: /home/max/.netbeans/7.3 Cache directory: /home/max/.cache/netbeans/7.3

Some plugins require plugin Editor Settings Storage to be installed. The plugin Editor Settings Storage is requested in implementation version 201302132200. The following plugin is affected: ANTLRWorks Editor

Some plugins require plugin Editor Options to be installed. The plugin Editor Options is requested in implementation version 201302132200. The following plugin is affected: ANTLRWorks Editor

Please also note that the version of the plugin is 2.0.0.1, not 2.0.1 as is the only option in the "version box".

Thank you for your assistance.

Press Enter after the { character.

@members {
}

josephredfern created an issue 2013-07-18

It might be nice to be able to run the test rig with input from a text area, rather than having to choose a separate file.

i.e. The dialog box presented when going Run->Run in TestRig would give the option for the use to enter their input directly.

Provide support for the traditional Ctrl-/ action to comment/uncomment a block of lines.

Currently it's unclear when a rule context in the Navigator has a syntax error.