[Libreoffice-bugs] [Bug 111338] LibO will update the registrymodifications.xcu for every color chosen in the color picker (since LibO 5.3)

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=111338

--- Comment #18 from Telesto <telesto at surfxs.nl> ---
(In reply to Aron Budea from comment #17)
> (In reply to Buovjaga from comment #15)
> > Yes, and all of this saving prevents loss of data. Why would you want to
> > make it more risky?
> Considering LO doesn't save the document after each keypress, I'm not sure
> saving various last-set config values is actually a case of preventing loss
> of data.
> 
> And if the following situation mentioned by Telesto is true, saving
> megabytes so often is far from great: "A xcu size of 2-4 MB isn't to
> exceptional causing a crazy amount of disk activity storing mostly trivial
> things"

FWIW: there are likely by far more instances where it's written. You can you
process monitor to check or read the XCU itself they look what's stored.

Noel his position if it it doesn't hurt performance it's no issue (or lets say
no big deal) and hard disk are design to handle lots of writes.

Which isn't untrue. And we can add a there likely more unoptimized programs;
and there are other instances where stuff is written to temporal files and
such.

And we can argue about they load at desktop for typical office desktop. And
replacement schedule (in the Western world). So hitting they maximum writes not
likely to happen

Or we can also argue against they developing country's. Where assume cloud
solutions not being they obvious choice (yet); price/quality of the internet
connection. People working with far older (second/third hand) systems, I
assume.

If it's easy to prevent, it might be wise to do so. They costs are in they area
of more code complexity and more stuff which can break down. And no auto-save
stuff is hard to verifier to (Luke Kendall still encountering kind of timer
issue with auto-save; kicking in to often once in a while. But time consuming
business to track down).

So there is a trade-off here. They whole timer stuff can of course be prevented
by saving they xcu in a SQLite database (assuming it does make true what's
advertised about reducing writes). But objection here likely be plain xml is
'easier' to access with an editor compared to dumping it into a SQLite
database. And of course they downside of updating another external package. An
advantage would be that the size of they sqlite should be smaller (as there a
columns so non repetitive xml markup stuff)

And there are some other area's where SQLite would be nice (see Julien: bug
134421)

There is no straightforward answer to this, IMHO. Depends on what's valued.
It's surely not something most users will notice if changed. So the achievement
here isn't unique selling point. More topic out of principle

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20201021/683f8a7a/attachment.htm>