Atelier

Syndicate content 81 

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.

0   0 1
0

replies

564

views

0

rating

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.

0   0 1
0

replies

355

views

0

rating

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"

+ 2   0 2
142

views

+ 2

rating

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

+ 1   0 1
221

views

+ 1

rating

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

 

 

 

Last reply 14 March 2016
+ 1   0 5
159

views

+ 1

rating

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:

Last reply 10 March 2016
0   0 5
210

views

0

rating

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

Last reply 3 March 2016
0   0 3
350

views

0

rating

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.

Last reply 3 March 2016
+ 3   0 6
1,069

views

+ 3

rating

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.

Last reply 3 March 2016
+ 9   0 5
3,201

views

+ 9

rating

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!

Last reply 3 March 2016
+ 1   0 4
343

views

+ 1

rating

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:

+ 3   0 0
0

replies

167

views

+ 3

rating