CQ-editor

Query would be much more viable OpenSCAD alternative if it was packaged into a standalone CQ-editor application and published via homebrew, etc. I'm also interest in Zoo [4](fka KittyCAD). They're trying to create a modelling tool that combines model-by-code and model-by-mouse. With some AI layered on top. They have an interesting architecture where they stream geometry to your local device from the cloud. Should be great for performance, but ties you to the cloud. [0] https://github.com/CadQuery/cadquery [1] https://en.wikipedia.org/wiki/Open_Cascade_Technology [2] https://cadquery.readthedocs.io/en/latest/intro.html#why-cad... [3] https://github.com/CadQuery/CQ-editor [4] https://zoo.dev/

ok a little effort to get it to work, involving dumping the xkb keymap and adding in a suitable entry, but I think that it’s literally impossible to support under X, though you may be able to remap it to a different key like F20 in some way at a lower level, but my attempts at that failed). It’s not been without its troubles. Screen sharing is only possible at the screen granularity rather than individual windows, and I think Zoom is still broken because they did things stupidly in the past (using a GNOME screenshot API many times per second instead of the compositor-neutral screen sharing API that did exist when they implemented their thing) and are still unravelling them. I’ve also had a couple of apps require tweaks to unbreak, e.g. https://github.com/CadQuery/CQ-editor/issues/266, if you build it with a version of Qt that supports Wayland (the default, though their first-party distribution doesn’t), you have to explicitly tell it to use xcb instead of wayland or it crashes on startup. But honestly that’s all I can think of. Oh, one more thing, I guess. Cursor sizing is comically broken in Sway. With `seat seat0 xcursor_theme Adwaita 96`, I get cursors at at least five different sizes when hovering over different windows. Some ignore it and use the default size multiplied by the scaling factor. Some use it but ignore the scaling factor. Some use it and multiply by the scaling factor. Some use it and multiply by the scaling factor rounded up to the next integer. Some do different things altogether. I haven’t diagnosed it all yet.

point of it booting in "safe mode" or giving me a black screen. - post conda install, some binaries didn't want to run anymore because conda-installed libs were newer. To be fair these grievances are old: I've avoided conda like the plague for - easily - the last 5 years, and they might have cleaned up their act. However, I still find the notion of having to install 2 gigs worth of stuff on my machine only to try a simple CAD package for a few hours a rather offending proposition. Call me an old curmudgeon if you have to. To be fair to the cadquery folks: they seem to have realized the issue and they now offer what looks like a somewhat self contained binary dowload of the cq-editor package [2]. Finally, I'll leave you with this, taken from the cadquery homepage itself [1] (note the use of the word "polluting" in there, looks like I'm not the only one feeling this way): For those unfamiliar (or uncomfortable) with Anaconda, it is probably best to install Miniconda to a local directory and to avoid running conda init. After performing a local directory installation, Miniconda can be activated via the [scripts,bin]/activate scripts. This will help avoid polluting and breaking the local Python installation. In Linux, the local directory installation method looks something like this [1] https://github.com/CadQuery/cadquery#alternative-anaconda-in... [2] https://github.com/CadQuery/CQ-editor/releases