go to post John Murray · Oct 7, 2016 You wrote:from Cache Studio, when I examine the output of the class given above, I get the error message:...Please tell us exactly how you are using the class from within Studio.
go to post John Murray · Oct 4, 2016 By adding that repo I was able to upgrade to 1.0.255.I guess that my original Atelier kit was built on Eclipse Mars, and that the developers recently moved up to Eclipse Neon but the upgrade mechanism didn't cope with this. Okay for a pre-release version of Atelier, but let's hope a similar thing doesn't happen once it's become a released and widely deployed tool.
go to post John Murray · Oct 3, 2016 This is with a standalone install of Atelier.I also have an Eclipse Mars.2 instance (Eclipse 4.5.2) that I had previously added Atelier 1.0.165 to. This one was able to upgrade Atelier to 1.0.255 successfully via "Check for updates".
go to post John Murray · Sep 9, 2016 set %session.EndSession=1See the class documentation for the %CSP.Session class, of which %session is an instance.
go to post John Murray · Aug 30, 2016 Any progress on this yet? My 1.0.90 Atelier's "Check for Updates" still tells me it finds none. I've already updated my 2016.2 FT instance to the latest you've published (build 721), so I expect my Atelier won't play well with that until it gets updated too.
go to post John Murray · Aug 26, 2016 As I read your code, you're not doing any locking. So isn't it theoretically possible that two workers could grab data from the same node of the work global at exactly the same instant?
go to post John Murray · Aug 26, 2016 Zipfile now contains keys valid until the end of this year, but the text on the page at https://wrc.intersystems.com/wrc/BetaPortal20162.csp#keys still reports them as expiring at the end of August:
go to post John Murray · Aug 25, 2016 I'm subscribed to the article: Are there different levels of subscription? Specifically, you asked if I am "subscribed to changes in content".
go to post John Murray · Aug 25, 2016 The "could not attach to target" message makes me wonder if you're having problems using Studio to debug CSP pages. In that case you might be interested in trying the Serenji debugger from George James Software as an alternative. It offers a different way of debugging CSP pages.John MurrayGeorge James Software
go to post John Murray · Jul 28, 2016 That's what I suspect. And if correct then it's about time the UI and documentation caught up.
go to post John Murray · Jul 25, 2016 As an addendum I'd like to point out that since Wine is available for OS X you can now also run Serenji on OS X. See https://wiki.winehq.org/MacOSX for how to get Wine going on this platform.I have edited the original post to reflect this.John
go to post John Murray · Jul 21, 2016 If you want a complete, closely integrated source control solution that's simple to add to your Caché / Ensemble environment, please take a look at our product Deltanji. This is ready for the approaching "new world" of Atelier, but equally happy working with older versions right back to 2009.1.John MurraySenior Product EngineerGeorge James Software
go to post John Murray · Jul 14, 2016 Not answering your questions, but are you aware of the SetFlags and SetQualifiers methods of %SYSTEM.OBJ ? These can be used to set namespace-specific defaults as well as systemwide defaults. Maybe they'll let you ensure "u" behaviour for certain namespaces even if you remove the "u" flag from Studio's settings.
go to post John Murray · Jul 13, 2016 By "not available" Eduard means that InterSystems doesn't publish the source code (i.e. the INT or MAC). Only the OBJ is available, which is what executes when the code you are looking at runs.
go to post John Murray · Jun 30, 2016 I don't need it, but my experience is that InterSystems consistently maintains a very high standard of technical and professional competence among its staff, so knowing that the author of a post or a response is a member of ISC staff may be useful to readers.Additionally, an ISC person may find it helpful in the event that someone whose name they do not recognize as being a colleague posts something that might benefit from follow-up through internal channels.Think of it as equivalent to the way in which Global Summit badges usually give a discreet indication that the wearer is a company employee.
go to post John Murray · Jun 29, 2016 Joel, I suggest you also add the Atelier tag to this posting. At the moment it's only tagged "Git" and I only found it by accident.
go to post John Murray · Jun 23, 2016 Glad to hear that System Defaults are working for them. My main gripe with that mechanism is how cumbersome Portal's UI is for making the setting in the right place. Added to that, it's just too easy for someone to adjust a setting directly, filing the new setting into the production class where it (a) overrides the System Default and (b) propagates when the class gets transferred.
go to post John Murray · Jun 22, 2016 Out of interest, are all other settings of the production's configuration items identical between DEV and PROD? Or are you using System Defaults successfully to ensure that, say, hostname/port of outbound target system is different in DEV versus in PROD?Many Ensemble sites that use our Deltanji source control tool to propagate code from DEV to PROD choose to exclude the production class itself from that workflow. Some maintain multiple variants of the class, e.g. one for DEV and another for PROD, versioning each variant only within its own environment, and using a diff tool such as Beyond Compare (which Deltanji integrates with) to propagate applicable production changes from DEV to PROD.
