I have an idea for getting around my ConflictError problem without a major
redesign. But it involves DataSkins containing DataSkins. I have a few
questions about this...

The base DataSkin will be in a Rack. Would there be any issues in making
the embedded DataSkins (contained on the base DataSkins) use this Rack as
well?  Seems like it might result in the confusion about which DataSkin a
PlugIn on the Rack worked with.

Would it be better to use Customizers in some way... either have the base
Dataskin or perhaps the Specialist also inherit from the Customizer?

Phillip, I think you've considered this (didn't you once mention converting
PropertySheets to DataSkins). What issues do you think I should be aware of
in planning for this.

I tried to dig around in the list archives, but I couldn't come up with a
search pattern with any applicable hits. So I'm sorry if I'm reiterating
something already discussed.

Thanks in advance for any help...


John Eikenberry
[[EMAIL PROTECTED] - http://zhar.net]
"A society that will trade a little liberty for a little order
 will deserve neither and lose both."
                                          --B. Franklin

Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope )

Reply via email to