RE: [10x] Vision/Overview/Capability statement

>I need to do some more reading on the mailman site to build a consistent
>template for the screens.
>I like the idea of making them ZPT and CSS.

Cool. Did you see my last post about the test server? I have a good chunk 
of the Mailman interface running now, so you can actually start coding 
against the API there. However reading Mailman code is good (it is fairly 
straight forward).

>Do we want to use Formulator?  I now use Formulator for every application.

I am one of the biggest supporters (having contributed two fields).

>Something I do with Formulator is every form is a container consisting of.
>  _ index_html  self-calling handler
>  - form  _formulator_
>  - form_questions_and_layout  'DTML_Doc'
>  - form_instructions  'DTML_Doc'
>  - required_mark  'DTML_Doc'
>  - processData   'DTML_Method' or 'Script' -handles everything after
>Validation(Mailman API)
>  - confirmationMessage  'DTML_Doc' - called by processData

Okay, but remember this has to be put in the File System. Just make one 
container for me as a demo and I will comment on it...
I am also usually against these index_htmls. It is almost a misuse. ;-)

>I only show this to you to pursue a ZMailman template that would make GUI
>manipulation easier for zMailman.  This is my attempt to separate
>presentation from logic and make everything an object.

Well, I am for this model. Like above, a small sample would be nice to see...

>Does this help or wrong direction?

No, definitely the right direction.

>What does the "email address" validation, Mailman or Zope?
>I use Formulator for this now.

In the first round Formulator should check it and then Mailman will do it 
in more depth in anyway.

PS: You don't have to be shy posting to the Mailing List. This is exactly 
the stuff everyone should see. :-)

Regards,
Stephan

--
Stephan Richter
CBU - Physics and Chemistry Student
Web2k - Web Design/Development & Technical Project Management