<_whitenotifier-f>
[solvespace] jwesthues commented on issue #295: Circle rendering is very conservative - https://git.io/JfPsZ
rpavlik has quit [Remote host closed the connection]
ohsix has quit [Ping timeout: 272 seconds]
<_whitenotifier-f>
[solvespace] gnbl commented on issue #622: Invalid file path when dragging .slvs file on .exe (Windows drag and drop argument handling) - https://git.io/JfPKJ
<_whitenotifier-f>
[solvespace] gnbl edited issue #622: Invalid file path when starting Solvespace with argument (Windows, cmd and drag-and-drop) - https://git.io/Jf6d0
<_whitenotifier-f>
[solvespace] gnbl commented on issue #622: Invalid file path when starting Solvespace with argument (Windows, cmd and drag-and-drop) - https://git.io/JfPKC
<_whitenotifier-f>
[solvespace] gnbl edited a comment on issue #622: Invalid file path when starting Solvespace with argument (Windows, cmd and drag-and-drop) - https://git.io/JfPKC
ohsix has joined #solvespace
rpavlik has joined #solvespace
azonenberg has joined #solvespace
<azonenberg>
Hey, is it possible to import a step or other non-solvespace geometry into a solvespace design?
<azonenberg>
i can convert if needed, the native input format i'd be working from is either STEP or IDF generated from kicad (board outline)
<whitequark>
unfortunately not
<whitequark>
it is unlikely there will be STEP support any time soon, IDF is more realistic but still hard
<whitequark>
er, wait
<whitequark>
yeah, IDF is fine, it's a fairly simple format with component outlines
<azonenberg>
i could convert to other file formats via say freecad
<azonenberg>
and this was an immediate term need
<azonenberg>
so the answer is, not possible
<whitequark>
right now there's just no import support for 3d geometry
<azonenberg>
Yeah thats what i was afraid of
cr1901_modern has quit [Read error: Connection reset by peer]
<whitequark>
(you can import DXF/DWG as a wireframe)
<azonenberg>
Should i open a ticket for IDF support then?
<whitequark>
yep
<whitequark>
btw, do you expect being able to constrain things to the stuff *on* the board?
<whitequark>
as opposed to the board outline
<whitequark>
because the problem there is maintaining referential integrity
<whitequark>
if I recall correctly IDF does not include refdes
<azonenberg>
I would like to be able to constrain to things like "standoff on enclosure concentric with screw hole on PCB" or "1mm from left side of this connector to edge of cutout in enclosure"
<azonenberg>
i would consider this a one-time import operation
<azonenberg>
i.e. convert idf to native solvespace geometry
<azonenberg>
without linking to the original IDF anymore, and not maintaining sync
cr1901_modern has joined #solvespace
<whitequark>
that's actually substantially harder than linking to original IDF
<whitequark>
solvespace can only represent geometry as parametric models
<whitequark>
(at the moment)
<whitequark>
hmm, now that I look at it closer, IDF *does* have refdes
<whitequark>
so we can link it nicely
<azonenberg>
oh perfect then
<whitequark>
this isn't all that easy to add due to various legacy issues, but STEP is borderline intractable
<whitequark>
so you're in luck
<whitequark>
last time I looked there wasn't even a sane STEP parser
<_whitenotifier-f>
[solvespace] azonenberg opened issue #625: IDF import support - https://git.io/JfP7I
<azonenberg>
Makes sense. Any idea on how long it will be before someone is going to have time to work on this? is some time in 2020 plausible?
<whitequark>
we have to cut the 3.0 release first, so subscribe to the "roadmap" issue
<azonenberg>
that was about to be my other question
<azonenberg>
last release was in 2016
<whitequark>
the plan is to do 3.0 as soon as possible
<whitequark>
what I need to do is a final round of merging small patches and cross-platform testing
<whitequark>
there will be no more large features going in
<azonenberg>
makes sense
<whitequark>
so 3.0 will definitely be in 2020
<whitequark>
mid to late
<azonenberg>
and yeah i'm busy on scopehal as you may have guessed
<whitequark>
i'm busy with nmigen, same deal
<whitequark>
I've long wanted IDFv3 support actually
<azonenberg>
it's starting to pick up, i had PRs from two different devs waiting to review when i woke up
<whitequark>
so it's something I have motivation to do
<whitequark>
oh, you don't want to see my inbox every morning...
<whitequark>
I cut down the number of things I maintain to the minimum and it's still very significant workload
<whitequark>
solvespace in particular has the issue that it works well but it's very hard to modify, and any nontrivial improvement turns into a multi-week refactor
<whitequark>
as a corollary, drive-by contributions usually aren't safely mergeable
<whitequark>
I've been working on that but you could hire multiple people full-time and it'd still take months if not years
<azonenberg>
lovely, lol
<azonenberg>
and well scopehal is in its infancy right now as a project. i mean sure i was working on it here and there going back to the start of my thesis
<azonenberg>
but it only got a user manual like six months ago
<azonenberg>
the first nontrivial commit from a third party was probably in the last 3 months
<azonenberg>
so it's still in that "everyone involved needs lots of hand holding" phase
<azonenberg>
there isn't yet institutional knowledge built up among a cadre of developers
<azonenberg>
everything is me
<whitequark>
there's a similar situation with solvespace in that the original developer is much less active than before
<whitequark>
so effectively there are tons of hidden invariants you can very easily break, and i'm the only active developer who knows them well
<whitequark>
took me something like a year to stop breaking compatibility or introducing UB with each commit
<whitequark>
well, I'm exaggerating but only a bit
<azonenberg>
lol wow
<whitequark>
it is very much one of those cases where the original dev had all the codebase in his head and it was fine
<whitequark>
until it wasn't
<whitequark>
it's elegant, but... clearly not written to be modified by more than one person
<whitequark>
still better than opencascade lmao
ohsix has quit [Read error: Connection reset by peer]