What I thought 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.
Eeek I wasn't looking to start a flame war :-( Twas just a suggestion thats all. Having started in plain AOLserver then moved on to OACS I find that the tcl/adp templating system is very productive and the results are very clean. What I was suggesting was as an option rather than compulsory.
I just like the fact that I can write a /foo/bar/index.tcl page containing a db query, and write a corresponding /foo/bar/index.adp page which displays the results of the query using the custom tags Vlad mentioned and call it with /foo/bar/index. I don't have to escape anything, I don't have to find the file containing the proc which is registered to that url, I can look in /foo/bar and know that the logic is in the tcl and the presentation is in the adp.
However, even with the OACS toolkit loaded I can still write a single tcl page, and adp page containing tcl code, a registered tcl procedure returning html or a tcl/adp pair - no options are lost its just an alternative.
Steve
-- 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.
