attached, you'll find a module for string and number testing. There is some
documention in the file. It is meant to be used in something like FormKit.
Any comments are welcome.
>Von: Chuck Esterbrook [mailto:echuck@...]
>Gesendet am: Donnerstag, 15. März 2001 16:58
>An: Stephan Diehl; webware-discuss@...
>Betreff: Re: [Webware-discuss] session and request variables
>At 03:44 PM 3/15/2001 +0000, Stephan Diehl wrote:
> >>We chose to go with named accessor methods instead of . The
> >>for this is at:
> >It always helps to read the documentation :-)
>No sweat. I understand that not everyone has had a chance to read every
> f documentation before they have a burning question that just can't wait.
> >Thanks a lot for this. I was already wondering, where to smuggle in my
>We really need an on-line Webware cookbook where we can dump this stuff
>into. We should either build one in Webware or simply using something thate
>I think the Python cookbook is going to be taken down after 6 months in
>order to encourage early contributions and make the hard copy publicationm
> ore valuable. This is an *impression* I got from talking to an O'Reilly
>person at Python9. Hope I'm not spreading any rumors.
>Anyway, the point is that if that's true, I'd prefer not to use that for
>Webware (assuming we could anyway).
> >By the way, is there already a first draft on FormKit available?
>Wow, the interest in FormKit is a lot bigger than I suspected.
>No it's not available, but I'm finally convinced that it's a higher
>priority than previously thought. *After* resolving my current bug and
>cutting 0.5.1rc2, I will clean up what I have and share it.
> >What I have in mind for form validation, is to have a special dictonary
> >for every form. This dictonary has the fieldnames as keys and constraint>
> information as data, for example:
> >The "string" constraints would match against a regular expression and
> 'number' constraint, if the value is in a certain interval.
> >I would then eat away the request fields (hence the dict access) and
> >either discard the not used fields or throw some exception.
>I have something similar: a list of field specs where each spec is a
>dictionary. I think I also make a dictionary keyed by name out of the listf
> or quick access. (The list is important for HTML generation; it
> he logical presentation order of the fields.)
>My current constraints are simply min/max length (for string) or value
> umbers). Also, whether or not the field is required. But it would be
> o add more constraints given the dictionary format.
>Webware-discuss mailing list
>+44 (0) 118 9711511
>Any opinions expressed in this email are those of the individual and not
>necessarily the Company. This email and any files transmitted with it,
>including replies and forwarded copies (which may contain alterations)
>subsequently transmitted from the Company, are confidential and solely for
>the use of the intended recipient. It may contain material protected by
>attorney-client privilege. If you are not the intended recipient or the
>person responsible for delivering to the intended recipient, be advised
>that you have received this email in error and that any use is strictly
>If you have received this email in error please notify the IT manager by
>telephone on +44 (0)118 9711511 or via email to
>internal.security@..., including a copy of this message. Please
>then delete this email and destroy any copies of it.
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.