Re: [Zope-dev] Next Step to Bug Resolution???

2009-01-16 Thread Tim Cook
On Mon, 2009-01-12 at 22:05 +0100, Martijn Faassen wrote: Okay, I'll take another look then and look at ObjectRef. Ah, yes, Dan pointed out to you that you are using a zope.schema.Field in a class instead of in a schema (an interface). That isn't right, and since the direct use of that

Re: [Zope-dev] Next Step to Bug Resolution???

2009-01-16 Thread Martijn Faassen
Hey, On Fri, Jan 16, 2009 at 11:37 AM, Tim Cook timothywayne.c...@gmail.com wrote: On Mon, 2009-01-12 at 22:05 +0100, Martijn Faassen wrote: Okay, I'll take another look then and look at ObjectRef. Ah, yes, Dan pointed out to you that you are using a zope.schema.Field in a class instead of

Re: [Zope-dev] Next Step to Bug Resolution???

2009-01-16 Thread Tim Cook
On Fri, 2009-01-16 at 15:55 +0100, Martijn Faassen wrote: I don't think a wiki page with a chronicle is necessary or even helpful; you need to give us the information necessary to find the bug, but no distracting surrounding information. Okay. To debug this problem, a developer will need

Re: [Zope-dev] Next Step to Bug Resolution???

2009-01-16 Thread Chris Withers
Tim Cook wrote: I would also like for you to explain just what it is about my attitude that you find so offensive/problematic? As a general rule of thumb, anyone who posts with more than on exlamation mark is likely on the wrong track. Cross posting to several lists is also a bit of a

Re: [Zope-dev] Next Step to Bug Resolution???

2009-01-16 Thread Martijn Faassen
Hey, To debug this problem, a developer will need the smallest possible example of code that demonstrates the problem. That means, I take it, just 2 schemas and a single form. Describe briefly what you expect to happen and what in fact happens. If that example can be done *without*

Re: [Zope-dev] Next Step to Bug Resolution???

2009-01-16 Thread Tim Cook
Thanks for all the assistance. On Fri, 2009-01-16 at 18:05 +0100, Martijn Faassen wrote: Yes, you do create new schema fields by subclassing from Field. It's just that we saw you putting a field not in a schema but in what looked like a concrete object. This has given me a BIG pause while

Re: [Zope-dev] Next Step to Bug Resolution???

2009-01-16 Thread Carsten Senger
Hi Tim, Tim Cook schrieb: Thanks for all the assistance. On Fri, 2009-01-16 at 18:05 +0100, Martijn Faassen wrote: Yes, you do create new schema fields by subclassing from Field. It's just that we saw you putting a field not in a schema but in what looked like a concrete object.

Re: [Zope-dev] Next Step to Bug Resolution???

2009-01-16 Thread Tim Cook
Hi Shane, On Tue, 2009-01-13 at 14:10 -0700, Shane Hathaway wrote: Sorry, but the patch doesn't make any sense. Your version of _validate_fields quietly skips validation entirely by default. First of all that is why I asked for others to look at it. :-) But I DID test it by inserting an

Re: [Zope-dev] Next Step to Bug Resolution???

2009-01-16 Thread Tim Cook
Thanks All, On Fri, 2009-01-16 at 21:55 +0100, Carsten Senger wrote: Sure you can have specialized fields that subclass from Field, TextLine, or another base class. E.g. RegistrationNumber(TextLine) that takes care to validate the input for a special format. But you use them in an

Re: [Zope-dev] Next Step to Bug Resolution???

2009-01-13 Thread Shane Hathaway
Tim Cook wrote: I DID submit a patch suggestion in the Launchpad bug report. I think you're talking about this: https://bugs.launchpad.net/zope3/+bug/301226 Sorry, but the patch doesn't make any sense. Your version of _validate_fields quietly skips validation entirely by default. Why

Re: [Zope-dev] Next Step to Bug Resolution???

2009-01-12 Thread Tim Cook
On Fri, 2009-01-09 at 11:05 +, Chris Withers wrote: I can't. The testrunner is already there and buildout-based development makes it trivial to run. svn already does the patch creation for you: $ svn diff be able to get past that bit. Perhaps a kind Zope dev will pick up on this.

Re: [Zope-dev] Next Step to Bug Resolution???

2009-01-12 Thread Martijn Faassen
Hi there, Tim Cook wrote: On Fri, 2009-01-09 at 11:05 +, Chris Withers wrote: [snip] So again, referring to the subject line. What are the next steps? I am trying to understand the history of the discussion, which has a lot of text and is widespread. I think Dan Korostelev tried

Re: [Zope-dev] Next Step to Bug Resolution???

2009-01-09 Thread Chris Withers
Hedley Roos wrote: Chris mentioned unit tests. You do not have to write a new unit test. What is required is to have a look at the tests and then identify one that is relevant to your problematic method. This test should be very easy to read. The hard part is for you to expand this test to

Re: [Zope-dev] Next Step to Bug Resolution???

2008-12-23 Thread Hedley Roos
Hi Tim I'm more involved with Plone but can provide a slightly more digestible answer :) Chris mentioned unit tests. You do not have to write a new unit test. What is required is to have a look at the tests and then identify one that is relevant to your problematic method. This test should be

Re: [Zope-dev] Next Step to Bug Resolution???

2008-12-19 Thread Dieter Maurer
Tim Cook wrote at 2008-12-18 08:35 -0200: ... Yeah we use the really cool, robust, well tested and trusted application server called the Zope Component Architecture because it really shows the strengths of the open source development process. Oh, by the way, after everything is installed you

Re: [Zope-dev] Next Step to Bug Resolution???

2008-12-19 Thread Tim Cook
Thanks Dieter, On Fri, 2008-12-19 at 19:41 +0100, Dieter Maurer wrote: I often approach situations like this with so called Monkey Patches: I replace or enhance classes or methods during startup (triggered by some startup event). This may not be optimal but allows me to solve my problems

[Zope-dev] Next Step to Bug Resolution???

2008-12-18 Thread Tim Cook
Hi All, I have had an issue on the table for months. I started a dialog about it here: http://mail.zope.org/pipermail/zope3-users/2008-October/008215.html The thread was interesting, helpful and did lead me to find an error in some schema definitions because of a misunderstanding of the