#Atelier

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.

Is there any official answer to this question: Does Atelier only support Unicode servers?

Thanks,

Joyce

Some Mac users have noticed "smart quotes" or "curly quotes" appearing in the browser-based Ensemble editors within Atelier. Specifically, typing "" may result in the output “” instead of the normal double quote characters.

I just used Help\Check for Updates and updated my Atelier from 1.0.158 to 1.0.165. Is there any information published about what's new/fixed in this compared to previous public builds? Having that information might help us target our testing and so increase the value of our feedback to you.

Hi -

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)

Hi -

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?

Thanks

Chip

I was writing a routine that called some class methods and when I typed in ##class( and the package, there was a drop down list of all the classes that match that package but when I selected one of the dropdown entries it added the package name again.

For example if I enter ##class(dim.

I am presented with a list of classes in the dim package but when I selected one of them,(dim.OccupationList), what ended up in the editor was

##class(dim.dim.OccupationList

On the Mac...

I've defined a Cache Connection to my local server. It worked for the last two days, but after an uninstall/reinstall of Atelier, it stopped working. The stack trace has these entries:

java.lang.RuntimeException: Can't read from secure storage node /com.intersys.eclipse.connmgr/ensrc

Caused by: org.eclipse.equinox.security.storage.StorageException: No password provided.

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.

Found in:

• atelier-1.0.0AT.142.0
• Cache for UNIX (Apple Mac OS X for x86-64) 2016.2 (Build 636U) Wed Apr 13 2016 21:07:40 EDT

Breaks on FOR SOME when using a table reference:

Hi!

In every Atelier project you can find following hidden files:

.buildpath

.version

.connection

.project.

Should I include all of them into commit?

I understand that .project is mandatory. But what about the rest? Is there any general rule?

F.e. if we work in team and everybody has their own connection on locale machine .connection should not be included. Yes?

When I check for updates from by 1.0.116 I get this:

Presenter: Bill McCormick
Task: Migrate your development environment from Studio to Atelier
Approach: Give examples of various migration paths. Provide guidance for dealing with issues such as source control, source format, distributing code to previous versions, etc.

Moving from Studio to Atelier Session Code: ATMOVE In this session we will show you a variety of paths for migrating your development environment from Studio to Atelier. We will cover Source Control, Source Format, Distributing code to previous versions and more.

Content related to this session, including slides, video and additional learning content can be found here.

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.