On Fri, 2003-11-21 at 21:01, Timothy Larson wrote: > 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.
yep, I was thinking the same. > So far, I lean toward using an *optional* set of explicit views. But with explicit views, you would still need to know what view was used when a form is submitted, so the name of the view would then be embedded in the form itself? A problem I see with explicit views is that they need to be static (IIUC). I think a common use case will be that the template file is processed by the JXTemplate generator and that some widgets will be included conditionally. > 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. Could you expand a bit on this? -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
