Hmm... Note that http://code.jsoftware.com/wiki/System/Library#Scripts_included_with_J sort of wants a place to link to that talks about the system scripts.
I am not quite sure how to make that work with this table-of-everything concept. Any ideas? So far my best idea would be to break up that table into sections (maybe a first letter thing? api/arc, convert, data/debug/demo, ... or maybe just the top level classification...). It's a bit hard to digest as a whole no matter how we organize it. I also sort of want to make those system references link somewhere, but that's a mix of motivation and insight, to do it right. That said, I think we can expect to use code.jsoftware.com site search for some indexing needs, as long as its performance stays good. But it probably won't work for everything. We can also probably use category searches for some stuff. Thanks, -- Raul On Wed, Nov 1, 2017 at 5:59 AM, Henry Rich <henryhr...@gmail.com> wrote: > Yes, agreed. I have added a bit to the top of > http://code.jsoftware.com/wiki/Vocabulary/Libraries describing what to do; > feel free to add more. > > I have also created lines for the misc and util script you gave. There are > no descriptions; editors will have to fill those in. > > We can start thinking about the next phase, and what the final product will > look like. > > What about a set of pages containing lists of headings, one per script, and > a table for each script describing each entry point and how it is invoked; > and separately a keyword index pointing into the pages? > > Or maybe use Google to take the place of the keyword index. > > Henry Rich > > > On 11/1/2017 1:22 AM, Raul Miller wrote: >> >> Ok, note however that that Addons page that I modified is a landing >> page for the Addons top nav. If you go back to the page I modified you >> can see that Addons is bolded (and black) in that blue JAL bar. So now >> I need to think about that a little. >> >> Meanwhile, here's the system libs: >> >> require'general/dirutils' >> system=: (#~ +./@('.ijs' E. ])@>) {."1 dirtree '~system' >> dropto=:4 :0 >> ((#x)+1 i.~x E.y) }. y >> ) >> taketo=:4 :0 >> (1 i.~x E.y) {. y >> ) >> libnm=: ('.ijs' taketo '/system/' dropto ])L:0 >> >> >libnm system >> defs/hostdefs_aix >> defs/hostdefs_android >> defs/hostdefs_android_64 >> defs/hostdefs_darwin >> defs/hostdefs_darwin_64 >> defs/hostdefs_linux >> defs/hostdefs_linux_64 >> defs/hostdefs_sunos >> defs/hostdefs_win >> defs/hostdefs_win_64 >> defs/netdefs_aix >> defs/netdefs_android >> defs/netdefs_android_64 >> defs/netdefs_darwin >> defs/netdefs_darwin_64 >> defs/netdefs_linux >> defs/netdefs_linux_64 >> defs/netdefs_sunos >> defs/netdefs_win >> defs/netdefs_win_64 >> main/regex >> main/socket >> main/stdlib >> main/task >> util/boot >> util/configure >> util/pacman >> util/pm >> util/pp >> util/project >> util/scripts >> util/tar >> >> We can probably gloss over the architecture specific defs, which makes >> that a rather small list. I think I've seen various bits of >> documentation for a lot of these already, but it's not all wikidoc... >> but, basically, I guess we should start linking stuff in and building >> out the contents? >> >> Would it help to put together some boilerplates indicating page status >> along with a few general directions about plausibly nice edits for >> that stage f the page? >> >> Thanks, >> > > > --- > This email has been checked for viruses by AVG. > http://www.avg.com > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
