gt; >
> > And also "Josema Alonso" <[EMAIL PROTECTED]>
> > Subject: Re: FORMS & Xindice
> >
> >
> > I would be glad to consider applying a patch which was agreed upon the
three
> > of you.
> >
> >
> > Ivelin
> >
>
ch which was agreed upon the three
> of you.
>
>
> Ivelin
>
>
> - Original Message -
> From: "Christian Haul" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, December 21, 2002 3:47 AM
> Subject: Re: [Proposal] XMLForm:
>
Sent: Saturday, December 21, 2002 3:47 AM
Subject: Re: [Proposal] XMLForm: Data Provider
> Konstantin Piroumian wrote:
> > The instance:
> >
> >
> > John
> >
> >
> >
>
> I hope this comment is not completely off: I h
Konstantin Piroumian wrote:
The instance:
John
I hope this comment is not completely off: I have checked in a transformer
that extracts an (arbitrary) fragment and stores it (as DOM) using an
output
module. This can be used to extract form instance data. Coincidently, it
hi konstantin,
hi all,
first, thanks for your pointers.
I looked at the various "advanced" xforms constructs and have come to
following solution for realising it in "standard" xforms:
I will first introduce the solution and then put some questions, which
should be settled before implementation s
hi konstantin,
hi all,
first, thanks for your pointers.
I looked at the various "advanced" xforms constructs and have come to
following solution for realising it in "standard" xforms:
I will first introduce the solution and then put some questions, which
should be settled before implementation s
From: "Konstantin Piroumian" <[EMAIL PROTECTED]>
> From: "Jakob Praher" <[EMAIL PROTECTED]>
>
>
> Also see how the input controls are bound to the instance data using
binding
> expressions:
>
http://www.w3.org/TR/2002/CR-xforms-20021112/slice3.html#structure-bind-elem
> ent
Minor addition to this
Am Don, 2002-12-19 um 10.07 schrieb Konstantin Piroumian:
> From: "Jakob Praher" <[EMAIL PROTECTED]>
>
> > hi Ivelin,
> > hi all,
> >
> > for the last project I used a self-brewed, but kind-a grown, form
> > handling mechanism.
> >
> > now I'm going to use Cocoon XMLForms, because the more people
From: "Jakob Praher" <[EMAIL PROTECTED]>
> hi Ivelin,
> hi all,
>
> for the last project I used a self-brewed, but kind-a grown, form
> handling mechanism.
>
> now I'm going to use Cocoon XMLForms, because the more people use it the
> better it gets ( instead of inventing the wheel again ) and I l
hi Ivelin,
hi all,
for the last project I used a self-brewed, but kind-a grown, form
handling mechanism.
now I'm going to use Cocoon XMLForms, because the more people use it the
better it gets ( instead of inventing the wheel again ) and I like its
closeness towards w3c/xmlforms.
now to my idea:
10 matches
Mail list logo
