Steve Alexander wrote:
"Phillip J. Eby" wrote:
So, I am thinking perhaps I should split ZPatterns into two products:
PlugIns and DataSkins.
If 'PlugIns' includes plugins, plugin groups and plugin containers, then
that's a pretty good name :-)
(If I've missed bits out and the like, please
Chris Withers wrote:
'DataSkins' doesn't mean a lot to me as a name :S
What components would go into this product?
An object that has DataSkin as a base class allows a DataManager to look
after its data storage requirements. The DataManager stores all the
propertysheets and attributes, and
At 09:51 AM 7/28/00 +0100, Chris Withers wrote:
Steve Alexander wrote:
"Phillip J. Eby" wrote:
So, I am thinking perhaps I should split ZPatterns into two products:
PlugIns and DataSkins.
If 'PlugIns' includes plugins, plugin groups and plugin containers, then
that's a pretty good name
Steve Alexander wrote:
An object that has DataSkin as a base class allows a DataManager to look
after its data storage requirements. The DataManager stores all the
propertysheets and attributes, and works out what to do and who to
notify when things change.
Okay, makes sense...
There are
