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 6 of 12 — ← Prev page 1 … 4 5 [6] 7 8 … 12 Next page →
| From | Patricia Shanahan <pats@acm.org> |
|---|---|
| Date | 2012-12-06 20:26 -0800 |
| Message-ID | <fLmdneq_I9uE7VzNnZ2dnUVZ_rCdnZ2d@earthlink.com> |
| In reply to | #17552 |
On 12/6/2012 7:11 PM, Thomas 'PointedEars' Lahn wrote: ... > The FAQ is for people who are willing to do that, either because they know > that it is expected that you check a newsgroup's FAQ before you post or > because they are pointed to it in a posting. > > Therefore, that FAQ needs to be current and easily readable. I know that > the former is not the case, and you have confirmed my suspicion that the > latter is not the case, too. Which is why I applied for the job more than > two weeks ago and offered optional hosting of it on my server to increase > uptime, following the OP by Asen the day before. > > So – what exactly are we waiting for now? If the assumption is correct that > we do need a FAQ, why is it still not maintained? ... As I see it, the issue is whether, as a FAQ maintainer, you would be able and willing to set aside your own strongly held opinions, deferring to group consensus and/or vote. Ultimately, your articles only reflect on you. The FAQ is presumed to represent the views and attitudes of the newsgroup as a whole. It is like drafting a multi-author paper, or writing a technical manual that your employer is going to distribute to customers. Here's one way to resolve the impasse - just get editing, creating a new file with some other name on your server. Show how you operate as a FAQ-maintainer. Patricia
[toc] | [prev] | [next] | [standalone]
| From | Andrew Poulos <ap_prog@hotmail.com> |
|---|---|
| Date | 2012-12-07 20:40 +1100 |
| Message-ID | <ApWdnY7lDZcBJFzNnZ2dnUVZ_sadnZ2d@westnet.com.au> |
| In reply to | #17553 |
On 7/12/2012 3:26 PM, Patricia Shanahan wrote: > On 12/6/2012 7:11 PM, Thomas 'PointedEars' Lahn wrote: > ... > Here's one way to resolve the impasse - just get editing, creating a new > file with some other name on your server. Show how you operate as a > FAQ-maintainer. Perhaps if the maintainer was a paid position but certainly not for someone that will freely give of their time and expertise. Andrew Poulos
[toc] | [prev] | [next] | [standalone]
| From | Patricia Shanahan <pats@acm.org> |
|---|---|
| Date | 2012-12-07 01:58 -0800 |
| Message-ID | <EvOdnRfjYbMqIFzNnZ2dnUVZ_i2dnZ2d@earthlink.com> |
| In reply to | #17554 |
On 12/7/2012 1:40 AM, Andrew Poulos wrote: > On 7/12/2012 3:26 PM, Patricia Shanahan wrote: >> On 12/6/2012 7:11 PM, Thomas 'PointedEars' Lahn wrote: >> ... >> Here's one way to resolve the impasse - just get editing, creating a new >> file with some other name on your server. Show how you operate as a >> FAQ-maintainer. > > Perhaps if the maintainer was a paid position but certainly not for > someone that will freely give of their time and expertise. It's actually the other way round. If it were a paid position, he would be stuck with waiting for the group to work out how to reach agreement. In a volunteer situation, he might was well just get started, with anyone who is willing to help him, without bothering to wait for permission. My expectation is that, if he chooses to do so, he'll produce some FAQ-entries that are clearly better than the out of date material with have now, and his URL will be adopted as the working FAQ for the newsgroup. If I am wrong, and he is too rigid to be a good FAQ-maintainer, that will also become obvious, and the group will have to find some other solution. Patricia
[toc] | [prev] | [next] | [standalone]
| From | Thomas 'PointedEars' Lahn <PointedEars@web.de> |
|---|---|
| Date | 2012-12-07 14:32 +0100 |
| Message-ID | <11045641.EKsec1E7oM@PointedEars.de> |
| In reply to | #17555 |
Patricia Shanahan wrote: > On 12/7/2012 1:40 AM, Andrew Poulos wrote: >> On 7/12/2012 3:26 PM, Patricia Shanahan wrote: >>> On 12/6/2012 7:11 PM, Thomas 'PointedEars' Lahn wrote: >>> ... >>> Here's one way to resolve the impasse - just get editing, creating a new >>> file with some other name on your server. Show how you operate as a >>> FAQ-maintainer. >> Perhaps if the maintainer was a paid position but certainly not for >> someone that will freely give of their time and expertise. > > It's actually the other way round. If it were a paid position, he would > be stuck with waiting for the group to work out how to reach agreement. No, in a paid position there would be a superior telling me to do it (whether I want to or not, and whether my colleagues agree with that or not). > In a volunteer situation, he might was well just get started, with > anyone who is willing to help him, without bothering to wait for > permission. The issue here is a little bit more complex than you think. It is not only permission I am waiting for, it is also file access. Jim Ley is hosting the FAQ and FAQ Notes on his webspace. He holds the keys to the FAQ, he has said he “would be wary transferring [access and control] to anyone without a clear mandate from the group - so controversial figures need support”, and AFAIK he has not replied to *our* e-mails yet. > My expectation is that, if he chooses to do so, he'll produce some > FAQ-entries that are clearly better than the out of date material with > have now, and his URL will be adopted as the working FAQ for the > newsgroup. If I am wrong, and he is too rigid to be a good > FAQ-maintainer, that will also become obvious, and the group will have > to find some other solution. The problem with that approach is that it is not what I volunteered for. Being the cljs FAQ maintainer is not going to be my primary avocation. You (being retired?) might have that much extra free time on your hand; I have not. If you read this thread more carefully, the idea was to improve the existing FAQ (on my site if possible), to salvage the combined knowledge of regulars there in some way, and as a bonus improve its uptime and access speed. What you are proposing is for me to create a new FAQ from scratch instead, in my free time, while the current outdated FAQ continues to be online as *the* cljs FAQ, continues to be posted daily here, and going to waste. Because as I understand it I can not simply copy the current FAQ content and do with it as I please; nor would I want to. PointedEars -- Anyone who slaps a 'this page is best viewed with Browser X' label on a Web page appears to be yearning for the bad old days, before the Web, when you had very little chance of reading a document written on another computer, another word processor, or another network. -- Tim Berners-Lee
[toc] | [prev] | [next] | [standalone]
| From | Patricia Shanahan <pats@acm.org> |
|---|---|
| Date | 2012-12-07 07:22 -0800 |
| Message-ID | <yOWdnadVKMhylF_NnZ2dnUVZ_oUAAAAA@earthlink.com> |
| In reply to | #17560 |
On 12/7/2012 5:32 AM, Thomas 'PointedEars' Lahn wrote: ... > The issue here is a little bit more complex than you think. It is not only > permission I am waiting for, it is also file access. Jim Ley is hosting the > FAQ and FAQ Notes on his webspace. He holds the keys to the FAQ, he has > said he “would be wary transferring [access and control] to anyone without a > clear mandate from the group - so controversial figures need support”, and > AFAIK he has not replied to *our* e-mails yet. ... That does seem like a problem. Is there anyone non-controversial in the group? Patricia
[toc] | [prev] | [next] | [standalone]
| From | Scott Sauyet <scott.sauyet@gmail.com> |
|---|---|
| Date | 2012-12-07 11:19 -0800 |
| Message-ID | <f4da0dd3-3384-4ecd-9305-5efab0b33a67@r4g2000vbi.googlegroups.com> |
| In reply to | #17563 |
Patricia Shanahan wrote:
> Thomas 'PointedEars' Lahn wrote:
> ...> The issue here is a little bit more complex than you think. It is not only
>> permission I am waiting for, it is also file access. Jim Ley is hosting the
>> FAQ and FAQ Notes on his webspace. He holds the keys to the FAQ, he has
>> said he “would be wary transferring [access and control] to anyone without a
>> clear mandate from the group - so controversial figures need support”, and
>> AFAIK he has not replied to *our* e-mails yet.
> [ ... ]
> That does seem like a problem. Is there anyone non-controversial in the
> group?
How much fun would that be?
Probably not. But the ones who would probably generate the least
controversy are not particularly active anymore, and have in any case
fairly recently declined nomination. I'm thinking especially of
Richard Cornford, Lasse Nielsen, and perhaps RobG. Other with the
technical chops and little in the way of interpersonal controversy
might have problems with the requirements for excellent English
skills, although I think with extra editorial help could be excellent
maintainers, people like Asen Bozhilov and Dmitry Soshnikov. And I
still think people with temperaments like Stefan Weiss' would be among
the best we could have. But I would be most happy with a group that
had common access to a Github repository or some other shared resource
to make edits, with a single person with the authority to settle
internal disputes within the group.
If I can find time soon, I will try to set up something like that just
to see if it could work.
And by the way, anyone who wants to can work with the XML format of
the FAQ as it stands. It's at
<http://jibbering.com/faq/index.xml>
The HTML output is at
<http://jibbering.com/faq/>
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.
-- Scott
[toc] | [prev] | [next] | [standalone]
| From | Thomas 'PointedEars' Lahn <PointedEars@web.de> |
|---|---|
| Date | 2012-12-07 21:11 +0100 |
| Message-ID | <2577143.ucGkk5BXOF@PointedEars.de> |
| In reply to | #17568 |
Scott Sauyet wrote: > And by the way, anyone who wants to can work with the XML format of > the FAQ as it stands. It's at > > <http://jibbering.com/faq/index.xml> > > The HTML output is at > > <http://jibbering.com/faq/> What about copyright? PointedEars -- Sometimes, what you learn is wrong. If those wrong ideas are close to the root of the knowledge tree you build on a particular subject, pruning the bad branches can sometimes cause the whole tree to collapse. -- Mike Duffy in cljs, <news:Xns9FB6521286DB8invalidcom@94.75.214.39>
[toc] | [prev] | [next] | [standalone]
| From | Patricia Shanahan <pats@acm.org> |
|---|---|
| Date | 2012-12-07 16:19 -0800 |
| Message-ID | <dsSdnUctS4Y9Gl_NnZ2dnUVZ_oWdnZ2d@earthlink.com> |
| In reply to | #17572 |
On 12/7/2012 12:11 PM, Thomas 'PointedEars' Lahn wrote: > Scott Sauyet wrote: > >> And by the way, anyone who wants to can work with the XML format of >> the FAQ as it stands. It's at >> >> <http://jibbering.com/faq/index.xml> >> >> The HTML output is at >> >> <http://jibbering.com/faq/> > > What about copyright? The copyright notice in <http://jibbering.com/faq/index.xml> says "This FAQ is (C) Copyright Contributors on behalf of the newsgroup comp.lang.javascript. Upon change of the FAQ maintainer, the copyright will automatically pass over to the new maintainer." I'm not sure of the legality of such a self-contradictory notice, but it at least creates a case for claiming that the newsgroup participants, collectively, are the copyright owners. Presumably one or more individual contributors could assert copyright to their contributions, and we might need to remove those items and write clean new ones. Patricia
[toc] | [prev] | [next] | [standalone]
| From | Dr J R Stockton <reply1249@merlyn.demon.co.uk.invalid> |
|---|---|
| Date | 2012-12-08 18:33 +0000 |
| Message-ID | <cq+BhhOKg4wQFw6T@invalid.uk.co.demon.merlyn.invalid> |
| In reply to | #17568 |
In comp.lang.javascript message <f4da0dd3-3384-4ecd-9305-5efab0b33a67@r4 g2000vbi.googlegroups.com>, Fri, 7 Dec 2012 11:19:34, Scott Sauyet <scott.sauyet@gmail.com> 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. No newsgroup FAQ maintainer can be expected to live and be willing to work forever. A good newsgroup FAQ maintainer finds, and maybe even trains, a replacement. The only qualifications required of a newsgroup FAQ maintainer are sufficient commands of the language and of the given topic of a FAQ. 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. Therefore, the only satisfactory master, editable, representations are "ASCII" text and straightforward HTML+CSS (with use of ECMAscript allowed). 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. -- (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 | Scott Sauyet <scott.sauyet@gmail.com> |
|---|---|
| Date | 2012-12-08 22:14 -0800 |
| Message-ID | <9af7f027-c78f-491d-a427-4576adfcc768@10g2000yqk.googlegroups.com> |
| In reply to | #17615 |
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.
> 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.
> 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.
> 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.
-- Scott
======================================================================
I've been talking about making our FAQ more easily editable, and I
have made an initial stab at an approach that I think would be
worthwhile. I have taken Chapter 10 of the FAQ, and make fourteen
separate plain-text files, one for each FAQ section. At the bottom of
this page, below the next cut line ("===...===") is one example,
section 10.2, "How do I access a frame's content?", chosen because it
has more distinct types of content than most in this chapter. The
conversion of these fourteen sections took me between one-and-a-half
and two hours, but I became significantly faster as I proceeded.
The content is, IMHO, in a format suitable for posting to the group
right now. We would presumably append some boilerplate about the
location of the full FAQ and perhaps proficient hosting, and might
prepend the phrase "FAQ Topic", which I didn't include here. But
outside that, I think it's already in a format well-suited for
posting. Its format, though, is also a well-known text format used in
many places on the Web, a format known as Markdown. [1] The advantage
of using Markdown is that we can readily convert it to HTML. You can
test it for yourself and convert it to vanilla HTML using the Markdown
dingus [2]. But I've already done that for all fourteen of these
sections:
<http://scott.sauyet.com/Javascript/Demo/2012-12-09a/>
I have no indexing yet, just the raw output of running a small
conversion script on these markdown files. The one included below is
at:
<http://scott.sauyet.com/Javascript/Demo/2012-12-09a/10.2/>
The Markdown format of each of them is alongside the HTML; you can
find them by appending `index.md` to the HTML url:
<http://scott.sauyet.com/Javascript/Demo/2012-12-09a/10.2/
index.md>
I am no designer, and this is probably not the prettiest output format
we could create. If we decide to go with something like this
technique, I would hope that someone with better design skills would
build us some beautiful CSS. We could also decide later if we want to
include some client-side syntax highlighter for the source-code
examples. (My initial vote would be yes.)
I have not gotten around to trying to build the single-page FAQ. That
would involve much the same techniques, with additional work for the
table of contents. I'm not worried about doing that. If we decide to
do something like this, that would involve a smaller effort than
converting the remaining sections to the new format.
The technology stack I used here is a bit outdated, and I would like
to update it if I can before we proceed. I used Showdown [3], which
is a Javascript port of Markdown to do the conversion, running in
Mozilla's Rhino. The script used to load the files is fairly
esoteric, borrowing many techniques from an older version of JSDoc
Toolkit [4]. It converts these fourteen files in just a few seconds.
Eventually, this would have to be hooked up with posting the output
files to a web server. I'm sure we could easily automate that.
I actually would like to rewrite all this to run in Node.js, using a
different Markdown port, called js-markdown-extra [5], which adds some
features we might like that aren't included in Markdown or in the
Showdown port of it, things like simple tables and definition lists,
but those would be later decisions, only if folks here like the
general idea.
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. (For those who don't
know Github, a "pull request" is a very simply mechanism to ask one
person to look at a set of changes you've made to your copy and, if
you like them, include these changes in their own.)
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.
So that's my proposal. Please let me know what you think.
Below the cut-line is a sample section.
-- Scott
[1] http://daringfireball.net/projects/markdown/
[2] http://daringfireball.net/projects/markdown/dingus
[3] https://github.com/coreyti/showdown
[4] http://code.google.com/p/jsdoc-toolkit/
[5] https://github.com/tanakahisateru/js-markdown-extra
======================================================================
10.2 - How do I access a frame's content?
=========================================
To reference another frame on the _same domain_:
------------------------------------------------
The content window of a `FRAME` or `IFRAME` can be
accessed by the `frames` collection.
Example:
> var fwin;
> fwin = self.frames[0]; // or:
> fwin = self.frames["iframeName"];
or, from the `IFRAME` or `FRAME` element:
> var iframeEl = document.getElementById("myFrame");
> // Nonstandard, but widely supported.
> var fwin = iframeEl.contentWindow;
> // DOM2 HTML Standard.
> var fdoc = iframeEl.contentDocument;
A global identifier `moomin` in the the iframe's content window
is accessed as `fwin.moomin`.
To communicate between frames on _different_ domains:
-----------------------------------------------------
Where supported, (IE8, Firefox 3, Opera 9, Safari 4), use
`window.postMessage( message[, port], otherDomain);`.
Example: <http://jibbering.com/faq/example/postMessage.html>
Where `window.postMessage` is not supported, the `window.name`
property
can be set on the other window, which can poll for updates to that
property using `setInterval(checkWinName, 100);` where `checkWinName`
is a function that polls to check the value of
`self.name`.
----
* <http://en.wikipedia.org/wiki/Same_origin_policy>
* <http://www-archive.mozilla.org/docs/dom/domref/
dom_frame_ref5.html>
* <https://developer.mozilla.org/en/DOM/window.postMessage>
* <http://msdn.microsoft.com/en-us/library/cc197015(VS.85).aspx>
[toc] | [prev] | [next] | [standalone]
| From | Stefan Weiss <krewecherl@gmail.com> |
|---|---|
| Date | 2012-12-09 13:56 +0100 |
| Subject | FAQ source format (was: Maintainer of the FAQ) |
| Message-ID | <ka21pq$dnj$1@news.albasani.net> |
| In reply to | #17623 |
On 2012-12-09 07:14, Scott Sauyet wrote: > I've been talking about making our FAQ more easily editable, and I > have made an initial stab at an approach that I think would be > worthwhile. [...] > The content is, IMHO, in a format suitable for posting to the group > right now. We would presumably append some boilerplate about the > location of the full FAQ and perhaps proficient hosting, and might > prepend the phrase "FAQ Topic", which I didn't include here. But > outside that, I think it's already in a format well-suited for > posting. Its format, though, is also a well-known text format used in > many places on the Web, a format known as Markdown. [1] Thank you. I think Markdown is a good choice for the source format. It already looks pretty much like the auto-posted FAQ sections, even down to the delimiters for inline code. It would certainly make a lot editing easier than the current XML source. It would make the FAQ auto-poster script much simpler. A couple of years ago, I've helped with some changes in that script (which is written in Perl, btw). IIRC, it didn't even use an XML parser to process the source; it was all done with regular expressions. That's why some of the posted entries look badly formatted, especially when nested structures are processed (such as lists). > <http://scott.sauyet.com/Javascript/Demo/2012-12-09a/10.2/> > > The Markdown format of each of them is alongside the HTML; you can > find them by appending `index.md` to the HTML url: > > <http://scott.sauyet.com/Javascript/Demo/2012-12-09a/10.2/ > index.md> Looking good! A minor point: I would personally prefer a different markup (markdown) for code blocks. Instead of using >-style block quotes, we should use indentation. That's the usual way to do it in Markdown, and it would make it easier to copy&paste code snippets. Some other random thoughts: - The FAQ and related tools should be using Unicode/UTF-8 throughout. There used to be problems with certain newsreaders and Usenet servers, but using a legacy character set or encoding in this day and age wouldn't be right. - Currently, not all sections are posted to the group (some would not make sense as stand-alone text without the surrounding context). Similarly, some parts used to be posted more frequently (the Monday and Wednesday posts), but that appears to have been dropped some time ago. - The FAQ items and sections in the current source have embedded numerical IDs, in addition to text labels. I'm not sure if a static hierarchy is a good way to organize a changing document. It might be better to have an external index file instead. > We could also decide later if we want to > include some client-side syntax highlighter for the source-code > examples. (My initial vote would be yes.) Yes, that would be a nice enhancement. For example, CodeMirror can be used to highlight code (without displaying an editor). BTW, thanks again for mentioning CodeMirror earlier this year, we've been using it successfully for a while now. > I have not gotten around to trying to build the single-page FAQ. That > would involve much the same techniques, with additional work for the > table of contents. I'm not worried about doing that. If we decide to > do something like this, that would involve a smaller effort than > converting the remaining sections to the new format. I think that's something that can wait until the actual content has gotten an overhaul. From what I've seen, the general opinion is that the FAQ is too long as it is. Some of the content could be moved to a Recipes section, or removed completely. > I actually would like to rewrite all this to run in Node.js, using a > different Markdown port, called js-markdown-extra [5], which adds some > features we might like that aren't included in Markdown or in the > Showdown port of it, things like simple tables and definition lists, > but those would be later decisions, only if folks here like the > general idea. I like the idea of using JS for most of the FAQ tools. The js-markdown-extra project has an interesting warning about infinite loops, but that can probably be worked around (or fixed in the code). At some point, the FAQ autoposter script should also be rewritten in JS. There are now NNTP modules for Node.js, so I don't expect too much trouble there. > 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. I like this idea a lot, even more than using a wiki. Pull requests and issues would be public, and the maintainer(s) could then decide which of them to merge into the official version. GitHub also provides discussion pages for all pull requests and issues. In addition, every contributor would have a local copy of the whole repository, which avoids the scenario where a single FAQ maintainer gets hit by a train or has to run from the authorities in, say, Belize ;) - stefan
[toc] | [prev] | [next] | [standalone]
| From | Patricia Shanahan <pats@acm.org> |
|---|---|
| Date | 2012-12-09 08:09 -0800 |
| Subject | Re: FAQ source format |
| Message-ID | <i9adnRbql755KlnNnZ2dnUVZ_hmdnZ2d@earthlink.com> |
| In reply to | #17627 |
On 12/9/2012 4:56 AM, Stefan Weiss wrote: > On 2012-12-09 07:14, Scott Sauyet wrote: ... > A minor point: I would personally prefer a different markup (markdown) > for code blocks. Instead of using >-style block quotes, we should use > indentation. That's the usual way to do it in Markdown, and it would > make it easier to copy&paste code snippets. I agree. I've recently done some posting on Stackoverflow. They use indentation for blocks of code. I typically write my code in Eclipse, and use its "Source - Shift Right" between selecting the code I intend to paste and copying it. >> 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. > > I like this idea a lot, even more than using a wiki. Pull requests and > issues would be public, and the maintainer(s) could then decide which of > them to merge into the official version. GitHub also provides discussion > pages for all pull requests and issues. In addition, every contributor > would have a local copy of the whole repository, which avoids the > scenario where a single FAQ maintainer gets hit by a train or has to run > from the authorities in, say, Belize ;) The sooner it gets onto Github the sooner the rest of us can start helping out. Any scripts or tools should be hosted there as well. Patricia
[toc] | [prev] | [next] | [standalone]
| From | Scott Sauyet <scott.sauyet@gmail.com> |
|---|---|
| Date | 2012-12-09 19:12 -0800 |
| Subject | Re: FAQ source format |
| Message-ID | <50f43742-4ce2-4699-830d-3496210478f7@o6g2000yql.googlegroups.com> |
| In reply to | #17629 |
Patricia Shanahan wrote: > Stefan Weiss 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. > >> I like this idea a lot, even more than using a wiki. [ ... ] > > The sooner it gets onto Github the sooner the rest of us can start > helping out. Any scripts or tools should be hosted there as well. It's there. I will start another thread with more detailed information. -- Scott
[toc] | [prev] | [next] | [standalone]
| From | Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> |
|---|---|
| Date | 2012-12-10 20:49 +0000 |
| Subject | Re: FAQ source format |
| Message-ID | <eWfB+FOIrkxQFwQb@invalid.uk.co.demon.merlyn.invalid> |
| In reply to | #17629 |
In comp.lang.javascript message <i9adnRbql755KlnNnZ2dnUVZ_hmdnZ2d@earthl
ink.com>, Sun, 9 Dec 2012 08:09:42, Patricia Shanahan <pats@acm.org>
posted:
>I agree. I've recently done some posting on Stackoverflow. They use
>indentation for blocks of code. I typically write my code in Eclipse,
>and use its "Source - Shift Right" between selecting the code I intend
>to paste and copying it.
I have a JavaScript Autoindenter in my js-quick.htm; press Indt IN A
LOCAL COPY.
The code is short : the indentation is not as many would wish. But the
idea could be developed further.
This is the code, which has been indented by itself.
function Indt_(G) { var In=0, S2=" ", Lines, J, LL, K, SS, Line, C
Lines = G.Code.value.split("\n") // Code to Lines
for (J=0, LL=Lines.length ; J < LL ; J++) { // Per line
Line = Lines[J].replace(/^\s+|\s+$/g, "") // Trim the Line
if (!Line) continue // Empty
SS = "" ; K = In ; while (K--) SS += S2 // Build padding
if (!/^[A-Z]/i.test(Line)
&& !/^\/[/*]|^[{}]/.test(Line)) SS += S2 // Some Continuations
K = Line.length ; while (K--) { // Count +{ -}
C = Line.charAt(K) ; In += (C=="{") - (C=="}") }
Lines[J] = SS + Line } // Indent the Line
G.Code.value = Lines.join("\n") // Lines to Code
GetLen_(G) // Show good margin
if (In) alert("Net { } = " + In) }
--
(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-09 18:59 -0800 |
| Subject | Re: FAQ source format (was: Maintainer of the FAQ) |
| Message-ID | <0c625d16-2664-452b-ba35-fab7a57c3099@f4g2000yqh.googlegroups.com> |
| In reply to | #17627 |
Stefan Weiss wrote:
> Scott Sauyet wrote:
>
>> I've been talking about making our FAQ more easily editable, and I
>> have made an initial stab at an approach that I think would be
>> worthwhile.
>> [ ... ] I think it's already in a format well-suited for
>> posting. Its format, though, is also a well-known text format used in
>> many places on the Web, a format known as Markdown.
>
> Thank you. I think Markdown is a good choice for the source format. It
> already looks pretty much like the auto-posted FAQ sections, even down
> to the delimiters for inline code. It would certainly make a lot editing
> easier than the current XML source.
That was one of my three major goals; I'm glad to hear that you agree
that the approach would help.
I think I could probably convert the rest of the FAQ inside a week in
my spare time, if I actually have spare time around the home
remodeling that I'm doing. If others are willing to help, I'm sure we
could complete this in short order.
> It would make the FAQ auto-poster script much simpler. A couple of years
> ago, I've helped with some changes in that script (which is written in
> Perl, btw). IIRC, it didn't even use an XML parser to process the
> source; it was all done with regular expressions. That's why some of the
> posted entries look badly formatted, especially when nested structures
> are processed (such as lists).
This was the second of my three major goals. I think we should be
able to make changes to the posting more easily. I didn't know it was
Perl, but would have guessed so. The XML format it's in now is not
pleasant. I didn't even try creating the new versions from it; I used
recent postings instead. Using text files would definitely make it
more straightforward to post, and we could easily add some metadata
that wouldn't be included in the postings or the HTML which could be
used to help us determine more sophisticated rotations schedules for
the FAQ questions.
> [ ... ]
> A minor point: I would personally prefer a different markup (markdown)
> for code blocks. Instead of using >-style block quotes, we should use
> indentation. That's the usual way to do it in Markdown, and it would
> make it easier to copy&paste code snippets.
Yes, that was detritus. I was trying to use js-markdown-extra in
place of Showdown, and there was some small bug which added an initial
space to the first line of code blocks, but not when then were marked
with the `>`. I simply forgot to remove them before posting.
> Some other random thoughts:
>
> - The FAQ and related tools should be using Unicode/UTF-8 throughout.
> There used to be problems with certain newsreaders and Usenet servers,
> but using a legacy character set or encoding in this day and age
> wouldn't be right.
Absolutely. I'm starting to regret removing my Open Solaris partition
in favor of an Ubuntu one, which I seem to have thoroughly trashed;
now I'm stuck working on a Windows XP partition, and although I
remember to switch the line endings, I forgot the character set.
> - Currently, not all sections are posted to the group (some would not
> make sense as stand-alone text without the surrounding context).
> Similarly, some parts used to be posted more frequently (the Monday and
> Wednesday posts), but that appears to have been dropped some time ago.
It would be simple enough to add some metadata, probably a comment at
the bottom of each document containing JSON-formatted information that
could be used to guide these decisions.
> - The FAQ items and sections in the current source have embedded
> numerical IDs, in addition to text labels. I'm not sure if a static
> hierarchy is a good way to organize a changing document. It might be
> better to have an external index file instead.
I'm mixed about this. You're probably right, but I do love the
simplicity of building everything up from such simple documents. If
we do have an index document and metadata, perhaps each chapter could
have its unique short slug, and each document a short id that could
serve as a slug, so the document listed earlier might end with a
metadata section such as
<!-- {
chapter: windows,
slug: accessing-frames,
// ... ?
} -->
and an index file would organize a table of contents, and, if we
choose, a one-page FAQ. Then this document might be available at
<http://clj-faq.example.com/windows/accessing-frames>
>> We could also decide later if we want to
>> include some client-side syntax highlighter for the source-code
>> examples. (My initial vote would be yes.)
>
> Yes, that would be a nice enhancement. For example, CodeMirror can be
> used to highlight code (without displaying an editor). BTW, thanks again
> for mentioning CodeMirror earlier this year, we've been using it
> successfully for a while now.
I'm glad CodeMirror has worked for you.
I would probably have included something like it already if I were not
more interested in getting this quickly in front of people.
>> I have not gotten around to trying to build the single-page FAQ. That
>> would involve much the same techniques, with additional work for the
>> table of contents. I'm not worried about doing that. If we decide to
>> do something like this, that would involve a smaller effort than
>> converting the remaining sections to the new format.
>
> I think that's something that can wait until the actual content has
> gotten an overhaul.
Definitely. This would not be top priority.
> From what I've seen, the general opinion is that the
> FAQ is too long as it is. Some of the content could be moved to a
> Recipes section, or removed completely.
Possibly, but I think that John Stockton makes a good case that some
people want to get to the FAQ page and do a simple text search. I
don't think it would be hard to include and if that's the case, then I
would choose to keep it around.
>> I actually would like to rewrite all this to run in Node.js, using a
>> different Markdown port, called js-markdown-extra, which adds some
>> features we might like that aren't included in Markdown or in the
>> Showdown port of it, things like simple tables and definition lists,
>> but those would be later decisions, only if folks here like the
>> general idea.
>
> I like the idea of using JS for most of the FAQ tools.
Using Javascript for the FAQ tools was my third major goal. The
language has become widely available on the server-side and for
general-purpose scripting. It seems a shame not to be eating our own
dog food here.
> The js-markdown-extra project has an interesting warning about infinite
> loops, but that can probably be worked around (or fixed in the code).
I'm not thrilled with the code in js-markdown-extra, but I haven't run
into the bug they mention. I was thinking of this, and any of the
other code I'm using now, as scaffolding. All of it is probably sub-
optimal, but we can continue to use it until we have a chance to re-
write it the way we like. For the moment, I'm back to using Showdown
anyway. But I am much more interested in writing the main processing
part over. I wrote this some years back, before Node, and it would be
much simplified by using Node and the concomitant libraries. But
again, I wanted something available quickly, so I didn't spend the
time to figure out those details.
> At some point, the FAQ autoposter script should also be rewritten in JS.
> There are now NNTP modules for Node.js, so I don't expect too much
> trouble there.
Yes, I haven't used them yet, but I went looking to see that they
existed because I want to use them in an unrelated project. They
should make that part of the project straightforward.
>> 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.
>
> I like this idea a lot, even more than using a wiki. Pull requests and
> issues would be public, and the maintainer(s) could then decide which of
> them to merge into the official version. GitHub also provides discussion
> pages for all pull requests and issues.
All of which is good, but it does have a significant downside.
Discussions about a newsgroup's FAQ should, IMHO, take place in that
group. I would want to ensure that GitHub was only used for the
mechanics of the process and not for significant discussions of how
FAQ content should be altered.
> In addition, every contributor
> would have a local copy of the whole repository, which avoids the
> scenario where a single FAQ maintainer gets hit by a train or has to run
> from the authorities in, say, Belize ;)
Damn it all! How'd you find out? :-)
I did post another version of those same files, in UTF-8, with plain
indentation for code examples. It's at:
<http://scott.sauyet.com/Javascript/Demo/2012-12-09b/>
It has the same structure as the earlier one. Just append "index.md"
to one of the page URLs to see the Markdown source.
I have also created a GitHub account and a repository for these
efforts, but I will start a new thread to detail them.
-- Scott
[toc] | [prev] | [next] | [standalone]
| From | Patricia Shanahan <pats@acm.org> |
|---|---|
| Date | 2012-12-09 20:13 -0800 |
| Subject | Re: FAQ source format |
| Message-ID | <SdWdnaHcGqjr_FjNnZ2dnUVZ_i0AAAAA@earthlink.com> |
| In reply to | #17641 |
On 12/9/2012 6:59 PM, Scott Sauyet wrote: ... > I think I could probably convert the rest of the FAQ inside a week in > my spare time, if I actually have spare time around the home > remodeling that I'm doing. If others are willing to help, I'm sure we > could complete this in short order. ... I should have some spare time this week. What can I do to help? Patricia
[toc] | [prev] | [next] | [standalone]
| From | Scott Sauyet <scott.sauyet@gmail.com> |
|---|---|
| Date | 2012-12-09 20:50 -0800 |
| Subject | Re: FAQ source format |
| Message-ID | <ae980ddf-5dd7-4958-bcda-291726334a37@u19g2000yqj.googlegroups.com> |
| In reply to | #17646 |
Patricia Shanahan wrote:
> Scott Sauyet wrote:
>> I think I could probably convert the rest of the FAQ inside a week in
>> my spare time, if I actually have spare time around the home
>> remodeling that I'm doing. If others are willing to help, I'm sure we
>> could complete this in short order.
>
> I should have some spare time this week. What can I do to help?
There is a GitHub repository at
<https://github.com/comp-lang-javascript/faq-alpha>
I started a new thread, titled, "Potential FAQ mechanism on GitHub".
If you want to pick a chapter and start converting it to this format,
it would be much appreciated. Perhaps you can post a quick note to
that thread to say what you're working on so we don't duplicate
efforts.
I'm not thrilled with the current structure of a folder named with the
question number including a file named "index.md", but I think until
we figure out exactly how we want it to work that's easy enough, and
it will be straightforward to change later. Feel free to send a pull
request when you're ready.
Thanks!
-- Scott
[toc] | [prev] | [next] | [standalone]
| From | Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> |
|---|---|
| Date | 2012-12-10 20:41 +0000 |
| Subject | Re: FAQ source format (was: Maintainer of the FAQ) |
| Message-ID | <6WRIe2MwjkxQFwU$@invalid.uk.co.demon.merlyn.invalid> |
| In reply to | #17627 |
In comp.lang.javascript message <ka21pq$dnj$1@news.albasani.net>, Sun, 9 Dec 2012 13:56:25, Stefan Weiss <krewecherl@gmail.com> posted: > >I like the idea of using JS for most of the FAQ tools. The >js-markdown-extra project has an interesting warning about infinite >loops, but that can probably be worked around (or fixed in the code). > Can it be assumed that any FAQ maintainer will have ready access to Internet Explorer? If so, one can use HTA pages to make text processing tools, in a language that any FAQ maintainer must largely know. If an example of an HTA is required, search for SEAKFYLE. -- (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 | Scott Sauyet <scott.sauyet@gmail.com> |
|---|---|
| Date | 2012-12-10 18:09 -0800 |
| Subject | Re: FAQ source format (was: Maintainer of the FAQ) |
| Message-ID | <282eefc7-db5e-4f60-93d3-400a88b8d720@a6g2000vbh.googlegroups.com> |
| In reply to | #17665 |
Dr J R Stockton wrote: > Stefan Weiss posted: >> I like the idea of using JS for most of the FAQ tools. The >> js-markdown-extra project has an interesting warning about infinite >> loops, but that can probably be worked around (or fixed in the code). > > Can it be assumed that any FAQ maintainer will have ready access to > Internet Explorer? If so, one can use HTA pages to make text processing > tools, in a language that any FAQ maintainer must largely know. If an > example of an HTA is required, search for SEAKFYLE. No, I would definitely not make the assumption that a FAQ maintainer has ready access to Internet Explorer. Although I do at the moment, there have been plenty of times when I didn't have ready access at either home or work. I would suggest that these days Node.js, which has become a simple install for Windows, Mac, and many flavors of Linux, would be a better environment for doing Javascript-based development. And the number of readily-available libraries is impressive for such a young technology. -- Scott
[toc] | [prev] | [next] | [standalone]
| From | Patricia Shanahan <pats@acm.org> |
|---|---|
| Date | 2012-12-09 07:06 -0800 |
| Message-ID | <9sWdnQByYP1JNVnNnZ2dnUVZ_uadnZ2d@earthlink.com> |
| In reply to | #17623 |
On 12/8/2012 10:14 PM, 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. (For those who don't > know Github, a "pull request" is a very simply mechanism to ask one > person to look at a set of changes you've made to your copy and, if > you like them, include these changes in their own.) > > 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 Votes could take place in a Github code review discussion to avoid cluttering the newsgroup. By the way, +1 on the general approach. Patricia
[toc] | [prev] | [next] | [standalone]
Page 6 of 12 — ← Prev page 1 … 4 5 [6] 7 8 … 12 Next page →
Back to top | Article view | comp.lang.javascript
csiph-web