in reply to Re: Seeing Perl in a new light
in thread Seeing Perl in a new light
Your Mother...Hopefully I will only need this one file to build the framework for all of the rest. I am thinking about naming it base.pl then do "base.pl" on every page of the site or something similar. If I understood the module making mojo, I would probably be able to use base, but that requires more than I know now.
The first thing I need to know is how to grab file and directory names. I haven't been able to find anything on google about getting things from the environment, if that is the correct term. Then I have to learn how to write a regex. Fun, fun, fun.
As for the other files, the ones that I do not want to include in the navigation, do not worry. I will still be using my css file, images, and any javascripts that can not be replaced with Perl. What I was discussing is where to put them. See below.
/root /files - Where everything that is not meant for the viewing public goes. -or- /root /css - Where my style sheet(s) will go. (I may break it up into smaller pieces.) /images - Where my images will go. /javascripts - Where my javascripts will go. /other - Where everything else that is not meant for the viewing public goes. -or- /root /files /css - Where my style sheet will go. /images - Where my images will go. /javascripts - Where my javascripts will go. /other - Where everything else that is not meant for the viewing public goes.
When I write the navigation, I will exclude those directories from it. I am just not sure which way I want to go right now. Currently, I have everything crammed into the root directory that is site wide like my style sheets, images, etc. I may go with the first or third option, since it would be easier to exclude just one directory, than four or more.
|
---|