Jeremy Epstein wrote:
interpret a "covert save" as any time the application elects to take
such an action without the user explicitly telling the application to do
so. By "explicitly" I mean:
1) the user clicks a "save" button when presented with one
2) the user selects a "save" or "save event" option in a menu-bar while
the event has focus
3) the user enters a keyboard shortcut for "save" indicated by the menu
while the event has focus.
In the Chandler Web UI, you should also add:
4) The user drags to move or resize a calendar lozenge, and drops on the
canvas.
In both cases the web UI has a buffer of items to display in the dash
but a user action causes those items to go stale (because of the edit)
or be irrelevant (because of the sort). Even with all the "AJAX"
goodness the server still does the heavy lifting. You really need to
have Matthew or Bobby chime in for a definitive answer here. I do not
know all the specifics of the persistence layer.
Yes, since we are talking about potentially large sets of data, we are
doing both paging and sorting on the server. There may be some
opportunities for optimization, but we haven't really discussed how much
client-side smarts we can build in (and where we can build it in) to
avoid hits to the server.
Matthew
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
