Duh. The first argument to the constructor is the class. I feel really, really stupid right now. I've got to remember not to ask questions whilst hung over.
-- Cheers, Curtis Poe Senior Programmer ONSITE! Technology, Inc. www.onsitetech.com 503-233-1418 Taking e-Business and Internet Technology To The Extreme! ----- Original Message ----- From: "Curtis Poe" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, August 08, 2002 10:41 AM Subject: [Templates] Runtime determination of plugin name > I'm sure this is answered somewhere in the docs, but I can't find it (I'm > curious why Google returns no matches when doing a site: search on > template-toolkit.org). > > When I use a plugin -- [% USE my_plugin %] -- how can a plugin determine its > own name? I am building stuff that uses plugins in some strange ways and it > would be helpful if a plug can "self-identify". I started out by doing > something like the following: > > [% USE my_plugin "some_identifier" %] > > However, having to pass that identifier every time means a chance for a typo > every time. > > To forestall the inevitable "why": I have pages that can have multiple > plugins that are forms. When a user fills out a form and submits it, each > plugin on the page checks to see if it "owns" the form data. It does this > by adding some identifying data to the original form data. If it owns it, > it can process it. Otherwise it ignores it. > > -- > Cheers, > Curtis Poe > Senior Programmer > ONSITE! Technology, Inc. > www.onsitetech.com > 503-233-1418 > > Taking e-Business and Internet Technology To The Extreme! > > > _______________________________________________ > templates mailing list > [EMAIL PROTECTED] > http://www.template-toolkit.org/mailman/listinfo/templates > _______________________________________________ templates mailing list [EMAIL PROTECTED] http://www.template-toolkit.org/mailman/listinfo/templates
