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.
The FT keys InterSystems currently make available to us in the zips from the download pages are due to expire at the end of this month (31-Aug-16). Will there be new keys soon?
Also wondering when we might expect new FT builds for 2016.2 and 2016.3. The last published ones were 24-Jun-16 and 16-Jun-16 respectively.
I haven't seen an Atelier update for a while either.
I have been meaning to make a post about this topic for a few weeks and the other day an issue came in through the WRC about it so it seems this is a conversation we should be having. I want to begin by taking a few moments to explain "Why Atelier" then we can talk about what this means in the general sense for Studio and Atelier and Caché developers. We have wrestled with what to do with Studio for years. When I moved to Product Management in 2008 this was already a "thing". At the time we could not reach a consensus. Some felt Studio was fine as is.
I've seen a few reports of issues for Mac users where every relaunch of Atelier throws errors related to Secure Storage . Trying to save a server connection displays the error:
Secure storage may be corrupted: see Help section on troubleshooting.
The server connection also has a red X with a corresponding message in the Error Log:
Most of projects on Caché, obviously, written not only in Cache ObjectScript, and should contain sources in other languages. Such as js or css for web-projects or any others. And it would be pretty good, if I could see all of files in one project, and possible to edit all of them. How to be in this case ?
And I think it is not a good idea, to place all project's sources in one root folder. Our project contains over 3 thousands classes and routines, and it is too difficult to find anything in such folder. Is not a good for it to use Java-way, and place every package in subfolder ?
This is more of an eclipse thing, but I couldn't really find an answer when I searched. I created a new workspace, but I had updated my keyboard shortcuts in the first workspace and now I'm trying to import the changes. I successfully exported them as .csv, but I cannot find a way to import the changes into the new workspace.
Is is possible in Atelier to open a macro declaration? Using the context menu results in a "Current text selection does not resolve to a Script element" error in the status area at bottom of window.
Also the arguments for the macro are not shown on hover.
Doesn't seem to matter if the associated include file is added to the project.
When a class is opened from the Atelier explorer the full classname is used as the tab name. However classes opened from the server explorer only use the class shortname.
It would be nice to always use full classnames so it is easier to navigate open files:
I am using the latest publicly available build, 1.0.255. Here's what my Tools menu looks like, with highlights added by me to indicate the parts I'm trying to understand the purpose of:
I'm pleased to see the new Source Control menu in the recent 1.0.165 build. This gives me access to the features of the same server-side source control class as Studio has always supported. It is particularly relevant for our Deltanji source control tool.
Our class makes use of CSP to serve up some dialogs through which the user controls the source control operation. Two observations so far:
1. In Atelier the window you display our CSPs isn't resizable. In Studio it is.
Is there a way to return to where you were after using the Open Declaration F3? In studio you could use ctrl-shift-G to open the declaration and ctrl-alt-G to return.
I was writing a routine that called some class methods and when I typed in ##class( and the package, there was a drop down list of all the classes that match that package but when I selected one of the dropdown entries it added the package name again.
For example if I enter ##class(dim.
I am presented with a list of classes in the dim package but when I selected one of them,(dim.OccupationList), what ended up in the editor was
Hi, I just installed the TRYCACHE 2016.2.1 preview release into a 16.04 Ubuntu VM. The install is dirt simple. Very nice. I've installed Eclipse Neon and used your update site link to get Atelier. Also very simple and nice. Thank you!
I see there is a January update coming. Will it be possible to include a license that lets developers launch one terminal session while connected to the TRYCACHE instance via Eclipse?
When I try to do this, I'm exceeding the TRYCACHE license limit.
Development productivity? Isn’t it kind of an oxymoron? Anyhow, we all dream a magic tool which does the tedious job of the software development and leave the intuitive or creative part on the developer. Atelier is the next generation tool of InterSystems aiming to boost the productivity of Caché/ Ensemble based software development. Atelier is based on the popular Eclipse IDE platform, which makes available the “infinite” pool of third party tools for Caché developers. Those tools can truly boost the productivity. This short article gives some examples how third party plug-ins can help developing for Caché. It is an absolute beginner’s guide, beginner to Eclipse but experienced to Caché.
I just used Help\Check for Updates and updated my Atelier from 1.0.158 to 1.0.165. Is there any information published about what's new/fixed in this compared to previous public builds? Having that information might help us target our testing and so increase the value of our feedback to you.
It appears latest version of field test supports Rules. What does support of Ensemble rules in Atelier mean for Ensemble users? Does it mean compilation and development can now be done in new Studio? If yes, how indentation and aliment work with Atelier?
Some Mac users have noticed "smart quotes" or "curly quotes" appearing in the browser-based Ensemble editors within Atelier. Specifically, typing "" may result in the output “” instead of the normal double quote characters.
Presenter: Bill McCormick Task: Migrate your development environment from Studio to Atelier Approach: Give examples of various migration paths. Provide guidance for dealing with issues such as source control, source format, distributing code to previous versions, etc.
Moving from Studio to Atelier Session Code: ATMOVE In this session we will show you a variety of paths for migrating your development environment from Studio to Atelier. We will cover Source Control, Source Format, Distributing code to previous versions and more.
Content related to this session, including slides, video and additional learning content can be found here.
This article explains how Atelier helps you to improve software development productivity. One of the Ensemble features is the VDoc infrastructure. When someone develops HL7 v2.* production, She/ He is in a luxurious situation because Ensemble comes with a HL7 Schema editor. On the other hand this is not the case with XML VDocs. But with some effort you can turn Atelier to a handy XSD editor and close the gap.
Please follow the step-by-step guide to complete the job.
Presenter: Clayton Lewis Task: Use a modern, powerful tool for developing applications Approach: Demonstrate how Atelier leverages the capabilities of Eclipse
In this session we will show you how we have leveraged the capabilities of Eclipse to create a modern, powerful tool for developing solutions.
Content related to this session, including slides, video and additional learning content can be found here.
By replies
