Since bylocks wrote
Regarding this program, is there a way to get in touch with the Programmer?
i figured this thread might be the right one to post this, especially since it got me started in the first place. Btw.: I mailed him, too, but got no reply.
# AboutI am currently coding a Key-Bitting-Calculator (html, javascript) which is pretty much like
http://kstoerz.com/locksport/bitting/ but works offline and has some minor additional features. Though the main purpose was my personal usage, I now intend to make it available to others, too, by releasing the code. Neither do I have webspace nor know whether appending archives and/or scripts-like things are allowed here, so I added some screenshots instead (ScreenGrab! ftw).
# Current StatusFeatures- Calculate bitting code from measured depths (metric / imperial system)
- Calculate depths from bitting code
- Estimate the most fitting bitting-system for measured depths
- Create a key-image (Options: shift, profile type(lines / key-like with adjustable cut-angle), adjustable spacing, measure-grid in background(none / metric / imperial), dpi, cut-position-markings, displayable lines for spacing and bitting-levels)
- Create key-image as SVG, too
- Import (CSV) / export(CSV) of bitting-system-data
- Create SQL-commands for export
TODO / BUGS- SVG-output
- Fix plateau-mode
- Double check output (printing and measuring)
- Fix / Remove Yale-Keymark and Medeco-Keymark values
- Minor import-adjustments
- SQL-import
# QuestionsLacking a deeper knowledge of keys and locks however I am afraid to mess / to have messed things up, so here are some questions:
(1) I think about adding a key-tip to the images (maybe it is *pointless* though)
- Can one assume that the tip of the key is 90 degree sharp? Does it depend on the bitting system or should it be manually setable?
- Is it important, that the key-tip is centered in the middle of the key, or can I center it between the last cut and the top line?
(2) Currently the script , when in "plateau"-mode creates "mountains" between cuts, even between 0 to 0 (0 being a "no-cut") -> that wouldn't be an the blade anymore
- Can one assume like the smallest depth in the bitting system was the width of the key-blade, or would that be problematic in any way?
I'd like to keep the options to a minimal but useful level (stuff has to get done xD). It would be pretty to overload everything but that would become quite unformortable imho.
# ScreenshotsKey-images 1-3 show the same key. #1 has an imperial grid, #2 a metric grid, #3 doesn't have a fill, uses a line-profile and additional circle-marks. #4 shows what currently happens in plateau mode when the script tries to calculate the space between shallow cuts. I wanted to upload an svg, too but .txt / .svg are not allowed for attachments.
You do not have the required permissions to view the files attached to this post.