What to do with same-name buttons with state. Supply "ignore name" functionality.

Check for/ensure robustness during load and store.

Supply some way for the editor, when it tells Embeddedbuttons it exists, to specify the version number for its editor-specific string. What to do about documents....

Generation of events for refresh clustering .

Needs a careful description of what is expected from a button class. Should this be part of EmbeddedButtons or its documentation?

Pop-up enumerated-type buttons. Menus with doc. strings?

Create a real-valued button class. Functionality?

Feedback handlers. How closely related are they to button classes? Should they be kept apart? Implemented with button classes?

The df file needs to be cleaned up. What files do we really need?

Check on and formalize when documents have been edited.

Ensure robustness during load and save: No errors in parse or unparse.

Allow specification of no-name buttons.

Write ButtonLs

Write Phonelist

Write Squuncher

"Send this event to Tioga in the viewer with the current input focus"

"Move the input focus to the viewer containing this button and send this event to Tioga"

"Send this event to Tioga in this viewer, but don't move the current input focus."

Should those be the same application? Should they also be a feedback handler?

How about the same few applications for Gargoyle

Buttonizer++. Should people have to know that properties exist or how things are implemented to create buttons? What about a buttonizer form which takes text from the form and puts it in the right place?

The DF file should make it very clear what the various applications are, and what everything uses and what's available and how to use it all. ButtonApplicationsDoc.tioga?

EBTechReport.tioga -- a discussion of the issues raised by this project, some answers and justification to these issues, and a brief description of our implementation of those answers.

EmbeddedButtons -- The Design. It would be nice if there was a short document explaining how everything fits together. Perhaps this could be included with the exported interfaces. Some discussion should be given to repositories of common functionality. These repositories only have implementations

EmbeddedButtonsDoc.tioga -- a users guide to be released with EmbeddedButtons. Let's put this one off for a while.

ButtonApplicationsDoc.tioga?

ActiveButtonsDoc.tioga?

Inbutton should work

click and drag should pass events to EB. Finite state machine?

Feedback should not cause document to become edited.

Button should be able to work without requiring a selection.

Inbutton should work

click and drag should pass events to EB. Finite state machine?

Feedback should not cause document to become edited.