X-Git-Url: https://git.creatis.insa-lyon.fr/pubgit/?a=blobdiff_plain;f=Doc%2FWebsite%2FNews.html;h=633b6e6e440dbec262a5490cd678af0b97293a3c;hb=d3f296cee65d3eb391ef46a7c55bf2781f0cabbd;hp=49c6bfd6220f424385a9576d035241cd8a91682f;hpb=9b151f03db62fa25a4f99fe8509eacd445c33ebc;p=gdcm.git
diff --git a/Doc/Website/News.html b/Doc/Website/News.html
index 49c6bfd6..633b6e6e 100644
--- a/Doc/Website/News.html
+++ b/Doc/Website/News.html
@@ -103,28 +103,164 @@ Any contribution is welcome.
- 16-bits-LUT full Management
- User friendly management of Rescale Slope and
- Rescale Intercept
+ Rescale Intercept.
+ (Well... Maybe it's up to the application to deal with it, not to
+ gdcm ?)
- Allow manual adjunction / automatic recognition (pfff!...)
of the private Dicom Dictionary
to be used to parse Shadow groups against.
+
- User friendly way of anonymizing image when Patient's name is
+ carved in the Pixels :-(
+ - Missing Features
- State of the art
-
- gdcm UML Class Diagram current version.
-
+ gdcm UML Class Diagram current version.
+ - User Documentation
+
- Developper
+ Documentation
+
- New Features
+
+ - To try to make gdcm images PACS usable, user is now allowed to
+ gdcm what kind of image he wants to write, using :
+ void FileHelper::SetContentType (ImageContentType c);
+ Four different types are identify (probabely more will be added) :
+
+ -
+ 1) user created ex nihilo his own image and wants to write it as a Dicom image.
+ c : USER_OWN_IMAGE
+ -
+ 2) user modified the pixels of an existing image, using mathematical operations.
+ c : FILTERED_IMAGE
+ -
+ 3) user created a new image, using existing images (eg MIP, MPR, cartography image)
+ c : CREATED_IMAGE
+ wq -
+ 4) user modified/added some tags *without processing* the pixels (anonymization, etc)
+ c : UNMODIFIED_PIXELS_IMAGE
+
+ - Stupid difference between gdcm::ValEntry
+ and gdcm::BinEntry removed.
+ Only gdcm::DataEntry exist, now.
+ Should have been considered as a 'Bug Fix'.
+ Actually, it's an API breaking modification ...
+
+ -
+ std::string const &DataEntry::GetString() const
+ returns as a string (when possible) the value of the DataEntry
+ -
+ void DataEntry::SetString(std::string const &value)
+ Sets the 'value' of a DataEntry, passed as a std::string
+ -
+ void DataEntry::SetBinArea( uint8_t *area, bool self )
+ Sets the value (non string) of the current Dicom DataEntry
+ -
+ void DataEntry::CopyBinArea( uint8_t *area, uint32_t length )
+ Inserts the value (non string) into the current DataEntry
+ -
+ void DataEntry::SetValue(const uint32_t &id, const double
+ &val)
+ Inserts the elementary (non string) value into the current
+ (multivaluated) DataEntry, at the id> position.
+ -
+ double DataEntry::GetValue(const uint32_t &id) const
+ returns, as a double one of the values (when entry is
+ multivaluated), identified by its index id.
+
+ -
+ DocEntrySet::GetEntryValue() replaced by
+ DocEntrySet::GetEntryString()
+ - SerieHelper :
+ Add some methods, to split a 'SingleSerieUID' Fileset into
+ 'Extra Coherent' FileSets.
+ They return a std::map of 'Filesets' (actually : std::vector
+ of gdcm::File*)
+ The key is the 'Orientation', the 'Position'
+ or the value of a user choosen 'Tag'
+ - XCoherentFileSetmap SplitOnOrientation(FileList *fileSet);
+
+ - XCoherentFileSetmap SplitOnPosition(FileList *fileSet);
+
+ - XCoherentFileSetmap SplitOnTagValue(FileList *fileSet,
+ uint16_t group, uint16_t element);
+
+ These methods must be called by user, depending on what he wants
+ to do, at application time.- *he* only knows what his Series
+ contain !-
+ - To avoid memory leaks and seg faults the user intended classes
+ use now a Reference Counter.
+
+ - new() and delete() are replaced by
+ New() and Delete()
+
- Register() and Unregister() methods are
+ available.
+
+ -
- - Missing Features
+
+
- API breaking modifications (since previous version)
+
+ - Stupid difference between gdcm::ValEntry
+ and gdcm::BinEntry removed.
+ Only gdcm::DataEntry exist, now.
+ -
+
-
+
+
+ - Bug fixes
+
+ - Implicit VR - Big Endian (G.E Private) Transfert Syntax 16 Bits
+ images are now read correctly.
+
- File::GetZOrigin() returns accurate result in any case.
+
-
+
-
+
+
+ - Known Bugs
+
+ - Use of Implicit Value Representation writting mode may
+ causes troubles, when there are some SQ belonging to a
+ Shadow Group.
+ Better you use Explicit Value Representation writting mode ...
+ - Troubles on 'Big endian' processors (i.e. Apple/Motorola, SunSparc
+ ...) when writting 16 Bits images.
+
- Troubles on 64-bits processors.
+
-
+
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+ - State of the art
+
+ -
+ gdcm 1.1 UML Class Diagram version.
+
- User Documentation
+
- Developper
+ Documentation
- New Features
- Add the methods
@@ -387,13 +523,7 @@ Any contribution is welcome.
- Known bugs
- - Use of Implicit Value Representation writting mode may
- causes troubles, when there are some SQ belonging to a
- Shadow Group.
- Better you use Explicit Value Representation writting mode ...
- - Troubles on 'Big endian' processors (i.e. Apple/Motorola, SunSparc
- ...) when writting 16 Bits images.
-
- Troubles on 64-bits processors.
+