On 2/23/06, Peter Simmons [EMAIL PROTECTED] wrote:
of was one of the above people wanted to install a new component to add
some functionality to their site. e.g. add a shopping cart/checkout
component . I think it would be great if the site administrator could
add this component to their site
Been busy but caught up now, thanks for taking this further (and
everyone else I will get to the end soon).
In an earlier email I mentioned tools for making doing ZCML easier for
not technical types e.g. a site administrator that was mainly a content
creator (we have a lot of these as
Hi Roger, Jeff, Steve,
Roger Ineichen wrote:
the advantage of all this is that you need to look in just
one place to
understand a view class. You don't need to look in both
the ZCML and
the Python code, just the Python code. The ZCML becomes
simpler, and
more
Hi Jeff
-Original Message-
From: Jeff Shell [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 18, 2006 8:05 PM
To: [EMAIL PROTECTED]
Cc: Steve Alexander; [EMAIL PROTECTED]
Subject: Re: [Zope3-dev] Brainstorming about browser pages
On 2/18/06, Roger Ineichen [EMAIL PROTECTED
Hi all,
for ages now the magic of browser:page co. has annoyed me to a great extent.
I know their handler code well (we had to duplicate a lot of it for Five) and
think we can do better.
I've brainstormed about potential ways of making the creation of browser pages
more Pythonic (whatever that
Great page. Heres the first thing I don't like:
Registering it would probably work like this::
view
You would register them using a ``browser:pages`` call:
It is not immediately obvious to thew Zope3 newbie what the difference
between a page and a view is and why we would need to
* I feel that there are many usecases for multiple pages from one view
class which is why I've tried to come up with a solution that has
almost no magic (mind the almost). Does anyone have a better
solution without magic?
It's very clean and concise and relates directly to the url. I
On Fri, Feb 17, 2006 at 10:21:41AM -0800, ksmith99 wrote:
I think the template should be considered auxillary, not the view class.
That's how I've been thinking lately.
The view class is_a view and uses_a template.
ZPT isn't the only template option. As Z3 opens up, developers are going to
This is another infamously long post of mine. I'll summarize my
thoughts on the brainstorming here, with details below::
Summary / Quick Thoughts
I'm not fond of browser:page. I can't wait to revisit and remove a
few uses of browser:pages that I'm still supporting
On 2/17/06, ksmith99 [EMAIL PROTECTED] wrote:
I've only built a few simple sites with Z3, but 99% of my browser pages
require additional logic, especially since the prevailing opinion is that
you keep all logic and processing out of the template. (see tal:defines
considered harmful thread)
10 matches
Mail list logo
