xforms (W3C) intepreter in Python?

Paul Boddie paul at boddie.net
Mon Feb 3 10:46:17 EST 2003


"Brad Clements" <bkc at Murkworks.com> wrote in message news:<3e3a85d4_1 at spamkiller.newsgroups.com>...
> 
> I'll laugh here, I haven't tried the "novell xforms preview ". Just from
> reading the whitepaper and description I can tell it's not ready for me to
> deploy. In any case, it's fall out from their purchase of .. that company
> that makes SOAP tools.. Gee, can't recall.

Silverstream, isn't it? "Those people look as if they're hip to
cutting-edge technologies - let's buy them!"

> It's all lots of fun, but I'm getting tired of writing the same code over
> and over. I'd like a higher-level view of layout, validation, minimal
> client-side logic and submission.

Is the data being edited highly structured and hierarchical? When I've
had conversations with people about form validation, I get the
impression that most people make fairly simple forms, particularly
where Web forms are concerned. Indeed, many examples of form
validation technology seem to have about three fields and a button,
and they never seem to cover error conditions very satisfactorily.

When I've experimented with all this before, I've been aiming to
integrate the input of form data with the output/template system, with
special support for error conditions introduced through validation. I
think that the lack of integration throughout these processes is what
makes the usage of many tools much harder (or really, much more
tedious) than it ought to be.

Paul




More information about the Python-list mailing list