Vendors Name via UNO API / Basic Macros

[Thomas Krumbein]

Hi Miklos,

yes, thanks, that might be a practible way at this time.

Nevertheless - it is not a solution for the future.

I guess, there should be an implementation of the original product name,
version-number (major and minor) and actuall product name.

This should be easy accessible even for unexpierienced macro developers.

I will do a feature request or this :)


best regards
Thomas



Am 15.11.2013 14:11, schrieb Miklos Vajna:
> Hi,
> 
> On Fri, Nov 15, 2013 at 01:43:38PM +0100, Thomas Krumbein <thomas.krumbein at documentfoundation.org> wrote:
>> Thanks for this - I know the xcu files. But this is not an easy access
>> for (Basic-) macros. The way to do is: Search for this file, parse this
>> file and extract the vendor name... for basic marcos a very long way.
> 
> Why not use the css::configuration::ConfigurationProvider API instead?
> 
> I mean something like:
> 
>> oProvider = createUnoService("com.sun.star.configuration.ConfigurationProvider")
>> Dim aParams(0) As new com.sun.star.beans.PropertyValue
>> aParams(0).Name = "nodepath"
>> aParams(0).Value = "/org.openoffice.Setup/Product"
>> oSettings = oProvider.createInstanceWithArguments("com.sun.star.configuration.ConfigurationAccess", aParams)
>> xray oSettings.getByName("ooName")
> 
> HTH,
> 
> Miklos


-- 
## Unterstützung der freien Office Suite
## http://de.libreOffice.org  - www.LibreOffice.org
## Vorstand Freies Office Deutschland e.V.
## Mitglieder willkommen: www.FroDeV.org