[Story] Separate Layer and Feature Layer

[MurrayLF]

Separate Layers based upon function: rendering vs. device

Layers for rendering and for the device itself are currently intertwined/conflated. These should be separated for improved structure and easier implementation of additional layer types (e.g.; integration)

Existing code will need to be refactored to remove all instances of feature addition/removal from inside the microfluidic model and be moved to external functions.

We need to create an API that will simplify how new drawings/geometries are added/removed from the visualization layers

Additional Description

The layers types captured by the Microfluidic Device Model:

1. FLOW
2. CONTROL
3. INTEGRATION

The visual type layers:

1. Manufacturable artifacts (Feature)(s) (from FLOW, CONTROL and INTEGRATION)
2. Text
3. ComponentPort renders
4. Additional Render Objects
5. Grid + background

TODO - Create a class called PhysicalFeatures to allow the user and the toolchain to distinguish between UI elements and features that need to fabricate in the microfluidics.

Acceptance Criteria:

• [ ] Unit Test

[rkrishnasanka]

@zyrrron it'll be good if you can be involved with this part of the project since this will be relevant to moving your visualization engine to use 3DuF. We are basically doing some of these things to simplify things for the GUIDE tool.

[zyrrron]

I see. I am glad to do it.

[rkrishnasanka]

@MurrayLF I think separating the usage of the PhysicalFeature class is the only thing left on the docket for this.