Joerg Barfurth wrote: > Hi mathias, > > Mathias Bauer wrote: > >>>Unfortunately there is no API to control the finalized attribute (and >>>some other similar node attributes), so you have to do this by editing >>>the configuration file directly. > >> I wouldn't call this unfortunate. Without an API you can make *sure* >> that the value is not changed by a macro, Add-On or something else. IMHO >> this is important to make the "finalizing" feature useable. > > It is stored in a file and a macro, etc. could simply manipulate the > relevant file and then force a reload of the configuration. It gets just > more tedious. But that is unfortunate as it also disallows building > administration tools upon our UNO services. Instead such tools have to > manipulate the XML directly which is more prone to producing files our > services can't read.
Of course I assumed that there is no possible write access to the "share" directory so a direct file manipulation is not possible also. A manipulation of configuration data in a running OOo instance should never access anything in the "share" directory of OOo. My choice still would be to have an API in the configuration service like you want and disable it in OOo at runtime. OTOH the configuration service in an administrative tool with suitable access rights could provide this API access. Ciao, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
