[prev] [thread] [next] [lurker] [Date index for 2003/08/22]
On 22/08/2003 at 13:34 +0100, Arthur Bergman wrote: >Frankly, the browser is like an interface to the OS, and it should >really warn when you try and quit it. I use Pith to record browser state. http://www.blacktree.com/apps/ Inability to quit Safari wouldn't help if it crashed, by the way. This has been a subject of discussion across a few blogs fairly recently: http://www.plasticbag.org/archives/2003/08/quick_thoughts_about_global_undo.shtml 'that massive and aggravating UI problem that is what happens when you accidentally quit an application (like Safari ) that allows you to have many different pseudo-documents open that are lost immediately without any kind of dialogue when the application quits.' He doesn't note that Opera and Galeon optionally (well, for Galeon it's optional) save state on quit. http://undergroundlondon.com/antimega/archives/000269.html 'The lazy way to stop this would be for each app to add an "are you sure you want to quit?" dialogue box - but more often than not, I really do want to quit (note that creation applications do this, but traditionally 'reading' applications don't).' 'Better would be undo built into the operating system. No matter what you've just done, you can undo (even several times).' http://jerakeen.org/blog/software/web_browser_features 'For a start, they need to understand the concept of a 'dirty' (changed/unsaved state) window, and prompt the user if they try to close it, in the same way that you can't just close a changed document.' -- :: paul :: compiles with canadian cs1471 protocol
Generated at 14:02 on 01 Jul 2004 by mariachi 0.52