Readers of this thread may be interested in this discussion I just started about the export/import topic:
https://community.intersystems.com/post/studio-vs-code-migration-addres…
- Log in to post comments
Readers of this thread may be interested in this discussion I just started about the export/import topic:
https://community.intersystems.com/post/studio-vs-code-migration-addres…
Thanks for the suggestions. The solution I came up with can be seen at https://github.com/intersystems-community/vscode-per-namespace-settings
It installs a class, runs a method in it to create the web app so it uses the correct namespace, then deletes the class. Actually, it deletes a whole package which I named %Z.IPM.Bootstraps with the idea that this could be by convention a package reserved for exactly this purpose.
I had to devise a little hack to prevent the deletion from happening during packaging, otherwise the web-app-creating class wouldn't actually be in the package, meaning end-user installation would fail.
Maybe there's already a better way of achieving the effect I wanted.
Impressive, and I have some UI ideas. But your example doesn't use IRIS in any way, right?
Laurel is out this week after Global Summit. Once she's back at her desk next week I expect she'll post more. You're also welcome to email info@georgejames.com and she'll reply directly to you.
I think they might be MSM remnants. On that implementation of M(UMPS) $ZU() was the abbreviation for $ZUCI()
The term UCI was short for User Class Identifier.
Thanks for confirming the fix. I'm publishing 0.2.1 now.
Please post enhancement ideas on the repo, for better tracking.
Please change this to a relative path (no leading slash).
Also, there was a bug in how it handled a "docker-compose" type of configuration.
Please try this dev build by downloading the zip, extracting the VSIX and dropping it into VS Code's Extensions view. If it works for you I will publish a new version to Marketplace.
Move it outside the `objectscript.conn` object please.
That's one of the things the new extension is designed to achieve.
Great article, thanks! But is the first paragraph of the section titled "Insert con archivo" a test that we read carefully? Or intended to prove it wasn't written by a chatbot (which of course it wasn't)?!
@Evgeny Shvarov
Did my suggestion help you get started with this extension?
I'll be showing DX Jetpack on one of the stations at Drinks & Demos on Monday evening at Global Summit 2023.
I guess you need this one:
.png)
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#w…
Yes, I recommend you migrate away from using XML exports of class definitions.
Also welcome are reviews, which can be posted on Marketplace and on Open Exchange.
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.
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.
%UnitTest mavens may be interested in this announcement:
https://community.intersystems.com/post/intersystems-testing-manager-ne…
Unit testing from within VS Code is now possible. Please see https://community.intersystems.com/post/intersystems-testing-manager-ne…
@Michael Davidovich you might find this extension useful for exploring inherited methods etc:
https://marketplace.visualstudio.com/items?itemName=georgejames.objects…
@Iryna Mykhailova please also look at VS Code's recently-introduced Profiles feature. I imagine this could be useful in learning contexts.
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.
@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
Yes, you can do this in VS Code. Even better, when using the server-side editing paradigm a single VS Code instance can connect simultaneously to multiple namespaces on one or more servers, and you can drag/drop and copy/paste between them.
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"?
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.
Did you try using the "Add/Remove Programs" option in Windows (might be named differently depending on your exact version)?