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.
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:
When using the "XML Cache Script" export via the Export context menu option (right clicking on a class in the Atelier Explorer View) sometimes the export dialog is empty.
Other times it is pre-filled with the project selected and the individual class chosen as expected. When it is blank you can choose the project but within the list of all classes there is no package hierarchy making it difficult to find your class.
Cache for UNIX (Apple Mac OS X for x86-64) 2016.2 (Build 619U) Thu Mar 17 2016
After deleting a class on the server, Atelier still wants to believe it exists. I even deleted the project and the server. After re-creating them, it still believes the class exists. I log in with studio and it shows the class has been removed.
If I attempt to open the class in the server explorer, I get a null pointer exception, but I can open any other class.
I have just imported our Ensemble project (not a really big one, like two man-years) into my MacBook Air Ensemble 2016.3 instance to test many things (document model, etc.), Atelier among the others.
The "Production view" is not here, and I miss it.
The opening of Diagram Editor for BP is pretty hidden. I would even like having a switch, which would default to the Diagram Editor.
Anytime I click on the Open Diagram Editor, it waits for a while, ten produces an error and only then I can see the diagram.
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?
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
I am pleased to announce the next in the series of 2016.2 field test kits, 2016.2.0.585.0.
In the two weeks since the last field test posting Development has made over a hundred fixes and improvements in Atelier, Enterprise Manager, Ensemble and Caché.
In Atelier alone there were over a dozen changes including a fix for the incompatibility issue that Jamie Newton described in his posting of February 1.
I am pleased to announce the next 2016.2 field test kit, 2016.2.0.595.0.
It may look like a slow week, with less than fifty changes having been checked in, but this kit includes the following fixes to problems found by you, the ones running the kits in the field:
By replies
