Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.unit0.net!takemy.news.telefonica.de!telefonica.de!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="UTF-8" Message-ID: <5486107.giMBzBjr1v@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Mon, 17 Sep 2012 21:00:12 +0200 User-Agent: KNode/4.4.11 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+&. Newsgroups: comp.lang.javascript References: <5054ed07$0$6897$e4fe514c@news2.news.xs4all.nl> <5055ae9a$0$6850$e4fe514c@news2.news.xs4all.nl> <5056d6e4$0$6900$e4fe514c@news2.news.xs4all.nl> Followup-To: comp.lang.javascript MIME-Version: 1.0 Lines: 59 NNTP-Posting-Date: 17 Sep 2012 21:00:13 CEST NNTP-Posting-Host: 26f13629.newsspool1.arcor-online.net X-Trace: DXC=aT`EZ2Nn]>KAa;:RKVJ>LEic==]BZ:afN4Fo<]lROoRAnkgeX?EC@@@1CEWAg0_HNEDZm8W4\YJNLR=i2=[N6Y6J:A:?DdQAF\RH X-Complaints-To: usenet-abuse@arcor.de Xref: csiph.com comp.lang.javascript:15929 Tom de Neef wrote: > I find that coding in Javascript takes me ages. This must have to do with > the lack of a proper development environment. I am used to one (Delphi) > where the IDE checks spelling, offers a list of possible > properties/methods, warns against unassignments, dubious assignments, etc. > With Javascript I have to use a simple editor There still is no "Javascript" and no, you don't. > and none of such help is available. You might want to try Eclipse JavaScript Development Tools (JSDT) [1]. It is the best ECMAScript and DOM editor that you can get for free that I have encountered for years; it can do what you ask, and more. It still has some language bugs, though; primarily because it is based on a Java parser that cannot deal with the very dynamic nature of the language and the different patterns this allows. I am using it for all my ECMAScript-based scripts; JSX includes some of the JSdoc comments only for JSDT (for example, `@memberOf'). > The result is that you may get stuck without a clue. I must > learn to call upon JSlint in such cases. No, you don't. > But here I didn't. I followed what was happening in > inspection mode. thisTD.style.backgroundImage = "expl.bmp" did not raise > an exception and yet the attribute remained as was (empty string). That is strong indication that the value right-hand side was invalid. The setter of the style property prevented the change of the current property value to an invalid value. That is as close as you can get with DOM properties; an exception does not need to be thrown. See also jsx.dom.setStyleProperty() (and an improvement for that is coming to my mind now). > I tried url() but may have made a mistake with the quotes. Quotes in the `url(…)' value are optional per the Specification. Some non- conforming layout engines used to make a difference there, but I am not convinced they are relevant anymore. > I've learned one thing and hope to keep it at heart: validate html, css > and script before posting ACK. Trim your quotes to the relevant minimum, please. [3] PointedEars ___________ [1] [2] [3] -- When all you know is jQuery, every problem looks $(olvable).