go to post Bill McCormick · Jul 16, 2018 I make every effort to take a passive role here on the community but I have to make a statement here. What you are saying is that regardless you are leaving people with a broken experience. If Atelier does not get the added editors needed to support HealthShare development fully with integrated source then its appeal is greatly diminished as you have large pieces of work that miss out on integrated source control. But you can't go back to Studio either as it leaves you with no supported plugins for ANY source control system at all and means you have to make that implementation yourself via Studio Hooks. Neither of these situations is viable unless your intent is to leave people with no forward path for managing code and developing on ISC technology using any modern professional development approach.
go to post Bill McCormick · Dec 1, 2016 Hi Dmitry,As I mentioned we are still working to complete all functions in the COS parser. I will make certain the developers are aware of this syntax error.
go to post Bill McCormick · Dec 1, 2016 Hi John - I saw something similar when I ran update but in my case I did not get the signing warnings. I will pass this along to the right people. Thanks!
go to post Bill McCormick · Nov 30, 2016 You can jump from code you are looking at to referenced calls via the Ctrl-F3 shortcut. Studio's "GoTo" feature which allows navigation to a specific line+tag will be included in the 1.1 release.
go to post Bill McCormick · Oct 31, 2016 Herman - there is a place to report issues. Its the same as anything else with our product. The WRC is fully supporting Atelier and issues are tracked in the same manner as any other part of the product. We are encouraging general conversation here because it is of benefit to everyone and not specific to Atelier as a policy point. As for choosing Eclipse. It boils down to ecosystem. The editors you mention are all nice but none of them support the entire range of features we can get from Eclipse. You will note that by adopting a REST api we left it open for ourselves or anyone else to expand the functionality of any popular IDE on the market for use with our products.
go to post Bill McCormick · Sep 6, 2016 I did this as well but set it up with https which I found to be much simpler to do.
go to post Bill McCormick · Aug 29, 2016 This really boiled down to the band aid removal technique. The existence of a switch implies people are not under any pressure to make changes to their code. It gives them a reason to wait. The longer we left this in the longer we had to support it and the more questions about why something might work in one syntax but not the other. I hate causing partner's pain but in this case the sooner the better.
go to post Bill McCormick · Aug 26, 2016 We looked at and abandoned that approach in the early days because it is not flexible enough. You get only a single projection for a given class and any changes to it require a recompile of the class. Compose() is an attempt to move past those obstacles.
go to post Bill McCormick · Aug 26, 2016 Michal - if you can wait it might be better to stay on your current kit and then pick up the 17.1 FT as an update in 8-10 weeks?
go to post Bill McCormick · Aug 26, 2016 Herman Stefan can speak to the specific syntax changes to a larger extent then I can. I don't know your timing but I think the best answer is port to the current syntax and go live on 16.2 within a month or so if that is possible. I feel your pain on these changes. But I do believe the end result will benefit everyone in the long run
go to post Bill McCormick · Aug 25, 2016 Please read the announcement here: https://community.intersystems.com/post/announcement-about-cach%C3%A9-20... We have been holding updates of Atelier to finish refactoring to conform to the changes outlined there. Kits are being published for 16.2 today and a new Atelier kit will be available in "Check for Updates" today or tomorrow.
go to post Bill McCormick · Aug 18, 2016 There are multiple steps required here.1) The two csp applications that support the Zen app and the REST app must both be defined to store their license information ( cookie ) in the same location on the browser. You will need to make sure you have enabled cookies for sessions and that both apps put the cookie in the same location.2) In the CSP Rest page you must tell the csp server logic that you want to use sessions. To do this you need to ovverride the parameter "UseSessions" and set this to true. This will persist the session from call to call and will look for and update the session cookie in the http request.So you might do something like:/csp/mynamespace as the URL for the zen app and then have /csp/mynamespace/REST for the rest calls..Both would store the session cookie at /csp/mynamespaceThis should get the same license and user allocated to both applications.
go to post Bill McCormick · Aug 18, 2016 Just in case you are asking about why Cache has .mac files and .int files. These are shorthand for macro and intermediate. Both are routine files but have different roles at compile time.A mac file can contain macro code like $$$InsertCodeHere. When this routine is compiled in to intermediate code the macro has been evaluated and replaced with actual runnable objectscript code likewrite !,"Bill was here"You can only use macros in .mac routines. Classes support macros because they get compiled in to .mac's and then generate INT code
go to post Bill McCormick · Jun 22, 2016 Dmitry is correct - this is simply a feature of Atelier.ClassMethod getPerson(ByRef pParms,Output pObject As %RegisteredObject) As %StatusThis is perfectly legal and works just fine.
go to post Bill McCormick · Jun 17, 2016 We are working to get the latest node into the distributions. Its problematic because it requires newer versions of compilers then we are currently using. Once the compilers are upgraded the new node will ship in the distributions. In the mean time we are making them available separately thru the WRC
go to post Bill McCormick · May 23, 2016 Its not a select so you are going to have trouble firing the event programmatically. What are you trying to accomplish from a functional point of view?
go to post Bill McCormick · May 18, 2016 There are lots of ways to do this:1) Expose as stored procedure and call via the SQL gateway interface...2) Wrap in a web service and return the results that way3) ZN4) Use extended syntax5) Map the class / table / routine
go to post Bill McCormick · May 18, 2016 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.
