|Java menu knowledge base|
DHTML menus are toys - java menus are serious!
are "platform-independent", which means that when you write something
using these kinds of code, it will run on all sorts of different
platforms (i.e. all sorts of computer-types). This "platform-independence"
is important for the internet, as you never know what kind of computer
that are spelt like java commands. But the similarity stops here.
Java is a full-blown programming language, and its results are
"compiled" into small independent files (known as, for example, applets, servlets,
beans and applications)
which cannot be read by human eye and which execute very fast
when embedded in a web page. It is a powerful, efficient language and can create highly
interactive web page elements. Unlike DHTML menus, java menus can
be highly scalable (i.e. handle big indices without loss of performance). Java
menus have a number of other advantages as well, which stem from java's maturity
as a compilable programming language.
extension to HTML with code in the web page itself that can be read
and written by most web designers. It is simpler and
more limited than java. It is also much more vulnerable to
much more limited than java, it does have a few additional tricks up
is better at manipulating or modifying HTML code dynamically. Neither
of these features are needed for menus!
DHTML is not a programming language at all. It is
a feature of most version 4+ browsers. This feature allows the HTML to be modified
dynamically. You can modify the HTML (i.e. "take advantage of the DHTML-feature")
talk about "DHTML as a programming language", they usually mean "I'm using
means that there is usually NO difference whatsoever between a "DHTML menu"
A summary of some of the main disadvantages of DHTML:
- DHTML menus can't framebust; we can
- DHTML menus can't pop over Macromedia Flash, other applets or plug-ins; we can
- DHTML menus have to be inserted into every page; we only need one page
- DHTML menus face high compatibility problems
- DHTML menus have a large bytesize; we compress
- DHTML menus aren't scalable; we can handle vast indices