Eric Radman wrote:
On 12:22 Tue 12 Apr , Bill Janssen wrote:
The minimal Zope 3 code is a page template and a few lines of ZCML in a
Python package with an empty __init__.py to hook up a new view to an
existing object (say, a folder). There's no Python code *at all*
From my point of view, tha
> This works for small scale projects where only a few developers are
> expected to know the codebase.
Sure. It was a small scale example. For larger projects you'd use
more abstraction layers, accessing (for example) template strings via
method calls which would provide the ability to do thing
> Buggy? I don't think ZCML is buggy. Where's that coming from?
Sorry, didn't mean to knock ZCML specifically. I meant to say that
use of XML is inherently buggy when people have to edit it with a text
editor, because of the bad syntax. I have the same gripe with the XUL
used by Firefox. Nothin
Bill Janssen wrote:
I don't know about you, but generating HTML with pure Python code can be
messy--ONE reason why we introduce templateing languages in the first
place. Often (not always) the best way to end up with XHTML is to start
with a valid or almost-valid XML document and then infuse the dy
Bill Janssen wrote:
The minimal Zope 3 code is a page template and a few lines of ZCML in a
Python package with an empty __init__.py to hook up a new view to an
existing object (say, a folder). There's no Python code *at all*
From my point of view, that's the problem. I don't want to write in
s
Hey,
Not much debate from me here on this front, just a lot of agreement.
Ian Bicking wrote:
Martijn Faassen wrote:
[...]
One issue seems to be that Python programmers are automatically
allergic to domain specific glue languages like ZCML, especially when
they look like XML. I think this attitude
