Basic subcircuit support about mosaic HOT 6 CLOSED

Tricky thing is, how do you map the port names to the subcircuit port order. Here too a model needs to be able to specify its spice representation. Exposing this as a textfield is horrible UX but might work, but need a better system.

from mosaic.

Key thing I need to refactor: allow setting and changing the loaded schematic.

from mosaic.

Schematic can now be dynamically changed.

from mosaic.

Big question is, how do I want to structure subcircuits?

On the one hand I want the flexibility of Cadence/VHDL-like entity -> implementation abstraction, where different schematics can implement the same entity, and be swapped out when configuring a simulation.

On the other hand the common case is probably just one implementation per entity, and I want to have the simple UX of just being able to "drill down" in a schematic, and run a simulation without having to specify every single component.

Maybe it'd work to just build the UI for the single-implementation case, and leave it up to the simulator to do substitutions. So like, you can just simulate the schematic as drawn, or you can provide a configuration which will override subcircuits and parameters.

from mosaic.

Pffffew... It's starting to come together. You can now specify the background and port layout, and select an image URL on top of that.

There is a bug that causes the image to be dragged https://stackoverflow.com/questions/69178308/how-to-prevent-dragging-of-an-image-element-inside-a-svg

And spice generation needs a complete overhaul. To begin I need to refactor the code that gets the element ports and matches them to wires, potentially using the index I described above. Then I actually need to add code to print the x elements and the .subckt elements.

from mosaic.

Ok, bug fixed, edit links added for peak drill-down performance.

Spice export still bust. Broken version up at http://wishfulcoding.nl/mosaic

from mosaic.