[sword-devel] Web Interface
sword-devel@crosswire.org
sword-devel@crosswire.org
Sun, 23 Feb 2003 19:13:13 EST
--part1_8f.29e54be3.2b8abd99_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In a message dated 2/22/2003 7:53:49 PM Pacific Standard Time,
m.p.donadio@ieee.org writes:
> And I reply:
>
> Yes, you are correct. Technically, all of those broswers support
> JavaScript, but without the proper DOM support, what use is JavaScript
> in a browser for real applications?
DOM level 0 support is very common on both Netscape 2 and IE. DOM level 1 and
DOM level 2 is usally the problem.
>
> Look at most books on JavaScript. About 25% or less is dedicated to
> actual JavaScript, and the the rest is DOM support.
Yea, but which DOM you talk about. The DOM level 0 which Netscape support in
Netscape 2 and 3 (also IE) or the DOM level 1 and 2 which Netscape 7 support?
I totaly agree with we need be careful to use DOM level 1 and 2. Even when we
use DOM level 0 we need to becareful. For example. IE support document.all
but non of the Netscape document.all
And document.all is neither in DOM level 0, 1 or 2.
From the Netscape compatability testing we peform in the last several years,
the biggest problem we face is document.all, and people using obsleted layer
support. Also, peoepl need to use "event" in IE and "e" in Netscape to
reference to Event.
>
> Pushing any computation onto the client is a really bad idea. Covering
> all client tagets cases is a royal pain. If most users can't be counted
> on to have their clock and timezone set properly, then all bets are off.
You can always keep thing in the server. That is ok, however, the trade off
is the increase of client-server traffic and slow performance. Nothing is
impossible, the question is what you want to trade.
--part1_8f.29e54be3.2b8abd99_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<HTML><FONT FACE=3Darial,helvetica><FONT SIZE=3D2 FAMILY=3D"SANSSERIF" FACE=
=3D"Arial" LANG=3D"0">In a message dated 2/22/2003 7:53:49 PM Pacific Standa=
rd Time, m.p.donadio@ieee.org writes:<BR>
<BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">And I reply:<BR>
<BR>
Yes, you are correct. Technically, all of those broswers support<BR>
JavaScript, but without the proper DOM support, what use is JavaScript<BR>
in a browser for real applications?</BLOCKQUOTE></FONT><FONT COLOR=3D"#0000=
00" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2 FAMILY=3D"SANSSERIF" FACE=
=3D"Arial" LANG=3D"0"><BR>
<BR>
</FONT><FONT COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2=
FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0">DOM level 0 support is very=20=
common on both Netscape 2 and IE. DOM level 1 and DOM level 2 is usally the=20=
problem. </FONT><FONT COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff"=
SIZE=3D2 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"><BR>
</FONT><FONT COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2=
FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"><BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"><BR>
Look at most books on JavaScript. About 25% or less is dedicated to<BR=
>
actual JavaScript, and the the rest is DOM support.</BLOCKQUOTE></FONT><FONT=
COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2 FAMILY=3D"S=
ANSSERIF" FACE=3D"Arial" LANG=3D"0"><BR>
<BR>
</FONT><FONT COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2=
FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0">Yea, but which DOM you talk=20=
about. The DOM level 0 which Netscape support in Netscape 2 and 3 (also IE)=20=
or the DOM level 1 and 2 which Netscape 7 support? I totaly agree with we ne=
ed be careful to use DOM level 1 and 2. Even when we use DOM level 0 we need=
to becareful. For example. IE support document.all but non of the Netscape=20=
document.all<BR>
And document.all is neither in DOM level 0, 1 or 2. <BR>
From the Netscape compatability testing we peform in the last several years,=
the biggest problem we face is document.all, and people using obsleted laye=
r support. Also, peoepl need to use "event" in IE and "e" in Netscape to ref=
erence to Event. </FONT><FONT COLOR=3D"#000000" style=3D"BACKGROUND-COLOR:=20=
#ffffff" SIZE=3D2 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"><BR>
</FONT><FONT COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2=
FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"><BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"><BR>
Pushing any computation onto the client is a really bad idea. Covering=
<BR>
all client tagets cases is a royal pain. If most users can't be counte=
d<BR>
on to have their clock and timezone set properly, then all bets are off.</BL=
OCKQUOTE><BR>
<BR>
You can always keep thing in the server. That is ok, however, the trade off=20=
is the increase of client-server traffic and slow performance. Nothing is im=
possible, the question is what you want to trade.</FONT></HTML>
--part1_8f.29e54be3.2b8abd99_boundary--