#Atelier

Does the Caché installer do all of the necessary setup for using Atelier when upgrading a pre-Atelier instance?

I just upgraded an Ensemble 2016.1 instance to 2016.2 and the /api/atelier web application wasn't created automatically. Aside from creating this web application is there anything else that needs to be done to support Atelier?

** UPDATE **
See my comment below -- this was caused by a permissions problem during the upgrade. After fixing the permissions problem and upgrading again Atelier works.

Some thins I have noticed, which I am not sure are bugs or features to come.

1.) Go to type declaration (F3 or ctrl+click on a class/variable/method)

It doesn not work on object variables and methods

Where it does work, it opens the related class but it is not editable.

2. )There is no code indentation correction/ctrl+L ?

Is this planned?

I would very much prefer to have formatting even if it means loosing some COS "functionalty".

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.

I am trying to debug a class on Atelier and it is not stopping at the defined breakpoint.

Atelier IDE Version: 1.0.107 - Cloud Connection

I have already taken a look at the Community´s Atelier Debugging Video and followed the steps without success.

Can anybody help me on that?

Tks.

Studio supports an option to display arguments using multiple lines. Is there an equivalent option for Atelier? The Studio setting is under Tools->Options, Environment->Class and is controlled by the "Multiline method arguments" flag.

I have existing projects in my Atelier environment. Where can I go to see which namespace they were created in?

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:

This is handy when debugging errors with a line reference and complex macros.

Is is possible in Atelier to open a macro declaration? Using the context menu results in a "Current text selection does not resolve to a Script element" error in the status area at bottom of window.

Also the arguments for the macro are not shown on hover.

Doesn't seem to matter if the associated include file is added to the project.

(Version: 1.0.142, Mac OS X)

When a class is opened from the Atelier explorer the full classname is used as the tab name. However classes opened from the server explorer only use the class shortname.

It would be nice to always use full classnames so it is easier to navigate open files:

Is there an equivalent to Studio's GoTo feature so I can easily navigate to zXXX+4^ABC label when debugging code?

I had no luck finding it so far.

Thank you!

Dan

When using the "XML Cache Script" export via the Export context menu option (right clicking on a class in the Atelier Explorer View) sometimes the export dialog is empty.

Other times it is pre-filled with the project selected and the individual class chosen as expected. When it is blank you can choose the project but within the list of all classes there is no package hierarchy making it difficult to find your class.

I have just imported our Ensemble project (not a really big one, like two man-years) into my MacBook Air Ensemble 2016.3 instance to test many things (document model, etc.), Atelier among the others.

The "Production view" is not here, and I miss it.

The opening of Diagram Editor for BP is pretty hidden. I would even like having a switch, which would default to the Diagram Editor.

Anytime I click on the Open Diagram Editor, it waits for a while, ten produces an error and only then I can see the diagram.

Version: 1.0.123

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.

Any thoughts would be appreciated.

James