Hi,

leyki leykiou wrote:

> Firstly i d like to thank you for your quick response..Starting from the
> last what i meant was that i am able to open a file from the API using the
> loadComponentFromURL method,but i was looking for a method of the API to
> pass my XSLT filter package as a parameter ,lets say, so that the
> transformation is applied prior to opening the file and when my file loads
> it's and odt file , not an xml that it was in the beginning..

This is an interesting idea but unfortunately currently not supported.
As the name of the xslt file basically is nothing more than some "user
data" for the filter adaptor I think that changing the adaptor to accept
them as arguments instead of configuration data could be an interesting
thing to think about.

For the moment you must install you xslt as a filter. I'm currently
updating the DevGuide to describe how to do that (currently the DevGuid
only describers how to install filters that are UNO components). Each
filter can be part of the OOo build or an OOo extension (for xslt that
will work only in the upcoming 3.0 version, not in 2.x).

Once the documentation is up to date, I will announce that in
http://blogs.sun.com/GullFOSS. I will also try to provide a sample
extension to show how you can deploy an xslt into Ooo easily.

A rough estimation for that is end of the week.

Regards,
Mathias

-- 
Mathias Bauer (mba) - Project Lead OpenOffice.org Writer
OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
Please don't reply to "[EMAIL PROTECTED]".
I use it for the OOo lists and only rarely read other mails sent to it.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to