#Development Environment

I want to be able to view generated items from visual studio code. In Studio there was an option in the open dialog:

Specifically, I added a namespace to my workspace for editing (Using InterSystems Server Manager) and I want to be able to access the generated items in this namespace.

I am currently trying to better my development process by using Visual Studio Code because I'm more familiar and comfortable with it than Studio.

I've followed the guide here, but I'm still having issues. I initially didn't have the Web Socket protocol allowed on my Web Gateway server, but I enabled that and restarted the server with no luck.

Hello folks,

Hi

When trying to sync a class to the server where the server class has been updated by another user, I, as expected, get the Conflict Resolution Wizard.

I can then use the wizard to copy code from the server side to my local copy using the arrows also as expected.

But when I have integrated the remote code into what I think is my local copy how do I save it so that it gets integrated into my local copy and synchronised to the server.

We have started playing around with Atelier, primarily to enable us to commit our existing Ensemble code within source control (GIT).

It seems Atelier works well with classes and routines however is unable to directly export lookup tables and HL7 schemas. Can someone confirm/validate this is the case? if so, when will this functionality be made available as it's absence is a deal breaker for us?

Suppose I want to create an Eclipse plugin designed to be added to Atelier, and my plugin needs to perform some processing on the server that the current Atelier project is configured to connect to.

Is there a way I can use the connection credentials that have already been entered by the user? I don't really want to make them enter these again into my own plugin.

Atelier shows the classes on server side as non editable grayed versions.

Is there a way to directly load class file from server and just start to edit that version?

Mikko

When I go to the 2016.2 FT download page I'm also offered a link to the Atelier Beta:

Hi developers!

Every day coding with IRIS and docker I call the following 3 commands in VSCode terminal. Always the same for any projects:

docker-compose build   ; to build the container

docker-compose up -d   ; to run the IRIS in container

docker-compose exec iris iris session iris ; to open the IRIS terminal

Is there any way to map the key sequence which will type me the rest?

e.g.

Just starting to use Atelier and having problems with making server connections. I have tried both the super server port and the web server port and both fail with either Unexpected end of file from server (Secure connection disabled) or PKIX path building failed (Secure connection enabled). On a different server I get Connection refused: check the web server configuration.

Anyone run into this before?

In response to a comment on his posting about source control hooks and Atelier Bill McCormick used the example of Studio's SOAP Wizard and talked about providing more information about how Atelier will support this kind of extension.

My Atelier (1.0.116) has a Tools menu with an Add-Ins option and a "Soap Wizard" (sic) submenu.

Is there any information available to us yet about how we can add our own add-ins of this kind?

In Studio whenever you write ##class( and then you start writing it will autocomplete the classname.

I can't find how to do that in atelier.

Well my last post got cut off for some reason. I am trying the new beta and wondering about the following functionality from Studio that I don't find in Atelier:

F12 = Open the routine and jump to the tag of the current call the cursor is on in a routine

F2 / <Ctrl> F2 = jumping to a bookmark / toggling a bookmark

<Ctrl> G = Jump to a tag in the code

When might these things be in Atelier? I use them a lot in Studio and the absence of these really slows me down.

Hi there.

I'm really interested in using Atelier for its source control ability, and I have found a fair bit of info when it comes to starting a new project and then pushing that project to a chosen source control system.

However, my environment has a lot of existing code which was developed within Studio and Ensemble, and placing entire namespaces within a single project file feels wrong.