Re:

IMHO it would be better to use an ID transform output filter
to
generate ODF then transform that flat ODF "data
file" using whatever
parameters and processor you like.  Although I've not
thought it
through completely, it seems to me that the introduction of
generalized
parameters just before export could break ODF, or, more to
the point,
be used to "demonstrate" that the OO ODF
implementation is broken.  Not
that certain companies in Redmond, WA would ever consider
doing that to
Sun's Java (too late they already did!), er, I mean Sun's
OpenOffice.


--Gannon
--- Svante Schubert <Svante.SchubertSun.Com> 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 <stephengreenublgmail.com> 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
<gildororonarmail-on.us> 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:
dev-unsubscribexml.openoffice.org
> >>> For additional commands, e-mail:
dev-helpxml.openoffice.org
> >>>
> >>>
> >>
> >> --
> >> 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: dev-unsubscribexml.openoffice.org
> >> For additional commands, e-mail: dev-helpxml.openoffice.org
> >>
> >>
> > 
> >
>
------------------------------------------------------------
---------
> > To unsubscribe, e-mail: dev-unsubscribexml.openoffice.org
> > For additional commands, e-mail: dev-helpxml.openoffice.org
> > 
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribexml.openoffice.org
> For additional commands, e-mail: dev-helpxml.openoffice.org
> 
> 



       
____________________________________________________________
________________________
Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now
(it's updated for today's economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyh
erenow  

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribexml.openoffice.org
For additional commands, e-mail: dev-helpxml.openoffice.org

 I think you must be referring to some different meaning of
parameters
than the one in particular we are using, I at any rate am
referring
specifically to xslt parameters which I can't see how those
can be
used to demonstrate that ODF is broken.


Cheers,
Bryan Rasmussen

On 10/9/07, Gannon Dick <gannon_dickyahoo.com> wrote:
> IMHO it would be better to use an ID transform output
filter to
> generate ODF then transform that flat ODF "data
file" using whatever
> parameters and processor you like.  Although I've not
thought it
> through completely, it seems to me that the
introduction of generalized
> parameters just before export could break ODF, or, more
to the point,
> be used to "demonstrate" that the OO ODF
implementation is broken.  Not
> that certain companies in Redmond, WA would ever
consider doing that to
> Sun's Java (too late they already did!), er, I mean
Sun's OpenOffice.
> 
>
> --Gannon
> --- Svante Schubert <Svante.SchubertSun.Com> 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
<stephengreenublgmail.com> 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
<gildororonarmail-on.us> 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:
dev-unsubscribexml.openoffice.org
> > >>> For additional commands, e-mail:
dev-helpxml.openoffice.org
> > >>>
> > >>>
> > >>
> > >> --
> > >> 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:
dev-unsubscribexml.openoffice.org
> > >> For additional commands, e-mail:
dev-helpxml.openoffice.org
> > >>
> > >>
> > >
> > >
> >
------------------------------------------------------------
---------
> > > To unsubscribe, e-mail: dev-unsubscribexml.openoffice.org
> > > For additional commands, e-mail: dev-helpxml.openoffice.org
> > >
> >
> >
------------------------------------------------------------
---------
> > To unsubscribe, e-mail: dev-unsubscribexml.openoffice.org
> > For additional commands, e-mail: dev-helpxml.openoffice.org
> >
> >
>
>
>
>
>
____________________________________________________________
________________________
> Boardwalk for $500? In 2007? Ha! Play Monopoly Here and
Now (it's updated for today's economy) at Yahoo! Games.
> http://get.games.yahoo.com/proddesc?gamekey=monopolyh
erenow
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribexml.openoffice.org
> For additional commands, e-mail: dev-helpxml.openoffice.org
>
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribexml.openoffice.org
For additional commands, e-mail: dev-helpxml.openoffice.org