On 9/19/05, Peter Speltz <[EMAIL PROTECTED]> wrote: > On 9/18/05, Frank Carnovale > Like if I prefer to use FB > objects in templates rather than hashes of HTML Elements, the > interface should be the same that gets the object or hashes there and > they should get put into the same template variable (I think anyway) > and I hate to say it but that should probably be classmetadata.cgi. > Seems as good a place as any to me. > > (There issue with classmetadata was just about not making cgi for > every page right? Or was there more to it than that?) >
opps. I forgot that the standard way of using FB is from the template. Is that right. In which wase the object would no need to get assigned to FB. I'm starting to come around and believe making inputs in the templates is the way to go, too. I think it is easier to maintain if you know all inputs are made in the Templates rather than , View or Model class or Templates as it is now. If the in the long run I believe. I think I will patch to_cgi so it can be used in a template. Currently, it returns a hash but I think with a wantarray check, it could return a hash ref to a template. I'm thinking as I think Dave H and Dave B are that moving the input making to the templates would unhook Maypole from form making altogether and make maintaining and evolving easier since users are expected to override the templates. The out of the box functionality would not change at all. -- pjs ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Maypole-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/maypole-devel
