Re:Show HN: Atopile – Design circuit boards with code
by mawildoer on Monday February 05, 2024 @02:14PM
(#39265604)
Interesting! Haven't come across it before but those linked `~>` operators do indeed quite familiar. If you're familiar with GraphDSL do you have some elements we should look into?
[ Parent
| on HN ]
Re:Show HN: Atopile – Design circuit boards with code
by voctor on Monday February 05, 2024 @04:43PM
(#39267661)
By reading some code here https://github.com/Timot05/logic-card/blob/main/elec/src/log...
I wonder if with directional arrows, instead of writing "out ~ switch.in; switch.out ~ power.gnd", we could write "out ~> switch ~> power.gnd" instead?
But without distinction between in and out ports it may not be possible to check if connections are valid ones.
Anyway, this project really makes me want to learn electronics! Congrats!
Re:Show HN: Atopile – Design circuit boards with code
by mawildoer on Monday February 05, 2024 @07:56PM
(#39269390)
You're absolutely right! We've been thinking very similar ways about "dipole" components and how to best do this; and I think you've nailed it.
What about using dunder __in__ and __out__ attributes? Easy enough to implement for us and overload for folks in the future.
Re:Show HN: Atopile – Design circuit boards with code
by voctor on Monday February 05, 2024 @02:52PM
(#39266167)
I've only worked with Akka Graph DSL to build some data pipelines or protocol stacks. And I've loved working with it!
The equivalent of atopile signal would be port with Akka I think. A combination of ports gives us a shape. A source shape is just one OUT port. A flow shape is one IN and one OUT port, etc.
I'm very new to electronics so I don't know if it makes sense, but connecting all these ports with directional arrows was really helpful to understand the data flow.