I'm still quite new to JavaScript so excuse me if my question sounds stupid.
JavaScript is worlds apart from Object Pascal and I'm still finding my way
around.
I'm working on a JavaScript clock that will show the time for all major
Australian cities. I'm not sure how to approach the whole timezone offset
thing. I know there is a function getTimezoneOffset() but I'm not sure how
to implement it.

Here's a piece of code (implementing time for two cities only at this
stage). I would appreciate it someone could demonstrate how I can implement
an offset. Perth is 3 hours (or 180 minutes) behind Sydney, so how could I
implement the time difference?


function SydClock()
{
var SydTime=new Date();
var SydHours=SydTime.getHours();
var SydMins=SydTime.getMinutes();
var SydSecs=SydTime.getSeconds();

if (SydHours>=13)
SydHours-=12;
if (SydHours==0)
SydHours=12;
if (SydSecs<10)
SydSecs="0"+ SydSecs;
if (SydMins<10)
SydMins="0"+ SydMins;
{
ClockFrm.SydDisplay.value=(SydHours + ":"
+ SydMins + ":" + SydSecs);
setTimeout('SydClock()',1000);
}
}

function PerthClock()
{
var PerthTime=new Date();
var PerthHours=PerthTime.getHours();
var PerthMins=PerthTime.getMinutes();
var PerthSecs=PerthTime.getSeconds();

if (PerthHours>=13)
PerthHours-=12;
if (PerthHours==0)
PerthHours=12;
if (PerthSecs<10)
PerthSecs="0"+ PerthSecs;
if (PerthMins<10)
PerthMins="0"+ PerthMins;
{
ClockFrm.PerthDisplay.value=(PerthHours + ":"
+ PerthMins + ":" + PerthSecs);
setTimeout('PerthClock()',1000);
}
}


Thanx in advance!

DeLpHi_gUy

JRS: In article <3fd9b68c_1>, seen in news:microsof
t.public.scripting.jscript, DeLpHi_gUy <fringeit> posted at
Fri, 12 Dec 2003 23:37:20 :-

>I'm still quite new to JavaScript so excuse me if my question sounds stupid.
>JavaScript is worlds apart from Object Pascal and I'm still finding my way
>around.

For javascript, you should read the news:comp.lang.javascript FAQ -

>I'm working on a JavaScript clock that will show the time for all major
>Australian cities. I'm not sure how to approach the whole timezone offset
>thing. I know there is a function getTimezoneOffset() but I'm not sure how
>to implement it.

- which will lead you to information about that.


>Here's a piece of code (implementing time for two cities only at this
>stage). I would appreciate it someone could demonstrate how I can implement
>an offset. Perth is 3 hours (or 180 minutes) behind Sydney, so how could I
>implement the time difference?

If Perth Time & Sydney time are ALWAYS 3 hours apart - and I doubt that,
because the difference in their standard times is 2 hours, and if the
code is always being run in Sydney, then subtract three hours from
Sydney local.

Otherwise, you need a solution to the general problem; to produce
Sydney, Perth, etc., clocks which show correctly on any properly-
configured browser anywhere, starting with UTC/GMT. No short cut will
be really worthwhile, except for places that have no Summer time. You
will need the Summer Time Rules for each location

In Australia: NSW, ACT, Vic, & SA apparently change, at 02:00h local
winter time, on the last Sunday of October and the last Sunday in March.
Que, NT, and WA do not change. Tasmania changes at that time on the
first Sunday of October and last Sunday of March. Other territories can
vary.

I believe Sydney is in NSW, and Perth, when not in Scotland, is in WA.

If so, Perth time is Beijing time.

with (PT=new Date()) { setUTCHours(getUTCHours()+8)
value = LZ(getUTCHours()) + ':' + LZ(getUTCMinutes()) }

will be a start. That approach is inadequate for NSW, ACT, Vic, & SA.


> if (SydHours>=13)
> SydHours-=12;
> if (SydHours==0)
> SydHours=12;

> setTimeout('SydClock()',1000);

Don't use the damfool 12-hour clock - Australians should be intelligent
enough to understand the 24-hour one, and, if not, they need training.

Don't setTimeOut( ..., 1000); that will miss seconds. Instead,
calculate how long until safely within the next second.

