Forum OpenACS Development: acs-tcl package

11: acs-tcl package (response to 9)
Posted by Andrew Piskorski on
Yes, it sure would be nice to be able to take the stock OpenACS acs-tcl package (with ad_proc, ad_page_contract, the db api, watchdog procs, etc. etc.), drop it into a plain old AOLserver with no OpenACS, and have it Just Work. Last time I did something like that, it required lots of fiddling just the parts I needed to work at all.
13: Re: acs-tcl package (response to 11)
Posted by Malte Sussdorff on
Hi Andrew, could you do the effort again (taking out the acs-tcl package) and clean it up so that:

- All procedures that are required by acs-tcl that are independent of OpenACS but somehow made it into a different directory, are moved into acs-tcl.
- All procedures in acs-tcl that rely on code in OpenACS are moved to acs-kernel.

If I'm not mistaken this should enable us to maintain an acs-tcl package that is clean of OpenACS dependend code and can be reused everywhere else. We might even upload all these enhancements to the AOLserver CVS 😊.

I'd assume if we want to make a policy out of this, we would have to TIP this, therefore it would be nice to get some feeling if people agree to be doing this. I for myself am sold to the idea and it makes a lot of sense to me (as I was always wondering why we have acs-kernel and acs-tcl and this differentiation posted by Andrew makes utter sense and should be published in guidelines).

14: Re: acs-tcl package (response to 13)
Posted by Andrew Piskorski on
Malte, since it's clear now that other people would like it too, yes, I'm willing to work on acs-tcl as you describe. Not right now though, and I can't give you a timeline either, as I have other things on my plate at the moment. But I'll definitely add it to my list as of now.