X-Git-Url: https://git.creatis.insa-lyon.fr/pubgit/?a=blobdiff_plain;ds=sidebyside;f=Doc%2FWebsite%2FMain.html;h=44819b9cbe73fb430b45351dba894a40d7d146ce;hb=42ec5425b062744aedda5268e17876788d895609;hp=3d0e0a4e4bfc4ea46b78264b9317b7da7aaf18d0;hpb=c1e7f4c3fa2daa65aa9c5e5eb4b111ee3e83e403;p=gdcm.git
diff --git a/Doc/Website/Main.html b/Doc/Website/Main.html
index 3d0e0a4e..44819b9c 100644
--- a/Doc/Website/Main.html
+++ b/Doc/Website/Main.html
@@ -18,7 +18,7 @@ Gdcm is yet another C++ library dedicated to reading/parsing and writing
DiCoM.
-
What gdcm IS
+What gdcm IS
@@ -59,7 +61,7 @@ Gdcm is yet another C++ library dedicated to reading/parsing and writing
-What gdcm is NOT
+What gdcm is NOT
Except for
@@ -67,7 +69,7 @@ Except for
gdcm does NOT implement any other part of the Dicom base standard
(as opposed to other C++ based with open license libraries like
- DCMTK .
+ DCMTK
or
CTN).
@@ -75,7 +77,8 @@ In particular gdcm is not aware of:
- the Dicom network file exchange protocol (Query/Retrieve),
-- the Dicom media storage formats,
+
- the Dicom media storage formats (well ... it knows about the DICOMDIR
+-reading and writing- and its parts PATIENT, STUDY, SERIES, IMAGE)
- Print, Verification
@@ -92,7 +95,29 @@ Among all the features of the
gdcm doesn't implement (yet?)
- the integration of (optional) overlays on image.
-
+
+ - a support to write files according to the
+ various classical Jpeg encodings
+ (only read methods are provided)
+
+ - a support to deal with JPEG 2000 encodings
+
+
+Gdcm also still needs
+
+- an enhanced and simpler API to access the various forms of pixel data
+ (e.g. RGB, GrayLevel, RawData...),
+
+- a decent user's guide (currently, only a partial doxygenation is
+ available),
+
+- the python wrappers to be fixed,
+
+- a simple
+ wxWidgets
+ Dicom file editor.
+
+