On Oct 4, 2006, at 10:54 AM, Reid Ellis wrote:
On Oct 4, 2006, at 13:47, Ted Leung wrote:
On Oct 4, 2006, at 10:03 AM, Morgen Sagen wrote:
My thought was that if we could generate occurrences and/or load
relevant items from the next and previous weeks in the background
(Andi suggested OnIdle), that could save some time when the user
clicks the week navigation arrows. Does anyone see any pitfalls
in this approach? Is it possible to load items into the main
repository view from another thread? Also, I would need some
guidance in determining exactly which items need to be pre-loaded.
I'm concerned that this optimization is specific to the week view,
and that having item preloading happening in the background will
acutally penalize the user if they are looking at the dashboard
not the week view. As the app grows, the number of different
paths through the UI will increase, which makes preloading harder,
because there are more possible future paths to "predict".
Ted
I would expect this background loading to only happen when the
current view is the week view.
Reid
To answer Ted's question, I was imagining this only happening when
the week view was displayed.
Come to think of it, you would think the minical would trigger the
loading of a couple months worth of events anyway. Does the minical
manage to *not* load events in its range? Ah, but the minical only
displays events that are in "Mine" collections, and this particular
test collection is probably not designated as Mine. So as currently
implemented, my guess is that all Dashboard items occurring in the
current and following month are loaded anyway.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
