There are a number of components that need a UI for specifying links to other objects, e.g.:
- Concept maps and other SharedDrawing-based tools support linking of URLs or objects to figures
- Zoomable maps support linking of objects to spots
- Text objects support linking and embedding other objects
A unified UI for these could have the following elements:
- A field for the (local) name of the link
- A widget for selecting the link. This could include:
- An option for "none"
- An option for choosing a link to an existing object. Initially this could just be a text field, though a more user-friendly widget should eventually be added. A tree-based widget would probably be the simplest approach, but a multi-column selector might be better. (We should see if anybody has looked into usability implications of these in NeXT or OSX.)
- An option for creating a new object. This would require configuration of a set of templates and a destination directory.
- An option for entering a URL
- A field for description or other app-specific extras
|