update my tasks

[gdcm.git] / Doc / Website / Main.html

diff --git a/Doc/Website/Main.html b/Doc/Website/Main.html
index 457d9d9122aaa07a1f45eb8e90f19d63777fd343..cdb7fb589f442145df45b772d40ac95b99442271 100644 (file)
--- a/Doc/Website/Main.html
+++ b/Doc/Website/Main.html
@@ -28,7 +28,10 @@ Gdcm is yet another C++ library dedicated to reading/parsing and writing
    <UL>
    <LI>ACR-NEMA version 1 and 2
    </LI>
-   <LI>Dicom version 3 (including various encoding like jpeg or RLE).
+   <LI>Dicom version 3.0 (including various encodings of jpeg, RLE).
+       Please refer to
+       <A HREF="ConformanceSummary.html">gdcm conformance summary</A>
+       for more details.
    </LI>
    </UL>
 </LI>
@@ -70,10 +73,12 @@ or
 <BR>
 In particular <B>gdcm is not aware</B> of:
 <UL>
-<LI>the Dicom network file exchange protocol,
+<LI>the Dicom network file exchange protocol (Query/Retrieve),
 </LI>
 <LI>the Dicom media storage formats,
 </LI>
+<LI>Print, Verification
+</LI>
 <LI>ANY OTHER PART of Dicom.
 </LI>
 </UL>
@@ -88,6 +93,25 @@ gdcm doesn't implement (yet?)
 <UL>
   <LI>the integration of (optional) overlays on image.
   </LI>
+  <LI>a more complete supports of the 
+     <A HREF="ConformanceSummary.html">various Jpeg encodings</A>
+  </LI>
+</UL>
+Gdcm also still needs
+<UL>
+<LI> an enhanced and simpler API to access the various forms of pixel data
+     (e.g. RGB, GrayLevel, RawData...),
+</LI>
+<LI> a decent user's guide (currently, only a partial doxygenation is
+     available),
+</LI>
+<LI> the python wrappers to be fixed,
+</LI>
+<LI> a simple
+     <A HREF="http://www.wxwindows.org/">wxWidgets</A>
+     Dicom file editor.
+</LI>
+</UL>
 </UL>
 
 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>