viewer

any one can help in :

  1. how to implement weasis to run same as osimis button in the explorer
    and to view the study.

  2. how to install and run stone web viewer as in the link of instruction it is not clear.

regards
hassan

Yeah good question about stone web viewer, I guess it should have a way to compile it as a static asserts to be served by an http server.

However I think we have to wait a bit, Sebstien just release it, it is a project they was working on it for years, documentation should come, they are always documenting very well their applications, so i’m sure it will come.

Salim

Hello,

  1. There is no integration of Weasis into the Orthanc Explorer yet. I can’t tell whether this is possible. If you want to use Weasis with Orthanc, you’ll have to configure query/retrieve from Weasis to Orthanc, as with any DICOM modality:
    https://book.orthanc-server.com/dicom-guide.html#dicom-move

  2. I think that everything is explained in the Orthanc Book:
    https://book.orthanc-server.com/plugins/stone-webviewer.html

If something is not clear, please tell us what can be improved.

Regarding Salim’s remark, the static assets of the Stone Web viewer are already served by a plugin (“StoneWebViewer.so” or “StoneWebViewer.dll” depending on the platform). This plugin has almost no intelligence, except to serve the static assets, to serve the configuration for the viewer (as extracted from the section “StoneWebViewer” in main configuration of Orthanc), and to install the yellow button “Stone Web Viewer” in the Orthanc Explorer.

HTH,
Sébastien-

Dear Sebastien,

Where can I find / Generate the static assets if I want to serve it using my OrthancToolsJS Backend ?

Does they are generated at the compilation process along dll/so files ?

Best regards,

Salim

Hi Salim,

They can be found here (“wasm-binaries.zip”):
https://lsb.orthanc-server.com/stone-webviewer/1.0/

Sébastien-

Dear Sebastien,

It works very well, it took me 10 minutes to integrate it in OrthancToolsJS, I now selfhost your compiled version in my backend and the dicomweb endpoint is under a reverse proxy. (unfortunaltly it will take us some time to release the new version of OrthancToolsJS as we are in the middle of internal redisgn of OrthancToolsJS).

Two small questions :

1 - Does that link path will be stable (except the version number) so I can include it in a CI builing pipeline ?
2- The viewer is great but are missing small tools to be functional, especially the line / angle measurement, and the ROI tools (the tools of Osimis webviewer) did you plan to integrate it someday in this distrubution ?

Thanks again, amazing work.
The next version of OrthancToolsJs will integrate both OHIF and Stone Of Orthanc.

Best regards,

Salim

Dear Salim,

This is excellent news, we’re looking forward to the new version of OrthancToolsJS!

Regarding your questions:

1- Yes, the path should be stable (except the version number).

2- Yes, we would love to re-implement the annotations/measurements features of the deprecated Osimis Web viewer. As explained in the FAQ, we’re looking for industrial sponsors to this end:
https://book.orthanc-server.com/plugins/stone-webviewer.html#faq

Regards,
Sébastien-

Thank you for the new stone viewer,

Can you pleases separate all the network calls of dicom web or orthanc REST api outside the webassembly complied file to regular JS files to ease the use of the viewer in full static servers or applications, like serving the dicom files without backend pacs or even from dicomdir zip archive with out the need to modify the webassembly & recompile it.

Thanks.

We certainly won’t modify the Stone Web viewer to adapt it to your personal taste.

Source code is available under the AGPL license, feel free to modify it under the terms of this license:

https://hg.orthanc-server.com/orthanc-stone/file/tip/Applications/StoneWebViewer

https://book.orthanc-server.com/faq/licensing.html

Or get in touch with our commercial partner Osimis if you need custom developments:
https://book.orthanc-server.com/contributing.html