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

Collapse
4: Re: How to handle dotlrn-specific changes in core? (response to 1)
Posted by Andrew Grumet on 06/12/04 05:30 PM
That solution has the virtue of simplicity, it's much simpler than a callback mechanism.  But each specialty override would then have to carefully track changes in the original.  Sounds risky, no?
Collapse
5: Re: How to handle dotlrn-specific changes in core? (response to 4)
Posted by Malte Sussdorff on 06/12/04 05:57 PM
If .LRN wants to make changes to OpenACS core that are only applicable for .LRN, there is always the risk that other pages use the normal OpenACS API and therefore break. But this is live after forking ;).

On the other hand, the above approach has a *huge* drawback. If you reload the original TCL of OpenACS core, you will get the OpenACS function back, not the .LRN one. It is something all developers would have to be taught (if you use .LRN do not reload packages, but restart the server).