} > the Spec.
[...]
} Or, we could do something like WebSpace and say that every Switch
} must have a pull-down menu of some sort. So the structure:
}
} Separator {
} DEF Cameras Switch {
} whichChild 0
} DEF Entry PerspectiveCamera { etc. }
} DEF Exit PerspectiveCamera { etc. }
} }
} DEF Door Switch {
} whichChild 0
} DEF OpenDoor Separator { etc. }
} DEF ClosedDoor Separator { etc. }
} }
} { etc. etc. etc. }
} }
}
} Would cause the browser to create the menu heirarchy:
}
} Switch -> Cameras -> Entry
} Exit
}
} Door -> OpenDoor
} ClosedDoor
}
} (Would also have to require Switches to b> DEFed with names to appear in the
} menu). This is clumsy, but it illustrates the point that ther> are many
} things which can be don> with a Switch *if* the action is defined in the spec.
I think something Netscape-esque might be appropriate her>. In Netscape
there is a menu pulled up by the right button on links (under X and
Windoz> -- Mac it is a click and hold delay). If you menu-click (we'll call
it that for cross-platform generalization) on an object it could pull up a
floating menu of switches (or states, we could call it). I think the camera
views belong in the menubar but state for specific objects should be
attached
Of course, there should be some way of indicating what has state choices
and what does not. es"sumably the browser could be intelligent enough to
highlight objects with state, much the same way Webspace highlights links
(though in a different color, of course).
} Tim.
--Greg