gcodepreview VS egui

I've been working on this sort of thing for a while.

For a Japanese spin on this see Tsugite:

http://ma-la.com/Tsugite_UIST20.pdf

which I worked through at:

https://community.carbide3d.com/t/a-study-of-joinery/28492

Traditional joints (box, dovetails, or obscure variations such as Knapp (cove and pin)) require a vertical fixture and 3 setups (at a minimum) --- cut parts to length and machine internal features, mount four board and cut joints in 2 corners, flip boards (with correct orientation) and cut other two corners.

Rabbet joints are simpler --- so simple that they were covered in a video as "The Simple Box":

https://www.youtube.com/watch?v=V93xDM3lXsM

(ob. discl., I work for Carbide 3D)

There have been a number of programs developed for joinery. A current commercial option is:

http://www.g-forcecnc.com/jointcam.html

(but it requires a vertical fixture)

One commercial option became freely available:

https://fabrikisto.com/tailmaker-software/

and ingeniously has an option where a 30 degree V endmill is used, but to cut boards held at a 15 degree angle, affording a 90 degree cut with a great deal of control and flexibility --- this can multiply setups to 9.

A variation I've been experimenting with is full-blind box joints:

https://community.carbide3d.com/t/full-blind-box-joints-in-c...

They're reasonably easily drawn up, though they do have some rather specific tooling requirements (a narrow 90 degree V endmill, a square tool of that or smaller diameter, and to make things easier, a large V endmill)

One test project was so tight that after putting it together for a dry-fit before gluing I was unable to get it apart:

https://cutrocket.com/p/63781eaf9822f/

I've been working on a programming system to make this sort of thing a bit easier:

https://github.com/WillAdams/gcodepreview

and have some sketched out joints which I've not been able to make using existing CAM tools which I hope I'll be able to do using this system (if anyone could recommend books on conic sections, I'd be grateful --- that's where I got bogged down last time).

While I certainly appreciate the virtues of a Domain Specific Language, and that OpenSCAD has been wildly successful because of its limitations, the limitations are downright infuriating at times.

