40 lines
1.1 KiB
JavaScript
40 lines
1.1 KiB
JavaScript
/**
|
|
* Import namespace...
|
|
*/
|
|
|
|
import { OHIF, Metadata } from './namespace.js';
|
|
|
|
/**
|
|
* Import scripts that will populate the Metadata namespace as a side effect only import. This is effectively the public API...
|
|
*/
|
|
|
|
import './client/'; // which is actually: import './client/index.js';
|
|
|
|
/**
|
|
* Export relevant objects...
|
|
*
|
|
* With the following export it becomes possible to import "OHIF" from "ohif:core" and "Metadata"
|
|
* from "ohif:metadata" using a single import (a shorthand), like this:
|
|
*
|
|
* import { OHIF } from 'meteor/ohif:metadata';
|
|
*
|
|
* Which is equivalent to:
|
|
*
|
|
* import { OHIF } from 'meteor/ohif:core';
|
|
* import 'meteor/ohif:metadata';
|
|
*
|
|
* The second (extended) format should be used when other OHIF packages are also to be used within
|
|
* the current module. This makes it explicit that the following imports will populate their
|
|
* respective namespaces within the to "OHIF" namespace. Example:
|
|
*
|
|
* import { OHIF } from 'meteor/ohif:core';
|
|
* import 'meteor/ohif:metadata';
|
|
* import 'meteor/ohif:hanging-protocols';
|
|
* [ ... ]
|
|
* OHIF.metadata.setActiveViewport(...);
|
|
* OHIF.hangingprotocols.doSomething(...);
|
|
*
|
|
*/
|
|
|
|
export { OHIF, Metadata };
|