SlicerLiver v1.0 UI

[RafaelPalomar]

I've drafted a design for the UI following the labelmap approach in #31. While simple, this should be easy to implement and would allow a great degree of flexibility (e.g., multiple resections, multiple distance maps and computation of multiple segments). The main widgets are collapsible, so by default we can leave the resection open with the optional distance maps and vascular territories collapsed. The Vascular territories ui is based on the Slicer-VMTK extension, if you want to have a look at the details.

@davagh, @egipane could you have a closer look to this and see if this fills the requirements for a minimum viable product?

@ALive-research/alive-software what do you think about this approach?

@ALive-research/alive-all-users feedback, comments?

[davagh]

I think it looks nice and consists of all the information we need.
What do you think @egipane?

[egipane]

I believe that is a good starting point, although I would want to see widgets as mentioned in #31 to guide the loading of volumes and labelmaps. This could be as simple as buttons to go to other modules and trigger export to labelmaps.

Annotations to calculate vascular territories would need bold buttons to interact with markups (add, remove, group).

We should plan a new meeting to discuss the path to MVP.

[RafaelPalomar]

@egipane, thanks for the feedback, this is valuable. Let us discuss this in the next ALive software meeting