Hi, Alessandro!
Thanks for the great post!
I wonder if Cube Relationships can address the same problem? e.g. if we have in this case two cubes: Patients and Doctors based on DeepSee.Study.Patient and DeepSee.Study.Doctor respectfully would basic synchronization of the cubes solve all the update issues?
You are right. But I believe there are cases.
I don't know why Eduard needs it but e.g. if you consider implementing licensing on your ObjectScript solution with controlling logic in ObjectScript I believe you don't want the method of license checking to be overloaded. Final method in deployed mode could be a solution in this case.
If you can provide me access to an IRIS system on GCP Cloud, then sure.
You can provide the access to IRIS on GCP by yourself - it's open for everyone, as listed in the announcement.
What functionality would you like to see, and what would the target audience be?
This is simple. I wonder, what are the benefits of QEWD for developers on IRIS.
Note: I'm not around to do anything until early September
No rush here.
Hi, Ernesto! This is great!
You can make a Pull Request to the repo - so everyone can review/comment the changes too
Speaking about IRIS export - yes, it exports with <Export generator="IRIS"> which makes it complicated to import into Caché and Ensemble without manually changing the file.
I'd suggest @Kurro Lopez to export releases for IRIS and Caché/Ensemble separately for now and invite @Stefan Wittmann and @Benjamin De Boe to share guidelines what is the best way to develop on IRIS and make it available for Caché/Ensemble too.
Is there a way to prevent successful %Save() for the ClassDefinition?
Interesting. Didn't know about the option.
How could one remove Final keyword without changing the source code?
So you want to prevent users from changing the source code of the class.
Deploy it without a source code?
On my table:
Thank you, MIke!
Hi, Rob!
Does QEWD work with InterSystems IRIS?
And you can save extra $250 on your registration for Global Summit with Global Masters rewards. Learn more!
Web Terminal 4.8 released! Now supports InterSystems IRIS! See the details.
Hi, Jacquie!
Who are the speakers at InterSystems AI Symposium?
Great news, Jacquelyn, thank you!
You say it would be on a special AI event. So Babak will take a session on GS keynote on 30th of September or on an AI symposium on 3rd of October?
And... What about other languages?
Portuguese, Japan, German?
Who'll raise the flag? Anyone? )
Thanks, Francisco!
And the repo is also mirrored to Community Github
This is cool!
Thank you @Gevorg Arutunyan and @Kurro Lopez !
Hi, guys!
There is a community project of DSW reports - which provides a way to prepare and send DeepSee Web reports in PDF by schedule.
So, we introduced this feature to DC online analytics to have a weekly report in PDF - like this one.
If you want to receive this report on Mondays too please put your comment here, we'll put you on the list.
And you are very welcome to introduce your issues how we can improve it, or provide your pull requests.
Hi, Karthik!
Check DeepSee Web solution - it is Angular visualisation module for DeepSee Dashboards and you are able to introduce your own visualisation for any DeepSee widgets.
Hi, Scott!
It's obvious, but what about this?
^OSUWMCInstance = "TestClin"
^OSUMCLDAP("LDAPKey") = "/ensemble/"_^OSUWMCInstance_"/mgr/LDAPKeyStore/"
Actually I'm impressed how quickly you guys introduce in QEWD new trendy approaches for development. Though there is a difference here: what @Gevorg Arutunyan published supports Caché Objects and I doubt if QEWD does. Is there any Caché Objects support/mapping in QEWD?
And, any stats, Rob? Is it the most popular API in EWD and EWD3? And why it is not supported in QEWD?
If you like Visual Studio Code you can consider to try VSCode-ObjectScript extension. Github repo.
If you don’t use Studio, you can consider to try isc-dev tool, which is intended to simplify routine processes of import/export code, releases and patches.
Import it to e.g. USER and map to %All.
After that you’ll be able to import, export, release and patch in any namespace.
To work in a given namespace point the tool to a directory on the disk which contains repository in UDL or XML classes (preferablly UDL) with the following command:
d ##class(dev.code).workdir(“/work/github/myproject/src”)
Use following to import the code:
d ##class(dev.code).import()
To setup the mask introduce isc.json file into .../src folder with following content:
{“compileList”:”A*.INC,B*.CLS,C*.CLS,D*.DFI,E*.GBL”
”projectName”:”myproject”
”git”:0}
Call Init class to let dev.code use settings in the given namespace:
d ##class(dev.code).init()
After that you’ll be able to export all the project in one file with the release command:
d ##class(dev.code).release()
it will export all into one /mgr/database/myproject_release_ddmmyyy.xml file.
Once you commit your changes to git repo you’ll be able to have a patch release. Call
d ##class(dev.code).patch()
to get all the changed code into one patch release in /mgr/database/myproject_patch_ddmmyyyy.xml file.
To export all source code (including DeepSee staff) in UDL and organized in folders call:
d ##class(dev.code).export()
And call compile method to compile everything in your project, but not the whole namespace:
d ##class(dev.code).compile()
One of the projects which is maintained with this util is dsw-map: classes, globals, DFIs, releases.
Hi, Fabian!
Could you share please the call to export the compiled classes without source code?
