Re: [Zope-dev] A First Look at Zope3

[Chris Gray]

On Thu, 31 Jul 2003, Fred L. Drake, Jr. wrote:
> Chris Gray writes:
>  > but I see one problems.  The text
>  > input appears at the top of the list and the button to commit the change
>  > is at the bottom of the list.  This will become more inconvenient as a
>  > container's list of contents grows.  Perhaps the buttons should always be
>  > near the text input.
>
> That's a good idea, and very reasonable.  I will take this opportunity
> to note that simply pressing Enter (or Return, depending on your
> keyboard!) will submit the form as well.

Yep.  I had noticed that, and it is helpful.

> There is a zope3-dev list available that specifically deals with Zope
> 3; sending your comments and observations there will reach more of the
> active Zope 3 developers.

Thanks.  I'll move it over there.

Chris Gray


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )

[Zope-dev] A First Look at Zope3

[Chris Gray]

I checked out Zope3 from CVS yesterday and had a go at it for the first
time.  Granted that it is a work in progress, I did have a few comments
from a user's (rather than a developer's) perspective.

The API exposed to DTML and ZPT seems very sparse (compared to Zope2) at
this stage.  Is this the case or am I missing something?  As far as I can
tell there is as yet no way to even get the name of an object for doing
things like the old .  (I have figured out how to
add to the API for any particular class in the source code.)

About the new look to adding objects in a folder -- I see the point of
going to a list of contents with a text input to assign a name (so you can
see what names are already in use), but I see one problems.  The text
input appears at the top of the list and the button to commit the change
is at the bottom of the list.  This will become more inconvenient as a
container's list of contents grows.  Perhaps the buttons should always be
near the text input.

Chris Gray


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )

RE: [Zope-dev] bug in RESPONSE.appendHeader

[Chris Gray]

Glad to help.

The error in the documentation string seems to have propagated to other
locations.  It appears in /lib/python/Products/OFSP/Response.py(line 130)
and in the Zope Book
.

Chris

On Wed, 12 Jun 2002, Brian Lloyd wrote:

> > First off, the on-line documentation description of this method is 'Append
> > a value to a cookie'.
> > 
> > Second, it breaks if you are in fact adding a second value to a header
> > that already exists.
> 
> Thanks - I've checked in the fix for 2.6 and on the 2.5 branch.



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

[Zope-dev] bug in RESPONSE.appendHeader

[Chris Gray]

First off, the on-line documentation description of this method is 'Append
a value to a cookie'.

Second, it breaks if you are in fact adding a second value to a header
that already exists.

Either:




or:




causes an error because of what looks like a typo.

/lib/python/ZPublisher/HTTPResponse.py(line 391)

reads: h=self.header[name]

but should be: h=self.headers[name]

Chris



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

[Zope-dev] Who maintains ZPublisher?

[Chris Gray]

Who is _the_ or _a_ maintianer of the code for ZPublisher?

I've been rummaging around in the source code, mainly as a learning
exercise at this point.  I have some questions, possibly some suggestions,
and some documentation might come out of it.  So I'd like to know the best
person to bug ;-)

Thanks,

Chris Gray
Systems Analyst
University of Waterloo Library
"Maybe I think too much" --Paul Simon





___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

Re: [Zope-dev] Zope options order sensitive

[Chris Gray]

Hmmm... perhaps an undocumented feature rather than a bug?  Rereading the
doc string I find the description of the -X option mentions a case of
argument order making a difference; -X cancels preceding port options but
not following ones.

On Thu, 19 Apr 2001, Chris McDonough wrote:

> I understand.  Congratulations!  You've found your first bug!  ;-)
> 
> Can you file this with the Collector at
> http://classic.zope.org:8080/Collector ?
> 
> 
> - Original Message -
> From: "Chris Gray" <[EMAIL PROTECTED]>
> To: "Chris McDonough" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Thursday, April 19, 2001 4:21 PM
> Subject: Re: [Zope-dev] Zope options order sensitive
> 
> 
> > The example was fictional; the ips and ports have been changed to protect
> > the guilty.  I'm more interested in just understanding how the code works.
> >
> > It just struck me that given the way the server_info function works in
> > z2.py that you could get a situation where you meant to have zope
> > listening on only one address (specified with an -a option), but if
> > options for particular ports are specified for a server, it will listen to
> > that port for all addresses.  An -a will have no effect on what is set by
> > -m, -w, -W, -f, or -P if -a appears on the command line after them.
> >
> > ./start -f 21 -a special.zope.ip
> >
> > will set Zope listening only on the ip address special.zope.ip except it
> > will be listening at _all_ addresses on the machine for ftp requests on
> > port 21, which might not be the result the user intended.  It is not the
> > same as:
> >
> > ./start -f special.zope.ip:21 -a special.zope.ip
> >
> > Chris
> >
> >
> > On Thu, 19 Apr 2001, Chris McDonough wrote:
> >
> > > Not really... do you want to only listen on 127.0.0.1?
> > >
> > > - Original Message -
> > > From: "Chris Gray" <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Sent: Thursday, April 19, 2001 3:43 PM
> > > Subject: [Zope-dev] Zope options order sensitive
> > >
> > >
> > > >
> > > > I'm just beginning my study of the zope source.  Going through z2.py I
> > > > noticed that order matters in specifying command line options.
> > > >
> > > > For instance:   ./start -a 127.0.0.1 -P 8000
> > > > sets HTTP_PORT to:  [('127.0.0.1', '8080')]
> > > > but:./start -P 8000 -a 127.0.0.1
> > > > sets HTTP_PORT to:  [('', '8080')]
> > > >
> > > > I'm not far enough along yet to know if this makes a difference in the
> > > > end.  Does it?
> > > >
> > > > Chris


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

