On Fri, Aug 13, 2004 at 01:10:43PM -0400, Dossy Shiobara wrote: > was being said was some pairing of ".adp and .tcl" meaning for each > "page" there would be an .adp file AND a .tcl file that gets sourced > when the .adp is requested -- yikes.
You may or may not prefer it, but there's no "yikes" about it, it works quite well, and efficiently too. In AOLserver, Tcl code can be defined in a .tcl page, or it can be defined in a server-wide Tcl proc. These two locations for defining Tcl code aren't exactly all that different from each other. In the case of the OpenACS Templating System (and in all versions of ACS back to somewhere around ACS 3.4 or so), the .tcl pages are in fact compiled to Tcl procs and cached on first use, which eliminates any performance difference between the two places Tcl code can "live". It would be nice if some of the really handy page-oriented OpenACS procs, like ad_page_contract, ALSO worked the same way for procedures. It would also be nice if the Templating System implemenation could be cleaned up a bit and made easier to hack on. These are, however, quite minor complaints, and never bothered me much back when I was using the Templating System on a regular basis. Also, some of them have even been partially addressed already, e.g.: http://openacs.org/forums/message-view?message_id=197740 -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
