Just use XComponentLoader xComponentLoader = (XComponentLoader)desktop (XComponentLoader)UnoRuntime.queryInterface(XComponentLoader.class, desktop) For example, instead of XComponentLoader xComponentLoader = NET cast syntax rather than with the UnoRuntime.queryInterface() method. So far the main difference I've found between the CLI bindings and the other documentation is that with the CLI bindings you cast an object to a new interface using normal. The CLI bindings are mostly a port/mapping of the non-.NET object model, so you'll want to get into things like the non-.NET-specific OpenOffice API Developer's Guide. I've found Mark Alexander Bain's Creating an OpenOffice Calc Document with C# to be the most straightforward, hands-on, introductory article to controlling OpenOffice that way. It's analogous to how you can control Microsoft Office via COM.Ī set of CLI/.NET bindings come with the SDK, and are by default installed in ( example for SDK v3.0):Ĭ:\Program Files\_3.0_SDK\sdk\cli ![]() ![]() You can use OpenOffice this way to accomplish a number of different things one example is converting files from one file format to another. If you have OpenOffice installed, then you can use the "OpenOffice SDK" ( current version here) to control that instance from several programming environments, including.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |