Re: [api-dev] java windows
You can create dialogs or windows either using Java SWING/AWT (easy) or use the OOo Dialog Editor (tricky). Please note that you cannot change the LookAndFeel of SWING GUIs afaik. On 03/02/09 13:10, allirpa wrote: help. i'm currently working on an addon for open office writer. and i use java and netbeans' plugin for openoffice. i already have a menu and toolbar for the addon. my next step would be to make a dialog or anything like a window that would contain the functions for my addon. the point is showing a window or dialog. is it possible? your help is appreciated. thanks in advance. :) - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
[api-dev] UNO Object Inspector
Hi *! The Object Inspector allows the interested user a deep view into a Documents object structure, "live" in a running Office. See http://wiki.services.openoffice.org/wiki/Object_Inspector I heavily refactored the old code (I do not know the old authors...) of the Object Inspector to be robust and maintainable. Perhaps a feature might be lost... I uploaded a binary OXT-file "Object Inspector 2.0.0 (beta)" to API project's file section. Have a try and post your comments :-) Christian PS: I won't have the time to maintain the extension, perhaps someone find it interesting... the code is in the OOo SVN Repository (/contrib/sdk/examples/java/Inspector). - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
[api-dev] OptionsPageDemo sample extension
Hello! I have just finished my OptionsPageDemo extension. The OptionsPageDemo sample extensions shows how to integrate a custom options page within the existing tree of options pages (here: below Writer) and shows how to store and load the settings in and from the OpenOffice.org registry. The extension uses a custom registry schema to store configuration values. Additionally the extension shows how to add a custom help for an extension. I appreciate comments of any kind :-) See http://wiki.services.openoffice.org/wiki/API/Samples/Java/Office/OptionsPageDemo - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
Re: [api-dev] Netbeans OOo Plugin 2.0: How to add custom files for an option dialog to an add-on project?
On 12/11/08 14:06, Benjamin Vollmer wrote: [snip] Probably a referencing problem. Did you use %origin% to specify the location of the xdl file? Please note that %origin% is relative to the referencing xcu file! Ok, let us take my example. OptionsDialog.xcu is stored under "/registry/data/org/openoffice/Office/" and the option dialog file is stored under "/dialogs/". How should my entry look like? ../../../../../../%origin%/dialogs/Leaf.xdl (This didn't work for me.) Could you please try %origin%/../../../../../dialogs/Leaf.xdl ? This worked for me as I have the same directory structure. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] Netbeans OOo Plugin 2.0: How to add custom files for an option dialog to an add-on project?
On 12/11/08 11:43, Benjamin Vollmer wrote: - I didn't understand that the main class from the nb addon project must implement the XContainerWindowEventHandler interface. I used a seperate class for this because in the dev guide it seems to be also a standalone class, but this class was never instantiated. I think the problem here is that the CentralRegistrationClass, created by the wizard, needs the class names you want to register. By default this class reads the manifest entry named "registration.classname" and loads the classes specified here (space separated list). - Jürgen said it make sense to use a folder structure like "/registry/data/org/openoffice/Office/" for the data-configuration files. But my experience is that for the OptionsDialog.xcu this doesn't work. The refered .xdl Dialog will only be displayed when the OptionsDialog.xcu is in the root folder of the extension. Probably a referencing problem. Did you use %origin% to specify the location of the xdl file? Please note that %origin% is relative to the referencing xcu file! I'm currently working on a sample extension for Jürgen that shows how to add an Option page and extension help. I'll need some days to finally polish it, but if it helps I can provide a work-in-progress project earlier... :-) Regards, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]