[Zope-dev] RE: RFC : ZPatterns Customer Relationship Management Framework
Thanks for your comments on our model Philip, it is really appreciated and very enlightening. From your comments some other questions came to mind (I posted this on the Wiki as well): It seems that we did not give enough consideration for the pattern, Roles Before Objects but we can retrofit this pattern to our existing design without to much trouble. The area where I need more guidance is on the ability of a specialist to add attributes on top of objects. Thinking out load: Objects might have different attributes depending on the roles they play in various application frameworks. Specialists make it possible to add these attributes through AttributeProviders. One might create a Person ZClass with properties Name, Surname, Age. When the Person plays the role of Customer we will create a Customers specialist for that role providing us with services relevant to dealing with Customers. Let's say for now that the properties defined on our ZClass propertysheet for Person suffices for the Customer role. Our Person object also plays the role of Requester in our Requesters specialist. For this role we need an extra attribute, Priority. The Requesters specialist will ask the Customers specialist for properties Name, Surname and Age but will store the attribute Priority in it's own rack. For storage in the ZODB this will imply that the extra attributes will be stored persisently in the slots of the Requester. For non-ZODB storage like a SQL RDB one will have to add a table to the RDB. Roché ___ 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] Re: Discussion Story Building Mediums
Chris Withers wrote: Michael Bernstein wrote: After some more thought, I realized that this really needs to be a three-way gateway betrween a mailing list, a 'blog, and a newsgroup. I'm all up for doing the mailing list/weblog type bits but I have no idea how news _works_ and how it could be integrated into the Zope environment... Not really, but two-way gateways between mailing lists and News servers are pretty well understood, so it should be possible to let the mailing list sit between the two, and act as a compatibility layer. What do you think? Michael. ___ 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] PythonMethods: Can't Slice context.REQUEST.PARENTS
Okay, I figured that bit of braindeadness out (I just use a range that goes backwards, no .reverse() so everything is left as is. Now here is my next problem. Using context.REQUEST.PARENTS doesn't give me the DTML Document that called me (so to speak). I have: /test/new/foo_html My PARENTS shows Zope, Test, and New, but doesn't show foo_html. Is this because my PythonMethod is Internal vs. External? I didn't see any descriptions of what the differences are. The DTML Method version of my code can see the id/title of the foo_html via 'id', 'title' and 'title_or_id', but under python I just get: self.title_or_id() -- Zope, the folder that my method lives at m_self.title_or_id() -- Breadcrumbs (my method) context.title_or_id() -- New, the folder foo_html lives at And I have no idea what _ is for Any help is appreciated. Ciao! -- "Well Pumpkins, It looks like it comes down to that age old decision: Style or Substance. Hmm." --Vida and the "Girls" ( To Wong Foo, Thanks for everything, Julie Newmar ) The Doctor What: "What, Doctor What" http://docwhat.gerf.org/ [EMAIL PROTECTED] KF6VNC ___ 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 )
