marvingreenberg / sojoinery Goto Github PK

Makes things even more confusing to understand, e.g. on the Home page. The alignment when cutting the face isn't useful for anything, but it would make it much clearer how the joint mates up.

Typically box joints will be thru cut. The SVG you are generating still has a gutter for both pieces. Shouldn't the face piece be a thru cut with no gutter.

I'm assuming you are cutting the box joint with the wood held in a vertical workstation type of setup.

I usually cut them with several pieces held at once - so four 1/2" pieces for example. I can increase the material thickness to 2", but the gutter is still there.

Make sense? Seems like the cutter might be either 0 or maybe 1/8" assuming I am using a spoil board on each side of the piece.

neil

In order to ever support plugins implemented in different languages (python, js, or whatever) need to decouple the code from the existing backend.

(1) Need user authentication.
(2) Need to provide a simple example (and maybe a more realistic example) with one short python script and one configuration file
(3) Store and load from Firebase (?)
(4) Allow private? Latest version only?

When you "generate" the SVG, the SOdovetail page correctly keeps all the settings used. (Not true).
But on SOboxjoint, all the input fields are cleared. See

https://sojoinery.appspot.com/soboxjoint?ax=0.5&width=5.0&units=in&bitdiam=0.25&thickness=0.5

Actually, SOdovetail is not correctly keeping the units - it is also being reset (to in.)

Submitter: Test report
Email: [email protected]
None. Just a test

Generated UI is not properly generating adding "maximum" attribute on input type="number"

Since random code will be uploaded, running on internal servers, some concern for security is needed. On various cloud platforms like appengine, the problem is reduced, but a malicious app could be able to wander around loaded python modules to find, various application secrets like session keys or such. Simplest might be just run the untrusted apps in separate apps/vms.

The box joint should "over cut" in the "outside" corners to yield right angles, and extend the pocket cut similarly.

These choices give me a server error...

It'll look fine until you load it onto the SO

If the files are named more explicitly or with a hash, an existing file generated by one user could be immediately downloaded by another user. Or, more likely the same user regenerating the file. There may be an actual problem now because files stored may conflict since not all parameters are made part of the file name (like thickness.)

Not a big deal for the bulbous joints, but indicates a problem in the generated template evaluating the passed "helix" variable

I can't seem to download an SVG from the screen. If I click on either the image or the .svg name I would expect it do download as an .svg

But it downloads as a .svg.txt and if I change to .svg it does not open properly.

On a Mac using latest OS with Graphic for an SVG editor.

Add a component library tab. Possible fields name, svg, #, rating, user. Firebase? Node.js? Separate app?

Some of this will be addressed with range checking on the input fields (planned). But unexpected exceptions should always be caught with a friendly message displayed.

From issues raised in Issue #6

When setting a pin and tail width, the current behavior is to scale the sizes to exactly match the required length. An alternative approach is to reduce the size of the final tails as required. This is probably the more common approach when using jigs since the spacing is fixed. It also allows for matching pin and tail widths on, say, two different height drawers.

The box joint SVG is carrying over a dovetail name:

sodovetail_pinface_8.000in_a_0.500_b_0.500.svg

Process an uploaded SVG into an identical positive and negative (pocket) image with all corners radiused.