Hi guys!

Suppose you developed a tool, framework, library on InterSystems ObjectScript for InterSystems Data Platform, share it via Open Exchange and want people to install it.

What is the best strategy if it is a library and supposed to be called from different namespaces?

Here are the following thoughts:

1. Tool's developer should be able to use globals to read/store data the tool needs.

2. Tool's consumer should be confident, that the thing he/she installs will not harm the application's data.

3. A tool should be callable from any application's namespace.

4. Tool's installation(in general) should not request manual security changes (e.g. grant the write access to IRISLIB) and %YourClass is not an option.

5. It's easy to uninstall the tool - just delete the namespace/database (maybe delete some web-apps too).

0 10
0 416

Hi Community!

Here is the digest of what has happened on Open Exchange in November and December 2018!

Application Releases

We had 5 releases in November and December:

Cache ODBC for Node.js

This library aims to provide simple access to ODBC data sources for node.js.

Laracache

Laravel package providing InterSystems Cache as a data source using ODBC

DeepSeeButtons

Tool for analyzing your DeepSee Environment

DSW Reports

Addon for DeepSee Web which provides online reports and PDF emailing reports using InterSystems DeepSee dashboards

AnalyseThis

Utility to easily transform a CSV file into a personalized preview of DeepSee

0 0
0 195