Forum OpenACS Development: Re: How to handle dotlrn-specific changes in core?


	The Toolkit for Online Communities 15939 Community Members, 0 members online, 2258 visitors today			Log In	Register

Forum OpenACS Development: Re: How to handle dotlrn-specific changes in core?

OpenACS Home : Forums : OpenACS Development : Re: How to handle dotlrn-specific changes in core? : One Message

Back to OpenACS Development

26: Re: How to handle dotlrn-specific changes in core? (response to 1)

Posted by Andrew Grumet on 06/15/04 03:06 PM

Oy, sorry for the multiple corrections here. APM's actually a little different. The APM callbacks are for specific, one-time events for specific package versions. I'm pretty sure we wouldn't expect to invoke the "after-install" callback for acs-content-repository v5.1.0 multiple times with different arguments. The same can't be said for a hypothetical "on member state change" for user 123456.

27: Re: How to handle dotlrn-specific changes in core? (response to 26)

Posted by Jeff Davis on 06/15/04 03:27 PM

It's also worth pointing out that "naming conventions" have worked well for ad_page_contract and acs-templating (the template::widget::BLAH procs and ad_page_contract_filter_proc_BLAH procs are good examples of what I was thinking of).

Back to OpenACS Development