Re: Schema-by-interface options

George Lee wrote:
>>> In the meantime, my proposal is fairly low-risk and could bring a lot of
>>> benefits quickly (witness the amount of people who ask, "I'd like to add
>>> some company-specific metadata to each content type on my site" and get
>>> the answer "oh, erm, well, you could subclass everything, or you could
>>> monkey patch BaseObject"). In fact, Ben once said that the reason we
>>> made Schema() a method in the first place was that we wanted to make it
>>> possible to pull the schema in from other sources than just a
>>> class-attribute.
>> +100. I like it, and it solves a lot of real use cases for developers -  
>> today, without having to invest a lot of time learning new stuff.
> 
> 
> As one of those developers, I'd like to second this ... this would be amazing.
> 
> How does the decision-making process and timeline for Archetypes work? I've been
> eagerly checking the list to see if there's been any decision made on this...

Decisions are community driven.  Timeline is bound to Plone's.

I'm +0.5 for the proposal.  Mainly because many people seem to be
wanting it.  Personally, I could live with monkey patching schemas for
the time being.  I don't think the approach has many benefits over
monkey patching (i.e. calling ThisSchema.addField() directly).

Let's wait two more days to see if someone else comes up with good
arguments against this.  Otherwise I'd say it goes in.


Daniel


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642