Re: [Zope3-dev] Input widgets do too much
Garrett Smith wrote: ... Isn't there some pressure to get 3.1 out? Yes there is. > I'm all for refactoring widgets to simplify (or eliminate) the hefty baseclasses, but I had the impression that the release was heading into its final stages. It certainly should be. Unfortunately, it's waiting for bug fixes. You're right. It's probably best to save this for 3.2. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
RE: [Zope3-dev] Input widgets do too much
Jim Fulton wrote: > I'd like to make some changes to the widget API. > >http://www.zope.org/Zope3/MoreCleanupOfWidgets > > proposes some cleanup, but I'd like to go farther. > > I think widgets, especially IInputWidget have too much > responsibility, namely: > > - validation > > - applying changes > > Widgets should be responsible for > > - getting/managing user inputs, including >conversion from raw input (but not validation). > > - Rendering HTML > > Giving widgets this responsibility makes them harder > to implement (leading to complex base classes) and > a bit hard to use when more control is needed. > > I'd like to remove this functionality from widgets, > moving it to form code. > > Thoughts? Questions? Any objections to getting this into > 3.1? If not, I'll write a more detailed proposal. Isn't there some pressure to get 3.1 out? I'm all for refactoring widgets to simplify (or eliminate) the hefty baseclasses, but I had the impression that the release was heading into its final stages. -- Garrett ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Input widgets do too much
On Monday 25 April 2005 17:44, Jim Fulton wrote: > Thoughts? Questions? Any objections to getting this into > 3.1? If not, I'll write a more detailed proposal. I thought Gary was working on a complete rewrite for 3.2 anyways, or was that just related to forms? I am okay with making this a change in 3.1. As long as some of the very critical bugs get fixed in the trunk, I am not inclined moving forward with 3.1 anyways. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Input widgets do too much
I'd like to make some changes to the widget API. http://www.zope.org/Zope3/MoreCleanupOfWidgets proposes some cleanup, but I'd like to go farther. I think widgets, especially IInputWidget have too much responsibility, namely: - validation - applying changes Widgets should be responsible for - getting/managing user inputs, including conversion from raw input (but not validation). - Rendering HTML Giving widgets this responsibility makes them harder to implement (leading to complex base classes) and a bit hard to use when more control is needed. I'd like to remove this functionality from widgets, moving it to form code. Thoughts? Questions? Any objections to getting this into 3.1? If not, I'll write a more detailed proposal. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
