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.
Authors of a specific article may not realize that their article is
pertinent to other areas, which were not related to the articles' main
focus. However, someone reading the article could recognize this
relationship, and place a few new keywords in the article, which would
tie the article to the additional topic areas.
This process should be simple to do, and the additional keywords should
be displayed at the end of the article, to help future taggers
understand what was done before. There needs to be a way to add keywords
to any block of information, whether it be wiki pages, forum posts,
reference book chapters, etc. Finally, all of this information should be
available under one search engine, so there is no confusion on what the
process is to find the information.
So the issue is how to simply tag information, and keep track of the
tags. One doesn't need a specific "repository" for the various code
modules, wiki pages, forum posts, or books. If the information is on the
web, we just need a way to connect keywords to the url, and the see
those key words when looking at the document.
Skip
Randy MacDonald wrote:
Hello Skip;
The things that come to mind as sources of our own solutions are:
. krugle.com, which seemed to be the latest thing a year or so ago;
. CPAN, which is the ultimate solution for reusing community code, if
it wasn't for Perl users ;-)
. Google Code , or something like that.
I'm wondering if and how these things could be adapted for J solutions.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
