#Atelier

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.

Atelier needs Java 1.8 to run, but manage diferent versions of Java can be tricky in OSX

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.

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:

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.

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:

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:

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?

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

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.

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.

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!

Since we announced last week that Atelier would only be available as an Eclipse plugin, some of you have been asking about how to convert from your standalone client. Here's what you might want to do.