All
Accepted answers
John Murray · Mar 11, 2016 go to post

That's interesting to know. It means that my experiment can become:

USER>s oResult=##class(%Library.File).FileSetFunc("c:\s\","*.txt")
 
USER>while oResult.%Next() {w !,oResult.%Get("Name")}

...

And now static code analysis that detects classmethod references can spot the use of the secret FileSetFunc method within the class that implements the query I'm using.

John Murray · Mar 11, 2016 go to post

What version of Ensemble / HealthShare is running its webserver at chft-eprtiedev.xthis.nhs.uk:57772 ?

John Murray · Mar 11, 2016 go to post

Thanks for putting so much time and effort into this Mike.

Would you be willing to offer the examples etc as PDF downloads as an alternative to .docx files?

Maybe also worth deleting the "Sample Page" item from your site.

John Murray · Mar 11, 2016 go to post

One caveat about transferring globals between namespaces / instances using XML format is that by default when you load the XML into the target namespace the global(s) in your XML file will be pre-killed. In other words, it's a "replace" operation rather than a "merge" one. This may be exactly what you want in many situations, but if you've been used to using other utilities to export and import globals then it's different.

To override this behaviour, add the "/mergeglobal=1" qualifier during your import, for example as the second argument (qspec) to $system.OBJ.Load(), which is of course the Load classmethod of %SYSTEM.OBJ.

See more qualifier documentation here.

John Murray · Mar 10, 2016 go to post

Hermain, I think yours predates the point where ISC implemented the ability to update Atelier from within Atelier. I suggest you download the latest kit and install that. Thereafter you ought to be able to update from within. But bear in mind I'm not an ISC person, so my advice might be incorrect.

John Murray · Mar 10, 2016 go to post

Thanks for sharing this detailed information Jamie. I noticed that the headers have links to a wiki on GitHub, but they're unreachable to me and presumably to other non-ISC folk.

John Murray · Mar 10, 2016 go to post

Was that repository URL pre-populated in your Atelier?

Maybe the response Dmitry gave to this post I created in the Atelier community will help you.

John Murray · Mar 9, 2016 go to post

Tiago,

Do you mean that when you are writing output from the server (e.g. from a source control class) you want to be able to control the colour of that text? I have never discovered a way of doing that, but let's see if anyone at ISC knows of an undocumented feature there.

John Murray · Mar 9, 2016 go to post

I can confirm that the 64bit Windows Ensemble download link is working for me.

John Murray · Mar 9, 2016 go to post

That worked. I guess the Developer Community application ought to do a better job with content expiration or something in order to make sure we see the correct images.

John Murray · Mar 9, 2016 go to post

Nicki, did you paste the wrong thing as your second image? Under the title "studio:" I'm seeing an Atelier "Create a New Project" dialog screenshot.

John Murray · Mar 9, 2016 go to post

Existing users of our Deltanji source code management tool, which runs natively inside Caché / Ensemble / HealthShare, may want to start using Atelier without having first to re-engineer their source control. I foresee a need for an Atelier user to be able to interact with a Deltanji dialog and then trigger a server-side action.

John Murray · Mar 8, 2016 go to post

Certainly looks strange that you can browse namespaces on the Server Explorer tab but the new project wizard says it can't find any. I don't see your symptoms on mine, but I'm connecting to a Windows instance of 2016.2. My Atelier "About" box shows version 1.0.107. Is yours that version too?

John Murray · Mar 8, 2016 go to post

In your version of Studio, if you open the File\Open dialog and right-click on a package name in the dialog's list, is the a "Delete" option?

John Murray · Mar 8, 2016 go to post

What is the $ZV of the server?

USER>w $zv

What security roles does the user nicki hold? Either check these using Portal, or connect to a terminal session as nicki and write $roles

USER>w $username
nicki
USER>w $roles
...

If you connect to this server using Studio and authenticate as nicki, what namespaces does Studio offer you?

John Murray · Mar 7, 2016 go to post

Thanks for spending the time to take us on such an informative backstage tour Ben. A lot of this aligns with what I've seen on the many sites where I've implemented our source code management product for customers.

John Murray · Mar 7, 2016 go to post

Interesting question. I expect you're already aware of how we can get the value of an environmental variable thanks to the GetEnviron method of %SYSTEM.Util

USER>w $system.Util.GetEnviron("TEMP")
C:\WINDOWS\TEMP
USER>

Maybe someone else knows how you can amend one. But if it's not possible, can you improve readability in your code by concatenating the components of your $ZF argument in several stages into a local variable, then passing that variable as the argument to $ZF ?

John Murray · Mar 6, 2016 go to post

Certainly Scott. You can now get the full-size PNG file by clicking on the image.

John Murray · Mar 5, 2016 go to post

This is a good question. One of the potential benefits of moving to Eclipse is the increased potential for an ecosystem compared to the Studio days. I think that even if Atelier source isn't opened up to us we will still be able to add stuff around it. But it would certainly be cool if InterSystems released it as open source.

John Murray · Mar 4, 2016 go to post

Thanks for fixing the image size so it doesn't bleed across other areas of the forum UI.

If anyone would like to have a full-size image, or the EA model file, or even the XMI that Umlanji emits, reply to this comment and I'll find a way to make them available.

John Murray · Mar 4, 2016 go to post

No, I don't think you have to switch over to the new paradigm until you're completely ready to (e.g. no-one using Studio anymore). Instead, follow Dmitry's steps, creating an Atelier project containing any of the classes that you want to edit. Don't hook the Atelier project up to an Eclipse source control provider; your namespace and the existing server-side source control class should continue to function the way it always has done.

This is how we anticipate existing users of our Deltanji (formerly VC/m) source control product will deal with the introduction of Atelier.  And perhaps not just existing users, seeing as Deltanji is available as a free Solo edition.

John Murray · Mar 4, 2016 go to post

Dmitry's answer should be what you need. I'd add that the paradigm shift between Studio and Atelier can take a little getting used to. With Studio we're accustomed to thinking of the code in a namespace as the "source of truth". We pull the code from there, change it, and push it back in order to store our changes (and to run the amended code). With Atelier we're more likely to be pulling code into our local filesystem using a source control provider, then editing it, saving it to our local filesystem, and eventually pushing it from there back to the source control repository. Using this mode of working, we only push it into a Caché namespace in order to run/debug it.

John Murray · Mar 4, 2016 go to post

I recall from the private beta period that they were talking about offering this as an option. Haven't found it in the field test build I'm currently using (1.0.0.201602110048)

John Murray · Mar 4, 2016 go to post

Stefan,

I had a PM from Bill after I posted yesterday, saying there was a problem with the blog site and that it was being attended to. Looks like they fixed it.

John