I wrote about the cost-benes of sessions in desktop apps here, http://www.usercreations.com/weblog/2004/02/05.htmlI concluded that a single, transparent session is the design sweet spot for apps that don't already have a strong notion of collections/concepts/topics/groups (eg, bookmark folders).
Robb On Apr 4, 2004, at 7:33 PM, Ryan McDougall wrote:
Do you agree that all applications should save their state such that they are no different from the time they were close to the time theywere reopened? If you agree should this be part of the HIG or similar UIpolicy? What are the positive or negatives of such a policy, were it implemented? Should there be a unified API/framework for apps to reuse so they can store their state? As an example of an app that goes a long way to save state in a real spatial or sessional way, see Eclipse's workspaces. Epiphany and Pan also save their current workload state in the event of a crash, but should they *always* save their state (ie: save the current web pages seen, or items queued for download), even if they are terminated normally? I think they should, and doing so provides a number of UI benefits. Consistent state meshes *especially* well with a spatial design, since the "real world" always has a consistent state. When I leave my papers spread out at work, they are sitting exactly where I left them the next day. I also think there should be a GNOME-wide policy and method to allow apps to save their state data is a consistent and easily manageable way. Cheers, Ryan Cheers, Ryan _______________________________________________ Usability mailing list Usability gnome org http://lists.gnome.org/mailman/listinfo/usability
Attachment:
smime.p7s
Description: S/MIME cryptographic signature