Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #17308 > unrolled thread
| Started by | Asen Bozhilov <asen.bozhilov@gmail.com> |
|---|---|
| First post | 2012-11-19 13:00 -0800 |
| Last post | 2012-12-23 19:13 +0000 |
| Articles | 20 on this page of 226 — 28 participants |
Back to article view | Back to comp.lang.javascript
Maintainer of the FAQ Asen Bozhilov <asen.bozhilov@gmail.com> - 2012-11-19 13:00 -0800
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-11-19 13:34 -0800
Re: Maintainer of the FAQ RobG <rgqld@iinet.net.au> - 2012-11-20 01:25 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-11-20 13:39 +0100
Re: Maintainer of the FAQ Asen Bozhilov <asen.bozhilov@gmail.com> - 2012-11-20 11:24 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1247@merlyn.demon.co.uk.invalid> - 2012-11-21 19:19 +0000
Re: Maintainer of the FAQ Andrew Poulos <ap_prog@hotmail.com> - 2012-11-22 14:09 +1100
Re: Maintainer of the FAQ Dr J R Stockton <reply1247@merlyn.demon.co.uk.invalid> - 2012-11-20 19:50 +0000
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-11-20 19:56 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-11-21 11:24 +0100
Re: Maintainer of the FAQ Dr J R Stockton <reply1247@merlyn.demon.co.uk.invalid> - 2012-11-22 23:34 +0000
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-11-23 11:07 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1247@merlyn.demon.co.uk.invalid> - 2012-11-24 18:30 +0000
Re: Maintainer of the FAQ jim.ley@gmail.com - 2012-11-22 03:06 -0800
Re: Maintainer of the FAQ Asen Bozhilov <asen.bozhilov@gmail.com> - 2012-11-22 07:15 -0800
Re: Maintainer of the FAQ Martin Leese <please@see.Web.for.e-mail.INVALID> - 2012-11-22 08:48 -0700
Re: Maintainer of the FAQ Dr J R Stockton <reply1247@merlyn.demon.co.uk.invalid> - 2012-11-23 20:00 +0000
Re: Maintainer of the FAQ "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2012-11-24 10:36 +0100
Re: Maintainer of the FAQ Dr J R Stockton <reply1247@merlyn.demon.co.uk.invalid> - 2012-11-25 19:16 +0000
Re: Maintainer of the FAQ John G Harris <john@nospam.demon.co.uk> - 2012-11-26 10:18 +0000
Re: Maintainer of the FAQ "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-11-26 12:50 +0200
Re: Maintainer of the FAQ Matt McDonald <matt@fortybelow.ca> - 2012-11-30 14:23 -0500
Re: Maintainer of the FAQ John G Harris <john@nospam.demon.co.uk> - 2012-12-01 09:24 +0000
Re: Maintainer of the FAQ Matt McDonald <matt@fortybelow.ca> - 2012-12-01 08:45 -0500
Re: Maintainer of the FAQ "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-12-01 16:17 +0200
Re: Maintainer of the FAQ Gene Wirchenko <genew@telus.net> - 2012-12-12 19:30 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-01 18:50 +0100
Re: Maintainer of the FAQ Cezary Tomczyk <cezary.tomczyk@gmail.com> - 2012-12-02 19:25 +0100
Re: Maintainer of the FAQ Cezary Tomczyk <cezary.tomczyk@gmail.com> - 2012-12-02 21:31 +0100
Re: Maintainer of the FAQ Asen Bozhilov <asen.bozhilov@gmail.com> - 2012-12-05 03:48 -0800
Re: Maintainer of the FAQ "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2012-12-05 12:55 +0100
Re: Maintainer of the FAQ "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-12-05 14:52 +0200
Re: Maintainer of the FAQ Andrew Poulos <ap_prog@hotmail.com> - 2012-12-06 06:16 +1100
Re: Maintainer of the FAQ Matt McDonald <matt@fortybelow.ca> - 2012-12-05 16:56 -0500
Re: Maintainer of the FAQ "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-12-06 00:20 +0200
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-05 14:47 -0800
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-06 07:11 -0800
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-06 08:37 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-06 17:50 +0100
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-06 08:57 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-06 18:32 +0100
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-06 10:34 -0800
Re: Maintainer of the FAQ John G Harris <john@nospam.demon.co.uk> - 2012-12-07 11:05 +0000
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-07 07:21 -0800
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-11 09:01 -0800
Re: Maintainer of the FAQ Gene Wirchenko <genew@telus.net> - 2012-12-12 19:37 -0800
Re: Maintainer of the FAQ Matt McDonald <matt@fortybelow.ca> - 2012-12-07 11:24 -0500
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-11 09:00 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1249@merlyn.demon.co.uk.invalid> - 2012-12-07 20:54 +0000
Re: Maintainer of the FAQ Christoph Becker <cmbecker69@gmx.de> - 2012-12-08 03:42 +0100
Re: Maintainer of the FAQ Good Guy <hello.world@example.com> - 2012-12-08 02:53 +0000
Re: Maintainer of the FAQ Dr J R Stockton <reply1249@merlyn.demon.co.uk.invalid> - 2012-12-09 16:43 +0000
Re: Maintainer of the FAQ John G Harris <john@nospam.demon.co.uk> - 2012-12-07 11:16 +0000
Re: Maintainer of the FAQ Dr J R Stockton <reply1249@merlyn.demon.co.uk.invalid> - 2012-12-08 18:45 +0000
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-06 10:40 -0800
Re: Maintainer of the FAQ John G Harris <john@nospam.demon.co.uk> - 2012-12-06 15:16 +0000
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-06 08:48 -0800
Re: Maintainer of the FAQ Tim Streater <timstreater@greenbee.net> - 2012-12-06 18:31 +0000
Re: Maintainer of the FAQ Dr J R Stockton <reply1249@merlyn.demon.co.uk.invalid> - 2012-12-06 23:06 +0000
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-06 16:24 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1249@merlyn.demon.co.uk.invalid> - 2012-12-08 18:06 +0000
Re: Maintainer of the FAQ Stefan Weiss <krewecherl@gmail.com> - 2012-12-07 01:29 +0100
Re: Maintainer of the FAQ Tim Streater <timstreater@greenbee.net> - 2012-12-05 22:24 +0000
Re: Maintainer of the FAQ Cezary Tomczyk <cezary.tomczyk@gmail.com> - 2012-12-05 23:36 +0100
Re: Maintainer of the FAQ Stefan Weiss <krewecherl@gmail.com> - 2012-12-07 00:35 +0100
Re: Maintainer of the FAQ Andrew Poulos <ap_prog@hotmail.com> - 2012-12-07 10:45 +1100
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-06 16:01 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1249@merlyn.demon.co.uk.invalid> - 2012-12-07 21:00 +0000
Re: Maintainer of the FAQ Tim Streater <timstreater@greenbee.net> - 2012-12-08 10:17 +0000
Re: Maintainer of the FAQ Stefan Weiss <krewecherl@gmail.com> - 2012-12-07 01:12 +0100
Re: Maintainer of the FAQ Cezary Tomczyk <cezary.tomczyk@gmail.com> - 2012-12-07 23:22 +0100
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-08 04:46 +0100
Re: Maintainer of the FAQ John G Harris <john@nospam.demon.co.uk> - 2012-12-08 15:56 +0000
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-08 09:00 -0800
Re: Maintainer of the FAQ Good Guy <hello.world@example.com> - 2012-12-08 17:54 +0000
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-08 20:53 +0100
Re: Maintainer of the FAQ Cezary Tomczyk <cezary.tomczyk@gmail.com> - 2012-12-09 11:02 +0100
Functions in JavaScript vs. mathematics & the name "JavaScript" "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-12-08 23:31 +0200
Re: Maintainer of the FAQ Mike Duffy <Use_guestbook_page@website.in.sig> - 2012-12-09 02:02 +0000
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-08 23:12 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1249@merlyn.demon.co.uk.invalid> - 2012-12-09 16:44 +0000
Re: Maintainer of the FAQ Wally W. <ww84wa@aim.com> - 2012-12-10 01:30 -0500
Re: Maintainer of the FAQ John G Harris <john@nospam.demon.co.uk> - 2012-12-08 16:04 +0000
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-08 08:37 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-08 21:34 +0100
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-08 21:49 +0100
Re: Maintainer of the FAQ John G Harris <john@nospam.demon.co.uk> - 2012-12-09 11:05 +0000
Re: Maintainer of the FAQ Christoph Becker <cmbecker69@gmx.de> - 2012-12-06 03:24 +0100
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-06 16:09 +0100
Re: Maintainer of the FAQ John G Harris <john@nospam.demon.co.uk> - 2012-12-06 15:23 +0000
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-06 17:44 +0100
Re: Maintainer of the FAQ John G Harris <john@nospam.demon.co.uk> - 2012-12-07 15:03 +0000
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-06 09:05 -0800
Re: Maintainer of the FAQ Christoph Becker <cmbecker69@gmx.de> - 2012-12-06 18:59 +0100
Re: Maintainer of the FAQ Christoph Becker <cmbecker69@gmx.de> - 2012-12-06 19:24 +0100
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-06 19:26 +0100
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-06 14:11 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-07 03:07 +0100
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-06 18:36 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-07 04:11 +0100
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-06 20:26 -0800
Re: Maintainer of the FAQ Andrew Poulos <ap_prog@hotmail.com> - 2012-12-07 20:40 +1100
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-07 01:58 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-07 14:32 +0100
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-07 07:22 -0800
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-07 11:19 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-07 21:11 +0100
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-07 16:19 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1249@merlyn.demon.co.uk.invalid> - 2012-12-08 18:33 +0000
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-08 22:14 -0800
FAQ source format (was: Maintainer of the FAQ) Stefan Weiss <krewecherl@gmail.com> - 2012-12-09 13:56 +0100
Re: FAQ source format Patricia Shanahan <pats@acm.org> - 2012-12-09 08:09 -0800
Re: FAQ source format Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-09 19:12 -0800
Re: FAQ source format Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-10 20:49 +0000
Re: FAQ source format (was: Maintainer of the FAQ) Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-09 18:59 -0800
Re: FAQ source format Patricia Shanahan <pats@acm.org> - 2012-12-09 20:13 -0800
Re: FAQ source format Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-09 20:50 -0800
Re: FAQ source format (was: Maintainer of the FAQ) Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-10 20:41 +0000
Re: FAQ source format (was: Maintainer of the FAQ) Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-10 18:09 -0800
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-09 07:06 -0800
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-09 19:12 -0800
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-09 20:11 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-10 20:32 +0000
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-10 17:53 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-12 21:07 +0000
Re: Maintainer of the FAQ Wally W. <ww84wa@aim.com> - 2012-12-12 21:52 -0500
Re: Maintainer of the FAQ John G Harris <john@nospam.demon.co.uk> - 2012-12-13 16:05 +0000
Re: Maintainer of the FAQ Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-15 00:40 +0000
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-13 08:09 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-15 00:40 +0000
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-15 11:02 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-16 17:58 +0000
Re: Maintainer of the FAQ "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2012-12-17 11:22 +0100
Re: Maintainer of the FAQ Gene Wirchenko <genew@telus.net> - 2012-12-17 10:40 -0800
Re: Maintainer of the FAQ "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2012-12-17 20:05 +0100
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-18 00:31 +0100
Re: Maintainer of the FAQ Osmo Saarikumpu <osmo@weppipakki.com> - 2012-12-18 10:18 +0200
Re: Maintainer of the FAQ "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2012-12-18 13:38 +0100
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-18 14:59 +0100
Re: Maintainer of the FAQ John G Harris <john@nospam.demon.co.uk> - 2012-12-18 16:33 +0000
Re: Maintainer of the FAQ Gene Wirchenko <genew@telus.net> - 2012-12-18 09:26 -0800
Re: Maintainer of the FAQ "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2012-12-18 23:09 +0100
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-18 23:47 +0100
Re: Maintainer of the FAQ Gene Wirchenko <genew@telus.net> - 2012-12-18 15:21 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1251@merlyn.demon.co.uk.invalid> - 2012-12-18 16:32 +0000
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-18 08:11 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1251@merlyn.demon.co.uk.invalid> - 2012-12-19 18:26 +0000
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-20 06:55 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-21 15:46 +0100
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-21 06:59 -0800
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-21 08:27 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-21 19:12 +0100
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-21 15:30 -0800
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-21 08:24 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-21 19:09 +0100
Re: Maintainer of the FAQ Dr J R Stockton <reply1251@merlyn.demon.co.uk.invalid> - 2012-12-21 20:21 +0000
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-22 08:58 -0800
Re: Maintainer of the FAQ Jeff North <jnorthau@yahoo.com.au> - 2012-12-14 08:01 +1100
Re: Maintainer of the FAQ Adam Silver <adambsilver@gmail.com> - 2012-12-14 00:28 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-15 23:25 +0000
Re: Maintainer of the FAQ Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-15 00:39 +0000
Re: Maintainer of the FAQ Jeff North <jnorthau@yahoo.com.au> - 2012-12-16 00:23 +1100
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-15 15:00 +0100
Re: Maintainer of the FAQ Osmo Saarikumpu <osmo@weppipakki.com> - 2012-12-16 17:14 +0200
Re: Maintainer of the FAQ Dr J R Stockton <reply1251@merlyn.demon.co.uk.invalid> - 2012-12-17 18:33 +0000
Re: Maintainer of the FAQ Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-16 17:32 +0000
Re: Maintainer of the FAQ Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-16 17:24 +0000
Re: Maintainer of the FAQ Jeff North <jnorthau@yahoo.com.au> - 2012-12-18 17:15 +1100
Re: Maintainer of the FAQ Dr J R Stockton <reply1251@merlyn.demon.co.uk.invalid> - 2012-12-19 18:57 +0000
Re: Maintainer of the FAQ Osmo Saarikumpu <osmo@weppipakki.com> - 2012-12-27 23:03 +0200
Re: Maintainer of the FAQ Jeff North <jnorthau@yahoo.com.au> - 2012-12-28 11:14 +1100
Re: Maintainer of the FAQ "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2012-12-28 09:12 +0100
Re: Maintainer of the FAQ Dr J R Stockton <reply1249@merlyn.demon.co.uk.invalid> - 2012-12-08 18:24 +0000
Re: Maintainer of the FAQ Tim Streater <timstreater@greenbee.net> - 2012-12-07 10:11 +0000
Re: Maintainer of the FAQ Gene Wirchenko <genew@telus.net> - 2012-12-13 09:25 -0800
Re: Maintainer of the FAQ Andrew Poulos <ap_prog@hotmail.com> - 2012-12-14 07:26 +1100
Re: Maintainer of the FAQ "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2012-12-13 21:45 +0100
Re: Maintainer of the FAQ Dr J R Stockton <reply1249@merlyn.demon.co.uk.invalid> - 2012-12-07 21:06 +0000
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-08 02:45 +0100
Re: Maintainer of the FAQ Andrew Poulos <ap_prog@hotmail.com> - 2012-12-08 13:30 +1100
Re: Maintainer of the FAQ Dr J R Stockton <reply1249@merlyn.demon.co.uk.invalid> - 2012-12-09 17:00 +0000
Re: Maintainer of the FAQ Tim Streater <timstreater@greenbee.net> - 2012-12-08 10:14 +0000
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-05 09:03 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-05 18:39 +0100
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-05 11:56 -0800
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-05 12:30 -0800
Re: Maintainer of the FAQ Andrew Poulos <ap_prog@hotmail.com> - 2012-12-06 08:54 +1100
Re: Maintainer of the FAQ Cezary Tomczyk <cezary.tomczyk@gmail.com> - 2012-12-05 23:38 +0100
Re: Maintainer of the FAQ Matt McDonald <matt@fortybelow.ca> - 2012-12-13 14:18 -0500
Re: Maintainer of the FAQ Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-15 00:09 +0000
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-16 01:54 +0100
Re: Maintainer of the FAQ Dr J R Stockton <reply1251@merlyn.demon.co.uk.invalid> - 2012-12-17 18:32 +0000
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-18 07:06 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-18 17:54 +0100
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-18 11:38 -0800
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-18 12:50 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-18 23:23 +0100
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-18 19:46 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-19 18:10 +0100
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-19 11:31 -0800
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-19 22:54 +0100
Re: Maintainer of the FAQ Stefan Weiss <krewecherl@gmail.com> - 2012-12-19 16:36 +0100
Re: Maintainer of the FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-05 22:49 +0100
Re: Maintainer of the FAQ Dr J R Stockton <reply1249@merlyn.demon.co.uk.invalid> - 2012-12-06 23:21 +0000
Re: Maintainer of the FAQ John G Harris <john@nospam.demon.co.uk> - 2012-12-06 15:08 +0000
Re: Maintainer of the FAQ Stefan Weiss <krewecherl@gmail.com> - 2012-12-07 01:01 +0100
Re: Maintainer of the FAQ Adam Silver <adambsilver@gmail.com> - 2012-12-06 07:40 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1249@merlyn.demon.co.uk.invalid> - 2012-12-06 23:51 +0000
Re: Maintainer of the FAQ Good Guy <hello.world@example.com> - 2012-12-08 02:19 +0000
Re: Maintainer of the FAQ Christoph Becker <cmbecker69@gmx.de> - 2012-12-08 03:57 +0100
Re: Maintainer of the FAQ Good Guy <hello.world@example.com> - 2012-12-08 03:06 +0000
Re: Maintainer of the FAQ Cezary Tomczyk <cezary.tomczyk@gmail.com> - 2012-12-08 09:34 +0100
Re: Maintainer of the FAQ Good Guy <hello.world@example.com> - 2012-12-08 13:36 +0000
Re: Maintainer of the FAQ Jeff North <jnorthau@yahoo.com.au> - 2012-12-22 16:19 +1100
Re: Maintainer of the FAQ Patricia Shanahan <pats@acm.org> - 2012-12-22 08:59 -0800
Re: Maintainer of the FAQ Jeff North <jnorthau@yahoo.com.au> - 2012-12-23 13:38 +1100
Re: Maintainer of the FAQ "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-12-23 10:49 +0200
Re: Maintainer of the FAQ Gene Wirchenko <genew@telus.net> - 2012-12-23 16:58 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1252@merlyn.demon.co.uk.invalid> - 2012-12-24 21:03 +0000
Re: Maintainer of the FAQ Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-27 09:33 -0800
Re: Maintainer of the FAQ Dr J R Stockton <reply1252@merlyn.demon.co.uk.invalid> - 2012-12-28 21:33 +0000
Re: Maintainer of the FAQ Jeff North <jnorthau@yahoo.com.au> - 2012-12-28 11:16 +1100
Re: Maintainer of the FAQ John G Harris <john@nospam.demon.co.uk> - 2012-12-28 09:08 +0000
Re: Maintainer of the FAQ Jeff North <jnorthau@yahoo.com.au> - 2012-12-28 22:01 +1100
Re: Maintainer of the FAQ John G Harris <john@nospam.demon.co.uk> - 2012-12-28 11:26 +0000
Re: Maintainer of the FAQ Dr J R Stockton <reply1251@merlyn.demon.co.uk.invalid> - 2012-12-23 19:13 +0000
Page 7 of 12 — ← Prev page 1 … 5 6 [7] 8 9 … 12 Next page →
| From | Scott Sauyet <scott.sauyet@gmail.com> |
|---|---|
| Date | 2012-12-09 19:12 -0800 |
| Message-ID | <1d471d4c-0cfa-43d1-a3ee-0490ea1553b8@j4g2000yqh.googlegroups.com> |
| In reply to | #17628 |
Patricia Shanahan wrote: > Scott Sauyet wrote: >> [ ... ] >> I was hoping to host this material on Github, which would allow users >> to easily grab their own copies of it, and make it almost trivial for >> them to share proposed changes to FAQ sections. [ ... ] > >> Although I still like the idea of a group of maintainers, regardless >> whether we have a group or an individual, I think this would be an >> easier way for anyone to maintain the FAQ. > > I have a suggestion for running a group of maintainers - adopt the > Apache voting process,http://www.apache.org/foundation/voting.html I'm mixed about that idea. I love working by consensus. I am the only person I've ever met who considers himself both an atheist and a Quaker. Part of the appeal of the Quakerism is the way Quakers manage to conduct their affairs through a rigorous process of consensus. But I've rarely found it to work over the Web. comp.lang.javascript can grow fairly contentious. Some of the members who have the most to offer are often at the center of such controversies. I would be afraid that the ability of a single member to veto any proposals would too often end up holding the group hostage to individuals' particular notions. > Votes could take place in a Github code review discussion to avoid > cluttering the newsgroup. Votes, yes. But I would prefer most discussion happen in the newsgroup itself. > By the way, +1 on the general approach. Thank you. -- Scott
[toc] | [prev] | [next] | [standalone]
| From | Patricia Shanahan <pats@acm.org> |
|---|---|
| Date | 2012-12-09 20:11 -0800 |
| Message-ID | <SdWdnabcGqhS_VjNnZ2dnUVZ_i2dnZ2d@earthlink.com> |
| In reply to | #17643 |
On 12/9/2012 7:12 PM, Scott Sauyet wrote: > Patricia Shanahan wrote: ... >> I have a suggestion for running a group of maintainers - adopt the >> Apache voting process,http://www.apache.org/foundation/voting.html > > I'm mixed about that idea. I love working by consensus. I am the > only person I've ever met who considers himself both an atheist and a > Quaker. Part of the appeal of the Quakerism is the way Quakers manage > to conduct their affairs through a rigorous process of consensus. But > I've rarely found it to work over the Web. comp.lang.javascript can > grow fairly contentious. Some of the members who have the most to > offer are often at the center of such controversies. I would be > afraid that the ability of a single member to veto any proposals would > too often end up holding the group hostage to individuals' particular > notions. Apache has different voting rules for different situations. I suggest going with majority for all FAQ decisions. However, if someone votes -1 on something they should give reasons and the other maintainers should give careful consideration to those reasons. Patricia
[toc] | [prev] | [next] | [standalone]
| From | Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> |
|---|---|
| Date | 2012-12-10 20:32 +0000 |
| Message-ID | <23YbGkLWbkxQFwXT@invalid.uk.co.demon.merlyn.invalid> |
| In reply to | #17623 |
In comp.lang.javascript message <9af7f027-c78f-491d-a427-4576adfcc768@10 g2000yqk.googlegroups.com>, Sat, 8 Dec 2012 22:14:56, Scott Sauyet <scott.sauyet@gmail.com> posted: >Although I'm posting this as a response to John Stockton's message, >below my direct response to him is a description of what I've >attempted in order to make a simpler-to-maintain FAQ. I'd appreciate >it if those interested in this thread would read that, even if you are >not interested in my dialog with Dr. Stockton. > >====================================================================== > >Dr J R Stockton wrote: >> Scott Sauyet posted: > >>> I'm all for changing the source to something simpler than that XML. I >>> would choose a set of Markdown files that could be submitted directly >>> as the body of messages to this group and could be combined into a >>> complete HTML FAQ or linked as individual pages with a simple script >>> or simple web app. If I find time this weekend (ha!) I will attempt >>> something like this. >> >> [ ... ] >> The only qualifications required of a newsgroup FAQ maintainer are >> sufficient commands of the language and of the given topic of a FAQ. > >I disagree. There are other qualifications regarding temperament, >sociability, commitment to the job, competence with USENET, and many >others as well. Not disagreed. I was using qualifications in the narrower sense of core technical competencies. >> Therefore, a newsgroup FAQ should be maintained in a representation >> which any possible future maintainer can already or with trivial effort >> handle, and other representations should be derived from that. > >That's what I've been striving for. And I can't tell if you think my >suggestion would be moving toward that goal or away from it. I don't have time currently to give it the attention it deserves. >> Therefore, the only satisfactory master, editable, representations are >> "ASCII" text and straightforward HTML+CSS (with use of ECMAscript >> allowed). > >I'd rather it not involve HTML or CSS for day-to-day maintenance. Of >course if it's presented over the Web, there would be some of each >involved, but my goal would be to mostly avoid both and use a simpler >text format, ideally one that would serve directly as the regular >postings to the group. I will describe my efforts to that effect so >far below. If one wants it to appear on the Web, it needs to be in HTML+CSS, as TXT files of this length are not so easy to read, especially by the younger elements. For the Newsgroup, it must be TXT style. I believe that it is sufficiently easy to find (and keep with the master copy) text to/from HTML converters. But the method must support all formatting required in either distributed version (at present, IIRC, it does not). Since this is a JavaScript group, and the predominant interest is in JavaScript for the Web, it is reasonable to expect any maintainer to be able to work with HTML+CSS, as well as TXT. >> The form of the existing FAQ as seen in the newsgroup has suffered >> because of limitations in the method used to generate it from the form >> in which it is edited. > >I agree. Again, I don't know if you think I was suggesting something >helpful or not, but please take a look at what I'm working on below >and see if you think it would make FAQ maintenance more >straightforward. I see that you mention tools that I have never heard of or completely forgotten about or never understood. They may be nice for you, but it has one fatal flaw. A new FAQ maintainer has to learn something new. But it is easy to see that you have committed an important error. The main text is in a font face, and I think maybe a font size, which is not the one that I have chosen as what I prefer to see in my browsers. You have, as it happens, chosen a nice face and a suitable size for me; but in a document of the nature of a FAQ the user's choice for basic text should never be overruled. I cannot see whether you have done so, and it may in this case be totally irrelevant. BUT: also, all Web pages should be tested with Firefox Zoom Text Only. FireFox is a major browser, and ZTO can be much appreciated, especially by older readers. I do NOT want to read a document in which every little section is its own page; and I rather dislike coloured ink for basic text. 10.4 : "Popup windows cause usability problems and are generally best avoided." - "... windows often cause ...". The author's assumption may be valid in public Web JavaScript, but should not be extended to other fields unless proven equally correct there. Real Life has intervened; I now have less time at the computer, and more other things to do on it. -- (c) John Stockton, Surrey, UK. ?@merlyn.demon.co.uk Turnpike v6.05 MIME. Web <http://www.merlyn.demon.co.uk/> - FAQish topics, acronyms, & links. Proper <= 4-line sig. separator as above, a line exactly "-- " (SonOfRFC1036) Do not Mail News to me. Before a reply, quote with ">" or "> " (SonOfRFC1036)
[toc] | [prev] | [next] | [standalone]
| From | Scott Sauyet <scott.sauyet@gmail.com> |
|---|---|
| Date | 2012-12-10 17:53 -0800 |
| Message-ID | <18e8688c-731a-46ce-b81f-bdf3b30e1a5d@10g2000yqo.googlegroups.com> |
| In reply to | #17664 |
Dr J R Stockton wrote: > Scott Sauyet posted: >> Dr J R Stockton wrote: > >>> Therefore, the only satisfactory master, editable, representations are >>> "ASCII" text and straightforward HTML+CSS (with use of ECMAscript >>> allowed). > >> I'd rather it not involve HTML or CSS for day-to-day maintenance. Of >> course if it's presented over the Web, there would be some of each >> involved, but my goal would be to mostly avoid both and use a simpler >> text format, ideally one that would serve directly as the regular >> postings to the group. I will describe my efforts to that effect so >> far below. > > If one wants it to appear on the Web, it needs to be in HTML+CSS, as TXT > files of this length are not so easy to read, especially by the younger > elements. For the Newsgroup, it must be TXT style. I believe that it > is sufficiently easy to find (and keep with the master copy) text > to/from HTML converters. But the method must support all formatting > required in either distributed version (at present, IIRC, it does not). > > Since this is a JavaScript group, and the predominant interest is in > JavaScript for the Web, it is reasonable to expect any maintainer to be > able to work with HTML+CSS, as well as TXT. I agree, but it's also important that it be as easy to work with as possible. If the FAQ is stored in text files in a format similar to that used in the daily posting, it would be quite easy to edit each section. That is the primary goal. The tools I'm investigating are ones to - make it simple to convert these text formats to both individual FAQ pages, which many people prefer, and to a single combined page, which a number of others prefer - make it easy for people to collaborate on the pages, so that, whether there is a single maintainer or a group of them, it's easy for anyone to make suggestions for changes, and easy for the maintainer(s) to quickly incorporate such changes - make it straightforward to present the daily posting and to understand what will be posted and how it will be formatted when it's posted >>> The form of the existing FAQ as seen in the newsgroup has suffered >>> because of limitations in the method used to generate it from the form >>> in which it is edited. > >> I agree. Again, I don't know if you think I was suggesting something >> helpful or not, but please take a look at what I'm working on below >> and see if you think it would make FAQ maintenance more >> straightforward. > > I see that you mention tools that I have never heard of or completely > forgotten about or never understood. They may be nice for you, but it > has one fatal flaw. A new FAQ maintainer has to learn something new. I think you may be missing a key point. I'm trying to create a collections of tools to automate almost all of the process. There is only one tool that people would have to know in order to directly contribute: GitHub. The rest would, ideally, all be run automatically. Once they're created, the maintainer(s) would not have to understand any of their details. But GitHub would be somewhat central in this view, as it would be the method of collaboration. This is little different from noting that currently the FAQ maintainer needs to have skills with FTP in order to maintain the FAQ. Somehow or another, what you write on your machine has to make it out into the world. GitHub is certainly more complex than FTP, but it's not particularly difficult to learn. > But it is easy to see that you have committed an important error. The > main text is in a font face, and I think maybe a font size, which is not > the one that I have chosen as what I prefer to see in my browsers. You > have, as it happens, chosen a nice face and a suitable size for me; but > in a document of the nature of a FAQ the user's choice for basic text > should never be overruled. I did try to make it clear that my design skills are not strong. I'm assuming that there will be someone here who could help create CSS that would meet the group's goals for clarity and attractiveness. > I cannot see whether you have done so, and it may in this case be > totally irrelevant. BUT: also, all Web pages should be tested with > Firefox Zoom Text Only. FireFox is a major browser, and ZTO can be much > appreciated, especially by older readers. I'm not sure there is a difference between Firefox's normal zoom mode and ZTO in a text-only page, but all the fonts will certainly scale properly in the design that's there. > I do NOT want to read a document in which every little section is its > own page; There are advocates for both positions. I was focusing on the easier one first, which was the individual pages, but did note that I would expect to also post an all-in-one FAQ out of the same source material. It will be only slightly more complex, but it was not available yet in the codebase I borrowed from older projects of mine. If we like the overall approach, I would expect to add it soon. But since I want to rework the code to run on a different sort of platform anyway, I would wait until that is done. > and I rather dislike coloured ink for basic text. Again, I'm assuming that the design will be thrown away eventually. I'm mostly interested in the infrastructure at this point. -- Scott
[toc] | [prev] | [next] | [standalone]
| From | Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> |
|---|---|
| Date | 2012-12-12 21:07 +0000 |
| Message-ID | <Y6wAFuQ4HPyQFw7P@invalid.uk.co.demon.merlyn.invalid> |
| In reply to | #17668 |
In comp.lang.javascript message <18e8688c-731a-46ce-b81f-bdf3b30e1a5d@10 g2000yqo.googlegroups.com>, Mon, 10 Dec 2012 17:53:39, Scott Sauyet <scott.sauyet@gmail.com> posted: >Dr J R Stockton wrote: >> Scott Sauyet posted: >>> Dr J R Stockton wrote: > GitHub is certainly more complex than FTP, but it's not >particularly difficult to learn. I found its home page. It is not obvious where I should go next. Therefore it is either too complex or badly designed. The demo FAQ section set should include the part of the FAQ leading to GitHub, with URLs for learning and for working. >> But it is easy to see that you have committed an important error. The >> main text is in a font face, and I think maybe a font size, which is not >> the one that I have chosen as what I prefer to see in my browsers. You >> have, as it happens, chosen a nice face and a suitable size for me; but >> in a document of the nature of a FAQ the user's choice for basic text >> should never be overruled. > >I did try to make it clear that my design skills are not strong. I'm >assuming that there will be someone here who could help create CSS >that would meet the group's goals for clarity and attractiveness. This is a newsgroup. No design skills should be used. Plain text won WWII; the losers started with Fraktur or similar; the other losers favoured squashed spiders. Any tarting up will reduce accessibility for some. Eschew surplusage. >> I cannot see whether you have done so, and it may in this case be >> totally irrelevant. BUT: also, all Web pages should be tested with >> Firefox Zoom Text Only. FireFox is a major browser, and ZTO can be much >> appreciated, especially by older readers. > >I'm not sure there is a difference between Firefox's normal zoom mode >and ZTO in a text-only page, but all the fonts will certainly scale >properly in the design that's there. To be sure, test. Test ASAP. If it is fundamentally an ASCII document, it will be OK. But introduce _any_ CSS layout with units other than (AFAIR) em & ex, and failure is probable. Just roam the Web using Firefox with ZTO turned on, and try a few steps UP of Ctrl-wheel on each site. Start, say, with a Google search results page - the results are OK, the foot is neatly OK, the top fails. Try www.nasa.gov. Try the heartlands of incompetence, www.usa.gov &http://www.whitehouse.gov/. Contrast https://www.gov.uk/ - and http://www.whitehouse.gov/our-government !!. But why "our"? - the WWW is WW. Parochial. http://www.canada.gc.ca/home.html is nearly right. http://www.govern.ad/ is rather good. >> and I rather dislike coloured ink for basic text. > >Again, I'm assuming that the design will be thrown away eventually. >I'm mostly interested in the infrastructure at this point. Indeed. But you are including that which should not be there. One should, by the way, also test printing in various browsers. One of our local help-the-people sites is OK on screen for me, dark enough text on light enough. But, printed in one common browser, the text is undesirably faint, though readable in a good light etc. Printed in another common browser, that part of the paper could easily be reused as lightly shop-soiled white paper. I expect that using black text on white or light pastel background on screen, with no special media CSS, would have been fine. -- (c) John Stockton, nr London UK Reply address via Home Page. news:comp.lang.javascript FAQ <http://www.jibbering.com/faq/index.html>. <http://www.merlyn.demon.co.uk/js-index.htm> jscr maths, dates, sources. <http://www.merlyn.demon.co.uk/> TP/BP/Delphi/jscr/&c, FAQ items, links.
[toc] | [prev] | [next] | [standalone]
| From | Wally W. <ww84wa@aim.com> |
|---|---|
| Date | 2012-12-12 21:52 -0500 |
| Message-ID | <rrfic8h8is509sm0eu6ngbacorge59cvct@4ax.com> |
| In reply to | #17684 |
On Wed, 12 Dec 2012 21:07:04 +0000, Dr J R Stockton wrote: >In comp.lang.javascript message <18e8688c-731a-46ce-b81f-bdf3b30e1a5d@10 >g2000yqo.googlegroups.com>, Mon, 10 Dec 2012 17:53:39, Scott Sauyet ><scott.sauyet@gmail.com> posted: > >>Dr J R Stockton wrote: >>> Scott Sauyet posted: >>>> Dr J R Stockton wrote: > >> GitHub is certainly more complex than FTP, but it's not >>particularly difficult to learn. > >I found its home page. It is not obvious where I should go next. >Therefore it is either too complex or badly designed. > >The demo FAQ section set should include the part of the FAQ leading to >GitHub, with URLs for learning and for working. > > >>> But it is easy to see that you have committed an important error. The >>> main text is in a font face, and I think maybe a font size, which is not >>> the one that I have chosen as what I prefer to see in my browsers. You >>> have, as it happens, chosen a nice face and a suitable size for me; but >>> in a document of the nature of a FAQ the user's choice for basic text >>> should never be overruled. >> >>I did try to make it clear that my design skills are not strong. I'm >>assuming that there will be someone here who could help create CSS >>that would meet the group's goals for clarity and attractiveness. > >This is a newsgroup. No design skills should be used. Plain text won >WWII; the losers started with Fraktur or similar; the other losers >favoured squashed spiders. Any tarting up will reduce accessibility for >some. Eschew surplusage. > > >>> I cannot see whether you have done so, and it may in this case be >>> totally irrelevant. BUT: also, all Web pages should be tested with >>> Firefox Zoom Text Only. FireFox is a major browser, and ZTO can be much >>> appreciated, especially by older readers. >> >>I'm not sure there is a difference between Firefox's normal zoom mode >>and ZTO in a text-only page, but all the fonts will certainly scale >>properly in the design that's there. > >To be sure, test. Test ASAP. > >If it is fundamentally an ASCII document, it will be OK. But introduce >_any_ CSS layout with units other than (AFAIR) em & ex, and failure is >probable. > >Just roam the Web using Firefox with ZTO turned on, and try a few steps >UP of Ctrl-wheel on each site. Start, say, with a Google search results >page - the results are OK, the foot is neatly OK, the top fails. Try >www.nasa.gov. Try the heartlands of incompetence, www.usa.gov >&http://www.whitehouse.gov/. Contrast https://www.gov.uk/ - and >http://www.whitehouse.gov/our-government !!. But why "our"? - the WWW >is WW. Parochial. http://www.canada.gc.ca/home.html is nearly right. >http://www.govern.ad/ is rather good. http://www.imdb.com/title/tt0102975/quotes Let us redefine progress to mean that just because we can do a thing, it does not necessarily mean we must do that thing. http://www.notebooksapp.com/ios/work-with-plain-text-notes/ Typing plain text is distraction free; there is no need to care about format and style, it is just about writing.
[toc] | [prev] | [next] | [standalone]
| From | John G Harris <john@nospam.demon.co.uk> |
|---|---|
| Date | 2012-12-13 16:05 +0000 |
| Message-ID | <3vaUn9IczfyQFw+Z@J.A830F0FF37FB96852AD08924D9443D28E23ED5CD> |
| In reply to | #17684 |
On Wed, 12 Dec 2012 at 21:07:04, in comp.lang.javascript, Dr J R Stockton wrote: <snip> >This is a newsgroup. No design skills should be used. Plain text won >WWII; the losers started with Fraktur or similar; the other losers >favoured squashed spiders. Any tarting up will reduce accessibility for >some. Eschew surplusage. Please don't think that 'design' is a synonym for 'complicated'. A really good design usually looks simple. It's the thought behind it that was complicated. As for plain text, books on document design recommend sans-serif for headings and serif for bulk text. It's just unfortunate that Times Roman looks good when printed by a laser or inkjet printer but rather nasty on a typical PC screen. That said, plain text is much better than whizzo complications that don't work in some browsers. I have to say that the current FAQ's css file looks as though its job is to replace all the browsers' default styles. Over the top methinks. <snip> >To be sure, test. Test ASAP. > >If it is fundamentally an ASCII document, it will be OK. But introduce >_any_ CSS layout with units other than (AFAIR) em & ex, and failure is >probable. <snip> I've never used Zoom for real so it would help me if you would have a look at <http://www.jghnorth.org.uk/faqdesign/faq2.html> and tell me if it looks ok so far. Likewise for the three background colours. John -- John Harris
[toc] | [prev] | [next] | [standalone]
| From | Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> |
|---|---|
| Date | 2012-12-15 00:40 +0000 |
| Message-ID | <dbjR9KZ1b8yQFwJy@invalid.uk.co.demon.merlyn.invalid> |
| In reply to | #17691 |
In comp.lang.javascript message <3vaUn9IczfyQFw+Z@J.A830F0FF37FB96852AD0 8924D9443D28E23ED5CD>, Thu, 13 Dec 2012 16:05:48, John G Harris <john@nospam.demon.co.uk> posted: >On Wed, 12 Dec 2012 at 21:07:04, in comp.lang.javascript, Dr J R >Stockton wrote: > > <snip> >>This is a newsgroup. No design skills should be used. Plain text won >>WWII; the losers started with Fraktur or similar; the other losers >>favoured squashed spiders. Any tarting up will reduce accessibility for >>some. Eschew surplusage. > >Please don't think that 'design' is a synonym for 'complicated'. A >really good design usually looks simple. It's the thought behind it that >was complicated. The 'thought behind' needs also to be right, which is harder if it is complicates. A complicated design is a burden to future maintenance. >As for plain text, books on document design recommend sans-serif for >headings and serif for bulk text. It's just unfortunate that Times Roman >looks good when printed by a laser or inkjet printer but rather nasty on >a typical PC screen. > >That said, plain text is much better than whizzo complications that >don't work in some browsers. > >I have to say that the current FAQ's css file looks as though its job is >to replace all the browsers' default styles. Over the top methinks. Isn't that a rather long way of spelling "inane"? I normally use a version of the FAQ with NO stylesheet when I actually want to emulate a typical intended FAQ reader for my own benefit. > <snip> >>To be sure, test. Test ASAP. >> >>If it is fundamentally an ASCII document, it will be OK. But introduce >>_any_ CSS layout with units other than (AFAIR) em & ex, and failure is >>probable. > <snip> >I've never used Zoom for real See <http://www.merlyn.demon.co.uk/www-use1.htm#ZTO>, now re-dogged. >so it would help me if you would have a >look at > <http://www.jghnorth.org.uk/faqdesign/faq2.html> >and tell me if it looks ok so far. Likewise for the three background >colours. This includes comment on the text itself. It appears well-nigh perfect, visually. Some would wrap the "bulk code" to within the page width, but I would not. But the typewriter font should match the bulk text font in height, line height, and width of a moderately wide character. OTOH, while the text font varies between OK & good at different zooms, I do think that for a computing FAQ the font should have A 0123456789 Z with tops and bottoms visibly level. In some Zooms, the thickness ratio between thick parts and thin parts of a character, e.g. sides and top of an "o", becomes too large. I suggest styling a pretty border at the bottom of the BODY element. There is a - after 10.1 but not after 10.2. The colours are *marginally* darker than I *now* prefer. OTOH I'd prefer the FAQ and my own pages not to look *too* similar. A further requirement for a FAQ author is that his/her keyboard should always generate the character, and only the character, that was intended. I have that problem, and it is not the fault of the hardware. The first "self" should not be in that font. Section 10.1 : the back button can at least be apparently disabled; examples can be found in links from <http://www.spacetoday.net/>. It can also be apparently modified; read any linked multi-page "Florida Today" article to the end, then use "Back" once; and contrast with other sites. Section 10.2 : frame content can be accessed (roughly?:) either as a DOM tree or as a BODY string. Examples or text should indicate both. Section 10.2 needs combining with other sections after which the whole should de digested stirred, and re-partitioned. The very last line seems to be in the language of another country <G>. http://www.jghnorth.org.uk/faqdesign/faq2.css : Incorrect date; should be 2012-12-13. IIRC, you have it in Finnish. I do not think it good to change A:link & A.visited. Personally, I use <TT> rather than <CODE>; it is twice as quick to type, and shorter. I think I would style red_box with width 60%, margin auto. But I've not checked. -- (c) John Stockton, nr London, UK. For Mail, see Home Page. Turnpike, WinXP. Web <http://www.merlyn.demon.co.uk/> - FAQ-type topics, acronyms, and links. Command-prompt MiniTrue is useful for viewing/searching/altering files. Free, DOS/Win/UNIX now 2.0.6; see <URL:http://www.merlyn.demon.co.uk/pc-links.htm>.
[toc] | [prev] | [next] | [standalone]
| From | Scott Sauyet <scott.sauyet@gmail.com> |
|---|---|
| Date | 2012-12-13 08:09 -0800 |
| Message-ID | <55e1ad32-a46d-4993-bfc6-423082713114@4g2000yqv.googlegroups.com> |
| In reply to | #17684 |
Dr J R Stockton wrote:
> Scott Sauyet posted:
>>> Dr J R Stockton wrote:
>>> Scott Sauyet posted:
>>>> Dr J R Stockton wrote:
>> GitHub is certainly more complex than FTP, but it's not
>> particularly difficult to learn.
>
> I found its home page. It is not obvious where I should go next.
> Therefore it is either too complex or badly designed.
So did you learn to use FTP from a particular web page? Would you
expect a new user to learn it that way now? The same is true to me
for GitHub, although I think GitHub is a little better in that it does
offer learning material on its front page.
> The demo FAQ section set should include the part of the FAQ leading to
> GitHub, with URLs for learning and for working.
The only demo FAQ sections I've talked about are the ones like this,
which were clearly labeled as very early experiments:
<http://scott.sauyet.com/Javascript/Demo/2012-12-09b/10.2/
index.md>
<http://scott.sauyet.com/Javascript/Demo/2012-12-09b/10.2/>
The former is meant to be a source format both easy to maintain and
easy to auto-post to the group. The latter is a sample output of an
attempt to convert this to a format that might be hosted on the web.
I believe I've made it clear that there would also be an all-in-one
document containing the entire FAQ, but that this was easier to work
with for the moment.
Posted on GitHub would be two things: First, the collection of
documents in the first format. Second, the collection of tools to
automate the conversion to the Web format and to auto-post the
documents to the group. I have started on the documents, and have a
very rough initial pass at the format conversion tools. I have not
done anything yet about the auto-posting tools. A few others have
volunteered to help do more of the documents.
But I was not expecting that GitHub would be the host of the FAQ, just
the source code repository, our means of collaborating on changes.
>>> But it is easy to see that you have committed an important error. The
>>> main text is in a font face, and I think maybe a font size, which is not
>>> the one that I have chosen as what I prefer to see in my browsers. You
>>> have, as it happens, chosen a nice face and a suitable size for me; but
>>> in a document of the nature of a FAQ the user's choice for basic text
>>> should never be overruled.
>
>> I did try to make it clear that my design skills are not strong. I'm
>> assuming that there will be someone here who could help create CSS
>> that would meet the group's goals for clarity and attractiveness.
>
> This is a newsgroup. No design skills should be used. Plain text won
> WWII; the losers started with Fraktur or similar; the other losers
> favoured squashed spiders. Any tarting up will reduce accessibility for
> some. Eschew surplusage.
Right now the FAQ has a style sheet showing someone's design ideas:
<http://jibbering.com/faq/faq.css>
We post plain text to the group. When we host things on the Web,
we'll see what the group wants. Your request for scalable fonts has
been heard. I believe that those pages already had them. Your
request for as plain styling as possible has also been heard. I'm
really not ready to hold these discussions myself. I'm focused on
getting my suggested infrastructure in good enough shape for the group
to decide if it's worth using.
>>> I cannot see whether you have done so, and it may in this case be
>>> totally irrelevant. BUT: also, all Web pages should be tested with
>>> Firefox Zoom Text Only. FireFox is a major browser, and ZTO can be much
>>> appreciated, especially by older readers.
>
>> I'm not sure there is a difference between Firefox's normal zoom mode
>> and ZTO in a text-only page, but all the fonts will certainly scale
>> properly in the design that's there.
>
> To be sure, test. Test ASAP.
>
> If it is fundamentally an ASCII document, it will be OK. But introduce
> _any_ CSS layout with units other than (AFAIR) em & ex, and failure is
> probable.
FTR, are you seeing any problems in this with the documents I posted?
Because as far as I can tell, they are working fine. I double-checked
because you raised the issue. But you don't seem satisfied by my
reassurances. Have you noticed an issue?
> [ ... ]
>>> and I rather dislike coloured ink for basic text.
>
>> Again, I'm assuming that the design will be thrown away eventually.
>> I'm mostly interested in the infrastructure at this point.
>
> Indeed. But you are including that which should not be there.
>
> One should, by the way, also test printing in various browsers. [ ... ]
Eventually, yes, when focusing on the design becomes a higher
priority.
-- Scott
[toc] | [prev] | [next] | [standalone]
| From | Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> |
|---|---|
| Date | 2012-12-15 00:40 +0000 |
| Message-ID | <EL2XpvYgb8yQFwLR@invalid.uk.co.demon.merlyn.invalid> |
| In reply to | #17692 |
In comp.lang.javascript message <55e1ad32-a46d-4993-bfc6-423082713114@4g 2000yqv.googlegroups.com>, Thu, 13 Dec 2012 08:09:04, Scott Sauyet <scott.sauyet@gmail.com> posted: >Dr J R Stockton wrote: >> Scott Sauyet posted: >>>> Dr J R Stockton wrote: >>>> Scott Sauyet posted: >>>>> Dr J R Stockton wrote: > >>> GitHub is certainly more complex than FTP, but it's not >>> particularly difficult to learn. >> >> I found its home page. It is not obvious where I should go next. >> Therefore it is either too complex or badly designed. > >So did you learn to use FTP from a particular web page? Would you >expect a new user to learn it that way now? The same is true to me >for GitHub, although I think GitHub is a little better in that it does >offer learning material on its front page. I first learned, and used, FTP at the DOS command line. I **think** my first home browser was in an ISP-supplied disc containing WS_FTP, the operation of which is obvious enough; I still use (upgraded) WS_FTP. My present computer supplier supplied a 64-bit FTP for Win 7 pro 64-bit, and demonstrated it. Later, I eventually managed to do a transfer with it unaided. Then I tried to load WS_FTP using the old loader. It worked perfectly. >> The demo FAQ section set should include the part of the FAQ leading to >> GitHub, with URLs for learning and for working. > >The only demo FAQ sections I've talked about are the ones like this, >which were clearly labeled as very early experiments: > > <http://scott.sauyet.com/Javascript/Demo/2012-12-09b/10.2/ >index.md> > <http://scott.sauyet.com/Javascript/Demo/2012-12-09b/10.2/> > >The former is meant to be a source format both easy to maintain and >easy to auto-post to the group. The latter is a sample output of an >attempt to convert this to a format that might be hosted on the web. >I believe I've made it clear that there would also be an all-in-one >document containing the entire FAQ, but that this was easier to work >with for the moment. The demo should include that so that those reading the demo can find the recommended parts of GitHub. >Posted on GitHub would be two things: First, the collection of >documents in the first format. Second, the collection of tools to >automate the conversion to the Web format and to auto-post the >documents to the group. I have started on the documents, and have a >very rough initial pass at the format conversion tools. I have not >done anything yet about the auto-posting tools. A few others have >volunteered to help do more of the documents. > >But I was not expecting that GitHub would be the host of the FAQ, just >the source code repository, our means of collaborating on changes. > > > >>>> But it is easy to see that you have committed an important error. The >>>> main text is in a font face, and I think maybe a font size, which is not >>>> the one that I have chosen as what I prefer to see in my browsers. You >>>> have, as it happens, chosen a nice face and a suitable size for me; but >>>> in a document of the nature of a FAQ the user's choice for basic text >>>> should never be overruled. >> >>> I did try to make it clear that my design skills are not strong. I'm >>> assuming that there will be someone here who could help create CSS >>> that would meet the group's goals for clarity and attractiveness. >> >> This is a newsgroup. No design skills should be used. Plain text won >> WWII; the losers started with Fraktur or similar; the other losers >> favoured squashed spiders. Any tarting up will reduce accessibility for >> some. Eschew surplusage. > >Right now the FAQ has a style sheet showing someone's design ideas: > > <http://jibbering.com/faq/faq.css> The FAQ is much better without it - which does not mean that ALL styling is bad, just that too much is bad. >We post plain text to the group. When we host things on the Web, >we'll see what the group wants. Your request for scalable fonts has >been heard. I believe that those pages already had them. Your >request for as plain styling as possible has also been heard. I'm >really not ready to hold these discussions myself. I'm focused on >getting my suggested infrastructure in good enough shape for the group >to decide if it's worth using. > > >>>> I cannot see whether you have done so, and it may in this case be >>>> totally irrelevant. BUT: also, all Web pages should be tested with >>>> Firefox Zoom Text Only. FireFox is a major browser, and ZTO can be much >>>> appreciated, especially by older readers. >> >>> I'm not sure there is a difference between Firefox's normal zoom mode >>> and ZTO in a text-only page, but all the fonts will certainly scale >>> properly in the design that's there. >> >> To be sure, test. Test ASAP. >> >> If it is fundamentally an ASCII document, it will be OK. But introduce >> _any_ CSS layout with units other than (AFAIR) em & ex, and failure is >> probable. > >FTR, are you seeing any problems in this with the documents I posted? >Because as far as I can tell, they are working fine. I double-checked >because you raised the issue. But you don't seem satisfied by my >reassurances. Have you noticed an issue? If I had so noticed, I would have indicated where. I'm just indicating to you and others what I consider to be basic rules for all strictly- informative document parts, to be broken only where necessary and with care. ***IF*** you have systematically broken them, then one of us is thinking incorrectly. If one or two visible breaks have slipped in, they are minor bugs, on a level with being unable, like me, to spell Phaedippides correctly. -- (c) John Stockton, nr London, UK. Mail via homepage. Turnpike v6.05 MIME. Web <http://www.merlyn.demon.co.uk/> - FAQqish topics, acronyms and links; Astro stuff via astron-1.htm, gravity0.htm ; quotings.htm, pascal.htm, etc. No Encoding. Quotes before replies. Snip well. Write clearly. Don't Mail News.
[toc] | [prev] | [next] | [standalone]
| From | Scott Sauyet <scott.sauyet@gmail.com> |
|---|---|
| Date | 2012-12-15 11:02 -0800 |
| Message-ID | <94d85931-0447-446a-b403-124e797ab4da@i1g2000vbp.googlegroups.com> |
| In reply to | #17706 |
Dr J R Stockton wrote:
> Scott Sauyet posted:
>> Dr J R Stockton wrote:
>>> The demo FAQ section set should include the part of the FAQ leading to
>>> GitHub, with URLs for learning and for working.
>
>> The only demo FAQ sections I've talked about are the ones like this,
>> which were clearly labeled as very early experiments:
>
>> <http://scott.sauyet.com/Javascript/Demo/2012-12-09b/10.2/index.md>
>> <http://scott.sauyet.com/Javascript/Demo/2012-12-09b/10.2/>
>
>> The former is meant to be a source format both easy to maintain and
>> easy to auto-post to the group. The latter is a sample output of an
>> attempt to convert this to a format that might be hosted on the web.
>> I believe I've made it clear that there would also be an all-in-one
>> document containing the entire FAQ, but that this was easier to work
>> with for the moment.
>
> The demo should include that so that those reading the demo can find the
> recommended parts of GitHub.
I'm sorry, but I'm not sure to what your pronoun is referring. What
should the demo include?
I've been at pains to explain that what I'm working on is an
infrastructure for maintaining the comp.lang.javascript FAQ. The
goals include making it as easy to maintain as possible by using a
simple plain text format such as Markdown, and making it as easy as
possible to collaborate and share possible changes (that's the reason
for Github). I also want simple auto-posting and HTML generation
systems written in Javascript. I was demonstrating only the latter at
the moment, as well as a simple Markdown version of the document.
But at this stage of the discussion there is no particular reason to
suggest that people seek out GitHub, except for those who would like
to participate in my experiment. For those people, what we have so
far is at:
<https://github.com/comp-lang-javascript/faq-alpha>
-- Scott
[toc] | [prev] | [next] | [standalone]
| From | Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> |
|---|---|
| Date | 2012-12-16 17:58 +0000 |
| Message-ID | <+idJTVMLvgzQFwH3@invalid.uk.co.demon.merlyn.invalid> |
| In reply to | #17712 |
In comp.lang.javascript message <94d85931-0447-446a-b403-124e797ab4da@i1 g2000vbp.googlegroups.com>, Sat, 15 Dec 2012 11:02:26, Scott Sauyet <scott.sauyet@gmail.com> posted: >Dr J R Stockton wrote: >> Scott Sauyet posted: >>> Dr J R Stockton wrote: > >>>> The demo FAQ section set should include the part of the FAQ leading to >>>> GitHub, with URLs for learning and for working. >> >>> The only demo FAQ sections I've talked about are the ones like this, >>> which were clearly labeled as very early experiments: >> >>> <http://scott.sauyet.com/Javascript/Demo/2012-12-09b/10.2/index.md> >>> <http://scott.sauyet.com/Javascript/Demo/2012-12-09b/10.2/> >> >>> The former is meant to be a source format both easy to maintain and >>> easy to auto-post to the group. The latter is a sample output of an >>> attempt to convert this to a format that might be hosted on the web. >>> I believe I've made it clear that there would also be an all-in-one >>> document containing the entire FAQ, but that this was easier to work >>> with for the moment. >> >> The demo should include that so that those reading the demo can find the >> recommended parts of GitHub. > >I'm sorry, but I'm not sure to what your pronoun is referring. What >should the demo include? Which pronoun? <g> The page which includes the demo should include, inside or outside the demo part, such links as might be wanted when reading or thinking about the demo. They could be a simple list outside the demo, or they could be included in the demo as a fictitious or pending section of the FAQ. >I've been at pains to explain that what I'm working on is an >infrastructure for maintaining the comp.lang.javascript FAQ. The >goals include making it as easy to maintain as possible by using a >simple plain text format such as Markdown, and making it as easy as >possible to collaborate and share possible changes (that's the reason >for Github). I also want simple auto-posting and HTML generation >systems written in Javascript. I was demonstrating only the latter at >the moment, as well as a simple Markdown version of the document. > >But at this stage of the discussion there is no particular reason to >suggest that people seek out GitHub, except for those who would like >to participate in my experiment. For those people, what we have so >far is at: > > <https://github.com/comp-lang-javascript/faq-alpha> That is not a first-visit-friendly page, for those who have not used GitHub. In order to comment meaningfully on whether using GitHub is a sensible choice for a FAQ, it is necessary to understand how GitHub is used. A newsgroup FAQ should be implemented in such a fashion that anybody who knows how to read and write News articles can step in immediately as the FAQ maintainer. It is difficult enough to find suitable maintainers; possibilities should not be forced to jump through extra hoops of learning before they can make alterations to the FAQ. Anyone who holds a responsible position should give some thought to what happens after he's gone -- that's why people write Wills, for example. Although the newsgroup covers all use of JavaScript-type languages, most usage of such (counting by author) is in Web pages, and all who write for Web pages should know basic HTML, and basic HTML is adequate for writhing a FAQ. So I see no benefit in another form of marking, however simple. -- (c) John Stockton, nr London UK. Mail, see Homepage. BP7, Delphi 3 & 2006. <http://www.merlyn.demon.co.uk/> TP/BP/Delphi/&c., FAQqy topics & links; <http://www.bancoems.com/CompLangPascalDelphiMisc-MiniFAQ.htm> clpdmFAQ; NOT <http://support.codegear.com/newsgroups/>: news:borland.* Guidelines
[toc] | [prev] | [next] | [standalone]
| From | "Evertjan." <exxjxw.hannivoort@inter.nl.net> |
|---|---|
| Date | 2012-12-17 11:22 +0100 |
| Message-ID | <XnsA12C73B6254DDeejj99@194.109.133.133> |
| In reply to | #17726 |
Dr J R Stockton wrote on 16 dec 2012 in comp.lang.javascript: > Although the newsgroup covers all use of JavaScript-type languages, most > usage of such (counting by author) is in Web pages, and all who write > for Web pages should know basic HTML, and basic HTML is adequate for > writhing a FAQ. So I see no benefit in another form of marking, however > simple. Indeed. While there could very well be genuine Javascript adepts who never have touched CSS, HTML or the DOM, I maintain we must expect such basic skills from the maintaining maintainer. -- Evertjan. The Netherlands. (Please change the x'es to dots in my emailaddress)
[toc] | [prev] | [next] | [standalone]
| From | Gene Wirchenko <genew@telus.net> |
|---|---|
| Date | 2012-12-17 10:40 -0800 |
| Message-ID | <8npuc8hrra8jqpr8hhaii21clk3t99dfm6@4ax.com> |
| In reply to | #17734 |
On Mon, 17 Dec 2012 11:22:29 +0100, "Evertjan."
<exxjxw.hannivoort@inter.nl.net> wrote:
>Dr J R Stockton wrote on 16 dec 2012 in comp.lang.javascript:
>
>> Although the newsgroup covers all use of JavaScript-type languages, most
>> usage of such (counting by author) is in Web pages, and all who write
>> for Web pages should know basic HTML, and basic HTML is adequate for
>> writhing a FAQ. So I see no benefit in another form of marking, however
>> simple.
>
>Indeed.
>
>While there could very well be genuine Javascript adepts who never have
>touched CSS, HTML or the DOM, I maintain we must expect such basic skills
>from the maintaining maintainer.
What would they be using JavaScript for?
I have never seen it used outside of a browser.
Sincerely,
Gene Wirchenko
[toc] | [prev] | [next] | [standalone]
| From | "Evertjan." <exxjxw.hannivoort@inter.nl.net> |
|---|---|
| Date | 2012-12-17 20:05 +0100 |
| Message-ID | <XnsA12CCC56F8DD1eejj99@194.109.133.133> |
| In reply to | #17744 |
Gene Wirchenko wrote on 17 dec 2012 in comp.lang.javascript: > What would they be using JavaScript for? > > I have never seen it used outside of a browser. Maybe the world, even the cyberworld, is bigger than you have seen. I use Javascript regularily serverside on a an ASP platform. I use Javascript in a cscript/wscript environment. ============================== Some other examples: V8 can run stand-alone or embedded in C++ applications. <http://code.google.com/p/v8/> Adobe's Acrobat and Adobe Reader support JavaScript in PDF files Some high-end Philips universal remote panels, including TSU9600 and TSU9400, can be scripted using a JavaScript-based tool called ProntoScript Sphere is an open source and cross platform computer program designed primarily to make role-playing games that use JavaScript as a scripting language The open-source Re-Animator framework allows developing 2D sprite-based games using JavaScript and XML Methabot is a web crawler that uses JavaScript as scripting language for custom filetype parsers and data extraction using E4X. The Unity game engine supports a modified JavaScript for scripting (in addition to C# and Boo) via Mono. DX Studio (3D engine) uses the SpiderMonkey implementation of JavaScript for game and simulation logic. Maxwell Render (rendering software) provides an ECMA standard based scripting engine for tasks automation. Google Apps Script in Google Spreadsheets and Google Sites allows users to create custom formulas, automate repetitive tasks and also interact with other Google products such as Gmail. Many IRC clients, like ChatZilla or XChat, use JavaScript for their scripting abilities. SpinetiX products media players and software use SpiderMonkey (JavaScript engine) to allow scripting through JavaScript within SVG files to create digital signage projects. -- Evertjan. The Netherlands. (Please change the x'es to dots in my emailaddress)
[toc] | [prev] | [next] | [standalone]
| From | Thomas 'PointedEars' Lahn <PointedEars@web.de> |
|---|---|
| Date | 2012-12-18 00:31 +0100 |
| Message-ID | <1912184.9IARt5OQqH@PointedEars.de> |
| In reply to | #17745 |
Evertjan. wrote:
> Gene Wirchenko wrote on 17 dec 2012 in comp.lang.javascript:
>> What would they be using JavaScript for?
>>
>> I have never seen it used outside of a browser.
>
> Maybe the world, even the cyberworld, is bigger than you have seen.
ACK.
> I use Javascript regularily serverside on a an ASP platform.
>
> I use Javascript in a cscript/wscript environment.
You are using Microsoft JScript in both cases.
> [examples of other ECMAScript implementations and their applications]
Good examples, except that you have mislabeled most of them, too.
PointedEars
--
var bugRiddenCrashPronePieceOfJunk = (
navigator.userAgent.indexOf('MSIE 5') != -1
&& navigator.userAgent.indexOf('Mac') != -1
) // Plone, register_function.js:16
[toc] | [prev] | [next] | [standalone]
| From | Osmo Saarikumpu <osmo@weppipakki.com> |
|---|---|
| Date | 2012-12-18 10:18 +0200 |
| Message-ID | <kap8sf$g3$1@speranza.aioe.org> |
| In reply to | #17748 |
On 18.12.2012 1:31, Thomas 'PointedEars' Lahn wrote: >> Evertjan. wrote: >> [examples of other ECMAScript implementations and their applications] > Good examples, except that you have mislabeled most of them, too. And many software programs use Jav... I mean ECMAScript implementations and their applications. It seems that my Program Files folder contains 941 .js files. Almost 900 of them belong to Dreamweaver (v. 8) which uses them for everything. -- Best wishes, Osmo
[toc] | [prev] | [next] | [standalone]
| From | "Evertjan." <exxjxw.hannivoort@inter.nl.net> |
|---|---|
| Date | 2012-12-18 13:38 +0100 |
| Message-ID | <XnsA12D8AD80A964eejj99@194.109.133.133> |
| In reply to | #17748 |
Thomas 'PointedEars' Lahn wrote on 18 dec 2012 in comp.lang.javascript: > Evertjan. wrote: > >> Gene Wirchenko wrote on 17 dec 2012 in comp.lang.javascript: >>> What would they be using JavaScript for? >>> >>> I have never seen it used outside of a browser. >> >> Maybe the world, even the cyberworld, is bigger than you have seen. > > ACK. > >> I use Javascript regularily serverside on a an ASP platform. >> >> I use Javascript in a cscript/wscript environment. > You are using Microsoft JScript in both cases. "Both"? I count 3. Jscript engine use, but without the DOM, and in the case of ASP-serverside with Request, Response, Session, Application, Server, etc,. functionalities. Gene did not talk about Javascript engines, but about the environment ["browser"]. He, so he implied, could not imagine the existance of other dimensions. >> [examples of other ECMAScript implementations and their applications] Who wrote that? Not me, I call the language Jacascript. > Good examples, except that you have mislabeled most of them, too. Why "too"? -- Evertjan. The Netherlands. (Please change the x'es to dots in my emailaddress)
[toc] | [prev] | [next] | [standalone]
| From | Thomas 'PointedEars' Lahn <PointedEars@web.de> |
|---|---|
| Date | 2012-12-18 14:59 +0100 |
| Message-ID | <9318321.jt3VhPffia@PointedEars.de> |
| In reply to | #17752 |
Evertjan. wrote: > Thomas 'PointedEars' Lahn wrote on 18 dec 2012 in comp.lang.javascript: >> Evertjan. wrote: >>> Gene Wirchenko wrote on 17 dec 2012 in comp.lang.javascript: >>>> What would they be using JavaScript for? >>>> >>>> I have never seen it used outside of a browser. >>> Maybe the world, even the cyberworld, is bigger than you have seen. >> >> ACK. >> >>> I use Javascript regularily serverside on a an ASP platform. >>> >>> I use Javascript in a cscript/wscript environment. > >> You are using Microsoft JScript in both cases. > > "Both"? I count 3. OK, three then. There is not much difference between CScript and WScript; both are part of the same environment, the Windows Script Host. (Which is why you put those in the same sentence, delimited only by “/”, is it not?) > Jscript _JScript_ > engine use, but without the DOM, and in the case of ASP-serverside > with Request, Response, Session, Application, Server, etc,. > functionalities. Not necessarily without the (MSHTML) DOM. However, all of the mentioned features are not part of the programming language, JScript, of course. > Gene did not talk about Javascript engines, There are no “Javascript engines”, and it does not change the fact that you have mislabeled ECMAScript implementations. > but about the environment ["browser"]. He, so he implied, could not > imagine the existance of other dimensions. I had understood that. It does not change the fact … >>> [examples of other ECMAScript implementations and their applications] > > Who wrote that? Not me, This is how one summarizes in Usenet. If you do not agree with my summary, you will have to explain why. But that will involve your understanding what, in general, you were *actually* talking about. > I call the language Jacascript. You called something “Javascript” that you mistakenly perceive to be a single programming language. >> Good examples, except that you have mislabeled most of them, too. > > Why "too"? Because you have mislabeled the first two/three examples as well. You are _not_ using “Javascript” there, you are using JScript, Microsoft's implementation of ECMAScript. See also <http://jibbering.com/faq/#jScript> or <http://PointedEars.de/scripts/faq/cljs/#jScript> (see also <news:2715826.m0UDekTA75@PointedEars.de>). HTH PointedEars -- Use any version of Microsoft Frontpage to create your site. (This won't prevent people from viewing your source, but no one will want to steal it.) -- from <http://www.vortex-webdesign.com/help/hidesource.htm> (404-comp.)
[toc] | [prev] | [next] | [standalone]
| From | John G Harris <john@nospam.demon.co.uk> |
|---|---|
| Date | 2012-12-18 16:33 +0000 |
| Message-ID | <rvRbiKD0rJ0QFwtK@J.A830F0FF37FB96852AD08924D9443D28E23ED5CD> |
| In reply to | #17753 |
On Tue, 18 Dec 2012 at 14:59:39, in comp.lang.javascript, Thomas 'PointedEars' Lahn wrote: >Evertjan. wrote: <snip> >Because you have mislabeled the first two/three examples as well. You >are _not_ using “Javascript” there, you are using JScript, Microsoft's >implementation of ECMAScript. <snip> Evertjan is talking about what ECMA 262 calls *ECMAScript execution environments*. It's not obvious that Thomas is. John -- John Harris
[toc] | [prev] | [next] | [standalone]
Page 7 of 12 — ← Prev page 1 … 5 6 [7] 8 9 … 12 Next page →
Back to top | Article view | comp.lang.javascript
csiph-web