Re: Schema provider/CA lookup status
Roché Compaan <roche-kb4xc5yObU3kQYj/0HfcvhBnub05S5/[email protected]> Sat, 29 Jul 2006 19:31:33 +0200
| Newsgroups | gmane.comp.web.zope.plone.archetypes.devel |
|---|---|
| Message-ID | <1154194293.14378.97.camel@kwaaitjie> |
On Fri, 2006-07-28 at 18:34 -0500, whit wrote: > Roché Compaan wrote: > > On Fri, 2006-07-28 at 08:52 +0100, Martin Aspeli wrote: > >> Roché Compaan wrote: > >> > >>> Lovely! Very nice and simple. I also like the name change from Variable > >>> to Extensible. > >> Bear in mind it's slightly different - it uses an adapter to > >> ISchemaExtender to extend the schema. This is meant to let third party > >> products plug in new schema elements. It doesn't really handle the case > >> when the schema is changed TTW, for example (which ATSENG does, though). > >> Still, if you want a different algorithm inside the Schema() method, it > >> should work the same. > > > > I would probably just override the Schema() method on classes that need > > ATSENG, or have a mix in class for schemas that need to be managed TTW. > > <cough> > > can we do this without mixins? What do suggest? At the moment I override Schema on the classes where I need to get a schema from ATSENG. If one wants to generalise this then a mixin is one possible approach. I suppose this is possible using an adapter as well? Can you show us how :-) -- Roché Compaan Upfront Systems http://www.upfrontsystems.co.za ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Archetypes-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/archetypes-devel