New post
AllAccepted answers
John Murray · Mar 17

A useful article, but I have a couple of comments:

1. I think "fallback" is a better choice for the "http.proxySupport" setting than "off", and it should still have the desired effect.

2. I'd like to understand exactly why you find it necessary to make the web gateway connect to IRIS as SuperUser rather than as CSPSystem (the default). On my test environments this isn't necessary, but I'm not using SSL/TLS as the Connection Security Level.

John Murray · Feb 11

Your screenshot shows the ObjectScript Explorer view, which was originally created for the client-side development paradigm in which you export to a folder on your workstation the routines/classes/etc you want to change, then manage them locally in Git. You then import your changes to the server that your `objectscript.conn` setting points to (the same place you may have exported them from).

In this case you can expand the Routines node of the tree shown in your screenshot, then with focus on that tree press Ctrl+Alt+F to invoke VS Code's tree search/filter widget. Here's a screenshot of me using this to narrow down the large number of INT routines in a VistA namespace:

The other development paradigm (server-side) may suit you better if you are migrating from InterSystems Studio.

In that paradigm, use the Servers view (at the bottom of your screenshot) to expand the Namespaces node of your server. Then use the pencil or the eye button to add to your VS Code workspace a folders that gives you direct access to the namespace (pencil if editing, eye if only viewing as read-only).

Also follow the instructions in the README of the InterSystems ObjectScript extension to enable proposed APIs.

Then type Ctrl+P and start entering the name of the routine you want:

You can also use the Ctrl+Alt+F tree widget on the VS Code Explorer view of your workspace.

John Murray · Dec 19, 2024

Please accept the in-article links to examples of Doxygenerate's output as fulfilling the "Online Demo" item. Running the app itself isn't at all exciting - it's the output people surely want to explore online.

Links (all to documents hosted on georgejames.com) are in these posts:

John Murray · Dec 18, 2024

Congratulations to the IPM team for achieving this hugely significant milestone.

To show my appreciation I installed 0.9.0 into a fresh namespace called IPM and told Doxygenerate to build documentation (HTML and PDF). Then I published the output on the George James Software website.

To see the results as a set of static web pages, go to https://georgejames.com/files/doxygenerate/IPM/index.html

To view the documentation as a PDF it's https://georgejames.com/files/doxygenerate/IPM/refman.pdf (586 pages).

And for a variant of the PDF with simplified inheritance diagrams it's https://georgejames.com/files/doxygenerate/IPM/refman-brief.pdf (364 pages).

The difference between the two PDFs can be seen by comparing page 63 (numbered 37 because of the extensive Table of Contents).

Also of interest is this inheritance diagram from page 59 (aka 33):

If you like the results please consider voting for Doxygenerate before the current contest ends on Sunday night.