 |
What is DHTML?
|
Dynamic HTML or DHTML is a method of creating interactive
web sites by using a combination of static markup language
HTML, a client-side scripting language (such as JavaScript),
and the presentation definition language Cascading Style Sheets
and the Document Object Model.
It may be used to create applications in a web browser: for
example to ease navigation, to create interactive forms or
to create interactive exercises to use in e-learning applications
such as WebCT. Because it can be used to dynamically move elements
around the screen, DHTML can also be used as a tool for creating
browser based videogames.
DHTML applications that are entirely self-contained in the
browser, without server-side support such as a database, are
sometimes referred to as Single Page Applications, or SPA.
See Comparison of layout engines (DOM) for a detailed list
of the API available in each browser to use in DHTML applications.
Competing techniques include Macromedia Flash for animation
and applets.
Some disadvantages of DHTML are that it is difficult to develop
and debug due to varying degrees of support among web browsers
of the aforementioned technologies and that the variety of
screen sizes means the end look can only be fine-tuned on a
limited number of browser and screen-size combinations. Development
for recent browsers, such as Internet Explorer 5.0+, Netscape
6.0+, and Opera 7.0+, is aided by a shared Document Object
Model.
About
this Tutorial
This tutorial is from The
Wikipedia which is published under the
GNU Free Documentation License.
 Transforming a Generic Java IDE to Your Application Specific IDE
One of the biggest challenges in application development today is how to factor in application-specific information. The answer lies in the ability to capture application evolution and developers' knowledge of building and extending the application as metadata so that it's not lost in time or translation. Once that can be done effectively, the combination of the application code along with application-specific metadata can be meaningfully packaged into reusable software asset modules. This white paper will discuss how 'Application Factories' can transform an IDE to play a central role in capturing both the application evolution and the developers' knowledge.
Request Your Free Whitepaper!
|
|
