New post
AllAccepted answers
John Murray · May 28, 2023

Since you are working client-side I think you need to set a intersystems.testingManager.client.relativeTestRoot setting to contain the workspace-relative path to the tests folder that's showing at the beginning of the breadcrumb in your screenshot.

Please see point 2 of https://github.com/intersystems-community/intersystems-testingmanager#wo...

John Murray · May 23, 2023

Thanks for the positive response. IMO the main thing needed before the Preview tag gets dropped is feedback from %UnitTest users.

One motivation for publishing the Preview is the upcoming Global Summit, which I hope will be a good opportunity for in-person discussion about this extension and others. Find me at the George James Software booth in the Partner Pavilion. 

John Murray · May 23, 2023

Outline information is always available in the CHANGELOG, and instead of waiting for a post here I suggest you configure VS Code to check for extension updates without installing them automatically. That way you'll know when you update this extension, and it's easy to review the CHANGELOG in Extensions view afterwards.

I think there's also a Discord channel that notifies about releases. 

John Murray · May 17, 2023

It looks like you are trying to use "Import and Compile" with an XML export. This won't work, as it only supports UDL-format exports. VS Code users can create those exports from the ObjectScript view.

Based on the hl7, inc and mac folders visible in your screenshot it looks like you might want to set the following in your VS Code settings before using the export if you want to replicate that style.

"objectscript.export.addCategory": true,

I also suggest you start off by opening an empty folder in VS Code, then export into that. This will avoid polluting your existing working folder structure while you get the hang of using VS Code with InterSystems servers.

John Murray · May 15, 2023

@Larry Overkamp my reply was focused on what @jaroslav rapp had posted.

You also wrote:

(We don't use a source control system.)

Have you considered changing this situation? If so please take a look at Deltanji from George James Software (my employer). Some videos are available at https://www.youtube.com/playlist?list=PLGnA3ZIngG4oOUCEmplIYgSknQpNOtF08

John Murray · May 15, 2023

With our 2023.2 release we are deprecating InterSystems Studio (deprecated
designates a feature or technology that InterSystems no longer actively develops, and for which better options exist). We will continue to maintain, release, and support InterSystems Studio for quite some time, and we appreciate that it is still an important tool for some customers. However, customers should be advised that we are not investing in it. Our focus is on VSCode.

In what sense is this an "attack"?

John Murray · Apr 24, 2023

For animated GIFs it would be neat if the DC software could use a technique such as this to automatically add a play/pause button:

https://codepen.io/chriscoyier/pen/pogQJER

That Codepen sample plays such GIFs by default unless user's browser preference is set for reduced motion (see the JS in the sample), but by not setting the 'open' attribute on the details tag (line 5 of the HTML in the sample) it could always start paused.

The technique relies on having a static image containing one frame of the animated GIF, so that would need to be done server-side when an animated GIF is uploaded.