BTW, could any of this delay be addressed by shipping Chandler with a
prebuilt repository?
--Grant
On Nov 10, 2005, at 3:56 , Pieter Hartsook wrote:
I think it is useful for a new user to see an already crafted item in
the initial view. It gives a focus and meaning to the context and
allows very simple discovery of significant parts of the UI (detail
view particulars of an event) that otherwise might take some futzing
around and some frustration before the user would see the same
richness of information.
It might save 3 sec. on initial startup, but might save several
minutes of the user's time jump-starting their understanding of
Chandler calendar functions. I vote to keep the initial event, even if
it slows things down on 1st start.
Pieter
On 11/10/05, Mimi Yin <[EMAIL PROTECTED]> wrote:
sounds fine to me.
On Nov 10, 2005, at 1:49 PM, Sheila Mooney wrote:
On Nov 10, 2005, at 1:39 PM, Heikki Toivonen wrote:
Alec Flett wrote:
So this leads me to two questions:
1) Are we willing to take the startup hit to show the welcome
note?
(especially important since this affects the absolute first time
that
the user starts the application - talk about making a first
impression!)
We could do the startup message in a different way which would
probably
be less of a perf hit. An idea that has been floating about would
be to
dump this text into an about dialog (or maybe a new Help > Welcome
dialog).
I would be ok with this. Mimi, Pieter what do you think? Any other
suggestions?
There has also been talk that the welcome note in the calendar is a
minor intrusion to the users calendar, so getting rid of it would
solve
this as well.
2) Do we need to adjust any of the other tests to clear the
detail view
before running the test, or do we adjust our definitions for what
consistitutes each test? (which is to say, the tests now include
something rendered in the detail view) I'm guessing that we
want to
adjust our definitions, rather than try to work with an empty
detail view.
I think we should adjust our tests to always have an event
selected. The
reason is that I think typical usage pattern is that you have an
event
selected all the time. And we should be measuring real world use
cases.
--
Heikki Toivonen
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
