Path: csiph.com!usenet.pasdenom.info!dedibox.gegeweb.org!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="UTF-8" Message-ID: <3623831.9nD1xclIA7@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Sat, 11 Jan 2014 15:53:08 +0100 User-Agent: KNode/4.11.3 Content-Transfer-Encoding: 8Bit X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. <10702590.VgB369Vi3A@PointedEars.de> MIME-Version: 1.0 Lines: 63 NNTP-Posting-Date: 11 Jan 2014 15:53:16 CET NNTP-Posting-Host: 45de2230.newsspool1.arcor-online.net X-Trace: DXC=aO2SXa9S;K4gP]QSEBQ^d4ic==]BZ:af>4Fo<]lROoR1nkgeX?EC@@0eQ4FNC@f86;DZm8W4\YJN<`M@=jf=Qm@DA3Rl497 X-Complaints-To: usenet-abuse@arcor.de Xref: csiph.com comp.lang.javascript:22565 Michael F. Stemper wrote: > On 01/10/2014 03:12 PM, Thomas 'PointedEars' Lahn wrote: >> Michael F. Stemper wrote: >>> On 01/06/2014 03:56 AM, jonas.thornvall@gmail.com wrote: >>>> I find it very hard to spot logical errors when dealing with Writing >>>> out to Canvas, normally i write out values from JavaScript with >>>> document.write() line by line in the HTML document as i step thru loops >>>> but using the canvas you just plot over values without implementing >>>> plotout logic? >>>> >>>> Have anyone a good idea? >>> >>> O'Reilly does. >>> >>> You can create a window for trace messages, using this technique >>> (straight from the Javascript Rhino book). >> >> I do not see the point of this error-prone, incompatible approach when >> you have console.log() & friends. > > I never heard of it before. However, I just tried it, and it's > definitely a superior alternative. Would I be right in guessing that > this is something that was added after the third edition of the Rhino > book was published in 1996? It is unlikely that any edition of a “Javascript Rhino book”, much less the third one, was published in 1996 CE. The Rhino project, for a JavaScript™ engine written in Java, was started at Netscape in 1997. [1] Either your “Rhino” does not refer to the Rhino project, or you may mean *2006* (that would correspond with a release in the Rhino 1.6 series [2a]). If you mean the book “JavaScript: The Definitive Guide”, by David Flanagan, which has a rhinoceros on its cover and whose *first* edition was published in 1996 [2b], you should read the reviews that are referred from the FAQ for comp.lang.javascript, . It is possible that console.log() or something like it has been available at least since the release of Mozilla 1.0 in 2002 [3], with the -console switch, Venkman, the JavaScript Debugger [4], or similar. However, it was not before the release of Firebug – I had beta-tested and reported on FireBug 0.4, as it was called when Joe Hewitt was developing it in 2006 [5] – that in-browser debugging and the “console” object came into widespread use. After there was Firebug, other browser vendors added built- in developer tools that mirrored its functionality: Chrome Dev Tools, Opera Dragonfly, and IE Developer Tools; in that order, I think. Finally, with the release of Firefox 4.0/Gecko 2.0 on 2011-03-22, the built- in Error Console was replaced with the built-in Web Console which also supported console.log(). [6] __________ [1] [2a] [2b] [3] [4] [5] [6] -- PointedEars Twitter: @PointedEars2 Please do not Cc: me. / Bitte keine Kopien per E-Mail.