We use cookies to personalize content, interact with our analytics companies, advertising networks and cooperatives, and demographic companies, provide social media features, and to analyze our traffic. Our social media, advertising and analytics partners may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services. Learn more.
One of our top priorities recently is improving Easel’s ability to work with complex projects. To that end, we’ve been looking for ways to make changes, large and small, to make Easel faster and more responsive. It’s very much an ongoing process, so you can expect to see Easel improve over time.
We thought people outside the company might be interested in the products of this effort, so I wrote up a short article—with diagrams! and equations!—explaining one improvement we made earlier this week:
Easel does bounding box calculations at various points both while creating/editing a design and while generating toolpaths. This optimization probably makes a bigger difference to designing than to toolpath generation. To be clear, though, it’s only one part of Easel’s workload, so the overall improvement from this particular change is just a few percent. (But small improvements add up!)
This is pretty nice. Seeing the precise bounding box is one of those small things that I just glazed over maybe because Easel is a web app, but the fact that you guys are working on stuff like this both big and small is what keeps me coming back to Easel.
