Re: [pidget-devel] new bindings

[David W. <dj...@ne...>]

Luke Ehresman wrote:

>Sparty,
>
>You mentioned on the pidget-users list some new ideas you had for how to
>handle bindings.  When you flush out your ideas some more, could you post
>them here?  I've been thinking about the problem too, and would be anxious
>to hear your thoughts on how it would actually be implemented.
>
>Luke
>
>
>-------------------------------------------------------
>This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
>The Event For Linux Datacenter Solutions & Strategies in The Enterprise 
>Linux in the Boardroom; in the Front Office; & in the Server Room 
>http://www.enterpriselinuxforum.com
>_______________________________________________
>Pidget-devel mailing list
>Pid...@li...
>https://lists.sourceforge.net/lists/listinfo/pidget-devel
>
>
>  
>
Indeed. We need to be able to retrieve information from widgets after a 
post. Originally databindings were the way you would do this. However, I 
consider them a little bit too complex to be useful in most 
circumstances. What I suggest instead is that we let the developers 
using Pidget specify names for widgets. In order to do this we need to 
be able to handle name conflicts between widgets which contain other 
widgets. For example, supposing we have a widget which represents 
information for a contact in a contact manager application it will most 
likely have multiple text boxes, checkboxes, and select boxes. If we 
place two of these widgets on a page what names will the form elements 
associated with them have? We don't want them to be named identically 
because we will not be able to retrieve the information from them on the 
other side of post if they are. To get around this issue I suggest that 
every widget's form name be dependent on it's parents widget's form 
name. Each form widget will have a method which will allow a parent 
widget to tell it's children what it's name is. In addition there will 
be two method for retrieving names from widgets: one for retrieving the 
form name which will be a combination of the parent's widget's form name 
and the name of the widget itself and another for retrieving the name 
assigned to the widget. What do people think? Is it a worthy idea?

--
David "Spartacus" Whittington