An interesting potential alternative (which hopefully won't result in a fork) is adding Python:

https://pythonscad.org/

which I've had some success with:

https://github.com/WillAdams/gcodepreview

ImplicitCAD is interesting --- and the (new?) ability to open files from GitHub is _amazing_ (OpenSCAD recently gained that same facility, _and_ it supports the customizer: https://seasick.github.io/openscad-web-gui/?https://raw.gith... ), but it's a heavy lift given the need to work out how to edit files, preview them, and so forth.

Do you have a need to?

Do you have a project which might be able to make use of this? What sort of work do you do?

I am bookmarking this for re-reading later because I hope it will help me to understand how to implement Bézier curves in a tool I've been working on for controlling a CNC machine/creating files for cutting on a CNC:

https://github.com/WillAdams/gcodepreview

(but first I have to get arcs working)

Interesting.

I've long been frustrated by traditional CAD/CAM, so finally worked up:

https://github.com/WillAdams/gcodepreview

which allows me to use:

http://pythonscad.org/

and:

https://github.com/derkork/openscad-graph-editor

to create joinery:

https://forum.makerforums.info/t/openscad-and-python-looking...

which would otherwise be tedious to draw up:

https://community.carbide3d.com/t/creating-drawers/19475/26

The problem here is that a fundamental question has not been answered, and as far as I can tell, has not been addressed by any of these visual environments:

What does an algorithm look like?

Herman Hesse alluded to this in his novel _The Glass Bead Game_, but despite decades of discussion and work, no one has made a convincing pysical representation of that system.

I love the concept, and have made some moderately complex attempts, e.g.,:

https://www.blockscad3d.com/community/projects/1430644

https://github.com/WillAdams/gcodepreview

it always devolves to screen size being out-paced by problem complexity --- one gets something of an inkling of this at:

https://scriptsofanotherdimension.tumblr.com/

Alternately, one can just break a project down into modules, but then the top-level view becomes the wall of text representation (albeit w/ nice lines or captured into pretty boxes) which one is ostensibly trying to escape.

I'd love to see someone succeed in this, and I've been using:

https://github.com/derkork/openscad-graph-editor

quite a bit, and put a bit of money towards:

http://nodezator.com/

or perhaps Solvespace --- certainly FreeCAD, and if you're inclined to do programming, OpenSCAD --- see: https://github.com/WillAdams/gcodepreview for an approach which uses RapCAD

Probably the hardest part, if you are new to egui, is to work out how to display the widgets you want. The egui demo site is quite handy in this regard. It features the egui widgets, and has GitHub links to the Rust code used to make each widget. This will help you replicate them in your own project.

Thanks for the feedback!

It is definitely fixable. Take a look at https://github.com/emilk/egui/issues/996 for some examples of how others have styled egui, or try out https://app.rerun.io/

Styling is done with `ctx.set_style`, but creating a nice style isn't very easy at the moment (basically you'll have to tweak constants in code, and then recompile). I'm working on making it easier as we speak though!

Nothing is wrong with that, it’s rather a workaround, ultimately I am trying to have one language only including the UI too (been playing with egui),so I don’t have to use JavaScript.

https://github.com/emilk/egui

FWIW, I opened an issue: https://github.com/emilk/egui/issues/4046

That's fair. I don't have experience with other immediate mode libraries. It's good to hear that it's not an intrinsic limitation

https://github.com/emilk/egui?tab=readme-ov-file#layout Here the author discusses the issue directly. They note that there are solutions to the issue, but that they all come with (in their opinion) significant drawbacks.

For my use case, if I have to do a lot of manual work to achieve what I consider behavior that should be handled by the framework, then I don't find that compelling and am inclined to use a retained mode implementation.

It totally depends on what IoT and what purpose, for example:

IIoT/PLC/industrial automation: most likely you will have to use vendors software, most if the time it’s crap, and a mix of several tech stacks like MSSQL/C#/C++

Sensors and such: depends on what are you building or using the sensors: the protocol mostly is MQTT, and if you would store it in a db postrrsql, elasticsearch, surreldb, influxdb among the most I used.

Robots/drones: on what I build, I use protobuf/grpc for performance and cross-language and direct linux socket io, and where needed websocket but mostly for any web interaction rather than the protocol itself. The tech stack for those, the embedded side is up to you or sometimes based on the sdk you are dealing with, the backend/frontend however, I used to use go/nodejs and for frontend svelte or a simple js library/framework, but recently I’m shifting and redoing everything in rust, embedded, backend and frontend (using something like egui https://github.com/emilk/egui).

When it comes to IoT, I try as much as possible to stay away from python unless you are scripting something else done in go/c++/rust, look at python as a glorified bash script, it’s useful for that or other data science work, but not in IoT.

Same goes with other tech you mentioned, it might suit one case but not another, for example, MQTT is good for sensor IoT type, but good luck controlling a drone with it, mongodb might be great to store a fleet of robots with its access credentials and such, but if you try to use it to store realtime data, it might not perform as expected, and so on.

AFAIK the Rust equivalent to C++'s Dear ImGui is egui.

The creator of Rerun (Emil Ernerfeldt) also created egui [1], an immediate GUI library for Rust. The library is similar to Dear ImGui but it is written in Rust and can be used for desktop and web apps (compiles to WASM and uses WebGL, demo [2]). Desktop apps can target OpenGL (does not display correct colors on macOS, does not work in VirtualBox on Windows) or WGPU (uses native APIs for each platform, works without any problems, but the binary is a big larger).

[1] https://github.com/emilk/egui

> [...] you can build UIs that are snappy and keyboard driven.

That's not an advantage that is exclusive to TUIs; after all, you're running your TUI inside a graphical application that emulates a terminal. (Unless you're rocking an actual VT102, in which case I bow down to you.)

In fact there's an entire class of applications that are extremely snappy and keyboard driven, by their very nature: games.

Some people have taken to writing GUI apps like you'd write a game, and the effects range from OK to fantastic. Check out Lagrange (https://gmi.skyjake.fi/lagrange/), AppManager (https://tildegit.org/solene/AppManager), Dear ImGUI (https://github.com/ocornut/imgui), egui (https://github.com/emilk/egui), and many others.