Christopher Lozinski wrote:
I think that there is a different tool for every job. Sometimes I think
Plone is the best solution, sometimes Zope 2 is the best solution.
Sometimes Zope 3is the best solution, and sometimes ZClasses are the
best solution.
Yes, you're right about different
On Thu, 2006-28-09 at 14:13 +0200, Philipp von Weitershausen wrote:
The problem is the lack of an exit strategy. If you only need a simpel
web app, fine. If you're creating a prototype, ZClasses are hard to get
out of without rewriting a whole lot of code.
In the words of The Pragmatic
Philipp von weitershausen wrote:
For these use cases it is not necessary to use a complex machinery
like ZClasses. The objects we're talking about here could be very very
dull, to the point where we don't need something like a dynamically
constructed class.
I appreciate all your comments.
Philipp von Weitershausen wrote:
Christopher Lozinski wrote:
I think that there is a different tool for every job. Sometimes I
think Plone is the best solution, sometimes Zope 2 is the best
solution. Sometimes Zope 3is the best solution, and sometimes
ZClasses are the best solution.
I
Jim Fulton asked
Chris, have you tried ArchGenXML?
I did do a project in Archetypes, in Plone. If I recall correctly,
Archetypes requires CMF. And that is way too much code to add to my
application. My workflow requirements are trivial. I think that
Archetypes is quite brilliant at
if zclasses(and some of the niceties that depended on them like
ZPatterns) could reliably roundtrip to the filesystem, would we be
having this conversation?
I don't know...it seems like if you tackled the less sexy problem of
making zclasses play with normal developer tool chain, the divide
