[Home] [Groups] - Message: [Prev in Group] [Next in Group]
4575: Re: [MUD-Dev] Java and Javascript
[Full Header] [Plain Text]
From: coder@ibm.net
Newsgroups: nu.kanga.list.mud-dev
Date: Fri, 13 Feb 98 16:15:06 -0800
References: [1]
Organization: Kanga.Nu
On 28/01/98 at 07:10 PM, Greg Munt <greg@uni-corn.demon.co.uk> said:
>Hope you can help me. I'm looking to implement some sort of graphical
>client, within a web browser. I know that this has been done before,
>without requiring the page to be reloaded. They used either Java or
>Javascript, can't remember which.
Of necessity it would be JavaScript. Java can be embedded in Web pages,
be used for standalone applications, etc. Javascript can only be embedded
in web pages.
>IIRC, Java is useful on the networking side, whilst Javascript is useful
>when you need firm control of the browser itself. Does anyone care to
>supply advantages/disadvantages of each, and what each should be ideally
>used for?
Iwoudl start with arguing why the browser interface is actually useful to
you as a MUD interface. Note that I am not arguing against using the
broswer interface to reach to the MUD, but using the browser interface
during your MUD interactions. I don't see much use for Forward and Back
buttons while MUDding, or Bookmarks, etc.
It makes more sense to me to have the browser lauch a Java application ala
plug-in.
>Should I be looking at both Java *and* Javascript, to complement each
>other, or should I concentrate on using just one of them? How much of the
> Java/Javascript functionality does the potential DHTML/DOM standard
>encompass?
Not much. See www.w3.org.
--
J C Lawrence Internet: claw@null.net
----------(*) Internet: coder@ibm.net
...Honourary Member of Clan McFud -- Teamer's Avenging Monolith...