Forum OpenACS Improvement Proposals (TIPs): Tip#131 (rejected) auto-mount acs-templating
I propose auto mounting acs-templating under /acs-templating for this.
We have been running with this on production sites for quite a while now, and I thought we had previously discussed or implemented this.
What about moving the editors to their own plugin type package that could be mounted if necessary? Define an interface for editors... store config info within each package instead of stuffing params into acs-templating for each new editor we want to support?
I think to actually release 5.5 we need to compromise and do this and think about an ideal design for the future.
I think we can move these into seperate packages, as they are optional, for the next release after 5.5 if someone wants to volunteer to come up with a design and do the work.
If others agree that this seems messy and is not an acceptable long-term solution, someone who's fiddled with the wysiwygs (and probably the person who originally stuck it all into acs-templating, if they're still around) should do some thinking about this now, while it's fresh and in front of us. Even if the work can't be done now, we should at least have an idea of how to move forward.