Sunday March 19th, 2000
#1 As Clear as Mud
by TonyG <firstname.lastname@example.org.Yuk>
Sunday March 19th, 2000 4:48 PM
You should be using the DOM for access to page elements, the version of JS is probably irrelevant
#3 Re: Re: As Clear as Mud
by spacecow <email@example.com>
Sunday March 19th, 2000 8:34 PM
Right you are...Mozilla uses the W3C DOM-1 spec, and parts of the DOM-2 spec. It does not include either IE DOM elements, or old Netscape 4.x DOM elements (except where they happen to match the W3C spec)
#7 Link doesn't work for me, either (n/t)
Monday March 20th, 2000 7:55 AM
You can click here to do this
you can click here to do that
Didn't that style of web page go out in about 95?
#9 Re: click here?
by mykmelez <firstname.lastname@example.org>
Monday March 20th, 2000 11:03 AM
No, riddley, this way of making links has never gone out of style, but it's worth mentioning again why it has never been considered the best way to do things:
When a user encounters a non-descriptive link (f.e. 'you can -click here- to visit the Rhino page' instead of 'you can -visit the Rhino page-') they must look elsewhere to figure out the target of the link and then back to the link to go to that target. This takes a miniscule amount of extra time and causes a very small amount of frustration, but the time and frustration are not insignificant, and they make reading a web page more difficult and less enjoyable than it needs to be.
The secondary problem is that a small link like '-here-' is more difficult to hit with the mouse, again necessitating extra time and frustrating precision. That's why in the example above I suggest making the words 'visit the Rhino page' a link instead of just 'Rhino page'.
Both engines are already being used in non-Mozilla, non-Netscape projects, in fact.
No, I don't meant a version that can be embedded into a browser, server or what ever (so far I understood this concept :-). I meant it as a stand-alone application, like the perl interpreter, e.g. that I can type in my shell:
so that the file "helloworld.js" is loaded and executed, and after execution, the interpreter stops. This not only requires a simple wrapper around the embeddable engine, but also a (portable, system independant) library which gives access to system resources, e.g. file/directory/network access. Maybe this already exists, but I haven't seen anything like. If you know something like, please give me a pointer...
The js shell is here: <http://lxr.mozilla.org/se…monkey/source/js/src/js.c>
I've been using spidermonkey... I'm interested in reading XML using DOM, but in my own project... not Mozilla. I have spider monkey embedded already. Is there a DOM implementation I can include? (or is it already included, and I'm too ignorant to find it?)