Re: Schema provider/CA lookup status

Just to get my cents rolling...  I'm open to getting this into
Archetypes 1.5, if it means more liveliness for the project.

Hurray!

What I think may happen is that I'll explore the space a bit in my product,
with a view to getting my experiences into whit's branch and then hopefully
into 1.5. When that happens I'll update my product to support the "standard"
mechanism. I can't have a dependency on an AT branch at the moment, it needs
to work with OOTB Plone 2.5 for now.



>  In the
> light of Rocky's latest formlib[1] tutorial though, I'm thinking that
> we should try and concentrate on Z3 schemas as soon as possible.
> (Which should of course land in its own component.)
> 

I agree, but I don't think the two conflict. Whit's stuff just gives you a
touch (but a very important touch) more flexibility in where your schema
comes from. I will be demonstrating the use of this pattern (hopefully to
good effect) soonishly, and in my uase case, it makes a *lot* of sense doing
this!



> The functionality you describe here (schema composition through
> components) is probably something that you'd need to add in Z3-land as
> well.  And Martin says he needs it today, so maybe it should go in.
> 

True, but the implementations would be radically different, so again, that
work would be orthogonal. If anything (and this is the case with a lot of
things) AT is the forerunner for doing things in a Z3-ish way (at some point
in the future). it still supports a bunch of real world use cases that z3
schemas can't do as easily or as readily yet.



> The only thing I'm afraid of is that we end up with too many ways of
> doing things (think AT/CA vs. formlib/Z3 schema).  I'd like to hear
> your opinions.
> 

To echo something Ben told me in Norway, we're sometimes so hung up on the
new and cool but not-quite-there-yet stuff in Zope 3 (i.e. z3 schemas are
great, but still don't cover all the functionality people needor involve
more integration work to get them to work with CMF, and the widgets are less
mature, etc) that we stop innovating in Archetypes. I completely agree that
we shouldn't overstretch ourselves, and that making AT more Z3-compatible
(the componentisation work) is paramount, but that doesn't mean we can't
also make AT more flexible and useful. Until the evidence suggests
otherwise, AT will have a looong shelf life still. :)

Martin
-- 
View this message in context: http://www.nabble.com/Schema-provider-CA-lookup-status-tf1921614.html#a5286322
Sent from the Archetypes - devel forum at Nabble.com.



-------------------------------------------------------------------------
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