4

How do I create a hybrid type (i.e. a type that keeps the convenience of model-driven types but takes advantage of schema-driven types on an as-needed basis)?

My most recent explorations have led me to model-driven dexterity types as the most convenient approach for dexterity development. I've been following this article: http://developer.plone.org/reference_manuals/external/plone.app.dexterity/model-driven-types.html in contrast to schema driven types documented here: http://developer.plone.org/reference_manuals/external/plone.app.dexterity/schema-driven-types.html.

The hybrid approach arose from a problem I've come upon with references, which so far do not behave predictably using model-driven types. I expect that schema-driven definitions will give me more fine-grained control in situations like this.

David Bain
  • 2,439
  • 1
  • 17
  • 19
  • What problem are you encountering with references? – David Glick Jul 09 '13 at 22:01
  • Let me second David's question on problems with references. If there's something that you can do with schema, but not with a model, file a feature request on Dexterity. Let's get it fixed. – SteveM Jul 10 '13 at 14:34
  • Making a mental note to file future references related issues when they come up. – David Bain Jul 10 '13 at 20:08
  • It looks like the problem occurs whether or not I use schema or model driven content types. The information associated with this question is still useful, but I've now opened an additional specific to Dexterity and references http://stackoverflow.com/questions/17619087/componentlookuperror-interfaceclass-zc-relation-interfaces-icatalog-wit – David Bain Jul 12 '13 at 16:03

1 Answers1

6

You can create a schema based on a model:

from plone.supermodel import model

class IMySchema(model.Schema):
    model.load('path/to/model.xml')

Any fields defined in the Python schema will take precedence over those with the same name defined in the model.

The model is loaded at the end of the ZCML configuration phase. This means there's a caveat: You can't refer to a field from the model at module scope anywhere. For example, registering a default value using the @form.default_value(IMySchema['foo']) decorator will not work, because the field hasn't been loaded yet at the time when the decorator executes at import time.

David Glick
  • 5,422
  • 17
  • 23