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.
EnsPlus, the Caché Objectscript plugin for Visual Studio, has now been upgraded to support all versions of Visual Studio 2015, including the free Community edition.
While Studio and Atelier are useful development interfaces, there are occasionally situations where a quick edit needs to be made to code and only terminal access is available. A useful set of tools to do this are the zload, zprint, zinsert, zremove, and zsave commands. These are abbreviated to zl, zp, zi, zr, and zs respectively. While each of these commands has its own page in documentation, this article will synthesize that information with examples to provide instruction for their combined use.
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.
Hi all - I'm running a Zen page that inherits from %Zen.Component.page, and I'd like to step through code and debug it. Is this possible, and how?
I've tried to attach to a process that I think is mine (it has my internal IP address) but is using "Unknown User". Any ideas on where to start debugging the page -- this page calls lots of other pages. I'd thought I'd start at the home page.
Perhaps I need to navigate to my page that I want to debug, and attach at that point.
Any info on the debugger in this atypical use is appreciated.
Heretofore is announced a new project which aims at providing a usable library for both running unit tests and collecting code coverage information at the same time:
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.
In Atelier when resolving conflicts with the server the screen shows the Local copy and Server copy and the differences, but depending on where the difference is you cannot tell what what the document is, you need to scroll to the top to see what it is before deciding what to do. It should indicate the class or routine name beside "Conflicting Server documents"
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'm trying to run a simple SQL query in atelier but it complains about the manager. I'm not sure if this is the best way to do it but here is what I got so far:
If you've got more than one developer on a project, do you each work in your own namespace? Or do you all use a common namespace?
Through my work at George James Software I have encountered many different Caché and Ensemble development setups. At risk of over-generalizing, the older and more established users of InterSystems technologies seem more likely to have all their developers working in a common namespace, whereas the newer 'converts' tend to favour giving each developer their own namespace.
As I know Atelier sources already on github, but I think in private repository. May you say when this project will be opened, and how about if I want to contibute to this project?
So another topic that has been of interest to a number of people since the beta was put up last week is in regard to Studio Hooks and Atelier. This requires a bit of background and then some discussion of how the architecture of Atelier necessitates some changes and then what our current thinking on the subject is.
By update
