If we want to only send selected fields to the browser, and not all empty fields are guarantied to be sent back by the browser, then it seem we need to know which selected fields were sent so we will know which selected fields to process on return.
To me this says we should either create explicit views of a form (to exist between the form definition and the form templates), or we need to collect (and possibly cache) the list of widgets that are in the template and use this list to drive the form's readFromRequest method. So far, I lean toward using an *optional* set of explicit views. This may even lead to the possibility of the view introducing view-specific widgets, driven by the same general set of needs that produced the aggregate widget. WDYT? --Tim Larson __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
