Forum OpenACS Q&A: Response to OpenNSD - should we or shouldn't we?

Collapse
Posted by Andrew Piskorski on
A central place to list and organize all AOLserver patches, contributed code, and the like would be useful.

Additionally, a lot of the OpenACS tcl code is in fact very useful in a non-ACS AOLserver environment, but as the code is currently structured, it's a significant pain to actually use it outside of OpenACS.

I would personally like to start refactoring some of packages/acs-tcl/tcl/*.tcl to work more easily in non-OpenACS environments, however, I've been refraining from suggesting it until I actually have the time to do the work.

I've personally successfully used the following ACS Tcl stuff outside of (Open)ACS:

  • ad_proc
  • ad_page_contract
  • db_api (and enhanced to support multiple databases)
  • Watchdog
  • util_memoize
  • Misc. various other utilities
  • Other OpenACS Tcl code which would be useful outside of OpenACS, but which I've never used, probably includes:

    • the Templating system
    • possibly the request processor in general, and certainly the part of it which lets you eliminate the .html, .tcl, or whatever file-name extension from your URLs.
    • basically anything that doesn't use the OpenACS database schema.