|
Introduction
The web evolved from static web pages. As a result the mindset of web
developers since then tended toward the belief that a web site must consist of
many separate pages. But the game has changed a lot from the early days. Now we
can do incredible things with the web. One of these things is the ability to
program a web site.
More ...
Scaling single page sites
"OK", you're probably thinking, "what do you do when the site
is huge and very complex?". You simply do what programmers typically do
when an application gets complex. You break it down into logical, well named
blocks and move them to another file.
Using query strings to "compress/decompress" a page
This page illustrates this technique. When you click on the
"More ... " link, the query string value for "decomp" is "intro"
is used to call the "showIntro" Sub, which contains the rest of the text
for the Introduction. This link, "Show Code", has for it's "decomp" value, "code" and
also targets a bookmark demonstrating that you can also open a page where you want
Show code
Using query strings to
simulate a "normal" web site
The "Single Page Web Sites" link from the menu on the left takes you to the tutorial
that illustrates how this is done. When using this method, index.asp will appear to be an
entire site. Only by noting the URL in the address box of the browser will the real
nature of the site be revealed.
Using query strings and form
values to run a application on a single page site
The "RAD Applications" link from the menu on the left takes you to the tutorial
that illustrates how this is done. It demonstrates how to call subs and functions
on single page sites while at the same time shows the methodology that I typically use
to develop my applications.
Recommended Reference:
To find out more about the pros and cons of using includes and server.execute see
Michiel van Otegem's fine article:
To include or not to include?
Other articles:
|