Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


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

            Bug ID: 92755
           Summary: Avoid temporary XML files in winreg configmgr backend
           Product: LibreOffice
           Version: unspecified
          Hardware: All
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: medium
         Component: framework
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: sbergman@redhat.com
                CC: fari.libreoffice@gmail.com,
                    libreoffice@lists.freedesktop.org

<http://cgit.freedesktop.org/libreoffice/core/commit/?id=5a02076358a547bae8a9b596d9722a7cd2d46c34>
"Windows registry configuration backend" added support to read configuration
data from the Windows registry (see
<https://wiki.documentfoundation.org/ReleaseNotes/4.2#Windows_Registry_changes>),
but does so by creating intermediary XML files.

<http://cgit.freedesktop.org/libreoffice/core/commit/?id=ecc617e797aa5ed329668114e54ec7ffa5c0e87b>
"configmgr: support reading from a dconf layer (WIP)" (which does something
similar for Linux dconf support), can now be used as a blueprint (modulo any
bugs that new code invariably still contains) how to avoid intermediary files
and directly feed into the configmgr's internal data structures.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.