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
https://community.intersystems.com/video/atelier-editing-and-debugging-demo
This video should get you started. I am working on a video about development workflow and a matching post I hope to publish shortly.
The test is not limited to two weeks. That was simply the expiration on the license. We updated the beta facility with a new version and a more generous license. Happy coding!
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!
John -
The WRC is handling any calls with regard to the beta cloud portal. I saw this and reached out to the cloud provider as the issue is coming from their side. I will let you know as soon as I hear back.
The HS team is launching a community here as well. The data platforms groups are the "trail blazers" for this project.
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
Congratulations John!
Its a demonstration class. The methods write text back to the Atelier console. Its to show that if you enable hooks we do in fact do all the right things.
To my knowledge it use TCP. In fact we moved away from in memory even for Extreme.. in the end the performance differences were slight. Stefan Wittmann can confirm.
It has been finished for months. We are chasing down a few issues that cropped up in the final rounds of QD. We do not promise specific dates but its status has been "imminent" since Jan 1. It will ship in Q1
Its unclear at this time. They will appear in the server explorer view for certain. In the examples above these are just classes in the end and certainly could be edited in Atelier. The rules implementation as an example is very specific to Studio and in Eclipse there are easier and better ways to make wizards and templates natively.
Atelier has a similar feature in its debugging context that allows for execution of COS. We are also integrating a built in terminal.
Hi John - Apologies. Our WordPress site is having difficulty. The index shows the text but no individual posts appear. Our tech guys are looking in to it now. If you click compatibility to get to the index you can see the text ;)
Hmmm. This is changed from the private beta. In the private beta version there was a save or "build" option. Save meant save locally and "build" meant to push the change to the server and compile. It looks like this got lost somewhere along the way. It was not meant to be.
There are means to load the UDL format of Atelier on the server as well.
There are ways around this. You can export code back from Atelier in XML format and not use source in Atelier. Its not recommended but it does work.
I strongly recommend people to each have their own system and to sync to a source control system as a preferred methodology. The one use case I have heard to justify putting a lot of developers on one box is where you are doing something like Ensemble and you have a complicated integration environment, perhaps with security restrictions that make it prohibitively difficult to replicate that set up across multiple systems. But even tasks like this become easier with tools like Vagrant that "package" an application and install it with standard customizations across multiple systems and even OSes.
Having a bunch of developers touching code in the same namespace is a perilous thing. How do you know what is production code versus something I was noodling on as an experiment this morning? Fighting over the same classes? These are all nasty repercussions of having a bunch of people editing on the same system.
We are still deep in a development phase. Robert Nagle does want to open source Atelier development at some point further along in the process. Its not yet clear exactly how we will do that but keep an eye here for an update.
Generally we favor ANTLR. The COS parser required complexity we were not confident we could achieve with ANTLR. Having said that we continue to debate this internally as Jonathan expressed. When we release Atelier we do anticipate publishing a lot of the code to open source. Dmitri I will reach out to you through the Russian office as we may be able to leverage your knowledge.
Great info Ben - thank you for sharing!
FYI - there are some changes coming here in 16.2
I posted a compatibility blog statement that has not been approved yet but there are a few changes coming in this area.
We continue to update both the client kits there and also the cloud server instance that supports it. Once you have Atelier installed you can upgrade it any time through the "Check for Updates" facility that is built in and get the latest kit. I upgraded my instance this way today!
I will have the text corrected as soon as possible
It should work automatically with recent clients. I am uncertain what build you were trying to update from but as of mid february we should be prepopulating the URL for you
Just go to "About Atelier"
There is a splash screen and it should show something like:
Version: 1.0.112
Which is build 112 of Atelier. We switched to this scheme about a month ago John.
Terrific.. thank you for confirming Herman.
And isn't that slick? :)
We are working on some infrastructure that will allow existing add-ins and templates to be called from Atelier. I just saw a demo today. Just keep updating :)
Thank you Nikki - this is a bug. It should check the project first and only go to the server if it cannot find the class locally in the project.
Shhhhhh John.. those are secrets :)
Yes this is creeping in though we know we have a few problems.
Don't give away my other secret.
Wow. Just wanted to say a great topic guys! Thank you
Just to clarify for people. We are not working to enhance DOCBOOK searching. You can use Google search today.. right now.. on our current documentation set via the community. This is an attempt to modernize the layout and look of what DOCBOOK presents once you have clicked a search result and displayed what you get.