 I'm happy to let you know that Role Bob and I think that the J Viewer is ready for beta. If you'd like to help us isolate the remaining bugs, please drop me an email and I'll send you installation instructions. There are a few new features I want to show, but first a quick review for those of you just joining. The J Viewer gives structured access to the J Wiki, which Bob Terrio has been curating as well as to the forums. It also supports full text search of the Wiki, the forums, and now the J Software repositories in GitHub. The table of contents on the left includes NuVoc, which behaves in a way that you should be familiar with by now, as well as the Ancillary pages. Clicking on a page title loads the page, including Forins, and this is probably a good place to show expanding the browser, which lets you get the entire foreign table visible on the screen at one time. Forums lets you browse the 6J forums, general programming and so on, by date, by thread, and by post. Tags are categorized pages that don't participate in the tag hierarchy that Bob has put together. Basically they're pages that have probably been indexed by somebody other than Bob. Jsaurus is an instant search feature. It has a small number of sentences, but it actually inspired the development of live search via a suggestion from Raul, and we'll get to live search in a minute. J Playground is in here, not particularly because it's helpful in this context, but just because it's cool and I'm trying to promote it because it's a great way of promoting J. We'll come to live search in a moment. Bookmarks behave more or less the way you'd expect. It's a way of saving pages for later reference. It's a bookmark button that lets you add and remove pages from your list of bookmarks. Home is the top category in the hierarchy that Bob has developed. So it can be, I think the hierarchy is nowhere deeper than five. And again, clicking on a page title will load the corresponding page on the right. I always like looking at gallery. A lot of interesting things, a lot of rabbit holes to find. Moving back to live search, again, this was inspired by a suggestion from Raul. The idea here is we've got a phrase input area and a words input area. And the phrase input area is particularly good for finding code fragments. So like slash code, tilde, for example. And what happens is that you get to see initially both wiki pages and forum posts. Forum posts come in and Rust wiki pages come in and a sort of teal. And clicking on a page, excuse me, a title will load it up over on the right. This is a good place to shrink the browser so you can see a little more of what's going on in the left. So the left column in live search is snippets or keyword and context. The right column is the title. Obviously all J program, J forum, J general and so on are from the forums. Essays sorting is a wiki page. If you're interested in GitHub hits, you can click GitHub, which is not on by default. They're violet. So slash code tilde has a number of hits in J playground on GitHub. If you search for slash code slash code, let's turn off GitHub. I didn't mention that there is a time slider so you can pick the years that you want to search. You can just say 2023 or you can go back in time. The further back you go, generally the more hits that you get slash code slash code behavior was originally observed. As far as I know by Roger, we if you want to define his commentary on it, the wrong way to do that would be to add the word Roger, the token Roger here. There is no phrase slash code slash code Roger that occurs in any document. But if you pop over to the words area and type in Roger. And then you say, well, let's take it back away. So let's go back in time a little more. There are quite a few hits. One the J4C hit where Henry Rich mentioned slash code slash code and gives credit to Roger. And then quite a few forum hits where Roger's either the author or his work on this is mentioned. One thing is that anytime there's a forum post, this show post and thread button shows up just above it. The effect of this is to teleport you over to the forum area and show you the post and the threads. You can go back to the original post find out what the what the conversation was about and follow it through. This particular feature is a huge time sink I found, but an entertaining one. The slider in the upper left addresses the fact that unfortunately font sizes tend to differ across platforms. So the slider lets you pick a font size that works for your platform. Nothing much to say about that. The debug button debug log is a mechanism for turning on very granular event logging. If you turn it on events will be logged to a table in a database, which I'll show you in a moment. This button here actually lets you snapshot the current log into the browser window over on the right. And that's of interest mostly to the developer, not really to end users. But what is interesting is that if you turn on debug log, all of the log records wind up in jwikivis.db in the j temp directory. So if you do have a problem, if there's an issue that comes up and you can reproduce it, turn on logging, reproduce the problem, turn off logging, and then just send this database, which is 10 or 11 megabytes to me along with the description of the situation. And it may be enough to help me figure out what's going on. One very important point, the application at your direction will download about 100 megabytes worth of content that then turns into about a gigabyte worth of content on disk. So that's a decompressed and indexed. That's a full text index as well as the structure of the wiki and the j forums. So you have to be comfortable with having that much content sitting on your hard drive. The content which is downloaded from a server is updated daily to reflect changes to the wiki as well as new forum posts, but you can download it as infrequently as you wish. The longer you wait to download a new version, the staler it will get so you'll be missing forum posts and changes to the wiki and so on. See these two buttons just above the left panel, local database is up to date and add on is up to date. When there is a new version of the j viewer or there is a new version of the database, the captions on these buttons will change to let you know. You can ignore them. There's no problem with that, but if you're interested in updating, you can just click the corresponding button and the update will happen. It is important to note that that 100 megabyte download can take a minute or two on a slower connection. And that's the story. Once again, we are entering beta. Anybody who would like to help us shake out the last of the bugs would very much appreciate your help. Just send me an email and I will send back installation instructions. Thanks very much.