Hi Bryan, hi all,
I am certain that providing parameters for XSLT filters is a desired
feature, but I am uncertain if the solution you suggested fits for all
scenarios.
Does every user have to write macros to handle parameters?
What if you want to combine multipel (XSLT) filters as one?
What does the others think concerning (XSLT) filter parameters in the
Office?
I am about to start a general follow-up thread where feature
requirements around XSLT transformation might be discussed.
I am curious about the input from the community and will summarize the
result.
Some further information concerning your problem inlined:
Bryan Rasmussen wrote:
Hi Svante,
I don't want to get to the dialogue, I want to call the dialogue.
XSLT can be thought of as a function into which the caller of the function
can pass a number of parameters, since OpenOffice does not have a way to
pass parameters to XSLT I am going to have to build a way to pass
parameters, why, because I have an XSLT based framework for doing
cross-media transformations of a lot of different XML formats, I want to
port it to OpenOffice. This application requires one parameter passed to it
which parameter is a list of parameters presented in XML form, one does not
need to pass this parameter as a parameter though, it can be gotten as an
external file. If it is gotten as an external file it needs to be updateable
though, as the list of parameters holds certain information that cannot be
known about the transform itself, this list of parameters includes:
1. The current year
2. The current month
3. The current numerical day
4. The path to the folder holding the current imported document
5. The name of the current imported document
6. possible user set and saved parameters.
4 and 5 can be static, I can just say you need to always import your
documents from the same folder where you have your transform and OO
template, or do these answer to the two default parameters sourceBaseURL and
sourceURL you discussed before?
You already able to receive the name of the current document
targetURL is the file URL to the document
targetBaseURL is the file URL to the document directory
The difference is the target file name.
At any rate 1,2,3 need to be written to the
parameters document so the xslt can get it. I would suppose the way to do
this would be to
1. Have a template
2. When template loads it uses OO macro/basic to get these values, reads in
parameters document, updates parameters document, saves.
3. I make an extra macro so the user can add parameters.
4. I could integrate this with calling the import dialogue, why? because I
think this will impart the understanding to the user of working with a
particular application, one takes these steps gets this response, does not
go to the import dialogue on ones own and just start importing - unless one
wants possible failures.
now that I've written it down though I can see that really #4 is somewhat
less important than the other ones. Do these other steps seem like a
reasonable way of handling the problem of passing parameters to a transform?
I should probably ask: will the transform be allowed to use the document
function to get them, or do I have to do some fiddling with
configurations/source code to allow this?
This should work.
- Svante
Sorry if I was unclear before, I figured it made more sense to try to keep
it at a general level since I would expect that other people would like to
set parameters in some way at some time.
Cheers,
Bryan Rasmussen
-----Oprindelig meddelelse-----
Fra: Svante Schubert [mailto:[EMAIL PROTECTED]
Sendt: 9. januar 2006 15:49
Til: [email protected]
Emne: Re: SV: SV: [xml-dev] catch import/export event of xslt filter?
Hi Bryan,
I am sorry. I still don't catch it.
Could you please explain your scenario step by step, how you get to the
dialog and what you desire to change and why you want this change?
- Svante
Bryan Rasmussen wrote:
Hi Svante,
During export the 'Save As' dialog (for files with existing import and
export filters)
During import the 'File Open' dialog or when the typedetection failed to
find an apropriate filter the 'Filter Selection' dialog. (If this is as
refers to the import/file choice on the menu, the title of the dialogue is
Import.)
Cheers,
Bryan Rasmussen
-----Oprindelig meddelelse-----
Fra: Svante Schubert [mailto:[EMAIL PROTECTED]
Sendt: 9. januar 2006 15:28
Til: [email protected]
Emne: Re: SV: [xml-dev] catch import/export event of xslt filter?
Hi Bryan,
Bryan Rasmussen wrote:
Is it possible to do one of the following then:
1. send parameters to the import export filter (I suppose not)
Only some default parameters as explained my recent mail
2. call the import file export dialogs, not the dialog for setting a
filter
but the dialogs for actually exporting or importing a document?
I have four dialogs in mind, when talking about filter:
During import the 'File Open' dialog or when the typedetection failed to
find an apropriate filter the 'Filter Selection' dialog.
During export the 'Save As' dialog (for files with existing import and
export filters) or 'Export' Dialog (for files with export filters only,
e.g. XHTML).
Or finally the 'XML Filter Settings' Dialog.
Please explain in more detail what dialogs you meant.
-Svante
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
