Mercurial > hg > orthanc-stone

comparison README @ 9:4cf45e539cd9

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
notes
author Sebastien Jodogne <s.jodogne@gmail.com>
date Wed, 19 Oct 2016 09:03:30 +0200
parents 00ff2cd06d13
children ed07f4bbf1a8
comparison
equal deleted inserted replaced
8:fcff71deac7b 9:4cf45e539cd9
14 14
15 Stone of Orthanc comes bundled with its own software-based rendering 15 Stone of Orthanc comes bundled with its own software-based rendering
16 engine (based upon pixman). This engine will use CPU hardware 16 engine (based upon pixman). This engine will use CPU hardware
17 acceleration if available (notably SSE2, SSSE3, and NEON instruction 17 acceleration if available (notably SSE2, SSSE3, and NEON instruction
18 sets), but not the GPU. This makes Stone a highly versatile framework 18 sets), but not the GPU. This makes Stone a highly versatile framework
19 that can run even on low-performance platforms. Stone is able to 19 that can run even on low-performance platforms. Note that Stone is
20 display DICOM series without having to entirely store them in the RAM. 20 able to display DICOM series without having to entirely store them in
21 the RAM (i.e. frame by frame).
21 22
22 Stone of Orthanc is conceived as a companion toolbox to the Orthanc 23 Thanks to its standalone rendering engine, Stone of Orthanc is also
23 VNA (vendor neutral archive, i.e. DICOM server). As a consequence, 24 compatible with any GUI framework (such as Qt, wxWidgets, MFC...). The
24 Stone will smoothly interface with Orthanc out of the 25 provided sample applications use the SDL framework.
25 box. Interestingly, Stone does not contain any DICOM toolkit: It 26
26 entirely relies on the REST API of Orthanc to parse/decode DICOM 27 Stone is conceived as a companion toolbox to the Orthanc VNA (vendor
27 images. However, thanks to the object-oriented architecture of Stone, 28 neutral archive, i.e. DICOM server). As a consequence, Stone will
28 it is possible to avoid this dependency upon Orthanc, e.g. to download 29 smoothly interface with Orthanc out of the box. Interestingly, Stone
29 DICOM datasets using DICOMweb. 30 does not contain any DICOM toolkit: It entirely relies on the REST API
31 of Orthanc to parse/decode DICOM images. However, thanks to the
32 object-oriented architecture of Stone, it is possible to avoid this
33 dependency upon Orthanc, e.g. to download DICOM datasets using
34 DICOMweb.
30 35
31 36
32 Comparison 37 Comparison
33 ---------- 38 ----------
34 39