Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Reconsideration of read-only mode | ||
---|---|---|---|
Product: | General | Reporter: | tora3 |
Component: | code | Assignee: | AOO issues mailing list <issues> |
Status: | CONFIRMED --- | QA Contact: | |
Severity: | Trivial | ||
Priority: | P3 | CC: | bemace, cmoulin, fd0man, issues, jonathan, kamataki, kpalagin, Mathias_Bauer, spencer8, srt2006, y-catch |
Version: | OOo 2.1 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
tora3
2007-01-05 02:51:53 UTC
reassigned *** Issue 75946 has been marked as a duplicate of this issue. *** I reported this bug to Ubuntu, and read the result of the discussion of Issue 75946. Incidentally, that is where I learned about the Edit File button, which is a nice feature. If it could be put somewhere in the File menu—and work “inline” without errors, that would be really nice, though. I can imagine that the errors before creating the new document would scare or deter some users. Yes, suppressing the error message would be a good step forward. Unfortunately this issue here is a little bit off-track in some other points. The points 9 and 10 are wrong as the user won't be able to save to the original location if step 5 resulted in an error message due to missing access rights. If a saving to this location was possible this error message wouldn't appear. And it mixes in another thing (the browser plugin) that is not related to the read-only mode per se: whatever we might do to the "normal" mode we won't allow for editing files in a browser window. This is not a safe environment as the browser can kill the plugged window at any time without a chance to save the content. Plugins shouls stay read-only all the time. I will see if we can do something against the error message when a user clicks on "Edit file" without having the necessary rights to access the file in writing mode. Immediately asking for creation of a copy would be better, I think. In a next step we can try to find out what might happen if we allowed write access anyway as then the user will get the error message when she tries to save. Voted on this, because sometimes users may want to edit a file "on-the-fly" and print it directly. If editing is disabled in "read-only" mode, users would have save the file first, edit & print the file and then delete the saved file, which adds extra steps and is enough to affect the usability. well maybe I'm not experienced enough, but I didn't actually know about the "Edit File" button until I read the bug#75946 as pointed by mtrausch today... I think allowing users to edit the file when opening a read-only file is okay, just give a warning message and popup the "Save As" dialog when user clicked "save" is sufficient. it seems MS Word also just popup the "save as" dialog box when user clicked "save" in read-only mode instead of disabling any editing, which definately made it easier than OOo to just edit "on the fly" and print. This is a major pain for us. In our case it's usually someone trying to view a generated spreadsheet on our intranet. Fill out a form, submit, and the browser prompts to open the spreadsheet. The problem is that when you start looking around the spreadsheet you see some data that's cut off, so you go to resize the column, but you can't. You have to click the Edit File button (which I only learned of thanks to this bug report), then confirm another prompt, and then it becomes editable, but it also scrolls back to A1 so you lose your place. There shouldn't be all these extra steps just to *view* information in a spreadsheet. With Excel you just open and adjust columns as needed, with no messing around. Issue 126877 makes this same request, which additional supporting arguments. |