Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.webbeat.web
  • Issues
  • #60
Closed
Open
Issue created Oct 31, 2014 by André Anjos@andre.anjos💬Owner

Experiment configurator block order could be improved

Currently, our experiment configurator uses the block order to determine the setup order in the configuration page. This not always translates to a reasonable organisation of the blocks. For example, if the user starts drawing on the right of the page, then the first blocks on the configuration page would be the last ones in the dataflow order. An uninformed user could find this particularly counter-intuitive.

This can be fixed in two ways:

  1. We allow the user to setup the "configuration" order by introducing some property that one can set while drawing the toolchain, or

  2. We try to devise what is the best order by looking at the "x" (ordinate) position of the block.

Assignee
Assign to
Time tracking