Let's come up with a plan for widgets. We have a very nice widget system
in Zope 3, but it's not perfect. There are a bunch of things that could
* the widgets are hanging out in dusty zope.app.form.browser. Perhaps
it's time to move them into zope.widget? Not even in a browser
subdirectory - after all, zope.widget is all about the browser!
* there are various widget registrations missing. We should make sure to
* Jim tells me "Don't look at SimpleInputWidget, it's too complicated".
This sounds wrong and zope2-like; something called Simple that's too
complicated. We need to figure out how to make that story less complicated.
* sources and terms are nice, but we should at least provide some basic
sources and register some basic terms for them; that bit is completely
missing in Zope 3 right now. People should be able to at make a simple
drop-down widget happen without having to figure out how to tie all
these components together - they should just import and use the right
source, perhaps import, use, and register the right term, and there they
I guess that would be the important part. (simplify the implementation)
* there are widgets missing. Lots of people have useful widgets.
Extensions with more widgets are very nice, but let's provide lots of
useful widgets in zope.widget, too.
Are people interested in developing a plan to tackle these issues? If
some of us chip in we may get somewhere.
Yes, tell me what's your plan and I try to find some time to help you.
didn't Gary Poster start a widget refactoring?
Mit freundlichem Gruss
phone +41 (0)41 781 01 78
mobile +41 (0)79 340 52 32
fax +41 (0)41 781 00 78
email [EMAIL PROTECTED]
END OF MESSAGE
Zope3-dev mailing list