Lucas,

This view bypasses what makes Cache such a compelling technology in my opinion. We are not "just" an OO database or a relational database. We support both models fluidly and give you the important features and functions of each in a complimentary fashion.

 

We are truly multi-model not Object with SQL or SQL mapped to Objects. We let you define structure in Objects where real world modeling is important but then seemlessly query data using SQL - which is what the language was designed for, not for defining data structures.

 

SQL is not evil. It has simply been abused for cases it was not intended in many DBMS implementations.

 

my .02 cents

Trevor - I would need a lot more information to provide you with a complete answer. I will give you the 50000 foot answer and then we may need to dig a little deeper.

 

There are no REST apis for interacting with the Studio Hook mechanisms at this time. As I said in the article that is really working backward from what Eclipse gives you out of the box and more toward building a Studio Hooks plug in for Eclipse instead.

 

Studio is a powerful tool and one that can lead to very creative things if the people using it are willing to invest in the entire stack needed to effectively add functionality to Studio. This stack requires knowledge and capability of leveraging:

 

HTML

CSS

CSP

ZEN

COS

%Studio.Template

Add-ins / Templates

 

I know a large number of people have done this work. We are trying to create an IDE that follows a more modern and standard approach to adding functionality to an IDE. What that means with regard to Studio Hooks may evolve or change over time but we are starting from the baseline that what Eclipse offers out of the box is better.

 

Let's talk for a moment about your larger question of add-ins and launching web pages that share license info from within Atelier. We have this issue ourselves. Let me give you a real world example:

 

One of the most frequently used templates in Studio is the Soap Client Add-in interface. This is a CSP document that provides an interface that lets you point to a URL or a WSDL document locally, parse it, decide how the classes to be generated should be processed and then eventually launches the import. The actual work is handed over the server and done in a process there with the compilation output redirected to the Studio. This is a very complicated piece of code and one that causes confusion and issues for people related to https, validation to access a given document or URL etc. But functionally it aligns closely to what you are describing above. For us to port that wizard as is we need to launch a web page from Eclipse. Let it do its thing, not bleed licenses when it actually connects to the server and does its thing and then we need to tell Atelier about the classes that were generated when it completes. We have a working model for this in development with Atelier at the moment. I don't have the source to hand but I can drag it up given some free time. I hope that comes close to addressing your general case.

 

 We want to encourage people to build these sorts of tools in Atelier using the Eclipse stack and framework as opposed to studio templates and server side functions. We know that people have existing code and will want to port it over as easily as possible of course. More later.. Apologies it took so long but the holidays you know!

I am not sure exactly what you are asking. The only current restriction is that you have to have a valid WRC credential for access to the online container. If you want to install a version locally then right now the answer is no. We will be updating this container at an aggressive rate. At a later date and as we get closer to release there will be more channels for accessing Atelier servers