Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • MRF MRF
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 86
    • Issues 86
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PACANOWSKI Romain
  • MRFMRF
  • Issues
  • #2
Closed
Open
Issue created Mar 11, 2019 by MURRAY David@dmurrayMaintainer

Refactor rendering process

Currently, many of the interactive rendering features (display function and GUI) are handled directly in the main file. These should be handled by dedicated classes. The main file should only handle parsing arguments and creating the necessary instances.

In the attached file is a draft of an UML to refactor. Please, feel free to propose any modification. mrf_uml_0_0.svg

Edited Jan 15, 2020 by MURRAY David
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking