For 0.7, this may be ok. However, over the longer term there will be
a need for people to have access to everything they have 'DONE'. I
realize this may complicate the UI for 0.7 and agreed we should find
the happy medium on the limit of how far back to go.
One thing we could do is ask 'dogfooders' how far back their 'DONE'
items go and do they ever reference it. Secondly, how far back do
users view their e-mail to reference things?
Mimi has this been asked before…somehow I remember replying questions
similar to this?
Thanks, -Priscilla
On May 15, 2007, at 1:51 PM, Bobby Rullo wrote:
Hi there,
Due to the nature of Cosmo UI as a web application, we have
identified a few areas where we find it helpul to put in some
constraints that don't exist on the desktop for reasons of server
load, bandwidth and performance.
One of these constraints is the nature of the LATER section.
Getting a single occurrence for every recurring event in the future
could be an expensive query with lots of results that the user
probably doesn't want (the "birthday" phenomenon is a good
illustration of this - do we really need to see every single
birthday in the next year in the later section?) Setting an
arbitrary yet reasonable limit could help things out here - maybe a
month or so into the future.
Similarly, expanding every single recurring item from now to the
beginning of time to get every DONE occurrence is taxing on
bandwidth and server load. Putting a limit on how far to go back
(say, one month back) would be very helpful.
Would this be an ok difference between web ui and desktop?
Bobby
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
