Atelier is InterSystems’ Eclipse-based development environment. It enables you to rapidly build solutions that leverage the performance, scalability, connectivity, and reliability of InterSystems’ comprehensive data platform.
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.
I have Caché/HealthShare installed in a local Ubuntu 16.04 LTS virtual machine. I've also installed Apache 2.4 from the apache2 bundle, and enabled SSL. I've configured Caché such that SSL/TLS is enabled on the SuperServer port but not required.
I have Atelier client installed on a Mac and every now and then it just stops working. Currently I am getting this error when I try to synchronize my workspace with the server.
Synchronization failed: [server is broken] java.lang.ClassNotFoundException: Provider org.glassfish.jersey.internal.RuntimeDelegateImpl could not be instantiated: java.lang.IllegalStateException: No generator was provided and there is no default generator registered
Is anyone else experiencing similar problems and if so, what is the work around?
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.
You probably have a similar experience. The more I use Atelier the more I miss INSPECTOR that I had in Studio!
First for PROPERTIES that can inherit a variable number of Parameters beyond imagination. take %XML.Adapter as the most obvious. next: Where to find all inherited methods that I eventually want to overload? Take %Persistent as example.
Or where or how can %OnBeforeAddToSaveSet() (the correct camel case) be overloaded ?
I am having trouble finding/using the ability to refactor inherited elements from super classes. In studio this was under the Class->Refactor->override menu. I did note a 'refactor' option on the right click menu, but if you attempt to choose it the option greys out as soon as you get the mouse pointer over it. Does this feature exist in Atelier as of yet?
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.
Hello everyone. So as title says, I used to install Eclipse with Atelier plugin recently to work in instead of Cache Studio and spotted that all my JS-code on CSP page is colored green as you can see here:
I couldn't find how to make code-detection on CSP files like JS files. All I found is this element which controls code inside HTML tag <script></script>
I know you're doing a big effort to build a new IDE in Eclipse ecosystem but Visual Studio Code is a new an even better and faster tool for coding... did you have any plans to release any COS extension for it in the near future? There you can already find extensions for all current more common progrmaming languages and it would be great to have COS as one of them.
To be able to replace current Cache Studio user functionality in our source control system, I need to access the current project name that the atelier file belongs to when being checked out and in within the UserAction method of the source control class. In addition to this, there also appears to be a problem in that when UserAction code is executed by the Atelier callbacks, the process is running as UnKnownUser instead of utilising the authentication values assigned in the Connection settings for the server.
Does anyone know if these properties are currently exposed?
Almost exactly three months ago Atelier 1.0 was released. If you are an early adopter and have any feedback to share, here's a thread we could use.
For instance, during the Field Test I posted this article about the two explorers, Atelier Explorer (AE) and Server Explorer (SE). Presumably more people are now using Atelier, so I'd be interested to hear how it's going.