2.12.2021, 9:00 - 11:00: Due to updates GitLab may be unavailable for some minutes between 09:00 and 11:00.

  1. 23 Mar, 2015 1 commit
  2. 06 Feb, 2015 1 commit
  3. 17 Dec, 2014 1 commit
    • Christian Schulte zu Berge's avatar
      Further work on workflow support: · 9b2ad449
      Christian Schulte zu Berge authored
      * Workflow stages now store the visibility of pipeline canvases
      * Extended PipelineFactory to also hold creator functions to create workflows
      * CampVisApplication now creates and initializes workflows when launched with "-w WorkflowName" parameter
      
      refs #13
      9b2ad449
  4. 16 Dec, 2014 1 commit
  5. 15 Dec, 2014 1 commit
  6. 11 Dec, 2014 1 commit
    • Christian Schulte zu Berge's avatar
      Some UI tweaks: · e5e3428c
      Christian Schulte zu Berge authored
      * Improved appearance of PipelineTreeWidget
      * Fixed IntPropertyWidget and FloatPropertyWidget recursively setting the widgets value, when the change event comes from the widget itself
      e5e3428c
  7. 10 Dec, 2014 1 commit
  8. 29 Nov, 2014 1 commit
  9. 24 Nov, 2014 1 commit
  10. 04 Nov, 2014 1 commit
  11. 29 Oct, 2014 2 commits
  12. 28 Oct, 2014 1 commit
  13. 23 Oct, 2014 2 commits
  14. 30 Sep, 2014 1 commit
  15. 27 Jul, 2014 2 commits
  16. 10 Jul, 2014 1 commit
  17. 02 Jun, 2014 1 commit
    • Christian Schulte zu Berge's avatar
      Further work on Lua scripting console: · f1b3cd9a
      Christian Schulte zu Berge authored
      * Implemented one single gloabel Lua VM for the entire CampVisApplication instead of one VM for each pipeline.
      * The global Lua VM has a "pipelines" table/array, holding the pointers to each loaded pipeline
      * ScriptingWidget support cycling through last executed commands via the arrow keys
      * LuaVmState supports redirecting Lua's print() function to a custom one that uses tgt::Logmanager for printing (just as proof-of-concept). This shall later be extended to pass all Lua output to the scripting console.
      f1b3cd9a
  18. 31 May, 2014 1 commit
    • Christian Schulte zu Berge's avatar
      Started implementation of a Lua console in campvis-application. · a33ee468
      Christian Schulte zu Berge authored
      With scripting enabled, the main window now has an additional scripting widget that allows to interact with a Lua VM. The current proof-of-concept implementation creates a Lua VM for every instantiated CAMPVis pipeline while the console just interacts with the first pipeline's one.
      However, the Lua VM concept has to be reiterated later anyway. It may make more sense to have just a single central Lua VM for the entire application, which is shared by each pipeline.
      a33ee468
  19. 05 May, 2014 1 commit
  20. 15 Jan, 2014 1 commit
  21. 13 Dec, 2013 1 commit
  22. 10 Nov, 2013 1 commit
    • Artur Grunau's avatar
      Dock DataContainerInspectorWidget in the MDI area · 95b2248a
      Artur Grunau authored
      DataContainerInspectorWidget was previously stored in a regular dock
      widget, but because of its rather large dimensions it didn't fit well in
      any of the docking areas.
      
      Put DataContainerInspectorWidget in an MdiDockableWindow and add it to
      the MDI area. It fits much better there, and can still be undocked if
      need be.
      95b2248a
  23. 02 Nov, 2013 3 commits
    • Artur Grunau's avatar
      MdiDockableWindow: new MDI helper class · 6d4262de
      Artur Grunau authored
      MdiDockableWindow has been extracted from MdiDockArea to simplify and
      better structure our MDI implementation. The new class takes care of
      creating all necessary representations (docked and floating window) of
      widgets added to MdiDockArea and seamlessly switching between them in
      response to the user's actions (window dragging, key presses, etc).
      
      MdiDockableWindow improves our MDI implementation in two ways:
      - MdiFloatingWindow and MdiDockedWindow instances shouldn't be
        interacted with directly; they're created and disposed of as needed,
        and therefore can't be used as a handle to access and modify an MDI
        window's state; MdiDockableWindow, in contrast, fits this role
        perfectly; it manages both representations of an MDI window, and as
        a result stays around as long as at least one of them is needed
      - managing state transitions of many sub-windows directly in MdiDockArea
        was becoming clumsy as signal mapping and dynamic properties were
        required; having a separate widget that only has to control the state
        of one sub-window makes the code related to state transitions much
        simpler
      6d4262de
    • Artur Grunau's avatar
      Add a "Tools" submenu to the main menu · dd068eea
      Artur Grunau authored
      The "Tools" submenu lists all standard docked tools offered by the
      application (i.e. "Pipeline tree", "Pipeline properties", and "Log
      viewer"), and lets the user toggle their visibility.
      dd068eea
    • Artur Grunau's avatar
      Initial implementation of a main menu · c8ef752b
      Artur Grunau authored
      This commit adds a simple main menu to the application. For the time being
      it only has 2 submenus, "File" and "Visualizations". The latter is created
      by MdiDockArea and lets users manage the visibility and placement of
      canvas windows.
      c8ef752b
  24. 15 Oct, 2013 2 commits
  25. 13 Oct, 2013 1 commit
    • Artur Grunau's avatar
      Refactor VisualizationPipelineWrapper and rename it MdiDockArea · 7e5e44b1
      Artur Grunau authored
      VisualizationPipelineWrapper has been renamed MdiDockArea, and refactored
      to make it easier to use it with arbitrary widgets. It now inherits from
      QMdiArea, which removes an unnecessary layer of indirection. Moreover, it
      creates MDI subwindows and floating windows only if necessary, i.e. when
      a widget stored in it changes state.
      7e5e44b1
  26. 08 Oct, 2013 3 commits
  27. 21 Sep, 2013 3 commits
    • Artur Grunau's avatar
      PipelineTreeWidget: provide a sensible height hint · d585148e
      Artur Grunau authored
      The sizeHint method has been overridden in PipelineTreeWidget to return
      a sensible height for the wigdet, while still reusing QTreeView's
      hardcoded width.
      
      The main window makes use of that to limit PipelineTreeWidget's maximum
      height and give any vertical space reclaimed in this way over to the
      widget displaying pipeline properties.
      d585148e
    • Artur Grunau's avatar
      Display pipeline properties in a scroll area · cfc3e7ba
      Artur Grunau authored
      To stop the widget that contains pipeline properties from constant
      resizing and taking space away from other widgets, its contents were put
      in a scroll area that only resizes horizontally, and scrolls vertically.
      cfc3e7ba
    • Artur Grunau's avatar
      Handle dragging VP widgets out of the MDI area · 62373ebf
      Artur Grunau authored
      The way visualization pipelines are displayed has been considerably
      reworked. A new class, VisualizationPipelineWrapper, is now responsible
      for creating all necessary representations (VisualizationPipelineWidget,
      PipelineMdiSubwindow) of a visualization pipeline and seamlessly
      switching between them in response to the user's actions (window
      dragging, key presses, etc). As a result, it's now possible to drag
      visualization pipeline widgets out of the MDI area and turn them into
      top-level floating windows.
      62373ebf
  28. 16 Jul, 2013 1 commit
  29. 15 Jul, 2013 1 commit
  30. 03 Jul, 2013 1 commit