June 26/27

[franknoirot]

Kurt

• updated cli to a new version, did 2 useful things
  • converted assemblies to a compound that can be exported our as an stl together
  • reduced file size
• will deploy the updates on max deflection and quality tooling soon
• might work a user selection of quality for downloads
  • Jeremy isn't sure if allowing quality control matters
  • discussed whether default download quality should be high or low, landed on higher for now. Will revisit if user base grows.
  • low quality for previews, user can't set level
  • finding a balance in download speed and quality. 0.2 deflection might be a good level.
  • the braille example is a great worst case example.
  • will follow up to check if the AWS settings are gzipping
• finished up some blog posts, 3d diff one
• general code cleanup, errors were returning CORS every time. Set up a default API gateway to capture them not get CORS messages.
• wants to deal with the 30sec timeout issue. Might require some new tooling to truly solve, like background jobs.
  • for big complex projects, would need ability to run background jobs.
  • Jeremy mentioned JupyterCadQuery project for inspiration. Maybe it's a simple limit for not-logged-in users to not manipulate large projects.
  • setting up transactional emails, got some headway with MailGun. Will allow for CascadeStudio deprecation.
• added a few extra lights to the render setup to show more detail.
  • useTexture hook from R3F can't be used until CascadeStudio is dropped.
• Jeremy mentioned a GH issue of user asking to not deprecate CascadeStudio.
  • wondering if there's a way to deprecate it still leave some tooling for those kinds of people, like a text to STL tool
  • short answer is no, long answer is maybe. The project is incredibly side effect heavy, and very tied to a front end browser.
  • any solution would require a lot of custom code.
  • could link over with encoded links to current projects in proper CascadeStudio
  • could move CascadeStudio tooling to subdomain
  • feels like a lot of work for a limited use case.
  • Will respond to the issue

Jeremy

• made changes to the cq-cli to support Kurt's work
• finished the braille example and docs. Search.openknow.org --> "braille" his example shows up now
• OpenKnowHow is working on an "openMeter"
• Semblage work. Took first steps toward multiple object selection, to support sweeps and more. Will continue to work on this.
• Will work on test suite for Semblage.
• has been working on ease of install for CadQuery and found a blocker, PyPi not supporting large enough files. Is related to the Conda issue previously discussed.
  • People keep asking for pip install, but the above issue makes it a nonstarter. Continuing to investigate.
• discussed another separate meeting, maybe monthly or quarterly, to allow OpenSCAD.

Frank

• Built out a draft of the /details view to begin discussing
• made a draft of mobile /details view while on a call with Kurt, issue with the camera built into mobile screens like a Samsung Galaxy S10+ is not an issue.
• fixed too purple share dialog issue
• made draft of homepage animations in Blender
• will work on beginning the new design system
• all discussed ThreeJS vs video animations on the homepage
  • concerned with blowing out CPU with multiple in-page animations
  • Jeremy mentioned issues with CadQueery docs stalling after they added in-page 3D models.
  • Kurt mentioned benefits of interactivity possibilities with Three animations
  • FJ will reimplement icing animation with Three marching cubes and see if it works
• will build out parameter control UI into /details view