This blog doesn't seem to be up yet. Maybe I just need to be more patient...
- Log in to post comments
This blog doesn't seem to be up yet. Maybe I just need to be more patient...
Link gives me an empty page at the moment:
+1 from me for this request.
The difference Tim gave in his first bullet is presumably down to the way that the projection methods get called after the class being projected has been compiled, whereas if you're using generator methods they're executing in the midst of the compilation.
I don't see that explaining the ones I'm getting shown under "My collaborations". This one for example:
https://community.intersystems.com/post/what-determines-value-defaultla…
Interesting. Are you able to tell us more about what you're doing with SonarQube?
Indeed. Presumably the "load and delete" defaults were a design decision based on the model of running unit tests elsewhere. That seems relevant for a build server, but not so friendly for the developer who you're trying to persuade to code the tests in the first place. Yes, Studio the source control hook facility can be your friend here provided you're prepared to spend enough time getting intimate with it.
Re your Atelier issue, does the "Configure server" link lead you to somewhere you can test the connection? Make sure that your Atelier connection is pointing to the port that your Cache Portal also goes to, and not to the port that your Cache Studio uses. That was an early gotcha for me in Atelier.
The Cache username that you connect with might not have enough privileges. One way to determine if this is you problem is to grant the user the %All role temporarily.
I empathize with the ISC developers who are dealing with this aspect of Atelier. I know from personal experience maintaining our tools that COS parsing can be a challenge. And just when you think you've got it cracked, something new gets added to the language, e.g. system class methods, JSON notation.
We at George James Software are paying close attention to this whole area. For a long time our source code management product Deltanji (formerly called VC/m) has integrated closely with Studio by using templates and add-ins as well as the source control class interface.
Atelier shifts the paradigm for source code management. We live in interesting times.
A few more caveats:
If you're planning to develop on a later version than you deploy onto, beware the occasional gotcha. For example http://docs.intersystems.com/ens20151/csp/docbook/DocBook.UI.Page.cls?KEY=EGRN_compatibility#EGRN_compatibility_hl7schemas identifies an issue with trying to import a 2014.1+ schema into a pre-2014.1 environment. I have seen at least one Ensemble site mangle their production by exporting a schema from 2014.1 or later and then importing it into an earlier version.
What a great way of encouraging participation here.
Has any information about system methods reached the documentation yet? On my 2016.2 FT (build 585) Documatic shows the methods of %Library.Object in a new section headed "SystemMethods" and summarized in a table titled "System Methods". The methods start with keywords systemmethod and systemclassmethod but a DocBook search on either of those terms doesn't get me any extra information.
Also, in Stefan's article the section about system methods says that the "live in a separate namespace" (my emphasis). I don't think he means namespace in the sense of %SYS, SAMPLES, USER etc, but rather that your own method called "new" can coexist with the systemmethod called "new".
OK, I'm seeing the change now.
Maybe worth adding a mention of 2016.2 to the page at http://www.intersystems.com/services-support/product-support/prerelease-trial-program/ so that folk who monitor that page for changes will hear about it.
What's the right support channel to use for the cloud-based Atelier FT server? I log in at https://wrc.intersystems.com/wrc/BetaPortalCloud.csp and click the "Launch Server" button. The button disappears immediately and is replaced by text saying "Your Atelier Server has been launched,
it will run for the next (expired)." and when I click on the xxx-.isc.appsembler.com/csp/sys/UtilHome.csp URL I am offered I get a page reading "
"