go to post John Murray · Oct 12 gj :: configExplorer uses an IRIS Docker container for its test / demo workspace. Please see https://github.com/gjsjohnmurray/gjConfigExplorer/tree/main/test
go to post John Murray · Oct 9 The same for the idea I linked gj :: configExplorer to. Still "Needs Review" and no bonus awarded yet. 🤞
go to post John Murray · Oct 9 gj :: configExplorer now has 2 DC articles. I also claim the Find a Bug bonus for https://github.com/intersystems-community/nodejs-bugreports/issues/1
go to post John Murray · Oct 9 A couple of updates on this technique: You'll need the Dev Containers extension from Microsoft installed. We can simplify the procedure by starting with the 'Dev Containers: Clone Repository in Container Volume...' command from Command Palette. This avoids needing a local clone of the repository in your Windows filesystem. I have updated the original post.
go to post John Murray · Oct 9 There's also Deltanji from George James Software, the pioneers of the production decomposition technique.
go to post John Murray · Oct 7 This comment no longer applies as of version 0.0.4 of the extension, published 2025-11-23. It's worth noting that the extension can't currently run on Windows without crashing VS Code's extension host (EH) process and thus impacting all other extensions. More information here, which I hope qualifies my entry for the 'Find a bug in InterSystems IRIS External Languages Offerings' bonus. For Windows users there's a workaround, as long as you have SSH access to a Linux host on which you can run Docker containers. Here's what to do: Launch VS Code on your Windows desktop. If you don't already have it, install the 'Remote - SSH' extension from Microsoft. From Command Palette run `Remote-SSH: Connect Current Window to Host...`. Enter your SSH connection string in the form `user@host`. When prompted for your password (top centre), enter it. Wait for the progress notifications (lower right) to complete and for the Remote panel on the status bar (far left) to confirm that you are connected. In Extensions view, find gj :: configExplorer and install it. This action will install it on the Linux server for use of the account you connected there with. It also installs Server Manager if necessary. When operating this way gj :: configExplorer executes in an EH on your Linux server. Connections to the target servers' superserver ports will originate from there, not from your Windows device. Resolving the server names / addresses will behave accordingly.
go to post John Murray · Sep 23 Is your /api/atelier web application enabled? Is your web server configured correctly to forward that endpoint to IRIS? Did you try the steps I suggested at https://community.intersystems.com/post/cant-connect-vscode-iris4health-...?
go to post John Murray · Sep 10 Great article, but your examples in Item 3 are missing the Do command with which to invoke the method.
go to post John Murray · Aug 26 Good memories of MSM-Workstation! Glad to see that you are still working with the InterSystems technologies.
go to post John Murray · Aug 19 I think the looping affects the core tests, not the expr ones. https://github.com/intersystems/tree-sitter-objectscript/issues/8
go to post John Murray · Aug 19 +1 for more info about building and using. So far I have succeeded in getting the tree-sitter playground working for the expr grammar: My attempts to do the same with the core and udl grammars only give a blank screen there, and DevTools shows an error.
go to post John Murray · Aug 18 Thanks for the appreciation. This is a brilliant community, and I am very pleased to be a member.
go to post John Murray · Aug 8 I develop and publish VS Code extensions targeting users of the InterSystems platforms. Occasionally an extension needs some support classes installed on the servers it works with. I propose establishing a naming convention for these classes, as follows: First dot-piece of the package name should be vscode Second dot-piece should be derived from the "publisher" property in the extension's package.json manifest, as follows: If publisher is "intersystems-community" then use dc Otherwise use the publisher string, transformed if necessary to conform to package-naming constraints (e.g. remove punctuation). Uppercase characters in the publisher string may be retained or folded to lowercase at the choice of the publisher, but the transformation should be applied consistently for all classes published by that publisher. For example, if the extension uses publisher ID Acme-Nadir their class names might begin vscode.AcmeNadir. or vscode.acmeNadir. or vscode.acmenadir. Third dot-piece should be derived from the "name" property of the extension, using the same transform guidance as above. Additional dot-pieces of the package name can be added at the choice of the extension author. Classnames should follow the convention proposed by @Robert Barbiaux in this article, i.e. be upper camel case (aka Pascal case).
go to post John Murray · Aug 8 A case(!) for lowercase package names was made by @Evgeny Shvarov in his 2021 post at https://community.intersystems.com/post/naming-convention-objectscript-p...
go to post John Murray · Aug 4 Thanks all. I feel honoured to have been awarded a double first! I couldn't have done it without @Timothy Leavitt 's excellent Test Coverage Tool package. Many thanks Tim.
go to post John Murray · Aug 2 Hmm, seems unfair they didn't take that view last year for my IPM in VS Code entry: https://community.intersystems.com/post/technological-bonuses-results-de...
go to post John Murray · Aug 2 I think IPM Explorer for VSCode has been incorrectly awarded the IPM bonus. From the bonuses article: This entry isn't published as an IPM package but as a VS Code extension on Microsoft's Marketplace.
