JavaScript API??

[JS]

Is there an API for JavaScript like for normal Java? I would like to which
methods it possible to call on a "document" object as an example.

[Hal Rosser]

"JS" <[e-mail]> wrote in message news:d7**********@news.net.uni-c.dk...

Is there an API for JavaScript like for normal Java? I would like to which
methods it possible to call on a "document" object as an example.

there's a good reference here
www.devguru.com

[DKM]

JS wrote:

"DKM" <de**************@hotmail.com> skrev i en meddelelse
news:11**********************@g44g2000cwa.googlegr oups.com...

JS wrote:

Is there an API for JavaScript like for normal Java? I would like to which methods it possible to call on a "document" object as an example.

You may be thinking about the various interfaces exposed by the DOM.
You can view them here

http://www.w3.org/TR/REC-DOM-Level-1...-one-html.html

Thats for DOM1. Then you have the newer DOM2 and DOM3.

Hmm could not find anything on the "onChanged" method and the "onload"
variable. These are just some of the build in fuctions that I stumple over
all the time and have no idea on where to find more info on.

Where should I search to find a description on all these functions and
variables??

Sorry about that. Try here:

http://www.mozilla.org/docs/dom/domref/

D.K. Mishra

[JS]

"DKM" <de**************@hotmail.com> skrev i en meddelelse
news:11**********************@g49g2000cwa.googlegr oups.com...

JS wrote:

"DKM" <de**************@hotmail.com> skrev i en meddelelse
news:11**********************@g44g2000cwa.googlegr oups.com...

JS wrote:
> Is there an API for JavaScript like for normal Java? I would like to

which

> methods it possible to call on a "document" object as an example.

You may be thinking about the various interfaces exposed by the DOM.
You can view them here

http://www.w3.org/TR/REC-DOM-Level-1...-one-html.html

Thats for DOM1. Then you have the newer DOM2 and DOM3.

Hmm could not find anything on the "onChanged" method and the "onload"
variable. These are just some of the build in fuctions that I stumple over all the time and have no idea on where to find more info on.

Where should I search to find a description on all these functions and
variables??

Sorry about that. Try here:

http://www.mozilla.org/docs/dom/domref/

This is the thing that I was looking for:

http://msdn.microsoft.com/library/de...ence_entry.asp

[Marcin Stêpnicki]

Dnia Thu, 26 May 2005 23:15:52 +0200, JS napisa³(a):

http://www.mozilla.org/docs/dom/domref/

This is the thing that I was looking for:

http://msdn.microsoft.com/library/de...ence_entry.asp

If you want your applications/webpages to work both in standards-aware
browsers (Gecko-based and Opera) and Internet Explorer, you actually need
both links.

--
Deep abysses I sink into and behind the light I go| http://apcoln.linuxpl.org
Now playing: Nothing | http://biznes.linux.pl
--------------------------------------------------| http://www.juanperon.info
JID: Ar**********@jabber.org | http://www.naszedzieci.org

[RobG]

JS wrote:
[...]

This is the thing that I was looking for:

http://msdn.microsoft.com/library/de...ence_entry.asp

Be careful, *always* read the standards information at the bottom of
the page.

The following are my interpretations of the more common statements:

1. Reference to a W3C standard - good to use with appropriate
feature testing.

2. "DOM Level 0", which means essentially legacy support, so likely
well supported but may be depreciated or less well supported in
future.

3. "There is no public standard..." - a Microsoft invention that may or
may not be supported by some other browsers. Use with caution, test
thoroughly and provide an alternative (e.g. innerHTML, innerText).

4. "This ... is a Microsoft extension to ... " - probably will only
work in IE, but there may be alternatives for other browsers.
e.g. XML Element or xml Object
Others may have some to add or different views...
--
Rob

[Richard Cornford]

RobG wrote:

JS wrote: <snip> 2. "DOM Level 0", which means essentially legacy support,
so likely well supported but may be depreciated or less
well supported in future.

<snip>

It is unlikely that HTML browsers will drop support for 'DOM Level 0' as
the features are so widely used at present that any new browser that
does not implement them will appear to be broken with much of the
Internet. Which would make them unattractive to users. And there are
moves to formally standardise much of what is considered 'DOM level 0'.

Richard.

[Michael Winter]

On 27/05/2005 05:28, RobG wrote:

[Microsoft documentation]

1. Reference to a W3C standard - good to use with appropriate
feature testing.

Be careful here. There is more than one occasion where Microsoft have
implemented a W3C-defined property, referenced the standard (usually a
draft, not the recommendation), but entirely failed to follow the
definition (or exhibit additional, undocumented behaviour that defies
that definition).

If you really want to use a standardised property that you're not
familiar with, always compare the official version against Microsoft's.

Two obvious examples are the document.getElementById and
HTMLSelectElement.add methods. The former will return a named element if
it cannot find an element with a matching id (undocumented), and the
latter has a fundamentally different signature. There are others, but I
can't think of them at the moment.

[snip]

Mike

--
Michael Winter
Replace ".invalid" with ".uk" to reply by e-mail.

[Thomas 'PointedEars' Lahn]

Richard Cornford wrote:

It is unlikely that HTML browsers will drop support for 'DOM Level 0'
as e features are so widely used at present that any new browser that
does not implement them will appear to be broken with much of the
Internet. Which would make them unattractive to users. And there are
moves to formally standardise much of what is considered 'DOM level 0'.

URL?

BTW: DOM Level (1 and) 2 HTML already standardize parts of DOM Level 0.
PointedEars

[Thomas 'PointedEars' Lahn]

Hal Rosser wrote:

there's a good reference here
www.devguru.com

No, you have been cheated on. For example, alert() was never
specified in ECMA-262 and is not specified in its current edition.
PointedEars