Date: Thu, 5 Feb 1998 13:27:09 -0600
From: escargo@anubis.network.com (David S. Cargo)
Message-Id: <199802051927.NAA08599@brutus.network.com>
To: calvin-ui98@dagobah.stwing.upenn.edu
Subject: Re: Mockup for UI
I took some notes at class and thought I would make some suggestions
based on our review with the TA.
We want to find a way to provide feedback saying what else MUST be
changed or provided before an archive can be generated. Ideally,
that feedback would always be available.
We could add a "Generate" tab as the last tab, on which the user can
see if everything is ready, and where the Test and Generate buttons
would be moved off of the Projects tab.
The Projects tab should be changed. From the version you saw last night,
the Test and Generate buttons would be moved as above, the autocreate
option would no longer be an option, the Projects List would be removed,
and the checklist in the lower left would be subsumed by our feedback
mechanism mentioned above.
When we save a project, we remember which tab the user was on. When
the project is opened again, we start with that tab. So, if the user
wants to regenerate an archive, the next time the user opens a project,
the user would be back at the generate tab again.
We could introduce a forcing function under the new project; we could
force the user to tell us what kind of processing is required for the
new project and then enable or disable the tabs required for that kind
of processing. So, if the user tells us that the project is for translating
a single mailbox to a single archive with no rewriting of subjects, we
disable the filter tab and the processing tab. This has the ADVANTAGE
of MAKING the user tell us what we need to do, and the DISADVANTAGE of
stopping the user in his or her tracks to answer questions instead of
letting the user explore on his or her own.
If a project has been opened (not created with New Project), then
all facilities will be available.
Any thoughts?
dsc