http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7804
--- Comment #26 from Kyle M Hall <[email protected]> --- I've been thinking about this issue all night. I can understand your motivations and thinking behind the necessity of using Module::Load::Conditional. Could you describe the changes that would need to be made in order to implement it correctly? Here is the current workflow: 1) A plugin is uploaded to the plugins directory. 2) The plugins.ini is parsed, this tells which which about the starting file only. 3) Koha gives a link to the plugin starting file. 4) The file is executed, is authenticates itself, and loads its template files independently of the internal Koha templating system ( TT is used for templates only because we can be sure TT is available, and also it is simply better than other templating systems, though a plugin could just as easily output html from the perl file or use HTML::Template ). 5) At this point, control is passed completely to the plugin, which is responsible for any subsequent perl file execution. Step 5 is where things will definitely change. As it stands, step 4 can be modified to use M:L:C easily, but step 5, not so much. I think step 5 will involve the plugin itself calling M:L:C via Koha::Plugins to continue its execution. If you could describe the workflow necessary for implementing M:L:C, it would help me out greatly. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