Re: [Zope-dev] Zope options order sensitive

[Chris Gray]

The example was fictional; the ips and ports have been changed to protect
the guilty.  I'm more interested in just understanding how the code works.

It just struck me that given the way the server_info function works in
z2.py that you could get a situation where you meant to have zope
listening on only one address (specified with an -a option), but if
options for particular ports are specified for a server, it will listen to
that port for all addresses.  An -a will have no effect on what is set by 
-m, -w, -W, -f, or -P if -a appears on the command line after them.

./start -f 21 -a special.zope.ip

will set Zope listening only on the ip address special.zope.ip except it
will be listening at _all_ addresses on the machine for ftp requests on
port 21, which might not be the result the user intended.  It is not the
same as:

./start -f special.zope.ip:21 -a special.zope.ip

Chris


On Thu, 19 Apr 2001, Chris McDonough wrote:

> Not really... do you want to only listen on 127.0.0.1?
> 
> - Original Message ----- 
> From: "Chris Gray" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, April 19, 2001 3:43 PM
> Subject: [Zope-dev] Zope options order sensitive
> 
> 
> > 
> > I'm just beginning my study of the zope source.  Going through z2.py I
> > noticed that order matters in specifying command line options.
> > 
> > For instance:   ./start -a 127.0.0.1 -P 8000
> > sets HTTP_PORT to:  [('127.0.0.1', '8080')]
> > but:./start -P 8000 -a 127.0.0.1
> > sets HTTP_PORT to:  [('', '8080')]
> > 
> > I'm not far enough along yet to know if this makes a difference in the
> > end.  Does it?
> > 
> > Chris
> > 
> > 
> > ___
> > Zope-Dev maillist  -  [EMAIL PROTECTED]
> > http://lists.zope.org/mailman/listinfo/zope-dev
> > **  No cross posts or HTML encoding!  **
> > (Related lists - 
> >  http://lists.zope.org/mailman/listinfo/zope-announce
> >  http://lists.zope.org/mailman/listinfo/zope )
> > 
> 


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

[Zope-dev] Zope options order sensitive

[Chris Gray]

I'm just beginning my study of the zope source.  Going through z2.py I
noticed that order matters in specifying command line options.

For instance:   ./start -a 127.0.0.1 -P 8000
sets HTTP_PORT to:  [('127.0.0.1', '8080')]
but:./start -P 8000 -a 127.0.0.1
sets HTTP_PORT to:  [('', '8080')]

I'm not far enough along yet to know if this makes a difference in the
end.  Does it?

Chris


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

Re: [Zope-dev] Suggestion: All wiki pages have the last modifieddate in the footer.ter.

[Chris Gray]

The FrontPage of a Wiki usually has a link to a RecentChanges page.  If
not you can find it by looking at the entire contents of the Wiki.

Chris


On Mon, 4 Dec 2000, Chris Withers wrote:

> "Jay, Dylan" wrote:
> > 
> > There is getting to be some out of date content and it would be great to see
> > which is which.
> 
> Now there's a great idea :-)
> 
> Chris
> 
> ___
> Zope-Dev maillist  -  [EMAIL PROTECTED]
> http://lists.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  **
> (Related lists - 
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope )
> 


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

Re: [Zope-dev] How to set a DTML-Documents properties

[Chris Gray]

to add the property prop_id='This is a string' to the document doc_id



to change that property to 'New string'



The details are in the API reference under the class ProperySheet.

Chris


On Sun, 26 Nov 2000, robert wrote:

> Hi there,
> I am looking for a way to set a DTML-Documents property from a DTML-Method.
> 
> Any advise is appreciated.
> 
> Robert
> 
> 
> 
> ___
> Zope-Dev maillist  -  [EMAIL PROTECTED]
> http://lists.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  **
> (Related lists - 
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope )
> 


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

[Zope-dev] Zope Book Question: 'context' doesn't work in PythonMethods

[Chris Gray]

I tried following one of the Zope Book examples to no avail.

>From the scripting chapter:

"Since Python Methods are bound the Zope objects, you can get access to Zope
objects via the context parameter. For example, this methods returns the
number of objects contained by a given Zope object:

Method id: numberOfObjects
Parameters:

return len(context.objectIds())"

I just get a Name Error on context and if I add context as a parameter I
just get told that the parameter was omitted from the request.  This works,
however:

Method id: numberOfObjects
Parameters: self

return len(self.objectIds())

Am I missing something?  Is this because Amos and Michel seem to be using
2.2.3 and I'm using 2.2.2?

adTHANKSvance
Chris


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )