On 7/21/05, Frank Schönheit - Sun Microsystems Germa ny <[EMAIL PROTECTED]> wrote: > Hi Matthias, > > >>One could manually de-register certain UNO services, so that certain > >>functionality becomes unavailable. > > > > How do I do that? > > The following snippet exemplarily disables the query design, but > de-registering the service which implements it:
This is cool. Thank you. I think this will be very useful, especially since we can write programs that enable or disable the functionality on request. I've just deregistered /IMPLEMENTATIONS/org.openoffice.comp.dbu.OApplicationController and that seems to get rid of the complete Base UI. Can you think of any bad side effects this may have? Is this controller used for any other services we might need? BTW, is there a reason why you deregister the abstract service and the implementation in your example instead of just the implementation? Is there a service I should be deregistering in addition to /IMPLEMENTATIONS/org.openoffice.comp.dbu.OApplicationController? I conclude that the following would probably be a good course of action to enforce our policy: - install with Base enabled (to make sure we have the DSB and other stuff we need) - de-register some services (probably just dbu.OApplicationController) - de-register .odb extension - remove "Database" from all Popups and the File Filters That should achieve the restrictions we want without the risk that some stuff we need will disappear in the future as the "Install without Base" feature progresses. Do you see a way for us to achieve the last part, i.e. removing "Database" everywhere for a standard installation with Base enabled? Christian Junker mentioned the programmatic access to the toolbar icons, but I guess that this won't allow us to remove "Database" from the quickstarter popup. Matthias --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
