On 8/10/05, Jürgen Schmidt <[EMAIL PROTECTED]> wrote:
Hi,

Andreas Schlüns wrote:
> Andrzej Wytyczak-Partyka wrote:
>
> OK - I see.
> I'm right ... you test cour component using basic ?
> You shouldnt do that .-) You should install your component
> using the PackageManager and(!) replace the configuration entry, which
> defines the default TaskCreator service used by the office.
>
> Then your service will be used for every new created frames inside OOo
> ... and you will have open documents automaticly inside your tabs.
>
> How can you install your component inside OOo ?
>
> a) Pack the following files into one ZIP file.
> window.uno.dll // your component
> window.uno.rdb // needed for using foo.XAWindow
> TabBrowse.xcu  // set your TaskCreator service as default

OK. I got it :-)

That is the old pkgchk mechanism. I would suggest that you create a
correct new style UNO package bundle.

1. Create a zip file with the extension *.uno.pkg
2. put your dll in the platform specific directory "Windows/window.uno.dll"
3. create a package descriptor file

Thanks Juergen, I'll switch to the new package mechanism later.
Right now I'd like to path the other things up.



And one further suggestion, i would rename the library and the type
library to maybe tabwindowsupport.uno.dll and tabwindowsupport.rdb

Yes, that's a good suggestion :-) I'll do that, along with some more clean ups.

Regards,
Andrzej

Reply via email to