Skip to content
Snippets Groups Projects
  1. Dec 04, 2020
    • Matthias's avatar
      applied requested changes · afcfebb5
      Matthias authored
      rm obsolete code; correct declare->define; rm 1-liner-braces; rm unnecessary else statements; precision hardcoded; static methods
      afcfebb5
  2. Dec 02, 2020
    • Matthias's avatar
      clang-format; Linux compilation · d50cde11
      Matthias authored
      d50cde11
    • Matthias's avatar
      Revert "clang-format; Linux compilation" · 0851a351
      Matthias authored
      This reverts commit edba7bcb82046fdb0b6b3622d8ef0b5e4b9fcf5b.
      0851a351
    • Matthias's avatar
      clang-format; Linux compilation · bd9844aa
      Matthias authored
      bd9844aa
    • Matthias's avatar
      clang-format; Linux compilation · bc4f5bee
      Matthias authored
      bc4f5bee
    • Matthias's avatar
      rm strategy related files; small correction · ea5b2f6a
      Matthias authored
      ea5b2f6a
    • Matthias's avatar
      Added Read&Write-classes for output data formats; redirected the relevant calls to these classes. · b04481b6
      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
      b04481b6
  3. Nov 28, 2020
  4. Nov 26, 2020
  5. Nov 25, 2020
  6. Nov 24, 2020
  7. Nov 20, 2020
  8. Nov 19, 2020
  9. Nov 18, 2020
  10. Nov 17, 2020
  11. Nov 12, 2020
Loading