https://bugs.documentfoundation.org/show_bug.cgi?id=144814
Eyal Rozenberg <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Settings that are stored in |LO options dialog has some |the document should be |settings specific to |marked as such |current document & stored | |within it Blocks| |102187 --- Comment #16 from Eyal Rozenberg <[email protected]> --- I staunchly support "solution 2". I claim that _no_ setting in an application's options dialog should be a document- or file-specific setting. The dialog should _only_ have application-level settings, inspecific to a single file, which are saved in the app's configuration files and apply to all relevant documents. I claim that this is what users expect; it is what's common in other applications; it is a reasonable, almost necessary, separation. I therefore disagree that the problem can be resolved by an indication or hint of what gets stored where. Instead of hinting or indicating we should just avoid this ambiguity from the get-go. Document-specific settings belong in document properties, or other document-specific dialogs. I myself had not even realized until the other day that this was even the case! And I consider myself to be a somewhat experienced user... That all being said... : * I recognize some settings are app-level defaults, which are saved in documents since the documents make a copy of those settings. For example, default Western language to use, or tab stop size etc. * There may be some settings for is ambiguous whether they should exist at document-level or app-level, and the way the dialog is structured has allowed the maintenance of this ambiguity without having to decide this way or the other, and without duplicating the default and per-document setting. ... and those need special care. -------- (In reply to John from comment #15) > I agree that changing how settings are currently organizing would be a large > amount of work. Probably too large. It's a lot of work, but not "too large" IMHO. Why? Because: 1. After all, it's just moving settings between dialogs. I mean, it's not about re-implementing the mechanisms affected by those settings or touching them at all. Dialog redesign is significant work, but it's not like there could be all sorts of arcane bugs, or perf issues, or refactoring hairy code etc. 2. It doesn't all have to happen at once. If targets for different settings are located, or created, they could have settings moved there gradually. We're in a messy situation already, so a partial move doesn't make things that much more messy 3. It doesn't all have to happen at once II: Since the options dialog is a rather stable entity, a move could be worked on gradually in some branch for a while before being rebased on the latest development version. > But what is much simpler is to add [D] after each setting that is stored per > document. I'm not sure it's simpler. I mean, it may be simpler to implement, but it would be quite a user-unfriendly eyesore IMO. So again - "solution 2": Let's separate app settings from document settings. Finally - I've rephrased the title to reflect the fact that the solution has not yet been chosen definitely, and to mention "Options dialog" explicitly. I also suggest that we change the severity from "enhancement" to "major". Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102187 [Bug 102187] [META] Options dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
