Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • M mods
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pub
  • mods
  • Issues
  • #5
Closed
Open
Created Sep 29, 2017 by Jake Read@jakereadMaintainer

System Features

'system' - level features I am keen to implement

Debug

  • 'pipe inspector' - what is in this data line? when is it updating?
  • UI shows some evidence that events are firing - lines 'heat up' or draw momentary event-paths...

Dataflow

  • merge, split (a-la grasshopper)
  • requires some thought w/r/t how data is globally handled. what can a mod expect is in any given data line? ask for all to have 'identifier' object, which contains some kind of header?
  • simple maths expression evaluator? sliders?

Layering & Abstraction

  • mods-in-mods i.e. bundles...
  • mods-as-function-calls within mods (woah) (if writing new mod, can call image_threshold(yourdata) / alternately with the graphic mod)
  • good 'graduating' exercise, pulling users from graphic programming into 'real' programming
  • requires some thought w/r/t events, etc. not-so-simply function returns.
Assignee
Assign to
Time tracking