Atelier

Syndicate content 77 

Mark All as Read

I was searching for the most simple way to connect from visual studio code to my local instance via terminal without having to change any window.

I know this can also be achieved via telnet but seems a bit overhead if you're in your local machine.

For me the simplest sollution is to open a terminal window in VS Code, navigate to the /bin folder of your instance installation and run .\csession.exe INSTANCENAME

For simplicity you can just include your /bin folder in your path so you don't even need to navigate there

Last reply 21 February 2020
+ 1   1 0
111

views

+ 1

rating

Every developer has made the mistake of accidentally leaving temporary debug code in place when they meant to remove it after debugging is complete.  The great thing about writing in ObjectScript is that there is a way to make temporary code be truly temporary and automatically self-destruct!   This can also be done in such a way that the code has no change of making it into your source control stream, which can be helpful as well.

Last reply 9 October 2019
+ 3   0 2
205

views

+ 3

rating

Hi,

This is a quick tutorial how to install and use TFS in Atelier. It is based on my self experience and some tricks that I 've noted.

If you are used to using visual studio maybe you feel that is a bit slow and heavy, but you have the same TFS panel as you have in Visual Studio, so don't need any special "training" to use it smiley

Last reply 15 February 2019
+ 12   2 8
987

views

+ 12

rating

One of the many benefits of using Atelier for your ObjectScript development is its integration with a wide range of source control systems. This integration enables you to use modern development workflows which increase collaboration while minimizing the risk inherent to volatile code bases. 

Veteran ObjectScript developers can tell you about the workarounds that were needed before they could use source control systems with products like Caché and Ensemble. One of these was to treat the data store itself effectively as a code repository. And so shared development environments became essential for many of our customers to be productive and successful. 

For code shops that rely on shared development environments, adopting Atelier might seem too complicated. This article aims to provide a practical example to guide your team towards success with Atelier. 

You can find an overview of the problems and solutions in this article here, which is a good place to start. This article assumes that you are familiar with the concepts introduced there. 

Last reply 2 January 2019
+ 8   0 2
451

views

+ 8

rating

The goal of this article is to give users of InterSystems products background on source control in general, and how it can be used with Atelier, an Eclipse plugin. Specifically, I'll be discussing what to do when all of your developers share a single dev instance of an InterSystems product where they can edit and compile code.

Last reply 23 December 2018
+ 2   2 2
393

views

+ 2

rating

The Eclipse environment persists perspective data to enable layout customization and other features. Sometimes when this data becomes out of date, Eclipse fails to clear references to it. For example, upgrading a plug-in can leave behind data about an earlier version of that plug-in. This mechanism applies to all Eclipse plug-ins and is not unique to the Atelier plug-in.

In light of this: You may find that after upgrading from Atelier 1.1 to 1.2, your Atelier perspective looks something like:

Last reply 13 June 2018
+ 5   0 3
562

views

+ 5

rating

There has been some confusion about how to edit Business Process Language (BPL) and Data Transformation Language (DTL) files in Atelier using the graphical editor. The following steps describe how to do this with Atelier version 1.0:

Copy the file you want to edit from the server to an Ensemble-enabled project in your Atelier workspace. To do this, find the file in the Server Explorer, right click and select Copy to project.

Open the file in the Atelier class editor just as you would any other class file.

Last reply 5 June 2018
+ 5   1 4
586

views

+ 5

rating

While testing Atelier 1.0.255 I noticed that the namespace subtree of my Atelier project used different icon shading for the top-level Classes folder compared with the top-level Routines one:

Drilling down into parts of the Wasabi package helped me work out the significance of white-filled icons versus brown-filled ones:

A package is white if there are no classes in it, but only subpackages.

Last reply 29 May 2018
+ 1   0 3
386

views

+ 1

rating

When defining a server connection in Atelier we are required to enter a username and password because these are mandatory fields in the dialog. However, if the /api/atelier web application definition on that server has only the "Unauthenticated" checkbox set in the section titled "Allowed Authentication Methods", then our Atelier connection will succeed even if we supply an invalid username and/or password.

Last reply 29 May 2018
+ 2   0 3
403

views

+ 2

rating

One of the benefits of Atelier is easy integration with source code management tools. Some Eclipse installations include the EGit plugin, or you can install it from the Eclipse marketplace. EGIt makes integration with Git and GitHub easy. Here are the steps I used to connect Atelier to a GitHub repository:

Last reply 23 March 2018
+ 8   0 4
1,769

views

+ 8

rating

Where did the RemoteSystemsTempFiles project come from?

If you're using Atelier, you may have noticed a project called "RemoteSystemsTempFiles" in the Atelier Explorer and Project Explorer views. This project is automatically created by the Eclipse Remote Systems Explorer (RSE) on start-up. The RSE allows you to connect to and work with a variety of remote systems.

You can either hide this project within your views, or remove it completely by following the steps below.

+ 5   0 1
0

replies

1,977

views

+ 5

rating

Hi Community,

I would like to share with you my experience regarding  to debugging via Atelier.

