1. 08 Jan, 2019 1 commit
    • Ben Boeckel's avatar
      vtkModule: add CMake code for the new module system · 1e8c0d1e
      Ben Boeckel authored
      The new module system is target-based rather than variable based. All
      information is passed between targets using target properties and
      leveraging CMake where possible such as for things like include
      directories and linking libraries.
      Where CMake doesn't handle things automatically, we store properties
      ourselves. This includes whether a module needs autoinit logic (and a
      function to handle adding the autoinit logic to a set of targets), which
      headers to wrap in various languages, etc.
  2. 22 Jun, 2018 1 commit
  3. 11 May, 2018 1 commit
  4. 19 Oct, 2017 1 commit
    • Jon Haitz Legarreta Gorroño's avatar
      DOC: Fix buildbot links in develop.md. · 92581891
      Jon Haitz Legarreta Gorroño authored
      The dashboard buildbot links can only be reached from the kitware network.
      When developers from the outside click the link, no buildbot list is
      This patch set uses the links available to people outside the kitware
  5. 17 Oct, 2017 1 commit
  6. 12 Oct, 2017 1 commit
    • David Gobbi's avatar
      Fix tabs and utf-8 quotes in source code · d636213c
      David Gobbi authored
      Some VTK source code still had tabs (even some of the .py files!).
      Also, several comments used utf-8 quotes, which are hard to tell
      from regular quotes by eye and can lead to confusing mistakes.
  7. 22 Sep, 2017 2 commits
  8. 10 Aug, 2017 1 commit
  9. 19 Apr, 2017 1 commit
  10. 19 Aug, 2016 2 commits
  11. 08 Jul, 2016 1 commit
  12. 07 Jul, 2016 2 commits
  13. 31 May, 2016 1 commit
  14. 08 Mar, 2016 1 commit
  15. 03 Feb, 2016 1 commit
  16. 02 Feb, 2016 1 commit
  17. 12 Jan, 2016 1 commit
  18. 29 Sep, 2015 1 commit
  19. 05 Aug, 2015 2 commits
  20. 06 Jul, 2015 1 commit
  21. 12 Jun, 2015 1 commit
  22. 16 Apr, 2015 2 commits
  23. 08 Apr, 2015 1 commit
    • Brad King's avatar
      Documentation: Update required Git version to 1.7.2 · ab5456f4
      Brad King authored
      Our 'git-gitlab-push' script requires Git 1.7.2 or greater to use the
      'git -c <name>=<value> ...' configuration option.  Since 1.7.2 came out
      in 2010 it is reasonable to expect developers to have it in 2015.
  24. 01 Apr, 2015 2 commits
  25. 31 Mar, 2015 1 commit
    • Dan Lipsa's avatar
      Redesign "vtkGhostLevels" arrays and related ghost functionalties. · 4dee0274
      Dan Lipsa authored
      Co-authored-by: default avatarYuanxin Liu <leo.liu@kitware.com>
      Co-authored-by: Berk Geveci's avatarBerk Geveci <berk.geveci@kitware.com>
       -The semantics of each unsigned char in the ghost arrays changes:
        Instead of storing a numeric value representing how far a cell is
        from the boundary, it is now a bit field specified by
        vtkDataSetAttributes::CellGhostTypes and
        vtkDataSetAttributes::PointGhostTypes.  The bit field is consistent
        with VisIt specs.
      - Previously, filters strip all ghost cells they request from upstream
        before finalizing the output. This is no longer done.
      - vtkUniform grids previously supported blanking through member arrays
        vtkUniformGrid::CellVisibility and
        vtkUniformGrid::PointVisibility. These arrays are removed and the
        blanking functionality are supported through the new ghost arrays
      - the "vtkGhostLevel" arrays for cell and point data are renamed to
        vtkDataSetAttributes::GhostArrayName() ("vtkGhostType").
      - the version for VTK Legacy files is increased to 4.0 and the version for
        VTK XML files is increased to 2.0. When reading older files we
        convert vtkGhostLevels array to vtkGhostType.
  26. 19 Mar, 2015 1 commit
  27. 18 Mar, 2015 1 commit
  28. 17 Mar, 2015 3 commits
    • Ben Boeckel's avatar
      docs: add buildbot information · 4265bc0e
      Ben Boeckel authored
    • Brad King's avatar
      Documentation: Add links to GitLab markdown documentation · 0bd3fbdb
      Brad King authored
      The "Review a Merge Request" section primarily depends on comments made
      in GitLab.  Link from this section to the GitLab markdown documentation.
      In particular, the special reference syntax options will be very
    • Brad King's avatar
      Documentation: Revise Merge Request creation instructions · 2f89fb53
      Brad King authored
      Move use of the "Submit merge request" button to the last step.  Add a
      step for the "Title" field before the "Description" field.  In the
      "Description" field, split various hints into bullet points to make them
      more distinct.  Provide a complete example of a description.  Explicitly
      state that the other fields may be left blank.
      Also mention in the "Review a Merge Request" section that "@" syntax
      presents completion.  It is better to use completion there than in the
      Description field because it will complete developers with access to
      the target repository instead of just the source repository.
      Inspired-by: Ben Boeckel's avatarBen Boeckel <ben.boeckel@kitware.com>
  29. 16 Mar, 2015 1 commit