Re: Proposed tabbed_pane widget changes
Michael Flanagan <[email protected]>
| Newsgroups | gmane.comp.windows.devel.netwindows |
|---|---|
| Message-ID | <[email protected]> |
Alex Russell wrote: >>>>Also, the current tabbed_pane widget doesn't play nice when used >>>>in forms. It seems as though it was intended as a display only >>>>mechanism. I would like to chance it's current behavior which is >>>>to actually sub out the content of the pane (it basically does >>>>DOM node swapping) for a different one, to a system where the >>>>visibility of a pane is determined by a CSS style of hidden / >>>>visible = false, whatever it is. This would have the benefit >>>>that the form fields would actually exist in the DOM then when a >>>>submit was done. >>>> >>>> >>>I think this makes some sense. Although this brings up the >>>question of whether or not all tabs are treated as a single form >>>or multiple forms? >>> >>> >>Ya, this I don't know about.... for now I'm happy that we're ahead >>of the old tabbed_pane widget (we have this working with the hidden >>div thing now). >> >> > >I don't think that re-implementing will necessarily be a good plan >anyway. Fixing and extending will get us there much more directly. > Aye, which is what we're doing. Sorry it that wasn't clear. All the changes we've made so far is the existing tabbed_pane widget. We're simply adding the new functionality to the existing widget. _______________________________________________ The netWindows developers list: [email protected] http://netwindows.org/mailman/listinfo/devel_netwindows.org