{"id":404,"date":"2009-07-07T13:38:38","date_gmt":"2009-07-07T17:38:38","guid":{"rendered":"http:\/\/patorjk.com\/blog\/?p=404"},"modified":"2014-01-25T17:53:39","modified_gmt":"2014-01-25T21:53:39","slug":"new-keyboard-layout-analyzer-less-lines-of-code","status":"publish","type":"post","link":"https:\/\/patorjk.com\/blog\/2009\/07\/07\/new-keyboard-layout-analyzer-less-lines-of-code\/","title":{"rendered":"New Keyboard Layout Analyzer, Less Lines of Code"},"content":{"rendered":"

I’ve uploaded a new version of my Keyboard Layout Analyzer<\/a>. You can see a full screen capture of the output page below. The new version has a layout similar to the one I discussed in my last post, and has a different chart set up, as well as a hand full of other small new features.<\/p>\n

\"The
The New Layout For Keyboard Layout Analyzer Output<\/figcaption><\/figure>\n

This new version is essentially a complete re-write of the old version. I had been making mental notes of features I thought would make the program a lot more useful, and after thinking about how I’d implement these new features, I realized I’d be better off just re-writing the application instead of modifying the old one. <\/p>\n

This re-write was also a way for me to “pay down” my “technical debt”<\/a> (I think I like that term), as I was able to more efficiently implement certain things to make them a lot more flexible. When I write stuff for fun, a lot of the time I just go with the first or second implementation I think of and then get to work. This re-write will probably serve as a good lesson learned, since the re-write was a little more painful than I expected. Only one of the new features that I thought up is in the program right now (the new chart set up), I didn’t have time to get to the rest of them, though I hope to implement them in the next couple of weeks.<\/p>\n

Here’s an overview of what’s in this version:<\/p>\n