This was originally posted on blogger here.
So you have a Plone content type with some fields. What are the properties of that content type? Well, you can look it up by finding in your file system the product that content type comes from, then examining the schema and finding out your information. Of course, if the product extends another product, then you have to look up that other product.
Introspection is what we really want. Python has it in spades. On pretty much any object in Python I can wrap it in
help(), or check the
__dict__ attribute. But you can't do this easily in Plone. Cooking up a universal instrospection view is something that ought to be done for my CMS of choice. I know there are lots of various barely documented utility methods I can find. I can wrap it up in a product and just use it by having a special introspection view that lays out some pretty HTML.
My coworker Reed pointed out that Zope 3, and the Five stuff in Zope 2 uses Interfaces that give some neat tricks you can do for introspection. I think I'll give that method a try. I think thats the right way to go because:
- The Zope 3 specification handles introspection much more gracefully than Zope 2. And the methods for doing it seem better documented.
- The technology is going that way anyhow.
Tags: plone python interfaces zope five legacy-blogger