The first programming project involves writing a program that parses, using recursive descent, a GUI definition language defined in an input file and generates the GUI that it defines, using a supplied lexical analyzer. The grammar for this language is defined below:
gui ::= Window STRING '(' NUMBER ',' NUMBER ')' layout widgetsEnd '.'layout ::= Layout layout_type ':'layout_type ::= Flow | Grid '(' NUMBER ',' NUMBER[',' NUMBER ',' NUMBER] ')'widgets ::= widget widgets | widgetwidget ::= Button STRING ';'| Group radio_buttons End ';' | Label STRING ';' | Panel layout widgets End ';' | Textfield NUMBER ';'radio_buttons ::= radio_button radio_buttons | radio_buttonradio_button ::= Radio STRING ';'
In the above grammar, the red symbols are nonterminals, the blue symbols are tokens and the black punctuation symbols are BNF metasymbols. Among the tokens those in title case are keywords. The character literals are punctuation tokens.
Below is an explanation of the meaning of some of the symbols in the above productions that should help you understand the actions that are to be performed when each of the productions is parsed:
- In the window production the string is name that is to appear in the top border of the window and the two numbers are the width and height of the window
- In the production for layout_type that define the grid layout, the first two numbers represent the number of rows and columns, and the optional next two the horizontal and vertical gaps
- In the production for widget that defines a button, the string is the name of the button
- In the production for widget that defines a label, the string is text that is to be placed in the label
- In the production for widget that defines a text field, the number is the width of the text field
- In the production for radio_button, the string is the label of the button
Your parser should properly handle the fact that panels can be nested in other panels. Recursive productions must be implemented using recursion. Syntactically incorrect input files should detect and report the first error.
Below is an example of an input file:
Window "Calculator" (200, 200) Layout Flow: Textfield 20; Panel Layout Grid(4, 3, 5, 5): Button "7"; Button "8"; Button "9"; Button "4"; Button "5"; Button "6"; Button "1"; Button "2"; Button "3"; Label ""; Button "0"; End; End.
The above input file should produce the GUI shown below:
Source Code Skeleton for Project 1
Sample Input Files
.zip file contains two classes, one that defines a lexical analyzer and a second that defines a syntax error. In addition, a third file that contains an enumerated type for the tokens is included. You should use this code when developing the first project.
Please post an example of valid input to this program in the "Ask the Professor" discussion area. I will check whether it conforms to the syntax defined by the grammar, and if it it does, show you what the corresponding output should look like.
Project Submission Instructions
You are to submit two files.
- The first is a .zip file that contains all the source code for the project, which includes any code that was provided. The .zip file should contain only source code and nothing else, which means only the .java files. If you elect to use a package the .java files should be in a folder whose name is the package name.
- The second is a Word document (PDF or RTF is also acceptable) that contains the documentation for the project, which should include the following:
- A brief description of your approach to the design
- A UML class diagram that includes all classes including any that were supplied . Do not include predefined classes. You need only include the class name for each individual class, not the variables or methods
- A test plan that includes test cases that you have created indicating what aspects of the program each one is testing
- A short paragraph on lessons learned from the project