..:: notes ::..
In this example, I have used a far more linear approach
than I typically would - I prefer to create "modules" that
can be invoked, (such as server-side includes) to enhance
maintainability, and reusability.
I chose this linear "fall-from-the-top-through-the-bottom"
approach to make the functional flow of the code easy to
follow.
My typical methodology would have been to break up the
application into many small, single-purpose components that
each had a highly focused role - use, and re-use them
throughout the application, or in several applications.
There are many "snippets" of code that I have developed
over the years that I continue to re-use, and that are in
use all over the world, such as my auto-copyright, as seen
at http://www.devx.com/tips/Tip/15913. This has been used on countless websites.
Simply stated, I believe in simple elements with real-world usefulness!
In a real-world application, I would have separated out the
VBScript functions, the meta tags (as an ASP include), the stylesheet
(this I have done even in this example for the sake of brevity), the
JavaScript functions, and probably would have created a reusable header and a footer. Most likely, I would have created
a "themes.asp" as an include, for constants. (I use the ".asp" suffix instead
of the common ".inc" because ASP includes are not directly readable over the
web, where INC includes are. This function, as a real-world application, would have also had a global.asa.
I would have also separated the logic from the presentation tier to the extent possible.
Don Demrow, 2005.05.09