[Zope-dev] ZPatterns: DropZone example

2000-06-28 Thread Steve Alexander
Hi folks, I've been looking at the DropZone example Phillip Eby provided on the ZPatterns Wiki. http://www.zope.org/Members/pje/Wikis/ZPatterns/DropZoneExample I've decided to start implementing it, so as to give myself an educational experience in using ZPatterns. I have an open question:

Re: [Zope-dev] ZPatterns: DropZone example

2000-07-04 Thread Phillip J. Eby
At 05:26 PM 6/28/00 +0100, Steve Alexander wrote: > >The suggested specialists in the Accounting framework are: > > Invoices > Orders > Customers > Products > >What I'm finding is that these are just the White-box specialists. A >clean design would seem to want all the specialists above, plus

Re: [Zope-dev] ZPatterns: DropZone example

2000-07-04 Thread Scott Parish
Thus spake Phillip J. Eby ([EMAIL PROTECTED]): > > That's all quite true, but it would probably be simplest to do such a thing > using AttributeProviders and SheetProviders in the white-box specialists. > It does seem reasonable to have those providers talk to an > AccountingProcessor object if y

Re: [Zope-dev] ZPatterns: DropZone example

2000-07-04 Thread Phillip J. Eby
At 02:21 AM 7/5/00 +, Scott Parish wrote: > >Does anybody out there have even the slightest clue about how to go about >using AttributeProviders and SheetProviders? A select few terse hints on >this subject would really help us (me) figure it out enough to start working >on some howto's. You

Re: [Zope-dev] ZPatterns: DropZone example

2000-07-05 Thread Jimmie Houchin
"Phillip J. Eby" wrote: [snip] > Peter Coad's design approach (which ZPatterns is heavily based on/biased > towards) emphasizes four major layers of classes in an application: > > 1) User Interface (GUI, forms, etc.) > 2) Problem Domain (the actual application purpose) > 3) Data Management (objec

Re: [Zope-dev] ZPatterns: DropZone example

2000-07-05 Thread Phillip J. Eby
At 03:12 PM 7/5/00 -0500, Jimmie Houchin wrote: >"Phillip J. Eby" wrote: >[snip] >> Peter Coad's design approach (which ZPatterns is heavily based on/biased >> towards) emphasizes four major layers of classes in an application: >> >> 1) User Interface (GUI, forms, etc.) >> 2) Problem Domain (the

Re: [Zope-dev] ZPatterns: DropZone example

2000-09-06 Thread Steve Spicklemire
Hi Steve, (and any others who might care to comment) I've been sorting through old ZPatterns email looking for inspiration and I came upon this: > "Steve" == Steve Alexander <[EMAIL PROTECTED]> writes: Steve> Hi folks, Steve> I've been looking at the DropZone example Phill

Re: [Zope-dev] ZPatterns: DropZone example

2000-09-06 Thread Steve Alexander
Steve Spicklemire wrote: > > Hi Steve, (and any others who might care to comment) > >I've been sorting through old ZPatterns email looking for > inspiration and I came upon this: > > > "Steve" == Steve Alexander <[EMAIL PROTECTED]> writes: > > Steve> Hi folks, > > Steve> I

Re: [Zope-dev] ZPatterns: DropZone example

2000-09-06 Thread Steve Spicklemire
Hi Steve, > "Steve" == Steve Alexander <[EMAIL PROTECTED]> writes: >> ShopperManager.InsertItemIntoShoppersBasket(shopper=aShopper, >> mi=aMarketItem, quantity=qty), Steve> Seeing as the context is clearly ShopperManger (or Steve> Shoppers), I don't think there's any need f