An integrated development environment (IDE) is a software application that provides comprehensive facilities to computer programmers for software development.
The official IDE for InterSystems Data Platform products is Atelier.
To simplify the upgrade processes and to keep up with industry standards, we decided to make Atelier only available as an Eclipse plugin. Those of you who are currently using a standalone Atelier client will not be able to upgrade to a later version.
Please go to the Atelier Download page or see the sections below for the detailed instructions about installing Eclipse and the Atelier plugin. Feel free to reach out to support or leave a comment down below if you have any questions.
Atelier 1.1.386 is now available! If you haven't subscribed to the NEW Atelier Beta channel, please follow the instructions on the Atelier Download page.
In trying to understand Atelier I am directed to go through its hierarchy type of documentation.
Is the Atelier documentation going to continue as a hierarchy or at some point is it going to be integrated into the InterSystems type of documentation?
When looking for an answer it would be nice to use only one method.
offers the latest features and bug fixes. It now updates your installation of Atelier to build 1.1.310 for Mac, Windows, Red Hat, SUSE and Ubuntu. Here’s an account of what’s recently been improved:
Since we announced last week that Atelier would only be available as an Eclipse plugin, some of you have been asking about how to convert from your standalone client. Here's what you might want to do.
Greetings fellow Atelier users! To help new users get started, we are planning to make a list of video tutorials (e.g., how to create an Atelier project). The first one is "Introduction to Atelier", which is a brief tour of the Atelier user interface. We'd appreciate it if you could watch this video and let us know your comments. We'll be relying on your feedback to create more video tutorials to make it easier for new users to learn Atelier.
Please feel free to post your comments below. We look forward to hearing from you!
https://www.youtube.com/embed/pFpbCkLemXA [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
It's been 6 months since InterSystems released Atelier 1.0 and we continue to roll out enhancements and new features through the beta channel (please see the Atelier Download page for details). In the meantime, we have received a lot of messages from the Developer Community with ideas for further improvements. Based on your feedback, we created a roadmap for Atelier 1.1 so you can conveniently track when specific features are going to be integrated.
We just faced an issue of the Atelier main menubar being disabled (greyed out) after upgrading the macOS development machine to High Sierra. I would like to share my findings about the issue and how to fix it.
One of the most important features during application development is the ability to debug your code easily. Because of the asynchrnous nature, a standard Node.js application server works single-threaded by default. When you are developing applications using an IDE like Visual Studio Code, you can very easily debug your Node.js process:
When I create a project and pull in files from the server, certain files (BPLs and DTLs) aren't synchronized, and when I try to sync them (without making any changes) I get a Resolve Version Conflict screen, with differences between the local copy and server copy. Sometimes the Parameters are in different places, or the Storage will be on top of one and on the bottom of the other, and sometimes the server copy will flat out have lines that aren't in the local copy at all.
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.
Is it possible to exclude certain folders from validating (i.e. generating errors/warnings in the Problems tab)? For example, I have *.js files from ckeditor and jquery libraries that are generating multiple errors that I'd like to suppress.
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.
Is anyone using Atelier with 3 environments (instances with multiple namespaces) (DEV, TEST, PROD) using GitHub as the source control.
I would be interested in how its all setup. So for example;
Would you have three branches for the code or 3 repo's.
Would you have three projects in Atelier to communicate with the environments and GitHub?
I have 3 existing environments that I wish to put under source control and also provide the ability to promote code between the environments in a controlled manner.
Is your development team following best practice now that source control and continuous integration testing are better supported by InterSystems new IDE Atelier?
Many teams are turning to Git as their version control system of choice because it never locks files, among other reasons. These teams may also be following a multi-server development workflow where changes are migrated from a DEV server to a TEST server to a PROD server. How should these teams organize their repository given this configuration?
I wanted to share a little tidbit which is in the Studio documentation (http://docs.intersystems.com/cache20152/csp/docbook/DocBook.UI.Page.cls?...) but many people who have been using the InterSystems Studio for a long time missed the addition of this *very* useful feature, and every time I mention this to an audience I see at least one face light up because of how excited they are to learn about it!
Within Studio, the Output pane (View -> Output) is actually misnamed. It is actually an Input/Output window which can be used to run Caché ObjectScript commands!
I just installed Atelier, but when I tried to start it, I got the error "Java was started but returned exit code = 13". What's the issue here? How can I fix it?
I need to get the source code of a class installed on a remote server. I have no Studio or Atelier access to it but I can manage REST and Web terminal access.
Recently GitHub introduced topics for the projects.
So you can change your InterSystems related projects introducing the topics to let it be categorized, more visible and searchable. Here is the list of good examples for your projects (some of them are clickable already):
offers the latest features and bug fixes. It now updates your installation of Atelier to build 1.1.291 for Mac, Windows, Red Hat and SUSE. Here’s an account of what’s recently been improved:
Cache Studio's inspector window can show me a Cache class's properties,methods parameters, XDATA blocks, Triggers, Foreign Keys, Queries and more, in a table in the Inspector window. Additionally, for properties, where the property accepts parameters, these parameters are listed together with possible value choices.
By update
