Here's the scenario. I write a post, click the Publish button to post it, but overlook the fact that because I didn't add a tag I'm still on the same page. The pink area highlighting what I forgot to fill in is out of sight at the bottom of the page. I carelessly navigate away (e.g. back button, or DC app tabs). There's no warning, and I've lost what I wrote.
Apparently if I pose a question (like this one) and subsequently discover an answer, I can't add that as an answer. I'd have to resort to a comment on the original posting, or editing the original posting.
After the March 15th DC update I posted one Question (as opposed to Article). I've been used to getting notified by email no more than an hour after someone responds to a post of mine. In the case of my question, I think I only got that email when someone posted a Comment on the question. When I went to read that comment I saw that there were several Answers that had been posted many hours earlier.
Prompted by the words Rick didn't actually say to his pianist in Casablanca, I want to draw attention to the the "Resend" button at the top of the Ensemble Message Viewer.
It's pretty easy to use. Find the message or messages you want to resend, set the associated selection checkbox(es), then click the button.
Among the outputs of our Yuzinji tool are two code metrics that it can be interesting to track over time as a development project proceeds. These are Size and XS. The first is fairly straightforward. As you write more code the size of your codebase increases. The XS metric (pronounced "excess") aims to quantify excessive structural complexity.
Since the March 15 update, Related Topic is now a mandatory field. My first post since the update was to this Developer Community Feedback group, and I found it hard to choose an appropriate Related Topic. I ended up picking "Online Learning" for that post, and will use the same for this one too.
One aspect of source code management is how to deal with the almost inevitable need to upgrade your Caché or Ensemble platform to a newer InterSystems release.
It's long been my experience that InterSystems does a very good job of maintaining backward compatibility. Code that works correctly on, say, 2012.1 is very likely to work correctly on, say, 2015.2 without any modification.
In response to a comment on his posting about source control hooks and Atelier Bill McCormick used the example of Studio's SOAP Wizard and talked about providing more information about how Atelier will support this kind of extension.
My Atelier (1.0.116) has a Tools menu with an Add-Ins option and a "Soap Wizard" (sic) submenu.
Is there any information available to us yet about how we can add our own add-ins of this kind?
When you create an Ensemble production your namespace acquires a new class definition. For example here is what the class that defines the Demo.Loan.BankUSProduction production in the ENSDEMO namespace looks like when opened in Studio:
If I have defined a class query in one of my classes and I want to use that query from a method of another class, what are the pros and cons of using the %SQL.Statement interface versus the %Library.ResultSet interface?
In this posting I want to raise the profile of a feature that arrived in 2009.1 but is perhaps not very well known.
It is sometimes useful to make certain packages, globals or routines available to all of your namespaces. Of course you can add the necessary mappings whenever you create a new namespace, but here's a simpler way.
All posts