Community
Participate
Working Groups
The unsaved notion (the * symbol) is confusing on shared editors. On the viewers side, it is completely disfunctional. This bug is marked as critical, because: When I try to close the editor it asks me "Save?" I click yes, and NOTHING HAPPENS. This mis-functionality could therefore lead to data loss! On the other hand, when I click on save, the * disappears, but again, nothing happens! Suggestion: Either implement remote saving (preferred), or disable the "changed" notion.
Disabling the "dirty" concept would be quite difficult if not impossible since it is up to each individual editor to return a boolean value when isDirty() is called. I'm not sure if I'm down with the concept of "remote saving" since just because you want to save doesn't mean the other person wants to save.
Here's another alternative: Let the editor keep its "dirty" flag. When saving, offer to save the file locally. If this is canceled or not done, the editor stays dirty.
>On the viewers side, it is completely disfunctional. This is not correct...save is functional, it just does not save to the workspace (rather, outside of the workspace). Point at the title bar to see the path. I also agree with Remy...we can't just disable the dirty flag, and I don't think its acceptable to save remotely. We can/could give more information about where the file is being saved to...or perhaps give some other save options (to workspace, etc). I'm going to move this bug from critical to normal severity.
I agree with Remy and Scott. IMHO it should be enough to let the user know where the file is going to be saved locally. I am not even sure, whether or not the realization of any more functionality of this kind is a good idea - since as Scott points out, you can actually determine the location of the file in the filesystem as described in his previous comment. Any more elaborate mechanisms seem to be a waste of effort, since general project sharing should be the next goal to pursue for DocShare. Project Sharing would essentially resolve this issue.
(In reply to comment #4) > > Any more elaborate mechanisms seem to be a waste of effort, since general > project sharing should be the next goal to pursue for DocShare. Project Sharing > would essentially resolve this issue. > Yes. I've created an enhancement request for this capability at bug #239048.
Given the comments below, I'm going to resolve this bug as a duplicate of bug #239048. *** This bug has been marked as a duplicate of bug 239048 ***
