Jim Fulton wrote:
I think that such a tool would be useful. I see no benefit in trying to
provide a through-the-web view. (Actually, I see a little benefit and
lots of downside.) I recommend a simple command line tool instead that
writes to standard output.
What would be the downsides of a
Here's another idea that occurred to me recently. I suspect this one
needs no vote, but perhaps it should be done sooner than other ideas
like the filesystem-based web root.
I want a way to inspect all of the indirections chosen in the course of
a web request or any other publishing
On Monday 13 February 2006 12:18, Shane Hathaway wrote:
Thoughts? Will it work? Should it be a priority?
I like the idea a lot and you could reuse quiet a bit of apidoc code to
produce some nice output.
But my main question is: How will you be able to do this? :-) I could see a
special hook
Stephan Richter wrote:
On Monday 13 February 2006 12:18, Shane Hathaway wrote:
Thoughts? Will it work? Should it be a priority?
I like the idea a lot and you could reuse quiet a bit of apidoc code to
produce some nice output.
But my main question is: How will you be able to do this?
On Mon, Feb 13, 2006 at 10:18:24AM -0700, Shane Hathaway wrote:
I want a way to inspect all of the indirections chosen in the course of
a web request or any other publishing operation. After executing a web
request, Zope will report all of the points where it made a decision
using the
On Monday 13 February 2006 15:21, Shane Hathaway wrote:
But my main question is: How will you be able to do this? :-) I could see
a special hook into the adapter lookup. But then you would just get every
adapter lookup sorted chronically. Will that be helpful? I think we would
have to
