Open Exchange

Syndicate content 3 

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).

Last answer 5 days ago Last comment 1 days ago
0 3
107

views

0

rating

Hi Everyone!

We have a good tidings for you! Recently, we launched a new block on Developer Community Site called "APP OF THE WEEK" (you can see it through all website pages on the right).

And now you have a great opportunity to promote your project!

Redeem a new reward that available for Global Master advocates only: "Open Exchange project promotion on Developer Community"

What benefits will it give you? See the details below.

0 1
0

comments

35

views

0

rating

WebSockets as a communication technology wins increasing importance.
In the SAMPLES namespace, you find a nice example for running a WebSocket Server.
There is also a useful example for a Browser Client. JavaScript does most of the work. 

My point is:
How to consume the output of a WebSocket Server in your application?

0 0
0

comments

46

views

+ 7

rating

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 1
0

comments

50

views

0

rating

Did you know that Caché (and now InterSystems IRIS) has available parser for ObjectScript ?

Well, technically, lexer. It hides under the name of %SyntaxColor class. This class provides API to the DLL used by Studio to do syntax highlighting. As a result if works only under Windows.

Last comment 3 December 2018
1 4
349

views

+ 3

rating

The data model of your solution based on InterSystems platforms constantly changes over time. But what do you do with the data that was entered before? Back then, the data was valid, but what’s happening to it now after a number of data model changes? The answer to this question can be provided by the IDP DV tool that checks the property data of persistent and serial classes according to the types of these properties. In case any discrepancies are found, the tool generates a detailed error report for the user.

Last comment 16 November 2018
0 2
192

views

+ 3

rating

Hi Community!

As you know we launched the InterSystems Open Exchange — the marketplace for solutions and tools on InterSystems Data Platforms!

But how to publish your application on OE?

Before we start, let me answer the few basic questions.

Last comment 24 October 2018
2 3
204

views

+ 4

rating