A company that needs a certain version can buy a source license for it
and snapshot NuVoc at its level.
I check many of the changes to NuVoc and I am taking steps to ensure I
check them all.
I think having release information in NuVoc would be a big mistake.
They are very rarely needed, and make pages hard to read. If J is going
to survive, most of its eventual users haven't seen it yet and we should
make it as interesting to them as possible. The goal of NuVoc was to be
1 easy to read by a bright newbie
2 useful as a quick reference
3 the official complete description of J
These are very hard to do simultaneously. We have Ian Clark to thank
for achieving 1 & 2 artfully, and me to blame for the ponderous
achievement of 3. Knowing when something was added isn't part of
NuVoc's mission: we have Release Notes for that.
Henry Rich
On 11/13/2023 4:17 AM, Jan-Pieter Jacobs wrote:
As to point 2), this is indeed something I have wondered about: Nuvoc is a
great reference, but are changes by random people consistently checked for
correctness (even if, one might assume, they are made in good faith)?
On a related note, knowing for which version of J some explanation in NuVoc
holds is near impossible: J changed a lot recently, and Nuvoc relates to
the last version (or even the last beta version?), but I wouldn't know how
to find back documentation for an older version. This might be of concern
for companies who want to stick with a certain version, yet have the
documentation for supporting maintainable software.
Just my two cents
Jan-Pieter
On Mon, 13 Nov 2023, 07:09 'robert therriault' via Programming, <
programm...@jsoftware.com> wrote:
== Report of Meeting 2023-11-02 ==
Present: Ed Gottsman, Raul Miller, and Bob Therriault
Full transcripts of this meeting are now available on the its wiki page.
https://code.jsoftware.com/wiki/Wiki/Report_of_Meeting_2023-11-02
1) Ed plans to record a screencast of the demo and send the files to Bob
so he can edit and post it up on Youtube. Ed feels the GitHub search tool
will be useful for intermediate users because it provides some options in
ways to use the code. Bob thinks that the important thing is that the code
that is found is actually being used and not just the way that J coding is
prescribed. This may be a very good way to onboard a J programmer to common
coding practices. The GitHub search might also be a way to see changes that
had taken place as new primitives are introduced. Ed plans to introduce the
GitHub tool at the next meeting of the British APL Association meeting.
2) Raul raised the point that there is a difference between the Dictionary
and NuVoc and that not all the information in the Dictionary has made its
way across to Nuvoc. Bob wondered whether NuVoc might be administrator only
edited to maintain the veracity of the source. Then there was a discussion
on labs and the ways that these might be incorporated into use for the wiki
and NuVoc. J Playground could accomplish this by loading labs into the edit
window and then could be accessed from the terminal line by line.
3) Bob asked about the way that breadcrumbs were used in the wiki. In the
new category tree, Bob has removed the breadcrumbs because they are
redundant. If a link on the category page takes you to a new page that is
not a category page then it might have a breadcrumb. Ed pointed out that
there is a back arrow on the browser that will always take you back. Ed
pointed out that two steps away would still be disconnected. Bob said that
the sidebar would still have the main categories and there would be access
to the map of the site on every page under the search bar.
4) Bob thinks that the J wiki search tool is working very well and feels
that it works well with the categorization. Ed felt that it is really
important to use the categorization because that is accessible for anyone
with a browser. The J wiki search is only available through JQt. Ed points
out that curation makes the ball of information in the wiki more
accessible, but what he has done is more about presentation and the J wiki
browser is the thing that accentuates the curation through good
presentation.
For access to previous meeting reports
https://code.jsoftware.com/wiki/Wiki_Development
If you would like to participate in the development of the J wiki please
contact us on the general forum and we will get you an invitation to the
next J wiki meeting held on Thursdays at 23:00 (UTC) Next meeting is
November 16, 2023.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