I'm developing a REST API and would like to attach to a process when I call the API via a REST Client tool, for example Postman. The purpose is to inspect values from HEADER and BODY of the HTTP request during the debugging process.

Come on! How am I doing? I am going to demonstrate that by using a class from SAMPLES namespace.

1 - Open Atelier;

2 - Open your REST Service class;

3 - Go to the method related to the URI that you need to debug;

Last reply 9 January 2018
+ 8   0 6
700

views

+ 8

rating

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 ?

Last reply 1 December 2017
+ 12   0 4
480

views

+ 12

rating

The Atelier beta update channel:

https://atelier.artifactoryonline.com/atelier/updates/beta/1.1

offers the latest features and bug fixes. It now updates your installation of Atelier to build 1.1.310 for Mac, Windows, Red Hat, SUSE and Ubuntu. Here’s an account of what’s recently been improved:

New Features:

Last reply 14 November 2017
+ 4   0 4
574

views

+ 4

rating

Greetings fellow Atelier users! To help new users get started, we are planning to make a list of video tutorials (e.g., how to create an Atelier project). The first one is "Introduction to Atelier", which is a brief tour of the Atelier user interface. We'd appreciate it if you could watch this video and let us know your comments. We'll be relying on your feedback to create more video tutorials to make it easier for new users to learn Atelier.

Please feel free to post your comments below. We look forward to hearing from you!

Last reply 6 November 2017
+ 4   0 2
605

views

+ 4

rating

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.

Last reply 12 October 2017
+ 7   0 10
1,292

views

+ 7

rating

We just faced an issue of the Atelier main menubar being disabled (greyed out) after upgrading the macOS development machine to High Sierra. I would like to share my findings about the issue and how to fix it.

This seems to be a known problem affecting several Java applications including Eclipse if the macOS user's primary language is not English: https://www.eclipse.org/org/press-release/20170925criticalbug.php

+ 4   0 1
0

replies

294

views

+ 4

rating

One of the most important features during application development is the ability to debug your code easily. Because of the asynchrnous nature, a standard Node.js application server works single-threaded by default. When you are developing applications using an IDE like Visual Studio Code, you can very easily debug your Node.js process:

First, download the free Visual Studio Code IDE (@code) and install it on your development machine.

+ 3   0 2
0

replies

1,203

views

+ 3

rating

Is your development team following best practice now that source control and continuous integration testing are better supported by InterSystems new IDE Atelier?

Many teams are turning to Git as their version control system of choice because it never locks files, among other reasons.  These teams may also be following a multi-server development workflow where changes are migrated from a DEV server to a TEST server to a PROD server. How should these teams organize their repository given this configuration?

+ 4   0 3
0

replies

724

views

+ 4

rating

The Atelier beta update channel:

https://atelier.artifactoryonline.com/atelier/updates/beta/1.1

offers the latest features and bug fixes. It now updates your installation of Atelier to build 1.1.291 for Mac, Windows, Red Hat and SUSE. Here’s an account of what’s recently been improved:

New Features:

Last reply 25 June 2017
+ 2   0 3
712

views

+ 2

rating

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.

Last reply 6 April 2017
+ 2   0 1
560

views

+ 2

rating

The article makes an attempt to demonstrate that Atelier is not just repeating the functionality of Caché Studio on a new IDE platform (Eclipse) but goes far beyond. Due to my personal experience, and challenges in former projects I picked first XSLT Debugging. Is it an ordinary task? Not at all. Who is doing XSLT every day? Probably none of us. Than why XSLT Debugging? Simply because there are solutions in our product portfolio which are using XSLT inside and those solutions require customization. Customizing XSLT without some sort of toolkit is more than challenging. The examples of such solutions starts with HealthShare IHE message, CDA vs. SDA transformations, goes through ZEN Reports, and ends by HealthShare CDA document viewer. Is that enough reason to spend time reading the whole article through not just the teaser?

Last reply 1 February 2017
+ 4   0 4
396

views

+ 4

rating

This article is one of the series which introduces Eclipse to experienced Caché/ Ensemble/ HealthShare users. The goal is to open the perspective of a developer who was using Caché Studio for years and make Her/ Him see deeply into the Eclipse world – far beyond Atelier. In other words it is an Atelier (Eclipse IDE for InterSystems technology) beginner’s guide. This time the topic is: editing XML files using Atelier.

+ 2   0 1
0

replies

539

views

+ 2

rating

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é.

Last reply 3 January 2017
+ 3   0 4
867

views

+ 3

rating

TaskStudio ActionAtelier EquivalentAtelier Keyboard ShortcutSee also ...
Display line numbers.View > Show Line NumbersWindow > Preferences > General > Editors > Text Editors > Show line numbersCTRL+,Atelier Editor Features: Line Numbers
Code completion assistanceImmediately suggests completions as you type, unless explicitly disabled.You must type CTRL+SPACE to invoke content assist.CTRL+SPACEEditor Content Assist
+ 5   0 1
0

replies

469

views

+ 5

rating