Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • M myplotlib
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • Yori Fournier
  • myplotlib
  • Merge requests
  • !9

I now separates between MyFig and MyFig_base. MyFig_base can be used by overwrit…

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Yori Fournier requested to merge myFigInterface into dev Jan 22, 2017
  • Overview 0
  • Commits 1
  • Pipelines 0
  • Changes 7

…ting the init function and the plot function, very much like in v1.0.0, you just don't need update, remark the axes should be created in init not in plot. The MyFig class however is smarter, and the user just need to overwrite defineKeywords and addAxes, yes, you don't need init! as their names suggests in defineKeywords you should update self.keywords, in addAxes you should add the objects MyAxes. Now the figure object reads a tuple of data object as argument (not optional anymore) each index for the axes. This behaviour can be overwritten in the function MyFig::formatRawdata, and MyFig::set_rawdata. Remark now the MyFig_base keywords became attributes: self.keywords['fignum'] -> self.fignum...

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: myFigInterface