Main UT OpenCCG page

This project is supported by a grant from UT Austin‘s Liberal Arts Instructional Technology Services.

This page is for internal coordination of the OpenCCG GUI development project.
For more information about the project or to use WebCCG, go here. The WebCCG tutorial is here.

Follow this link for the OpenCCG GUI tutorial.

Jason Baldridge, Principal Investigator
Sudipta Chatterjee, Research Assistant
Alexis Palmer, Research Assistant
Ben Wing, Research Assistant

• When the VisCCG is maximized, and then one clicks on “Lexicon” or whatever, the “File, Edit” etc menu bar goes away. done!
• Line numbers should update automatically
• Status message at each stage of compilation or last event – introduce a label box, maybe?
• Control-C and Control-V for editing
• Validate should say something to the effect that the grammar is valid, if there are no errors. Perhaps an Emacs style message in a line at the bottom? done!
• The new grammar template should leave whitespace between each of the sections, and it should already have stuff like “feature {\n\n}” in those areas.
• It would be preferable for the semantics display to have the nominal variables not be subscripted when in the main body of the logical form. They should only be subcripted when they are an argument to the satisfaction operator @.
• Features don’t display after initial creation. The grammar must be reloaded in order for them to appear in the Features tab. done!
• Changing to new tabs should not resize the window! done!
• When editing the lexicon, using the click-to-edit functionality can get into a wierd state, where it thinks you are editing, so it offers “Done” etc, but then gets confused when you accept one of the options (and you must accept one of the options). Fortunately, things don’t crash, but you must return to the “Edit” tab and then go back to the Lexicon tab. done!
• Clicking done on a category edit that was ill-formed leads to a cut-off of the family listing without any warnings or suggestions. The behavior would ideally be like using the validate button on that category.
• Non alphabetic characters such as apostrophes cause trouble for ccg2xml. They should be usable.

1. research differences between our expansions and parameterized macros, etc. in other systems (Alexis)
2. check in latest version of the system (Sudipta)
3. MMCCG slide and example, clean up CCG examples (do we need all three?) (Jason)
4. add ccg-format example on page showing shorthandy thing (Alexis)
5. find out what the setup will be for the demo and make sure whatever machines we need will be compatible with whatever the setup is (Sudipta)
6. decide on an estimated release date (Sudipta,Jason)
7. add Ojibwe examples (Alexis)
8. add screen shots (Sudipta)
9. general review and modification of slides (Jason, Sudipta, Alexis)
10. coordinate with Ben re: demo session (Sudipta)
11. plan for demo session (Sudipta, Ben)

1. Line numbers on edit
2. Debug mode

Top of page

1. general
   • DONE! Unsaved changes should be warned about — right now it quits directly!
   • DONE! Default template file loads when new file is created
   • rework template document structure
   • alter parsing mechanism to accommodate lexicon{}, morph{}, etc.
2. lexicon
   • DONE! 1st! Right-click pop-up menu editing for the categories
   • BUG-FIX! In the maximized mode, the top tool-bar disappears!
3. features
   • Make a tree-graph
4. testbed
   • Expand canvas
   • DONE! Add a new sentence – popup box
   • Button to test grammar against testbed & return report
5. rules
   • create
6. words/morph
   • check out ccg-grammardoc
7. paper for GEAF workshop
   • set up repository
   • brainstorm
   • goal: extended abstract (4 pages), due Monday, April 9

Top of page

• Graph/tree view for the feature hierarchy
• Right-click or pop-out edits on the Lexicon view
• [maybe] it would be cool if each expansions of subdirectories were maintained through expansion & collapse of parent directory
• help-over function (pre-item comments in source file brought up via editor interface – mouse-over, tool tip)
• collapsible categories in lexicon view
• implement display of morphology/words
• implement display of rules
• snazzy buttons for tabs
• allow split window/creation of multiple panes to view multiple tabs simultaneously
• OR put a spring button in each tab to pop window out (OR both panes and bouncy windows)
• implement grammar-testing capability from within GUI (tccg shell interface)
• use bigger fonts/add option menu for magnifications

• tutorial/walkthrough grammar demo
• create a tutorial/introduction or manual for the code itself
• separate out the code in the ccg.ply and ccg_editor.py files — basic overhaul of the functioning of the entire data

Top of page

1. general
   • DONE!Error handling — incorrect grammar specifications should localise error — error editing to be done in main edit view.
   • Unsaved changes should be warned about — right now it quits directly!
2. lexicon
   • DONE!Fix scrolling in the view
   • DONE!Home, Undo All with option buttons for quick edits
   • DONE!Colored highlight for current edit
3. features
   • DONE!In-place editor to edit feature hierarchy
4. testbed
   • DONE!Bring the number of parses column to the left so that it can be more easily traceable
   • DONE!Remove space from top of the headers
   • DONE!Quick editing in same pane
5. grammar writing
   • finish ojibwe grammar in ccg-format

1. general tasks
   • DONE! Add scroll bars
   • DONE! Edit boxes for individual categories
2. lexicon tab
   • DONE! add images for slashes
   • DONE! make it possible to edit an individual section and have it pop up that section while leaving the rest of the display visible; a number of ideas about this:
     • make it possible to edit individual category/word/feature –> this might bring up entire lexicon (e.g.) but highlight region (either highlight text or use colored cursor or something like that) corresponding to relevant category
     • make it possible for user who wants to edit only lexicon section to see only the relevant portion of the .ccg file (or testbed or whatever)
3. testbed tab
   • DONE! Change font colors for headers
4. grammar writing
   • DONE! Get CCGCookBook SF repository established

1. lexicon tab
   • DONE! retrieve checkbox menu for display (or not) of features
   • DONE! fix alignment for multiple categories & category members (cf. Arabic grammar)
2. features tab
   • DONE! initial view should show entire tree (everything expanded)
   • DONE! add menu (checkbox?) for ‘expand all’
3. testbed tab
   • DONE! remove ‘failure’ column
   • DONE! make ‘# parses’ column small
   • DONE! left-justify sentences (sentences should be the obvious focus of the page

Tasks to complete in preparation for LAITS talk.

1. tabs for testbed, lexicon, features
2. nice tree graph for features
3. get Arabic to compile
4. issues of colors, fonts, etc. (Alexis help)
5. make sure all path, etc. issues are working

1. help with more specific user-interface issues
2. work on specs for view/interface (refer to Grok manual)
3. overall management involving various people
4. update wiki page

1. PNGs of slash modalities
2. TeX/Tk font conversion
3. find a Tkinter package for displaying tree graphs

1. prepare slides/talk

Goals met [Alexis, 02/15/07]

1. Ojibwe grammar (lexemic) into ccg-format
2. demo of visualization component
   • ability to show or not show features using buttons
   • possibly ability to select which features to show
   • better display of modalities
   • improve display of hybrid logic stuff

Goals met [Jason, 02/07/07]

Top of page