Yet I did a JXforms search in google and the first page I came up with was
the project originator that said the project is dead.

What about integrating chiba into Cocoon instead. It has several active
developers and 90% of the W3C XForms implemented.

-- Robert

"Chris Clark" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
news:[EMAIL PROTECTED]
Yes.
JXForms has replaced it.  Woody is also in active development (although I
haven't checked it out).
To my knowledge, there aren't any docs for JXForms (but I haven't checked
recently).
I've reverse-engineered all I know about it from the sample and some playing
around.
JXForms isn't that far removed from XMLForms, I believe the underlying Form
object is still the same.  It still isn't a faithful implementation of W3C
XForms.
The model is encapsulated in javascript and the form is defined in an xml
source.

I have docs that I would love to put up on the wiki, unfortunately my
employer is a little protective when it comes close to anything that smells
like "intellectual property" so I don't dare post them.


> -----Original Message-----
> From: Robert Simmons [SMTP:[EMAIL PROTECTED]
> Sent: Thursday, August 28, 2003 7:54 AM
> To: [EMAIL PROTECTED]
> Subject: XMLForm Deprecated?
>
> I am reading though the local.blocks.properties and I see the followign
> lines:
>
> # Deprecated
> blocks ------------------------------------------------------------
>
> # Although these blocks are stable they have been deprecated in favour of
> other
>
> # blocks.
>
> #exclude.block.xmlform=true
>
> Has XMLForms really been deprecated? If so what has replaced it in
> functionality? Finally, where can I find documentation on its replacement?
>
> -- Robert
>
>
>
>
> ---------------------------------------------------------------------
> 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]

Reply via email to