Juergen Schmidt wrote: > Hi Andrea, > > first of all the better mailing list would be > [EMAIL PROTECTED] or > [EMAIL PROTECTED]
thanks for the tip. > > I agree that the documentation is not up-to-date and i will try to fix > this asap. Forgot the old mechanism. > > The format of an oxt package is described in detail in the DevGuide and > you can find examples in the SDK as well. > > You don't have to implement the XAddin interface. Therefore you need > (besides the DIL defintion) an appropriate CalcAddins.xcu where you > define and document the new addin functions. > > Under the node "AddInInfo" you insert a new node for your own addin, > something like "org.openoffice.addin.MyNewAddin". The next node > "AddInFunctions" is equal for all addins and opens the section where you > define your new functions. Here in the example a new function with name > "someValue". I am sure that the rest of the file is self explained ... > ... > <node oor:name="AddInInfo"> > <node oor:name="org.openoffice.addin.MyNewAddin" oor:op="replace"> > <node oor:name="AddInFunctions"> > <node oor:name="someValues" oor:op="replace"> > <prop oor:name="DisplayName"> > <value xml:lang="en">SomeValues</value> > ... > > Your C++ component should be the same as before but you don't need the > XAddin interface (see my posted Java example). > > Pack the xcu, your C++ lib and the type library in an oxt file and > that's it. > This will keep me busy for a couple of days. I will write here (or there) about my findings. Thanks very much for your explanation. Andrea --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
