#Atelier

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

Presenter: Clayton Lewis
Task: Use a modern, powerful tool for developing applications
Approach: Demonstrate how Atelier leverages the capabilities of Eclipse
 

In this session we will show you how we have leveraged the capabilities of Eclipse to create a modern, powerful tool for developing solutions.

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

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.

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

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.

In Atelier when resolving conflicts with the server the screen shows the Local copy and Server copy and the differences, but depending on where the difference is you cannot tell what what the document is, you need to scroll to the top to see what it is before deciding what to do.  It should indicate the class or routine name beside "Conflicting Server documents"

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

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. 

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

Hello! 

I'm trying to run a simple SQL query in atelier but it complains about the manager.  I'm not sure if this is the best way to do it but here is what I got so far:

Atelier Synchronization Logic

Background

I have 2 projects in atelier, A and B which map to namespace A and B on the same server.

Namespace B has some classes mapped from namespace A.

I then edit a mapped class in project A  and save it(I can see the changes in cache studio as well).

atelier A:

studio:

However in project B the class does not change, even if I click the "syncronize all files with associated namespace " button.

atelier B:

As I know Atelier sources already on github, but I think in private repository. May you say when this project will be opened, and how about if I want to contibute to this project?

Atelier shows the classes on server side as non editable grayed versions.

Is there a way to directly load class file from server and just start to edit that version?

Mikko

Currently when class is saved in Atelier it is automatically saved on disk and on server (if there is an active connection).

Is there any way to save file with class or routine just on disk, but not on server?

Hello! 

I'm trying to use iKnow but I get the following error "No iKnow-enabled namespaces found" in the Management Portal.

It was working on the 2015.2.2 version but now on 2016.2.0 it doesn't. I very new to Caché and iKnow so it's probably a simple problem. 

I was able to create a iKnow domain using the terminal and I can view it in the learning portal (http://localhost:57772/csp/sys/exp/_iKnow.UI.IndexingResults.zen).

What can I do to make it work in Atelier? I've tried authenticating with SYS:SYS and USER:USER but neither seem to have any namespaces.  

Very thankful for any help! 

There are still so many syntax highlighting errors in Atelier, which still exists from first beta public release.

So another topic that has been of interest to a number of people since the beta was put up last week is in regard to Studio Hooks and Atelier. This requires a bit of background and then some discussion of how the architecture of Atelier necessitates some changes and then what our current thinking on the subject is.

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. Others wanted to investigate a path

Hello! 

I'm trying to make a simple hello world program for iKnow but the documentation only shows examples using the scripting language or XML XData. 

The domain is already created and configured, what I hope for is to be able to work with the data in some high-level language. 

Is it possible to do something like this:

int domainId = 1;
IKnow iknow = new IKnow( domainId );
List concepts = iknow.getTopConcepts();

Any feedback will be greatly appreciated!

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

I am pleased to announce the next 2016.2 field test kit, 2016.2.0.595.0.

It may look like a slow week, with less than fifty changes having been checked in, but this kit includes the following fixes to problems found by you, the ones running the kits in the field:

• ALE2845, which fixes the cachejdbc.jar version
• JN1637, which fixes an issue that blocked debugging Atelier when used in conjunction with Kerberos
• DLP3508, which fixes a JSON issue with $compose()

The rest of the fixes have been spread among different areas of the product, chief among them DOCUMENT Data Model, SQL and Atelier.

Hi!

Are there any plans to support Kerberos authentication in Atelier to Caché connection?

Thank you.

Most of projects on Caché, obviously, written not only in Cache ObjectScript, and should contain sources in other languages. Such as js or css for web-projects or any others. And it would be pretty good, if I could see all of files in one project, and possible to edit all of them. How to be in this case ?

And I think it is not a good idea, to place all project's sources in one root folder. Our project contains over 3 thousands classes and routines, and it is too difficult to find anything in such folder. Is not a good for it to use Java-way, and place every package in subfolder ?

I am pleased to announce the next in the series of 2016.2 field test kits, 2016.2.0.585.0.

In the two weeks since the last field test posting Development has made over a hundred fixes and improvements in Atelier, Enterprise Manager, Ensemble and Caché.

In Atelier alone there were over a dozen changes including a fix for the incompatibility issue that Jamie Newton described in his posting of February 1.

In Caché major areas of focus include:

• SQL (ten changes),
• ECP and mirroring (11 changes),
• Objects and JSON (13 changes),
• DeepSee (nine changes), and
• Documentation (23 changes)