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.
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.
I would like to change the initial text that is generated by the New Class wizard in Atelier, but I'm not sure if I can or where to go to make the modification. I have a specific format for initial classes, and the wizard generated code isn't cutting it for me. I know it's trivial to take the generated text and just modify it, but if I could only have to do that in the wizard, that would be better.
The more generalized question is, which wizard output can be safely changed without fear of losing the change on upgrade, and where are these?
I'm getting this error a lot in Atelier. These are not extremely large files, and I can't seem to find a magic line count or byte size that triggers the issue to occur.
I'm using the latest (I believe) version 1.0.262. Is there a setting that allows larger files to be parsed successfully within the editor?
Does the Caché installer do all of the necessary setup for using Atelier when upgrading a pre-Atelier instance?
I just upgraded an Ensemble 2016.1 instance to 2016.2 and the /api/atelier web application wasn't created automatically. Aside from creating this web application is there anything else that needs to be done to support Atelier?
** UPDATE **
See my comment below -- this was caused by a permissions problem during the upgrade. After fixing the permissions problem and upgrading again Atelier works.
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.
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.
I've been trying to create a "sub packaged class" (i.e. TopPackage.SubPackage.Classname) but the current version of the "New Class Wizard" doesn't seem to allow me to do this.
If I try to specify a \project\subdirectory in the "Project" or I try to specify a Package.Subpackage form in the "Package", or I try to specify "Subpackage.Classname" in the "Class Name" they ALL fail to give me a "next" or "finish" button that works (the buttons stay greyed out)
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:
I installed Atelier on Windows in order to take a look at how the BPL and DTL graphical editors accessible via the "Open diagram editor" action work. The diagram editor is opened but I get the following error:
Message from webpage --------------------------- Unable to load SVG diagram. Please ensure your browser is supported for portal access.
It looks like Atelier uses IE in order to display the editor even though my Windows default browser is Chrome.
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.
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.
My comments here relate to Atelier 1.0.137 on Windows connecting to Ensemble 2016.2 FT build 627.
I've been looking at what the Atelier Explorer view (hereafter AE), whose root elements are projects, lets us do with the contents of the namespace that the project is connected to:
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:
We have noticed that when compiling with Atelier (either Atelier itself or sending the code through the REST interface) that the build will fail if all brackets '() {} []' are not closed. This includes brackets opened in comments.
For example, this will fail:
class myclass
{
//if someVar {
}
I do not know if this issue has been fixed or if this issue has been brought up, but it has been a nuisance over here.
I'm using Atelier 1.0.145 on Windows (x64). When I open the Help menu from the menubar the final entry (About Atelier) has a huge version of the Atelier icon alongside it. This distorts the menu. I can't post a screenshot here because my simplistic screen capture tool causes the faulty menu to close. But the large icon I see is also (correctly) displayed on the About box itself:
After having seen how Atelier is working, I've decided to start learning/using Atelier for an existing project.
I've installed, and after a bit of poking around, I've managed to get a project that includes my classes, and they compile and such (these were all from an existing export), but I see that NONE of my .csp files came along despite being in the export file.
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.
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.
Please make these dialogs easier to use, for example by treating a double-click on a list item as a signal to select the item and effectively click the "Next" or "Finish" button. Using Tools\Add-Ins as my example, on the first page:
By likes
