We recently built a site using Apache::ASP and DreamWeaver (seawa.org.au). By the sound of it you're on the right track, separating perl logic and html stuff, but you may be overcomplicating it, trying to run separate .pl files. (Which you could do with the 'require' perl keyword, BTW)
Firstly its best to keep subroutines to either .pm module files or to the global.asa. Its a pretty annoying thing (from mod_perl I think) but putting subroutines inside asp files or separate .pl files seems to cause issues and weird side effects. In point form - put reusable functions into global.asa and you'll be able to sit back knowing you can change them easily without weird side effects - don't be scared to put Apache::ASP code inside the .asp files. We did this and DreamWeaver handles it really well. It shows up in the WYSIWYG editor and the graphics guys had no trouble working around it. It also worked well putting it in templates etc. If you want something to run before the script starts look at the onScriptStart() (its something like that; can't remember off hand) in the global.asa. We used that for some clever password logic so you're guaranteed the password is checked no matter what page is requested. HTH Ellers At 5:02 PM -0500 5/6/02, Broc Seib wrote: >Hi, > >I can write an asp app like this: > >-------------------------------------------------------------- > <% > ## the top half of this file is where the bulk of my > ## code and app logic lives. In the end it produces > ## a data structure that represents what needs rendered > : > code > code > code > : > $my_struct = data that needs displayed on this page > %> > > > <some html> > <% render some of the page based on $my_struct %> > <some more html> > <some more html> >-------------------------------------------------------------- > > >It would be nice if I could split it up like the following: > > myapp.pl ## top half > myapp.asp ## bottom half > >The file myapp.pl would just contain code, subroutines, logic for >the app, basically ending with creating a data structure. > >The file myapp.asp would be the asp code/html to render the page >based on the data structure from the first file. > >This means I could better serve our staff w/ DreamWeaver type tools, >and tell them to just edit the .asp files and leave the .pl files alone. > >Couldn't Apache::ASP suck in a .pl file by the same name first if it >exists (and the conf file says to do so)? > > >-b > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
