On Mon, 30 Nov 2009 10:57:49 -0500 "Joe Pepersack" <j...@pepersack.net> wrote: > Define empty methods in your autohandler and override them in your > component. > > In autohandler: > <%method footer></%method> > > In my.comp: > <%method footer><& footer.comp &></%method>
Sorry for the confusion there, the fact that the arg was named "foot" had nothing to do with this (placing a footer in the component) -- it was just to indicate whether the component was being called as a popup, or at the bottom of the page. So there are some slight mods to the content. This format modification is the same for all the notes, so I didn't want to repeat the code in all of them, which putting them in a directory with an autohandler seemed a good idea, etc. 'cept the autohandler can't be given aa binary option (render as popup, or render as footer) without args. Ie, the note itself is basically just text. I guess I could also do this by calling a generic component (either popup or footnote) with the specific note-component as an argument (right now I am calling the specific note with an arg to pass to the generic formatting comp). BenRifkah Bergsten-Buret <mail.spammag...@gmail.com> wrote: > I don't know if it's documented but I'm able to get access to the cgi > parameters within the autohandler by doing this: > > my %args = @_; Thanks for that! No, I did not find any reference to it in the docs -- it is as if it had not occurred to anyone to supply an arg to the autohandler, which seems obvious to me! (otherwise it is just a static wrapper). MK ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
