Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #17686

Re: Potential FAQ mechanism on GitHub

Show all headers | View raw

In comp.lang.javascript message <5e684468-d1ae-4a31-a5b7-cba01316b6cc@u1
9g2000yqj.googlegroups.com>, Sun, 9 Dec 2012 20:12:41, Scott Sauyet
<scott.sauyet@gmail.com> posted:

>
>Or do you think this is a waste of time?  Should I not be pursuing
>this idea at all?  If so, please let me know why.


It will not work as a provider of a FAQ suitable got a general purpose
Usenet JavaScript group.  A few experts with nothing better to do will
compete in adding complications.

The thing that is needed is clarity of thought in the planning of the
content of the FAQ.

For example, analyse "9.4 How do I modify the content of the current
page?".  The question is clearly not what it should have been (IIRC, I
asked it) - it should (for me) refer to the visual textual content.

The answer should be along the lines of
 (1) Decide on or create the element to be modified
 (2) Obtain a reference to the desired element of the page
 (3) Assign to the property of the element that controls its appearance
     in the desired manner.
Lines should link to appropriate new sections.

For that question as written, the modification might include hiding and
un-hiding, moving in an XY sense, repositioning in the DOM tree,
altering the CSS in a button, etc.  The answer should include everything
compatible with the chosen wording of the question.

A FAQ should rarely include the questions literally as actually asked;
but it should include questions that the questioner will recognise as
answering what he was thinking of asking.

-- 
 (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>.

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Potential FAQ mechanism on GitHub Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-09 20:12 -0800
  Re: Potential FAQ mechanism on GitHub John G Harris <john@nospam.demon.co.uk> - 2012-12-10 11:26 +0000
    Re: Potential FAQ mechanism on GitHub Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-10 04:29 -0800
      Re: Potential FAQ mechanism on GitHub John G Harris <john@nospam.demon.co.uk> - 2012-12-10 18:35 +0000
        Re: Potential FAQ mechanism on GitHub Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-10 11:03 -0800
          Re: Potential FAQ mechanism on GitHub John G Harris <john@nospam.demon.co.uk> - 2012-12-11 11:02 +0000
            Re: Potential FAQ mechanism on GitHub Jeff North <jnorthau@yahoo.com.au> - 2012-12-12 01:27 +1100
              Re: Potential FAQ mechanism on GitHub John G Harris <john@nospam.demon.co.uk> - 2012-12-11 14:52 +0000
              Re: Potential FAQ mechanism on GitHub Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-11 22:31 +0100
                Re: Potential FAQ mechanism on GitHub John G Harris <john@nospam.demon.co.uk> - 2012-12-12 15:41 +0000
                Re: Potential FAQ mechanism on GitHub "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-12-12 18:47 +0200
                Re: Potential FAQ mechanism on GitHub Tim Streater <timstreater@greenbee.net> - 2012-12-12 23:20 +0000
            Re: Potential FAQ mechanism on GitHub Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-11 06:30 -0800
      Re: Potential FAQ mechanism on GitHub Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-12 21:13 +0000
  Re: Potential FAQ mechanism on GitHub Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-12 21:27 +0000
    Re: Potential FAQ mechanism on GitHub Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-13 08:29 -0800

csiph-web