To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=83285
------- Additional comments from [EMAIL PROTECTED] Tue Nov 6 22:00:08 +0000 2007 ------- MBA I don't think it would be easy to implement, however, it might not be so difficult either. Maybe there is a way to leave the user to do something with the document while it is been saved. For example, the user is free to move to any part of the document, or to chose something in the menu, or even to change a single page (for writer, calc or impress) while the rest is blocked. This is not that I'm am asking for something that will bring no benefit. I remember the old days of coding for IBM's OS/2. Back on that time they had a application model that they asked you to follow. In that model, every application had to have at least two threads: one only to handle the UI and the other to handle anything else. That way, even in a old 386SX with 8MB RAM, the user had a good impression on the responsiveness of the UI. Some software applications went even further. Every operation that could cause the user to wait would be assigned to a thread. Background file saving was one of the most visible effects. You are typing something. You don't want to lose work, so you press Ctrl+S a lot. However, you don't have to wait for anything, you just keep typing along. It is very unfortunate that the while technology has evolved a lot in 12 years, we are still doing (and designing) things that, in a sort of way, are worse than 12 years ago. What about not copying anything at all? What about having the user _think_ he can do anything by letting him create new things that are to be appended to the document when is finished saving? In this scenario, he would be allowed to create new paragraphs, pages, lines, characters or anything as long as it is beyond the end of the document. He would also be allowed to navigate the document or go through the menus. This "beyond the end of the document" feature could be implemented in a not optimum, but also, not difficult, way: just have a large buffer accepting keystrokes and mouse events until they can be all flushed to the document or to the appropriate handlers at the correct time (when the document is ready). What do you think? --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
