Hi all,
I was talking about how we could override default Koha modules with customized versions by just making sure those modules were located earlier in @INC. That got me thinking. at the moment we put Koha Plugins at the bottom of @INC, but we could actually put them at the start of @INC. They would be more dangerous as they'd be able to override any Perl module. but they would also be more powerful. In the context of a Koha where controllers are Perl modules (e.g. Mojolicious controllers) rather than Perl scripts, a plugin could override any controller in Koha. That could make for very powerful and seamless customizations. Anyway, something to think about. Cheers, David Cook Software Engineer Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
