#Atelier

Is it just me or is the sync mechanism way too slow and too trigger happy to be used for large projects? It keeps "Caching for server connection" which takes a good five minutes!

Has it been tested with a large number of classes and CPSs? I have about 2000 of each.

I recently installed Eclipse and Atelier and was able to connect to my dev environment and source control. However, when I open a CSP file everything inside <script> tags shows up green as if it's a comment.

I looked through all the preferences but wasn't able to fix this. Has anyone else run into this and/or know a solution?

Thanks,

Orion

In trying to understand Atelier I am directed to go through its hierarchy type of documentation.

Is the Atelier documentation going to continue as a hierarchy or at some point is it going to be integrated into the InterSystems type of documentation?

When looking for an answer it would be nice to use only one method.

How can I export project with CSP pages in it? The Atelier export wizard does not include the CSPs in the export list.

Hi there,

I'm currently getting myself acquired with Atelier and apart from having a lot of fun I noticed an issue that keeps me from merging changes to the server. When importing Files into my project it uses the right encoding (without telling it what encoding to use). When trying to synchronize it shows the Conflict Resolution, with the server side using the wrong encoding therefore displaying gibberish.

In Studio you can open class with typing / pasting full classname Ctrl+O dialogs filenamebox.

in Open Atelier Class/Routine Dialog (Ctrl+Shift+T) you can't give full class name (package.class) and

when typing only classname part it does not give you any hint about package of those classes it shows.

Its' a bit frustrating when we can have ( and we have) lot of classess named similarily in different packages

and we have lot of packages so the tree crawling is a bit slow.

Ok, Hopefully I am missing something simple. Where can I look to see the current server connection and namespace associated with a project in Atelier? I have looked at project properties and other places and cannot seem to find this information.

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!

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

InterSystems is ready for 2018 since Atelier 1.1 is now available as a stable release! Bring on the new year!

To subscribe to the NEW Atelier release channel, please follow the instructions on the Atelier Download page.

Stick with the beta update channel if you want to be an Atelier insider and get the latest new features and enhancements before anyone else. #VIP

With this release, you can:

Hi, Community!

You are very welcome to watch just uploaded InterSystems Atelier Welcome video on the InterSystems Developers YouTube Channel!

https://www.youtube.com/embed/gmHsmCf7VpY
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

Subscribe and stay tuned!

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.