Don't use individual timeouts for the cities; save overhead, and do them
all at once.

Don't repeat code; use functions. You should be familiar with the
concept from Delphi.

I believe that
NSW is TZ = nswST-10nswDT,M10.5.0/2:00,M3.5.0/2:00
and WA is TZ = WAT-8
except for the designators, which are arbitrary above.

For an analogue display, see my js-anclk.htm

Read on ...

Many thanks for your reply.
At the moment, NSW is on 'daylight saving' time so it is actually 180 mins
ahead of WA, as I originally mentioned. SA is 30 mins behind NSW and NT is
90 mins behind NSW. QLD is is 60 mins behind NSW.
VIC, ACT and TAS are the same as NSW.
As you suggested, I will need to consider daylight saving time and
accomodate for it appropriately in the code.
Yes, I am familiar with functions (and procedures) from Delphi but I've
changed the JS clock around numerous times and have rewritten the code -
trying to think of different ways to make it work. Unfortunately, I
currently lack the necessary JavaScript knowledge to take full advantage of
the language. I 'm therefore thankful for the links you have provided.
The clock will be running on a company intranet site in Sydney on IE6
browsers.
I agree with you that Australians should be intelligent enough to know the
24-hour clock, and in a lot of cases they are. However, it's not widely used
in the old Oz and if you spontaneously throw "23:46" at the average Joe,
they'll spend more time than necessary to tell you that it's "11:46 PM". I
guess in that respect I'm lucky I grew up in Europe! :-)

Thanks again.


"Dr John Stockton" <spam> wrote in message
news:ewzj
> JRS: In article <3fd9b68c_1>, seen in news:microsof
> t.public.scripting.jscript, DeLpHi_gUy <fringeit> posted at
> Fri, 12 Dec 2003 23:37:20 :-
>
> >I'm still quite new to JavaScript so excuse me if my question sounds
stupid.
> >JavaScript is worlds apart from Object Pascal and I'm still finding my
way
> >around.
>
> For javascript, you should read the news:comp.lang.javascript FAQ -
>
> >I'm working on a JavaScript clock that will show the time for all major
> >Australian cities. I'm not sure how to approach the whole timezone offset
> >thing. I know there is a function getTimezoneOffset() but I'm not sure
how
> >to implement it.
>
> - which will lead you to information about that.
>> >Here's a piece of code (implementing time for two cities only at this
> >stage). I would appreciate it someone could demonstrate how I can
implement
> >an offset. Perth is 3 hours (or 180 minutes) behind Sydney, so how could
I
[..]
> NSW is TZ = nswST-10nswDT,M10.5.0/2:00,M3.5.0/2:00
> and WA is TZ = WAT-8
> except for the designators, which are arbitrary above.
>
> For an analogue display, see my js-anclk.htm
>
> Read on ...
>
> --
> © John Stockton, Surrey, UK. ? Turnpike v4.00 IE
4 ©

JRS: In article <3fda7046_1>, seen in news:microsof
t.public.scripting.jscript, DeLpHi_gUy <fringeit> posted at
Sun, 14 Dec 2003 00:49:50 :-

>Lines: 119

>Many thanks for your reply.

(1) It is not yet evident that you have read it carefully enough.

(2) Quoted material should be reduced to what is needed, with responses
following.

"DeLpHi_gUy" wrote:
> > (2) Quoted material should be reduced to what is needed, with responses
> > following.
>
> Precisely. I'm not about to spend many tedious hours reading through an
> entire FAQ.
> I will cull whatever information I find useful.

He is referring to your response which included the full previous message,
not the FAQ.
Quoted material: What he said in the previous message that you're responding
to.
Responses following: Don't top post. He doesn't like it that way. You'll
notice he didn't continue with the topic other than to state you need to do
more reading. Instead he chose to correct you on your newsgroup etiquette,
which is OT.

JRS: In article <eDAe45jwDHA.1908>, seen in
news:microsoft.public.scripting.jscript, Roland Hall <nobody>
posted at Sun, 14 Dec 2003 07:08:04 :-
>"DeLpHi_gUy" wrote:
>
>He is referring to your response which included the full previous message,
>not the FAQ.
>Quoted material: What he said in the previous message that you're responding
>to.
>Responses following: Don't top post. He doesn't like it that way. You'll
>notice he didn't continue with the topic other than to state you need to do
>more reading. Instead he chose to correct you on your newsgroup etiquette,
>which is OT.
>
>Agreed.

Neither can yet be seen to have sufficed, since the OP has not yet
acknowledged finding, by the method described, what he needs.


I wrote :
(1) It is not yet evident that you have read it carefully enough.
(2) Quoted material should be reduced to what is needed, with
responses following.


The second, and only the second, refers to his manner of posting. The
first refers to his need to find a solution to his clock problem;
searching the c.l.j FAQ for reference to date and/or time would have
found what he needs to find.

But I don't suppose that you have studied the c.l.j FAQ adequately
either.

>
> (1) It is not yet evident that you have read it carefully enough.

Interesting. And what do you propose would make it evident?
>
> (2) Quoted material should be reduced to what is needed, with responses
> following.

Precisely. I'm not about to spend many tedious hours reading through an
entire FAQ.
I will cull whatever information I find useful.

Your original response would have sufficed.


>
> --
> © John Stockton, Surrey, UK. ? Turnpike v4.00
MIME. ©

"Dr John Stockton" wrote:
> Neither can yet be seen to have sufficed, since the OP has not yet
> acknowledged finding, by the method described, what he needs.

Correct. It has not been seen which means it cannot be determined to have
been sufficed nor can it be proven to not have been. I posted you were
telling him to keep reading.

"You'll notice he didn't continue with the topic other than to state you
need to do more reading."

> The second, and only the second, refers to his manner of posting.

As I stated. "Instead he chose to correct you on your newsgroup etiquette,
which is OT."

> The first refers to his need to find a solution to his clock problem;
> searching the c.l.j FAQ for reference to date and/or time would have
> found what he needs to find.

I didn't see it in the FAQ unless you're referring to links to other JS
help/info sites. Sending someone from a NG to a FAQ re: another NG, which
has links to other sites which may answer his question is not expedient
especially when he came here for answers, not links to other sites that have
links to others sites that may have the answers he requires. Why not just
answer the question here? I admit, you gave some very good information and
then you ridiculed him for not posting re: your views of proper NG
etiquette, WHILE he was thanking you for the help. That's like helping a
blind person half way across an intersection, or whatever they call it in
the UK when two roads cross each other (cross roads?), and as they speak of
their appreciation, you bitch them out for not having a dog, not walking in
a straight line and fumbling around while instructing them to just keep
walking in the direction you pointed them and eventually they'll make it to
the other side.

What I really liked is when you chose to point him in the direction of
another NG. Just how different do you think javascript and jscript are
these days? Do you think people here are not as intelligent as those that
visit the other NG? Perhaps they frequent both?! Or, is it because
Microsoft is a US company and this is a Microsoft NG? Surely you don't
think this site would be biased towards Microsoft, do you?

> But I don't suppose that you have studied the c.l.j FAQ adequately either.

I'm sorry Doc but I don't follow every link posted however, I did peruse it
back in 1998 but not at jibbering.com since it was not even created until
1999. I'm sure your definition and my definition of 'adequately' would
differ. And, after seeing it at 7.9, it appears not much has changed since
1.3.

I didn't see an answer to his question there unless you're referring to this
seemingly familiar link:

Manipulating times, dates and the lastModified date and time in javascript:
http://www.merlyn.demon.co.uk/js-dates.htm

I also didn't find a reference to Danny Goodman or his site,
http://dannyg.com/. Is he not a respected name in the world of Javascript?

I noticed in your tag that you use, Jsc. Is this to denote javascript? I
went to webopedia.com and searched for Jsc as a keyword.
http://webopedia.com/ You should take some time to adequately check it out
with the links they have to other references.


> --
> © John Stockton, Surrey, UK. ? Turnpike v4.00 IE
4 ©

JRS: In article <e9VQTA1wDHA.2452>, seen in
news:microsoft.public.scripting.jscript, Roland Hall <nobody>
posted at Mon, 15 Dec 2003 15:45:55 :-

>As I stated. "Instead he chose to correct you on your newsgroup etiquette,
>which is OT."

It is what he needs to attend to, if he feels that he may want further
help from me. You, of course, are no less OT.


>> The first refers to his need to find a solution to his clock problem;
>> searching the c.l.j FAQ for reference to date and/or time would have
>> found what he needs to find.
>
>I didn't see it in the FAQ unless you're referring to links to other JS
>help/info sites. Sending someone from a NG to a FAQ re: another NG, which
>has links to other sites which may answer his question is not expedient
>especially when he came here for answers, not links to other sites that have
>links to others sites that may have the answers he requires. Why not just
>answer the question here?

The answer is too long to be worth separating from where it is and
posting here. If you have sought the answer by the means indicated,
you should have seen that.

This newsgroup lacks a FAQ, and the c.l.j FAQ, though not perfect, is a
valuable and obvious resource.


> Do you think people here are not as intelligent as those that
>visit the other NG?

There can be no doubt about that, in many cases. However, that is
hardly the point. Much good work has been done in c.l.j and is
represented in the FAQ, while not being represented here; that is
significant.


>I didn't see an answer to his question there unless you're referring to this
>seemingly familiar link:
>
>Manipulating times, dates and the lastModified date and time in javascript:
>[..]

I believe that if Jim had thought that any more needed to have been put,
he would have put it. Please give the URLs of any useful javascript
sites that you have created.


>I also didn't find a reference to Danny Goodman or his site,
>[..]. Is he not a respected name in the world of Javascript?

IIRC, I looked at his site, and did not like it; I will look again. I
have a vague recollection that the site is either inconvenient to read
or rather outdated, but I could be thinking of another one.


>I noticed in your tag that you use, Jsc. Is this to denote javascript? I
>went to webopedia.com
> ...
Irrelevant. English writers of English have the right to create English
neologisms. It used to say JS, but that can be mistaken for my initials
(though I never use other than all three). Those who cannot understand
it will just have to do without that understanding. There are, however,
other lists of acronyms and abbreviations, and an adequate search will
find Jsc. BTW, can you find a reputable source that justifies referring
to an article's signature as a "tag"?





Let us look at the beginning of the thread again.

He wrote that he was new at javascript, so I first recommended him to
read the c.l.j FAQ (BTW, while AFAIK it has not been much redesigned, a
considerable number of entries have been added in the last three years).

He introduced his problem; I pointed out how the FAQ would have helped.

He gave code; I made a number of educational remarks on the topic.

I finished with "Read on ..." followed by a sig whose third line
contained :-

<URL:http://www.merlyn.demon.co.uk/js-index.htm>
Jsc maths, dates, sources.

That should be a sufficient guide.



What of use to anyone (apart, maybe, from citing dannyg) have you
contributed to this thread?

JRS: In article <GmsdVBAH2v3$EwPu>, seen in
news:microsoft.public.scripting.jscript, Dr John Stockton
<spam> posted at Tue, 16 Dec 2003 12:41:43 :-
>
>>I also didn't find a reference to Danny Goodman or his site,
>>[..]. Is he not a respected name in the world of Javascript?
>
>IIRC, I looked at his site, and did not like it; I will look again. I
>have a vague recollection that the site is either inconvenient to read
>or rather outdated, but I could be thinking of another one.


It is not inconvenient to read, except that it requires a width of
greater than 640 px. It does seem rather keen on puffing his book.
Some of the material is recently dated, but a great deal is not, and is
therefore liable to be misleading.

<URL:http://developer.netscape.com/viewsource/goodman_dateobject.html>,
for example, is nearly 7 years old. It knows nothing of the GMT/UTC
methods; their existence vitiates a significant proportion of the text.
"Please enter your birthdate..." accepts 2 29 1900, rendering it as Mar
1; if the year field is zero or blank, an alert asks for the month
value. The page seems not to support the interests of those in the 99%
of countries that do not use MDY dates. Date difference disregards
Summer Time.

A fairly recent version of W3's HTML-tester is rather unhappy about the
pages I tested.



The javascript laurels on which he is resting are showing their age.
When the site was still largely up-to-date, it ought to have been
recommended in the c.l.j FAQ; but the recommendation should not be there
now, unless rather qualified.

"Dr John Stockton"
> >>I also didn't find a reference to Danny Goodman or his site,
> >>[..]. Is he not a respected name in the world of
Javascript?
> >
> >IIRC, I looked at his site, and did not like it; I will look again. I
> >have a vague recollection that the site is either inconvenient to read
> >or rather outdated, but I could be thinking of another one.

Well, it is obvious he is more developer than designer. I'll grant you that
one.

> It is not inconvenient to read, except that it requires a width of
> greater than 640 px.

It was my understanding that the most popular screen size in use is 800x600.

> It does seem rather keen on puffing his book.

Granted. The publishing page alone is rather extensive.

> Some of the material is recently dated, but a great deal is not, and is
> therefore liable to be misleading.

This appears to be pretty current:
http://www.dannyg.com/pubs/jsdhtmlcb/index.html

He is also a MAC die-hard. I disagree with some areas because I know
better. I lived through them. APPLE DID NOT INVENT THE GUI INTERFACE! I
just had to say that. (O:= Steve Jobs may have been a pioneer but he's
wreckless and has no business sense. Steve Wozniak, IMV, was the real
brains in the group and John Sculley was an ass. I do agree with Danny on
where he thinks Apple should set their target but I doubt it'll ever happen
and the box design needs work. It looks like a Commodore crayon box. I
think it should come complete with an anotomicly correct Ken doll so people
know they're getting screwed.

I don't think anyone would only reference one site for development
information and I doubt you can say any site out there is completely up to
date.

Ex. I referenced a document at microsoft.com where it said that WMI came out
during an SP, I think it was, for NT. However, someone quickly pointed out
that the WMIPing only works with XP. The topic was using WMI to ping on W2K
Server.

Should one always go back through all their files and update or rewrite
routines or should they reference when they were created and let the visitor
determine if they are still valid? Perhaps as things changed, writing new
routines to keep your site current is warranted but should you then drop all
documents that were written long ago?

Do you have any files with this in there even though language was
deprecated?

<script type="text/javascript" language="javascript
src="somefile.js"></script>

"Roland Hall" <nobody@nowhere> writes:

> It was my understanding that the most popular screen size in use is 800x600.

That's probably incorrect. The last statistic I saw had 54% of the users
with screens larger than 800x600. Not that the screen resolution matters.
It is the size of the browser that is important.

On the internet, going for only the most popular size is simply bad
design. There are browsers out there (WebTV, Opera on mobile phones,
other browsers on PDA's) that doesn't even get to 640x480. A good desing
will degrade gracefully. Bad designs just break.

> Granted. The publishing page alone is rather extensive.

It took me quite a while to find *anything* that wasn't advertising.
I found some, and it was decent, although dated, but not a lot.

The first link under the "JavaScript" heading is:
Q. _How do I..._ in JavaScript?
A FAQ? No, advertising for his book. At least half of the Q's seem to
be advertising or about to his books in other ways (e.g., errata).

> This appears to be pretty current:
> [..]

The page or the book?

I didn't find anything on his site that was worth referring to. I'm
not saying it isn't there, it's just not that easy to find.
(Actually, I just found some of the "freebie" examples that look intersting)


/L

JRS: In article <#$13IfIxDHA.2136>, seen in
news:microsoft.public.scripting.jscript, Roland Hall <nobody>
posted at Wed, 17 Dec 2003 04:57:12 :-
>"Dr John Stockton"
>Javascript?
>
>Well, it is obvious he is more developer than designer. I'll grant you that
>one.
>>It was my understanding that the most popular screen size in use is 800x600.

It is naive to assume that Web pages must, or should, be viewed full
screen. My screen is 1280 wide, but I do almost everything in windows
under 640 wide[*] - and I don't just mean my own pages. The pity here
is that it is a little over 640 (i.e. one has to go a little over 640 in
order for the ends of lines to appear.). One should not impost a need
for a size slightly bigger than a standard size in cases where it is
perfectly easy to allow the standard size without adverse effect.

More importantly, using the default font size, which is itself
reasonable although he has overridden my choice of face, there are too
many words per line for the convenience of my eyeballs, which are more
accustomed to reading ordinary books.
[*] Likewise, my work surface here us a standard door; from the seat I
can only easily reach half of it, but I use the rest; I can only
read/write on a quarter or less.


>> It does seem rather keen on puffing his book.
>
>Granted. The publishing page alone is rather extensive.
>
>> Some of the material is recently dated, but a great deal is not, and is
>> therefore liable to be misleading.
>
>This appears to be pretty current:
>[..]

I wrote "some".


>Should one always go back through all their files and update or rewrite
>routines or should they reference when they were created and let the visitor
>determine if they are still valid? Perhaps as things changed, writing new
>routines to keep your site current is warranted but should you then drop all
>documents that were written long ago?

That's up to the site owner. History is of value for some purposes.
But out-of-date information is not nearly as useful as good new stuff,
even when not misleading.




>Do you have any files with this in there even though language was
>deprecated?
>
><script type="text/javascript" language="javascript
>src="somefile.js"></script>


The important part of that deprecation, AIUI, is that type= is better.

I think that, on my visible site at the time of writing, I have a small
number of such as
<script language="javascript" type="text/javascript" src="include1.js">
</script>
and more of
<script type="text/javascript" src="include1.js">
</script>

but none of
<script language="javascript" type="text/javascript"> SCRIPT </script>


Being now with thanks aware of this, I have used a quick pass of
MiniTrue to remove all instances of 'language="javascript" ' from the
local master copy. Since there is no real benefit, however, only those
in files gravity?.htm ( ? = 1 2 3 ) will be uploaded tonight; the rest
at their next significant change.


A tutorial site does need to be maintained.

"Lasse Reichstein Nielsen" wrote:
> "Roland Hall" <nobody@nowhere> writes:
>
> > It was my understanding that the most popular screen size in use is
800x600.
>
> That's probably incorrect. The last statistic I saw had 54% of the users
> with screens larger than 800x600. Not that the screen resolution matters.
> It is the size of the browser that is important.

Size matters? (O:= My point is 640x480 is not a target I think should be
written for. Not all sites can be widdled down to displaying at any
resolution unless their just text based or image are extremely small. It's
not like we're dealing with vector images here and any bitmap resized is
distorted. You could always make additional images or you can try to write
to your target, which is my recommendation. I don't think there is one plan
for all sites for all topics.

The last statictic you saw? Where? Is this a scientific study or some site
asking people what they use or manufacturer results of sales?

> On the internet, going for only the most popular size is simply bad
> design.

Ya', you're right. Why would you want to ever try to target the largest
group of potential buyers?

> There are browsers out there (WebTV, Opera on mobile phones,
> other browsers on PDA's) that doesn't even get to 640x480.

Yes, and I don't write to WebTV or Opera or PDAs. If I had a site that
required evaluating potential customers who (WebTV) have no money to spend
on technology, (Opera) like to color outside the lines, (PDAs) expect to
surf the net with every piece of electronic hardware they own, then perhaps
I do a cost analysis projecting a ROI and if positive, considering spending
the extra time and money to try to reach them.

> A good desing

in your opinion

> will degrade gracefully. Bad designs just break.

I'm not sure not writing to a target of less than 800x600, in itself, can be
consider a bad design.

> > Granted. The publishing page alone is rather extensive.
>
> It took me quite a while to find *anything* that wasn't advertising.
> I found some, and it was decent, although dated, but not a lot.

That's great but my point was to reference the man and his site, not to say
it is the most current or best location to obtain all information regarding
javascript but then neither is the FAQ. It's small and quite limited and
has to incorporate URLs to other sites that actually have content for people
including level 1 and beyond.

> The first link under the "JavaScript" heading is:
> Q. _How do I..._ in JavaScript?
> A FAQ? No, advertising for his book. At least half of the Q's seem to
> be advertising or about to his books in other ways (e.g., errata).

Really? I thought it was a breakdown of the book with a link to some code
that is included in the book.
http://examples.oreilly.com/jvdhtmlckbk/

> > This appears to be pretty current:
> > [..]
>
> The page or the book?

You can't figure it out or you want my opinion?

> I didn't find anything on his site that was worth referring to. I'm
> not saying it isn't there, it's just not that easy to find.
> (Actually, I just found some of the "freebie" examples that look
intersting)

Yes, but they do not cover UTC so the Doc would not be happy about that.

This guy is an author. He has sold a lot of books. He was referenced when
Christopher maintained the FAQ. What is wrong with giving people
recognition? Danny is not dead. He is still writing more books and
offering more code. Just because he does not have the latest and greatest
site devoted to Javascript is no reason to remove him from the FAQ. It's
just a link. Isn't it the opinion of the user that will determine if the
information is useful?

The Doc says, it doesn't cover this or that. Ya'? Point out 5 sites on the
Internet that cover everything you can do with Javascript. Not everything
has been deprecated from long ago. A lot of things are still relevant.

Danny is not promoting his site other than to generate income for his books.
The "How Do I..." is designed to give the reader and inside of what will be
covered in the book. It's called marketing. He also threw in some freebies
to further entice the reader.

Think about it. It's been said on this site before, MVPs work for nothing
other than gratitude. If Danny gave everything away how much would he sell?
I think he's a good author, his examples are clear and he's worth having a
link to. Perhaps you missed my point?!

"Dr John Stockton"
> >> It is not inconvenient to read, except that it requires a width of
> >> greater than 640 px.
> >
> >It was my understanding that the most popular screen size in use is
800x600.
>
> It is naive to assume that Web pages must, or should, be viewed full
> screen. My screen is 1280 wide, but I do almost everything in windows
> under 640 wide[*] - and I don't just mean my own pages. The pity here
> is that it is a little over 640 (i.e. one has to go a little over 640 in
> order for the ends of lines to appear.).

Which means on a screen resolution at 800x600 it should be easy enough to
read.

>One should not impost a need
> for a size slightly bigger than a standard size in cases where it is
> perfectly easy to allow the standard size without adverse effect.

And what is the standard size?

> More importantly, using the default font size, which is itself
> reasonable although he has overridden my choice of face, there are too
> many words per line for the convenience of my eyeballs, which are more
> accustomed to reading ordinary books.

Really, I thought the browser had control over the face? Define 'ordinary
books.'

>[*] Likewise, my work surface here us a standard door; from the seat I
> can only easily reach half of it, but I use the rest; I can only
> read/write on a quarter or less.

Your work surface is a door?

> >> It does seem rather keen on puffing his book.

Ya'. He's an author. Go figure.

> >> Some of the material is recently dated, but a great deal is not, and is
> >> therefore liable to be misleading.

Misleading? Isn't that kind of harsh? Are you telling me everything on
your site is 100% up to date? And if not, does that mean you are misleading
visitors?

>> The important part of that deprecation, AIUI, is that type= is better.
>
> I think that, on my visible site at the time of writing, I have a small
> number of such as
> <script language="javascript" type="text/javascript" src="include1.js">
> </script>
> and more of
> <script type="text/javascript" src="include1.js">
> </script>

Which means it will not pass a W3C validation.

> Being now with thanks aware of this, I have used a quick pass of
> MiniTrue to remove all instances of 'language="javascript" ' from the
> local master copy. Since there is no real benefit, however, only those
> in files gravity?.htm ( ? = 1 2 3 ) will be uploaded tonight; the rest
> at their next significant change.
>> A tutorial site does need to be maintained.

I would agree with that and I have seen many sites, set as tutorials that
are outdated but then I saw a server last week that was missing over 3 years
of updates not to mention all servers, workstations and accounts, including
the administrator were all blank.

What is that, 2 things we have agreed upon?

We have completely gotten off track. My original post, actually not
directed towards you but somehow I know you might respond, was that nobody
should be ridiculed when they're thanking you for helping them.

You're a pretty smart guy and you're probably more educated than most in
your field of expertise but perhaps it's your delivery that I don't
understand. I have actually even seen you use humor once which made me have
to go lay down. (O:=

Not everyone can remember everything about anything. Providing a link to
someone with a history in the topic of discussion can be beneficial.
Sometimes the present is clearer with a better understanding of the history
behind it which helps us to prepare for and shape our future. Not everyone
updates like some of us. Any worm that compromises a system because an
update was not performed proves this on a daily basis. Yes, "good new
stuff" is appealing but "old new stuff" is still new, to someone.