Hi Svante, I was actually thinking it could be done on the filter form, or the export form (to make it optimal). So in the filter form you would have a button with the words add parameters, clicking on that would open a dialogue with
parameter name___________ parameter value____________ + add more parameters parameter value could be defined via a macro or just input as a string (default), to write a macro click on button next to value saying something like (add function) At export time one could choose to export and to edit parameters for that particular export instance. As for the structure of parameters I would do as everyone else seems to do, to pass the parameter as a nodeset. So basically just allow one parameter you could name OpenOfficeParamsNode, and have it have the structure <parameters> <param name="foo">bar</param> </parameters> There seems to be a general tendency towards using this method although no standardisation/agreement on it. Cocoon and Exist also use the similar passing of parameters for HTTP querystring etc. Cheers, Bryan Rasmussen On 10/9/07, Svante Schubert <[EMAIL PROTECTED]> wrote: > Hi Bryan, > > You are right there is no GUI to add parameters to an XSLT processor not > even a UNO API. > > Even more currently the Xalan jars are simply hardwired into the Office. > > What about creating an UNO interface for XSLT processors and be able to > add an XSLT processor as office extension? > > Part of such an interface should than be the possibility to add > parameter, which might solve your problem. > > And if we would have an extension mechanism for XSLT processors we might > choose a different processor default, like Saxon for instance, enabling > XSLT 2.0 for OpenOffice.org. > > The bad news I won't be able to spend time on this in the next months. > > Cheers, > Svante > > > bryan rasmussen wrote: > > Hi Stephen, > > > > IIRC the XSL-T engine used is Xalan. Main problems are not so much to > > do with Xalan but with not being able to dynamically pass in > > parameters at transformation time from settings on the filter form, > > although OOo does pass in some parameters on its own, and difficulties > > with the document function, the solution I generally used has been to > > always establish an absolute path for my document function calls, and > > to set parameters in an external file I can generate via various > > methods - one method is generating parameters for a filter to access > > from an Xform. > > > > Cheers, > > Bryan Rasmussen > > > > On 10/7/07, Stephen Green <[EMAIL PROTECTED]> wrote: > >> Hi Gildor > >> > >> I would think the direction from ODF/XForms to XHTML/XForms is quite doable > >> because the ODF supports a limited subset of XForms (model, bindings, > >> lists and > >> submissions). Not so easy to have XHTML/XForms to ODF/XForms of course. > >> The challenge might be with the positioning of the form controls in the > >> XHTML > >> equivalent of the ODF which after all would be the main asset of using OOo > >> as > >> a WYSIWIG XForms editor. > >> > >> I've been trying to use the XSLT filter facility for OOo recently for > >> the first time in > >> earnest and have found some problems which I'm concerned might be due to > >> XSLT limitations and behaviors in the OOo XSLT engine. Anyone know which > >> engine is used and know of any such peculiarities, by the way? > >> > >> I truly hope you get on well in trying such a conversion. > >> > >> Best regards > >> > >> Stephen Green > >> > >> On 07/10/2007, Gildor Oronar <[EMAIL PROTECTED]> wrote: > >>> Dear all > >>> > >>> Is it possible to use the XForms documents created in OOO (host language > >>> is probably ODF) in X-smiles? If not, is it difficult to write some XSLT > >>> to transfer host language from ODF to XHTML so that can be used in > >>> X-smiles? Or any other XForm player. > >>> > >>> OOO is the best (?) WYSIWYG XForms designer available and it would be a > >>> pity if XForms designed in it can only be used with XForms-enabled ODF > >>> reader (e.g. ooo itself). > >>> > >>> I don't know how OOO export-as-xhtml works, is it an complex XSL sheet > >>> behind it? Then probably it's possible to adjust XSLT in it to make it > >>> happen. > >>> > >>> -- > >>> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >> > >> -- > >> Stephen Green > >> > >> Partner > >> SystML, http://www.systml.co.uk > >> Tel: +44 (0) 117 9541606 > >> > >> http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice > >> > >> --------------------------------------------------------------------- > >> 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]
