| 6 Jan 2024 |
 barnabyw | very interesting. I’m planning on putting my codecad repo on github soon, I will look into using that or something similar for it | 19:49:55 |
 yeicor | Sure, go ahead | 19:57:18 |
| yeicor | I am using ocp-vscode with the show_all function, and I found it easier to delete old "helper" objects than toggle their visibility in the interface | 19:58:54 |
| yeicor | * I am using ocp-vscode with the show_all function, and I found it easier to delete old "helper" objects than to toggle their visibility in the interface | 19:59:09 |
 Draek#9615 | Ah I see, fair point ! | 19:59:10 |
 philipsd6 | I do that too— the alternative iirc is to keep a list of objects to show and pass that into the show function. Because sometimes when troubleshooting I want to still show a helper object. But for the final version del makes sense. | 20:00:54 |
 felix.haeberle | Hi yeicor I love your project.
I started to read through the code and you wanted feedback so I write some questions here:
1. Is there a reason why you use the del function extensively
(Python would not need it, because it does its own garbage collection (but maybe there is a good reason why you do it...)
2. concerning handlebar_side_xy = (80, 25) # (center, start) and handlebar_size = (10, wall) # (width, height) I personally would find the code more readable if you would not use tuples here. The references with [0] and [1] are more cryptic (indirect) than a real name (data classes and named tuples might be something that you could use)
3. do you know that the python script can use a
if __name__ === "__main__":
... do something if the script is run directly
else:
.... do the stuff for importing it
Many python scripts use this for calling a function like main, but the concept can also be applied during the import phase.
I really like your concept with the to_fillet. I was not aware that this works the way you do it.
Furthermore is the split a nice. | 21:03:35 |
| felix.haeberle | * Hi yeicor I love your project.
I started to read through the code and you wanted feedback so I write some questions here:
1. Is there a reason why you use the del function extensively
(Python would not need it, because it does its own garbage collection (but maybe there is a good reason why you do it...)
ok that was already answered this is a neat trick.
2. concerning handlebar_side_xy = (80, 25) # (center, start) and handlebar_size = (10, wall) # (width, height) I personally would find the code more readable if you would not use tuples here. The references with [0] and [1] are more cryptic (indirect) than a real name (data classes and named tuples might be something that you could use)
3. do you know that the python script can use a
if __name__ === "__main__":
... do something if the script is run directly
else:
.... do the stuff for importing it
Many python scripts use this for calling a function like main, but the concept can also be applied during the import phase.
I really like your concept with the to_fillet. I was not aware that this works the way you do it.
Furthermore is the split a nice. | 21:04:15 |
| yeicor | 2. Yes, that would definitely help readability. Thanks!
3. I did not think of that. However, when I import a script I want to run all of its code in order to generate the part, and when I run the script I want to generate the part and also call ocp_vscode.show_all(); so I guess I wouldn't gain anything by restructuring the code in this case. | 21:39:28 |
 bernhard42 | Yes, I also use del for this case. On the other side, if you de-select a variable the viewer keeps it de-selected across runs, which is helpful for re-running code after changes | 22:01:09 |
| bernhard42 | The funny thing is, "show_all" was built for visual debugging only, but many people use it as their default show command. I didn't expect that 😂 | 22:02:33 |
| barnabyw | “always show (almost) everything” is the default behaviour of any GUI CAD software, so it doesn’t surprise me that people like show_all() so much | 22:04:46 |
| bernhard42 | The nice thing about build123d and ocp_vscode, these helpers usually can be built easily.
In algebra mode, I love to see locations, planes and axes by default. | 22:43:04 |
| barnabyw | yep, it’s like having a CAD program which you can easily script UI improvements for! | 22:44:31 |
| 7 Jan 2024 |
|  Red Sand Robot joined the room. | 00:11:30 |
 Antti Tuominen | now in b3d, | 01:39:59 |
| Antti Tuominen | 
Download image.png | 01:40:24 |
| Antti Tuominen | 
Download 20240107_030712.jpg | 01:40:39 |
| Antti Tuominen | 
Download 20240107_031905.jpg | 01:40:40 |
| felix.haeberle | Bike Mount | 07:42:00 |
 Roger Maitland#7070 | Is it made from laser cut carbon fibre? | 12:51:24 |
| Antti Tuominen | TPU :D | 13:29:11 |
| Antti Tuominen | 
Download 20240107_152950.jpg | 13:30:25 |
| Antti Tuominen | Just a textured sheet | 13:30:26 |
| Roger Maitland#7070 | Nicely done 😀 | 13:31:02 |
 clairbee | It's been two weeks since the initial version of PartCAD was released. Check out how far it has gone on https://github.com/openvmp/partcad/ . Now with Assembly YAML and OpenSCAD support. Parametrized parts and more intuitive ways of joining parts into an assembly are coming up next. | 19:56:54 |
|  nibnibs joined the room. | 20:12:55 |
 Jern#4673 | https://jdegenstein.github.io/parts-build123d/ was able to set up a test page here! thanks for setting it up | 23:22:16 |
| 8 Jan 2024 |
|  kaljr. joined the room. | 01:06:55 |
| Jern#4673 | 
Download image.png | 03:08:18 |
