[Zope] Basic, conceptual help / advice?

[sean.upton@uniontrib.com]

My take on this...

Better yet, use the CMF and keep your "controller" and "view-assisting"
logic in skins code, and your data/model related stuff in your Python
Product classes.

In trying to explain the CMF's wide-not-deep approach to this to some people
I work with, it has become clear to me that coding a Python product for the
CMF (if nothing else than becuase of the skins tool) is much cleaner than
trying to cram things like acquirable helper utility methods into a
specialized folder class and other sorts of strange things, and living by
the "logic in content types and tools, presentation and application code in
skins" way of the CMF is really the easiest way to accomplish this.  My CMF
coding is much more compartmentalized and easier to read than the stuff from
previous Zope projects I have worked on.

Sean

-----Original Message-----
From: Andy McKay [mailto:andy@agmweb.ca]
Sent: Wednesday, March 19, 2003 12:35 PM
To: zoper@disturbance.dhs.org
Cc: zope@zope.org
Subject: Re: [Zope] Basic, conceptual help / advice?


> Right now, I am implementing what needs to be a prototype in DTML, but
> it's already getting to be spaghetti, with UI and logic code all
> intermingled. I am leaning toward creating big external methods for the
> encapsulation that I need, but it just *seems like I am missing
> something*.

Write a Product and put all your logic there in Python, use DTML or ZPT 
to do your presentation.

http://www.zope.org/Documentation/Books/ZDG/current/Products.stx will help.
-- 
   Andy McKay


_______________________________________________
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )