Talk:Audio alarm: Difference between revisions

What you were saying about "hapless schmuck", etc. was very funny. I'll tell all the other geeks what you said. But, I, being blind, make non-visual programs. With the HTML meta command and the "http-equiv" set to "refresh", the variable sets the content to a number of seconds, followed by ";url=" and then the filename, ".mp3". I've written all kinds of apps like this since 2007, and, with my knowledge of using MediaWiki editing (which I got from editing thousands of other wikis between late 2009 and now), that this is a programmer's wiki paradise. I can write apps, as long as they are original in the RC community. I guess mine ripped off of other ones or something. And what ridiculous person would say, "no more document.write for JavaScript"? That, and it's "writeln" counterpart, are the only way to actually produce HTML that's being manipulated by JavaScript. You know, I'm obsessed with client-side JavaScript. The JS definitive guide doesn't mention HTML "server tags" and server JS. What book would I need for that? Or, better yet, what RC page? [[User:Star651|Star651]] 23:52, 25 July 2011 (UTC)

: Eh I know how meta refresh tag works. The input of seconds is counter-intuitive from a program design point of view: normal people are much more comfortable with hour:minute notations when dealing with time span of more than a few minutes, especially so for someone who's already sleepy. The document.write is bad because there's no promise what you write is valid HTML/XML but the text is forcefully injected into the document as source code anyway. It's generally better to manipulate the DOM via document.createElement, document.insertBefore, etc. The refresh is easily done with a <code>window.setTimeout() { location.href = new_address }</code>, and while the timer is ticking, you can do other things, even cancel the timer if you want to. Using DOM instead of HTML code has another advantage: you don't invoke a reparse/reflow of the whole document, the browser only need to work with the parent element. Even if you ''really, really'' want to produce raw HTML code, you can use <code>element.InnerHTML = some_html_text</code>. This way, if something is wrong with the html you produced, only the element is clobbered, and you get a proper error indication unlike <code>document.write</code>. document.write should be considered obsolete in all regards. --[[User:Ledrug|Ledrug]] 00:13, 26 July 2011 (UTC)