On Friday, 13. October 2006 17:11, [EMAIL PROTECTED] wrote: > On 13 Oct 2006 at 10:53, Also Sprach Matt Sergeant: > > On 13-Oct-06, at 7:39 AM, [EMAIL PROTECTED] wrote: > > > I thought I'd move some code from my plugin and put it into its own > > > plugin. However, the methods in the new plugin need to be used by > > > the first plugin. How do I go about doing this? > > > I presume I need to somehow put the new plugins object ref into > > > $plugin... > > > > Could you write a separate perl module and "use" it in both? > > Ah, yes. I'll give it a go. > I was thinking more in the lines of an actual plugin though. ie > set up in the config file and all that. With access to the AxKit2 object > etc. > I am writing a few methods for xml caching and I thought if it got > more configurable etc I would put it in its own plugin so others could > use it...
Check out the new messaging system that's in SVN. (You should already have it if you upgraded recently). It allows you to register "message handlers" (callbacks) that can be called from any plugin. See the docs of AxKit2::Plugin for details. -- CU Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
