CQ-editor VS xpra

I installed cadquery with cq-edit from github using the prebuilt package release for windows 10. This seemed to work great, cq-edit GUI launches and I can even model basic shapes. However when I try to run the printables file from above I get the error

There are other code-CAD derived tools but I recommend sticking to OpenSCAD at least for learning, for simplicity. There's also the seemingly great Cadquery that I haven't tried yet.

Use the latest version of cadquery. The version of cadquery that comes bundled with cq-editor binary isn't the most recent, and doesn't have support for cylinder.

On a previous laptop I used i3, then after a few years on Windows, I returned to Linux on my current laptop and decided to try Sway, and now I’ve been using it for almost a year and a half, but I set up i3 somewhere along the way too, which I have used when I needed screen sharing on Zoom.

I much prefer Sway. It handles output management much better than i3 (because it’s integrated and integrated well rather than being entirely up to you with xrandr—so this probably wouldn’t apply to full desktop environments like GNOME or KDE), supports mixed-DPI environments, properly supports high-DPI (though I’ve also been using patches for fractional scaling since I want 1.5×), avoids all tearing (which was what really surprised me when I first ran i3, I’d forgotten what the tearing was like), and supports my XF86AudioMicMute key (key code 256; it took 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.

CQ-Editor, download the prebuilt binary from the GitHub releases page https://github.com/CadQuery/CQ-editor

All this talk about anaconda etc is a little overblown. Just grab the release ZIP here and run the launcher. It drops you in the editor/debugger workspace with full functionality. https://github.com/CadQuery/CQ-editor/releases/tag/0.2 It doesn't appear to modify your system in any way.

I understand that other modes of using CadQuery require 'conda, but the basic built-in editor experience is self contained. Or am I misunderstanding something?

I tried this a couple of months ago, I found what it's trying to do very pleasant to use but the tooling around it is very annoying. The up-to-date version 2 isn't on pypi, conda is thoroughly unpleasant to have as an environment. There seems to be a drive to using it inside it's own editor https://github.com/CadQuery/CQ-editor while nice seems like wasted engineering effort in developing an editor when the language needs so much work. I didn't have much success structuring cad into modules as they wouldn't import well.

The point IMO of parametric cad in an existing language is to use the ecosystem. Lots of choices in this project make that really hard.

Anyways, I've just written that to make sure you know that the "code-CAD scene" or "state-of-the-art" is not OpenSCAD (and I'm not saying you don't know that), and that the ideas you had are really great, but they have already been brought to existence in CadQuery, CQ-Editor (the editor + visualization + debugging GUI for CadQuery), and the (still incipient) Semblage, that started to implement the "hybrid" approach of code-CAD + GUI based on CadQuery. I do believe another code-CAD program won't hurt at all, and there is even the possibility of collaboration between Fornjot and CadQuery and possibly Semblage, but I wouldn't say the world needs another code-CAD program. The world needs first to know about CadQuery and then decide its real needs. I've just read your blog post of your criteria for CAD software, and I really think that (apart from the community part, that requires that the project is known by many people, which seems to not be the case with CadQuery) CadQuery meets them nicely. If there is something I'm missing please let me know, specially if you already knew about CadQuery but it didn't suit your needs. Anyways, good luck with Fornjot!

The model is parametric using CADQuery, only problem is that I haven't implemented a way to move the charging pins right or left for the original's off-center port, just forward/back/together/apart. I'm planning to add that soon though, as well as clean up my variables so it's a bit more clear what does what.

FWIW I had decent success with Xpra on Linux, and it's still being actively developed, e.g. the HTML5 client is considered stable now: https://github.com/Xpra-org/xpra/

I use xpra for similar purposes (https://github.com/Xpra-org/xpra/)

> Xpra is known as "screen for X" : its seamless mode allows you to run X11 programs, usually on a remote host, direct their display to your local machine, and then to disconnect from these programs and reconnect from the same or another machine(s), without losing any state. Effectively giving you remote access to individual graphical applications. It can also be used to access existing desktop sessions and start remote desktop sessions.

I want to move to the "future", but I use several firefox profiles via xpra in combination with xdotool based hotkeys. The fluidity with which I can control my different profile windows without a mouse and with which I can switch between computers with no lag with this setup is a big reason why I have stuck with a Linux desktop, so I am sad to see those super powers go away for no perceived benefit. I have tried Wayland several times now and don't notice any performance differences, just more bugs in Wayland.

`xdotool search` seems like it has been deemed a security issue for reasons I can't understand (if someone has hacked in to the point that they can even run such query commands, surely I'm already pwn'd). Maybe I'm oversimplifying it, but to me it's like being upset that someone who broke into your house can see the color of your curtains. The powerful feature set of X far outweighs these minor security concerns.

And it looks like xpra is facing huge issues switching over https://github.com/Xpra-org/xpra/issues/387 :(, I have yet to be as satisfied with any other free remote desktop software (paid nomachine is close but less scriptable).

I hope these aren't fundamental limitations of wayland, but the challenges seem steep.

They all operate(d) their GPUs just fine. I'm a heavy user of VirtualGL + XPRA for remote graphics usage, which is a constant factor in my life and work. When they're not doing graphics of some sort, they're hunting pulsars in a GPU-centric compute mode.

I've long been a huge fan of Xpra https://github.com/Xpra-org/xpra , both because of its "screen for X" original focus (though now it supports shadowing an existing session).

There was NoMachine / nx / freenx but it always seemed to be a weird animal to me, requiring installation as a separate unix user, at least at the time.

One of my favorite bits of software is Xpra [0], "screen for X". You'd run it and it would start another X server (start apps in it with `DISPLAY=:1 xterm` or whatever), and you would "attach" it to your running X server with `xpra attach`.

You can attach to e.g. `ssh://hostname/:1`, so I ran a firefox instance on a homelab server and attached to it from my laptop and my desktop to not have to bother keeping bookmarks, tabs etc in sync.

[0] https://xpra.org/

I’ve used Xpra in the past to connect to a remote system for GUI stuff, but I almost exclusively use ssh because most of the time I don’t need to run a remote windowing system.

To add to this if you need to access graphical applications of an entire desktop environment you can use Xpra or MOONLIGHT (I suggest the second one if you want to game on the remote desktop or need very low latency in general), you can use both of these through a ssh tunnel (you need to enable this and X forwarding in the config) so if you setup and allow access to ssh correctly you can also use these without too much of a hassle.

Linux fernando-ipmh61r3 6.1.0-1006-oem #6-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 24 18:24:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux | NVIDIA-SMI 525.89.02 Driver Version: 525.89.02 CUDA Version: 12.0 | /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu/ jammy main universe restricted multiverse /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu/ jammy-updates main universe restricted multiverse /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu/ jammy-backports main universe restricted multiverse /etc/apt/sources.list:deb http://security.ubuntu.com/ubuntu/ jammy-security main universe restricted multiverse /etc/apt/sources.list.d/brave-browser-release.list:deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main /etc/apt/sources.list.d/cappelikan-ubuntu-ppa-jammy.list:deb http://ppa.launchpad.net/cappelikan/ppa/ubuntu/ jammy main /etc/apt/sources.list.d/librewolf.sources:Types: deb /etc/apt/sources.list.d/librewolf.sources:URIs: https://deb.librewolf.net /etc/apt/sources.list.d/librewolf.sources:Suites: jammy /etc/apt/sources.list.d/librewolf.sources:Components: main /etc/apt/sources.list.d/librewolf.sources:Architectures: amd64 /etc/apt/sources.list.d/librewolf.sources:Signed-By: /usr/share/keyrings/librewolf.gpg /etc/apt/sources.list.d/neon.list:deb http://archive.neon.kde.org/user/ jammy main /etc/apt/sources.list.d/nicotine-team-ubuntu-stable-jammy.list:deb http://ppa.launchpad.net/nicotine-team/stable/ubuntu/ jammy main /etc/apt/sources.list.d/obsproject-ubuntu-obs-studio-jammy.list:deb http://ppa.launchpad.net/obsproject/obs-studio/ubuntu/ jammy main /etc/apt/sources.list.d/openjdk-r-ubuntu-ppa-jammy.list:deb http://ppa.launchpad.net/openjdk-r/ppa/ubuntu/ jammy main /etc/apt/sources.list.d/org.kde.neon.net.launchpad.ppa.mozillateam.list:deb https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/ jammy main /etc/apt/sources.list.d/winehq-jammy.sources:Types: deb /etc/apt/sources.list.d/winehq-jammy.sources:URIs: https://dl.winehq.org/wine-builds/ubuntu /etc/apt/sources.list.d/winehq-jammy.sources:Suites: jammy /etc/apt/sources.list.d/winehq-jammy.sources:Components: main /etc/apt/sources.list.d/winehq-jammy.sources:Architectures: amd64 i386 /etc/apt/sources.list.d/winehq-jammy.sources:Signed-By: /etc/apt/keyrings/winehq-archive.key /etc/apt/sources.list.d/xpra.sources:Types: deb /etc/apt/sources.list.d/xpra.sources:URIs: https://xpra.org /etc/apt/sources.list.d/xpra.sources:Suites: jammy /etc/apt/sources.list.d/xpra.sources:Components: main /etc/apt/sources.list.d/xpra.sources:Signed-By: /usr/share/keyrings/xpra.asc