Okay, you are saying that the author is the only supplier of keywords on
the sites I mentioned. I haven't explored them in depth, so I'll have
to take your word for it. User-supplied keywords, seems like such a good
idea, I marvel that it has not been done.
Such a thing could prove useful for J documentation since, as capable as
Roger Chris and Eric are, I'm sure the audience is collectively smarter.
Skip Cave wrote:
Randy,
The code archiving sites you point out are handy, but they don't
address the problem I am trying to solve. The underlying problem is
that the person who wrote the code (or article, or wiki page, or book)
didn't use words that the person searching for the information is
using for the search. So, even though the information is available,
the searcher will never find it, because he isn't using (and probably
didn't know) the correct keywords to use in his search. This isn't
just specific for code modules. Articles on coding style, puzzles,
tutorials, etc. should all have the capability to contain additional
user-supplied keywords, which would broaden the chance that the
information will be found. I am convinced that this issue is the
biggest barrier to learning about J, as well as almost any subject.
--
------------------------------------------------------------------------
|\/| Randy A MacDonald | APL: If you can say it, it's done.. (ram)
|/\| ramacd <at> nbnet.nb.ca |
|\ | | The only real problem with APL is that
BSc(Math) UNBF'83 | it is "still ahead of its time."
Sapere Aude | - Morten Kromberg
Natural Born APL'er |
-----------------------------------------------------(INTP)----{ gnat }-
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
