Martin Aspeli writes: >>> I'm fine with putting widgets that are "real useful" (and well tested) >>> into plone.app.z3cform itself, just like with plone.app.form. I'd >>> expect Martin's autocomplete widget to be "real useful".
Actually I think I made a wrong assumption here: That it'd be Plone specific. It's probably not. In which case plone.widget.* makes more sense. > I don't actually think we should keep all widgets in plone.z3cform. The very > standard Plone ones (like Kupu) are a good idea. But it's a pain if we have > to rely on release of a "big" package to be co-ordinated. Packages are cheap > with eggs and dependency management. Is it a pain? I like the idea of having batteries included in plone.app.z3cform. That is, *Plone specific batteries*. This would give us better visibility and a "quality assured" feel. Either way works for me, though. -- http://danielnouri.org _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
