![]() I’d then have to start delving further into InDesign’s object model, which is a bit of a mess. The most important thing is to write a test that ensures the bars are all the correct width. If I make it more customisable, I think it would be worth test-driving the layout changes. The error handling’s a bit rubbish as well. You can’t customise anything apart from the fonts, so if you standardly use a different barcode design you’d need to do manual work to each barcode. I haven’t written tests for the rendering code, but that would be a good next step. Every time I changed something, or refactored, rather than checking to see if the barcodes still came out correctly I could just run the tests and get instant feedback. ![]() Also in that file are a number of tests used to ensure that barcode_library.js was doing the right thing. I used some of the basics from that to construct a very basic testing framework, contained in barcode_test.js. I’ve been reading Test-Driven JavaScript Development – an excellent book. Then the rendering code takes the barcode from the GUI, uses the library to get the bar widths, and draws the barcode with these widths and the fonts selected by the user.īecause I wanted to make the plugin easy to use, I wrote a shell script to concatenate the relevant JavaScript files and remove the #import lines. To order your barcode labels printed, visit our printed barcodes tool. Use the tool below to generate barcode labels in any of the nine various formats. The GUI code doesn’t contain any logic, it just lets the user enter the relevant details. Create unique print-ready barcodes (UPC, EAN, and more) for product labeling, inventory control, shipping, and more. barcode_library doesn’t know anything about InDesign, all it does is produce a data structure giving the relative bar widths. Really barcode_main.js should be split up into two files, one for the GUI and one for rendering the barcode.Įach part of the code does one thing.
0 Comments
Leave a Reply. |