I know its reinventing the wheel.
I am not outta school and eveything Pc related was self tought.
The content on the page is what i am least concerned about, my view is unless i understand it then i wont use it. The best way to understand it is do it yourself. I think there is far more satisfaction in doing it myself than using something someone else has done and accepting it to be the best i can do. Besides all that its just fun trying to do it myself and when its done i can say i did it. Maybe its an ego thing.
Regarding changing it from frames to server-size includes or a dynamic site. Uhm...I have very little clue as to what you are reffering to, will check out and see what conclusion i come to.
I came across a page that had something called liqued effects... really neat page. Had a marquee scrolling up and changed its layout according to the window size.
Otherwise thanks for the time and the feedback. Greatly appreciated.
Edit:
Classical hypertext navigation occurs among "static" documents, and, for web users, this experience is reproduced using static web pages. However, web navigation can also provide an interactive experience that is termed "dynamic". Content (text, images, form fields, etc.) on a web page can change, in response to different contexts or conditions. There are two ways to create this kind of interactivity:
Using client-side scripting to change interface behaviors within a specific web page, in response to mouse or keyboard actions or at specified timing events. In this case the dynamic behavior occurs within the presentation.
Using server-side scripting to change the supplied page source between pages, adjusting the sequence or reload of the web pages or web content supplied to the browser. Server responses may be determined by such conditions as data in a posted HTML form, parameters in the URL, the type of browser being used, the passage of time, or a database or server state.
The result of either technique is described as a dynamic web page, and both may be used simultaneously.
Client-side
The Client-side dynamic content is generated on the client's computer. The web server retrieves the page and sends it as is. The web browser then processes the code embedded in the page (normally JavaScript) and displays the page to the user.
The innerHTML property (or write command) can illustrate the "Client-side dynamic page" generation: 2 distinct pages, A and B, can be regenerated (by an "event response dynamic") as document.innerHTML = A and document.innerHTML = B; or "on load dynamic" by document.write(A) and document.write(B).
The problems with client-side dynamic pages are:
Some browsers do not support the language or they do not support all aspects (like write command and innerHTML property) of the language.
The information cannot be stored anywhere but the user's computer, so it cannot really be used for statistics gathering.
Search engines are not able to run client-side languages and cannot crawl links generated by them.
Some users have scripting languages disabled in their browsers due to possible security threats.
Ajax is a newer web development technique for creating client-side dynamic Web pages. Google Maps is an example of a web application that uses Ajax techniques
Server-side
Server-side dynamic content is a little bit more complicated.
The browser sends an HTTP request.
The server retrieves the requested script or program.
The server executes the script or program which typically outputs an HTML web page. The program usually obtains input from the query string or standard input which may have been obtained from a submitted web form.
The server sends the HTML output to the client's browser.
Server-side has many possibilities for dynamic content, but the use of it can be a strain on low-end, high-traffic machines. Some web sites use the Robots Exclusion Standard to keep web crawlers from accessing dynamic pages for this reason. If not properly secured, server-side scripts could be exploited to gain access to a machine [needs citation].
So if Wiki is right in its description then my page is dynamic...
It takes parms, commands and a location from the query string and proces's them, then if the user fits the auth lvl for the content, retrieves the content from a text file and prints it to xHTML.
