Re: [Zope-dev] Re: [Zope-PTK] PROPOSAL: Splitting ZPatternsinto two products
"Phillip J. Eby" wrote:
DataSkins themselves,
Okay, I'm being dumb again, but could someone explain to me how the name DataSkin came about and how it relates to what these objects do? :S
That might be, but the PlugIns part isn't really where it should be before it could even be proposed to go into the Zope core. The biggest hurdle remaining is full ZClass support.
How does this interact with DC's plans to redo ZClasses? (although I'm not sure there are plans here yet, I just got the feeling there were..)
Has anyone done anything with the 'glossary wiki' idea I punted out a while back?
I don't believe so. But I think that splitting the package will make documentation easier. Partly because it will allow starting from a fresh viewpoint that is DataSkins-centric and more use-oriented. I figure on leaving the ZPatterns Wiki alone for the most part until the DataSkins docs start to mature, and then yanking out documentation-type stuff from the ZPatterns Wiki and re-purposing it to focus on application design, object modelling, and the like, in the context of the DataSkins and PlugIns packages.
Sounds great :-) cheers, Chris
Chris Withers wrote:
"Phillip J. Eby" wrote:
DataSkins themselves,
Okay, I'm being dumb again, but could someone explain to me how the name DataSkin came about
Suggestion on zope-dev from Jason Spisak Fri, 19 May 2000 17:28:19 GMT, in response to Phillip looking for a better name than "Dynamic Data Object". ---- Phillip:
I'm not actually real fond of the DDO term, because "Dynamic Data Object" doesn't quite do justice to what these things actually are. I am definitely open to suggestions for a better name. (Facade? PlaceHolder? InsideOutObject? ExternalDataObject? BrainInjectedObject?)
Jason:
ZopeTupperware, AloofAttributeObjects, DataSkins :)
and how it relates to what these objects do?
Well, you can look at a normal object as having a interface "skin" through which you interact with the "flesh and bone" of its data. A Data Skin object is a bit like a clever virtual-reality glove, where its "flesh and bone" is actually somewhere else -- or perhaps nowhere at all, and is just generated from some algorithms. However, in both cases, the "skin" looks and feels exactly the same. Keywords: Encapsulation Delegation Transparency -- Steve Alexander Software Engineer Cat-Box limited http://www.cat-box.net
Steve Alexander wrote:
and how it relates to what these objects do?
Well, you can look at a normal object as having a interface "skin" through which you interact with the "flesh and bone" of its data.
A Data Skin object is a bit like a clever virtual-reality glove, where its "flesh and bone" is actually somewhere else -- or perhaps nowhere at all, and is just generated from some algorithms.
However, in both cases, the "skin" looks and feels exactly the same.
Ah, makes sense now :-) cheers, Chris
participants (2)
-
Chris Withers -
Steve Alexander