Le 30 mai 05 à 15:17, Jesse Ross a écrit :
Since circular menus are best for things where you know the number
of items, and know that there will be not many items. Vertical
menus are best for when you have lots of items and need
flexibility. Since the number of menu items operating on containers
are few, I would suggest that circular menus are the primary method
of menu interaction with containers. Since we don't know how many
installed Components a user might have, vertical menus make the
most sense for interacting with Objects.
I'm not completely convainced by circular menus -- sure they are
interesting, but they seem to me to be to limited to be used system-
wide; and in that case, I would prefer to NOT have two different
menus at the same time !
I visualize Annotations as the scribbles you make over a Project to
comment on it or show the relationships between items. I see this
almost like a Shelf, that can be turned on or off. Maybe I'm wrong
in that assumption?
Annotations the way I understand it are metadatas about something.
They can be more than just text too.
Projects are Folders that when activated/opened expand to the
entire width and height of the screen. Thus, you can only view one
project at a time. When it fills the whole screen, the Project can
be annotated -- marked up with drawings and text which act as
metadata.
not exactly ... projects aren't folders that expand to the whole
screen; their nature is not that. Projects are there to render a
project persistant, eg, to save its state -- which applications/
components are running, where, etc. They are also there to provide a
reification of the project concepts, and to handles metadata about
them. The interaction model proposed is indeed to zoom into a
project, and indeed, a project will likely be contained in a folder
at the filesystem level. But saying Projects are Folders is a bit too
unprecise I think.
Remember, I recommend that we have Zoom In and Zoom Out keys too.
Maybe we don't even need Zoom In and Zoom Out hotspots. The Zoom In
and Zoom Out keys should do a full jump from Project to Project or
Project to Document. Maybe Shift-Zoom In and Shift-Zoom Out zoom by
a smaller increment... maybe 10% of a regular Zoom In or Zoom Out.
Overall, I'm not much convainced by dozen of special modkeys...
The UI should be useable with a mouse, period. Now, for advanced
user, we could let them bind some functions on keys, but that's
another story..
--
Nicolas Roard
"Any sufficiently advanced technology is indistinguishable from magic."
-Arthur C. Clarke
