From: Peter D. <pet...@us...> - 2003-05-08 14:44:31
|
I=92d like to extend the template plugin functionality provided in OpenInteract/Template/Plugin.pm, which is called from templates with a OI.method() type syntax. I have my own perl object module with some functions to produce HTML for things like hyperlinks with javascript popu= p context menus. I guess in OI terminology this is a component. I use perl because the logic is too complex to fit into a template widget, and I mig= ht want to upgrade to a cross-browser javascript library like DOMAPI later. For now I am calling $R->template->handler() and passing in a pointer to = an object B, which is my equivalent of OI, and calling B.popup() in template= s. I didn=92t want to change the provided OI plugin code in case it is updat= ed. What is the best way of integrating my library component ? Also, for installation, I see oi_manage either installs a handler in an a= rea (e.g. oitest/pkg/fruit-0.15/oitest/Handler/Fruit.pm) or has a special cas= e for OI components, for example to install base_theme/OpenInteract/Theme.p= m one level about the Handler directory, but I cannot install my own site-specific module. Do I need to install components by hand or is there a better way ? Inspecting @ISA it looked like I could put my module in the oitest top le= vel directory which is where I put it for now. I did not want to put it in site_perl in case I use different versions in different customer areas. Although this works I have the repository tool grumbling it cannot find m= y module when it does a package check. Am I installing to the right place ? Thanks, Peter --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.478 / Virus Database: 275 - Release Date: 06/05/2003 |