|
On Tue, 13 Nov 2001 20:45:32 -0600 "Hall, Philip" <phall@spss.com> wrote: > Brad, > > > Again, as I said before, this is all one which source > you > > use. DHTML, in it's entirety (since it's definition > and > > uses keep changing) is using CGI, Javascript, and > > stylesheets or any combination of these. > > I think(*) you might be talking about dynamic HTML > creation (server-side) > rather than DHTML in the WC3 sense, where you have much > more control over > the placement (in real-time, based on user interaction) > of the page elements > within the browser withoou having to ask the server to > recreate/resend the > page. > > > (*) but I could be wrong No, you're right. But, the code needed for this "real time" interaction can be created by CGI, and a lot of the time is. Again, it's mainly Javascript and stylesheets that allow this real time interaction. Everything already exists as part of the web page (either embedded in the HTML or externally, like a CSS). There is no client/server interaction with DHTML to change fields, etc... It's HTML with a supercharger, but still HTML. It's not like an applet where there is actual client/server interaction. Whether it's dynamically created on the server, or static files that already exist, it's still DHTML, even in the W3C sense. Brad www.bvstools.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.