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

On 01/16/2012 02:09 PM, Caolán McNamara wrote:

On Mon, 2012-01-16 at 09:18 +0100, Stephan Bergmann wrote:

The UNO concept is to thread the (one and only) component context
instance through the code


Does the configmgr need the component context just for
Components::getExternalValue, which I imagine is to handle stuff like

officecfg/registry/data/org/openoffice/System.xcu work, i.e.

     <prop oor:name="Locale">
       <value oor:external=
           "com.sun.star.configuration.backend.LocaleBackend Locale"/>
     </prop>

where a com.sun.star.configuration.backend.LocaleBackend has to be
instantiated to get the value for the locale ? Or are there other uses ?

I suppose
officecfg::Office::Common::Misc::UseLocking::get();
for config items that don't/can't instantiate uno foo for their values
and
officecfg::Office::Foo::Bar::Baz::get(context); for ones that do/can is
probably not practical ?
The context is already needed to instantiate the com.sun.star.configuration.ReadOnlyAccess service. 

Stephan

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.