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


Hi Olivier,

On Mon, 2012-06-11 at 11:55 -0300, Olivier Hallot wrote:
It looks like services.rdb is now a xml file and
regcomp/regview/regmerge cannot handle it anymore. Besides, this xml
is a one-line file, so pretty hard to edit without unwindind it.

        Yep; crunching the whitespace makes it faster to parse, but much harder
to edit.

My 2 questions:
Is there a tool to handle services.rdb, beside pure xml text edition?

        I use  xmllint --format (from libxml2) to read it. We could of course
do some small XSLT-ness to have a newlines for each <component> - that
might make it easier to trivially remove components.

        Adding new components is even easier - just drop a file in
program/services/ - and it will be parsed & incorporated on next start.

How easy it is to have the extension manager GUI as a installable
module, or bundled optional extension? Is it something that can fit
into an easy hack? (I am seeking to clone the update manager feature
as starting point).

        You want to get rid of the extension manager GUI ? or you want a
separate, stand-alone "extension manager" GUI ? :-) or you want to make
it easier to edit the services.rdb ?

        Ultimately the services.rdb doesn't have to be crunched like that it
can be verbose and more human editable if you like that, but prolly
worth avoiding that for the default install.

        HTH,

                Michael.

-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot


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.