Hi everyone, my name is Ryan. I have been a lurker around here for a while now, but this is my first post here. The reason I am posting is that I have project and I need some help with it. I am currently in an online programming class where we are learning about the differences between languages, and our first 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. The project includes the grammar for the GUI language as well as the lexical analyzer for the project. With what we have learned so far in the class, I do not feel ready for this project and I am looking for some help to get me started. I want to make clear I am NOT looking for the answer to be handed to me, I am just looking for advice on where I should start and any resources that would be helpful. I appreciate any help that can be given. Thanks and have a good day!
I apologize everyone. I let my lack of confidence cause me to panic before actually thinking things through. I am going to give things a try and come back on here if I run into a specific problem. Sorry for wasting everyone's time.
posted 4 years ago
And its fully understandable. - just looking at the term: "parsing a GUI Definition language using recursive descent" gave me the shivers.
Sorry for the delayed reply; I've been super busy. I am close to getting it working, but I am running into some Problems. I am including the grammar for this project:
gui ::= Window STRING '(' NUMBER ',' NUMBER ')' layout widgets End '.'
layout ::=Layout layout_type ':'
layout_type ::= Flow | Grid '(' NUMBER ',' NUMBER [',' NUMBER ',' NUMBER] ')'
widgets ::= widget widgets | widget
Button STRING ';' |
Group radio_buttons End ';' |
Label STRING ';' |
Panel layout widgets End ';' |
Textfield NUMBER ';'
radio_buttons ::= radio_button radio_buttons | radio_button
radio_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
This is the code provided by the professor
And this is the parser I built:
Sorry for the length of the file, I just want to give everyone a feel of what I have and the scope of the project. Right now, one problem I know I am having is that my Parser is not properly handling nested Panels.
Placing the below text into a text file:
Window "Testing" (600, 500) Layout Flow:
Panel Layout Grid(4, 3, 5, 5):
Panel Layout Flow:
Panel Layout Grid(3, 3):
Should produce the following image:
Instead it produces this:
Any suggestions on what might be the source of the problem?
Thanks for the feedback, I was kinda wondering if that might have had something to do with it. The only question I have is how to I handle keeping track in the parser which panel I am adding to? I think that might be the root of the problem.
getWidgets() on line 10 will return false when it encounters END. Maybe leave getWidgets() but remove enclosing if().
I tried to compile your code but there are pieces missing. I'm assuming you omitted them because they were too long.