Seve - 8041128715219ADDD0C-A5D5-48CA-BBB3-0AEF7...

are we good for V2 >

will add few things more leds

Its amazing

Maybe less border spacing

can we order before open ?

<@757706909351411845> can we make it ?

yes it is possible to order new ones

but i'm wondering if we can make it even better too, do you think you could add a screen lol

and some buttons

perhaps something.... tetris like?

perhaps a way to plug in a battery

i'm thinking of how it can be more demo-able

screw the battery we can usb power it

maybe optional battery

interesting , I will start working on that ASAP , we ?can try to add a battery + USB options to power it

hell yea

yea i think a pico is hard to demo

i will hold up all your boards and show them off as a mostly-working pico

but it would be better if people could play mario or something

for mario you'd need 4 buttons on the left and four buttons on the right, and one or two buttons in the center (the start button)

also if you have a better you usually want to have an on/off toggle switch

i will design the 3d case as soon as you have something 🫡

godspeed

we probably have like 3-4 days to make this lol

it can be a separate product, i will be sending an update to investors with your PICO 😉

<@757706909351411845> https://github.com/tscircuit/copper-pour-solver/pull/55

can I get a review

<@757706909351411845>

<@757706909351411845>

oop

oh i did it

<@757706909351411845> hay I'm heading to bed let me know if this is what you meant if not would love some comments to help https://github.com/tscircuit/core/pull/2512

taking a look

this is interesting, i wonder if we should color traces based on global connectivity net key- i don't think it's wrong but it's interesting- maybe helpful

this looks pretty good so far, i just wonder if we should have a new render phase to make it more clear what's happening

you have a lot of db insertions that are "uncontrolled" like they don't have a class

that's generally not good- it means that it's hard to control the lifecycle of that db element, the group has to manage the lifecycle

i'm doing some experiments but tacit approval

i would MAYBE consider taking one of these snapshots that changed and making sure DRC isn't dramatically different haha- our DRC is a hero if it's not breaking with this new configuration (good!)

this is what i asked codex: ``` i'd like you to refactor this PR https://github.com/tscircuit/core/pull/2512/files, i think that it's not a good idea for the Group class to essentially be doing insertions into the db for source_net and source_trace, it would be better to introduce a new renderphase called ConnectExposedSubcircuitNets that creates classes that can manage that in the "regular" render process. ```

<@757706909351411845> can you check this https://github.com/tscircuit/footprinter/pull/669

and do you think we should chagne the port assign to be cathode pin 1 on core ?

yea we need to match IPC convention

users should use `D1.pos` and `D1.neg`

or `D1.cathode` `D1.anode` etc. to avoid pin numbering issues

maybe that's just something we have to put into the skill

we could also possibly have some basic DRC checks for common gotchas, a pinAttribute for isCathode and isAnode, then we can just make sure they're not accidentally connected to a net with isPower or isGround (V5/GND are automatically marked in circuit json with is_power and is_ground iirc)

<@757706909351411845>

the game boy is almost done , do we need storage or not

I dont think so

No not for this version

Maybe later

ok