>> I'm curious why you didn't go with OCCT for Solvespace.
I didn't start Solvespace, but Jonathan was apparently in a DIY mode after developing his take on constraint-based sketching. It's also very easy to go from NURBS curves to NURBS surfaces, the challenge begins at boolean operations which continue to be a source of bugs for us. This is really the only option other than OCCT and the code is small and approachable so I try to make it better.
Yeah. To quantify, OCCT is >1M lines of code, and SolveSpace's NURBS kernel is <10k. This general smallness is what subsequently made stuff like the browser target feasible, though it obviously comes with downsides too.
We'd welcome contributions, and it's much easier to contribute to the smaller codebase. I think there's potential for coding agents to accelerate this work since robust point-in-shell and shell-is-watertight tests are mostly sufficient to judge correctness, allowing the agent to iterate; loosely you could define your geometric operation as a function of whether a point should lie within the output region, then ask the agent to convert that to b-rep. I wouldn't currently expect useful progress without deep human effort and understanding though.
Would it be worthwhile to consider switching to OCCT (or make it optional)? It would make certain things such as fillets/chamfers much easier, I suppose, and it would make those boolean operation bugs go away. And exporting to various formats would be easy.
>> Would it be worthwhile to consider switching to OCCT
It would, and it has been considered. The sketch elements in solvespace are significantly decoupled from the solid model. That means we could substitute (via wrapper maybe) an OCCT object instead of our SShell class. Then you'd have to change a set of solvespace curves to OCCT curves to make extrusions from them and such. But that would be most of the work.
We do tag all triangles in the mesh with a sketch entity handle for flat surfaces so you can constrain points to a face. I'm not sure how that would be handled. We will also be tagging edges of the solid with sketch entity handles in the future so we can do chamfers and fillets - say by selecting a line entity and applying a modifier to it which gets applied to the NURBS shell. I'm not sure how that would go with OCCT.
Perhaps you could create both the shell and the OCCT object. Then when an edge is chamfered, you could look it up in the OCCT object (simply find all segments which are sufficiently close to the chamfered edge). And then call the OCCT chamfer function. Or something along those lines.
I'm really interested in your project! I'm a engineer in computer science and robotics, and in parallel, I'm going to run a workshop on building solar ovens at a recycling center. I'd love to base the workshop on your project and learn more about it.
Would it be possible to get your contact information so we can communicate further if you're open to it?
"Technology has become the idol of our society, but technological progress is—more often than not—aimed at solving problems caused by earlier technical inventions."
"Interesting possibilities arise when you combine old technology with new knowledge and new materials, or when you apply old concepts and traditional knowledge to modern technology."
This presupposes two questionable assumptions: that you have any choice in the matter, and that technology itself isn't the thing that is making your life nasty, brutish, and short.
I do not read something like that out of that quote.
Vaccines, emergency medicine, construction or farming equipment, all these things that make life easier, healthier and longer are not what GPs comment was about.
It talked about technology that was needed to fix problems created by earlier technology (think: someone has to write an ad-blocker because someone else optimized distributing advertisements).
Um, these technologies enable a larger human population, which then causes problems. Tractors enable ever larger tracts of the best land to be devoted to farming, to enable a larger population, to need more land to cultivate, etc.
Hypertherm | West Lebanon, NH | Full-Time | Director of Software Engineering
Hypertherm's mission is to provide customers with the best industrial cutting solutions in the industry. We are a 100% associate-owned company with our corporate office in Hanover, NH, USA, and have Associates in twenty-six countries around the globe. Globally focused, we design, manufacture, and support the world's leading cutting solutions, with a proud history of over 50 years.
Reporting to our General Manager, Software, as our new Director, Software Engineering, you will:
Work as a technologist to build, organize, and lead our high-performing go-to-market software product teams across multiple locations and multiple product lines (including SaaS, on-premise, embedded, perpetual, and subscription offerings) while defining & setting enterprise software engineering standards.
Lead and mentor the software and applications go-to-market product engineering team leaders development in all aspects of their roles to create an industry-leading team.
Play a crucial role in product scoping, roadmap, and architecture discussions with Marketing, Sales, and Product Management.
Envision and build our software engineering organizational structure, methods, and processes to scale for growth while working collaboratively in a matrix organization.
Robotmaster looks to have you join our multi-disciplinary team of software developers and venture “under the hood” and "power the tools" that make industrial robotic programming easier for our customers.
Hypertherm's Software team located in Montreal, Canada is home of Robotmaster, an award-winning and industry trend-setting approach to software technology providing innovations for quick and easy programming of industrial robots. See more about the exciting work we do here (www.robotmaster.com). Recipients of the Game Changer Award for Motion Control at the RoboBusiness Conference and CIO Review Magazine named us to its list of the 20 Most Promising Robotics Solutions Providers.
I have a work notebook, so the second screen in my setup is the notebook screen. This screen is there anyway, so there is no electronic waste. As for the energy, the notebook overall consumes about 10 W during normal use. My estimate for the screen's power usage is about half of that, so maybe 4-6 W. To put that into perspective, my body's baseline energy usage is 90 W.
I do also have two screens: one laptop for work and one PC for personal usage (my company does not allow me to use the laptop for personal usage). Individually we can all find "mitigating factors" but collectively we failed finding the right balance between comfort and sustainability.
The multi-screen trend is now pursuing its mainstreamification to every offices and home desktops. But at the same time Earth is sending us warnings: we need to slow down. Given the state of our knowledge on that matter, I am surprised that the general consensus on YN is not to have less screens and reserve the resources to better usage.