sci-bots / microdrop

Microdrop is a graphical user interface for an automated Digital Microfluidics control system.
BSD 3-Clause "New" or "Revised" License
25 stars 13 forks source link

Nesting/Groups for Protocol Organization (Trac #85) #89

Open cfobel opened 8 years ago

cfobel commented 8 years ago

Currently, Microdrop protocols are displayed as a table of steps with description of useful parameters such as duration, voltage, etc. However, this table becomes difficult to manage as the number of steps increase (100+ steps). To simplify the creation of protocols, we should be able to group a number of steps under headings defined by user. For example, I should be able to choose steps 30-50 and group them under the heading "Dispense Magnetic Beads". In addition, I should be able to copy or move the group within the table, as well as group edit its parameters. This would significantly enhance protocol creation, but also circumvents the need for designers to create defined functions for dispensing, mixing, etc., as users can easily create their own functions in the form of groups that are tailored to their application and device design.

Migrated from http://microfluidics.utoronto.ca/microdrop/ticket/85

{
    "status": "assigned", 
    "changetime": "2014-03-13T20:00:48", 
    "description": "Currently, Microdrop protocols are displayed as a table of steps with description of useful parameters such as duration, voltage, etc. However, this table becomes difficult to manage as the number of steps increase (100+ steps). To simplify the creation of protocols, we should be able to group a number of steps under headings defined by user. For example, I should be able to choose steps 30-50 and group them under the heading \"Dispense Magnetic Beads\". In addition, I should be able to copy or move the group within the table, as well as group edit its parameters. This would significantly enhance protocol creation, but also circumvents the need for designers to create defined functions for dispensing, mixing, etc., as users can easily create their own functions in the form of groups that are tailored to their application and device design.", 
    "reporter": "ngalpho1", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1394740848122658", 
    "component": "gui", 
    "summary": "Nesting/Groups for Protocol Organization", 
    "priority": "minor", 
    "keywords": "", 
    "version": "0.1", 
    "time": "2012-03-28T04:18:36", 
    "milestone": "", 
    "owner": "cfobel", 
    "type": "enhancement"
}
cfobel commented 8 years ago

Trac update at 20120330T20:22:52: ryan changed milestone from "0.2" to "0.3"

cfobel commented 8 years ago

Trac update at 20120627T17:02:00: ryan commented:

I think the easiest way to do this would be to allow protocols to contain steps or "sub"-protocols. Sub-protocols should be able to be saved/loaded/repeated just like regular protocols, and maybe we could have them shown as expandable sections within the protocol list?

cfobel commented 8 years ago

Trac update at 20120801T15:55:30:

cfobel commented 8 years ago

Trac update at 20140312T20:02:01: ryan changed milestone from "1.0" to "1.1"

cfobel commented 8 years ago

Trac update at 20140313T20:00:48: ryan changed milestone from "1.1" to ""