- May 10, 2023
-
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
- May 05, 2023
-
-
Wuttke, Joachim authored
-
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
- Apr 07, 2023
-
-
Wuttke, Joachim authored
-
- Apr 06, 2023
-
-
Wuttke, Joachim authored
-
- Feb 16, 2023
-
-
Mikhail Svechnikov authored
-
- Aug 18, 2022
-
-
Mikhail Svechnikov authored
-
- Jun 02, 2022
-
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
- May 30, 2022
-
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
- May 19, 2022
-
-
Wuttke, Joachim authored
-
- May 16, 2022
-
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
- Nov 11, 2021
-
-
Wuttke, Joachim authored
-
- Nov 09, 2021
-
-
Wuttke, Joachim authored
-
- Jun 28, 2021
-
-
- Mar 15, 2021
-
-
Matthias Puchner authored
-
- Feb 15, 2021
-
-
Matthias authored
-
- Dec 17, 2020
-
-
Wuttke, Joachim authored
-
Wuttke, Joachim authored
-
- Dec 10, 2020
-
-
Wuttke, Joachim authored
-
- Dec 02, 2020
-
-
Matthias authored
About the reader/writer classes: Each class contains methods for reading and writing (if applicable) of one format (INT, NumpyTXT, Reflecometry, Tiff). The code for reading and writing is copied from the OutputDataReadStrategy-implementations and from the OutputDataWriteStrategy-implementations. For TIFF, the code was already in a separate class (TiffHandler). This has been renamed and reworked a bit (only interface-wise, no implementation changes). Methods from the Tiff strategy have been integrated as well. The classes have no common polymorphy (no common base class/interface) since it is not necessary in the given implementation. This reduces code & dependencies and eliminates tricks or dummies for non-existing implementations like Reflecometry::write. Also in the one and only class which uses the readers/writers(IntensityDataIOFactory), polymorphy would not help since there is only one if-else, which would be necessary also in a polymorhic approach. However, the Reader/Writer classes are designed quite alike, so in case the future brings needs for polymorphy, this can be easily added. IntensityDataIOFactory: Code from OutputReader and OutputWriter has been integrated into IntensityDataIOFactory
-