A while back I started an article series on a utility named Ripsaw. I have since gotten pretty busy with other projects, and the only extracurricular thing I’ve worked on in the meantime is the lesson series on how to play “Spanish Fly”. I was also waiting for Visual Studio 2010 to hit release, but I haven’t moved up to Professional yet, so I may actually drop the whole project back down to VS 2008 when I start it up again.
On top of all that, Blogger is yanking the rug out from under me with some changes to how it updates certain sites, and I want to get that resolved before I add any significant new content. I just wanted to let everyone know that the project isn’t dead; in fact, there have been several times over the last few weeks when I’ve needed a utility like Ripsaw, so this is definitely going to get done eventually.
Share
In this installment of the Ripsaw article series we’ll start putting some actual code into an implementation of the COM interfaces that we specified in the last article. For those of you who just joined the series, Ripsaw is a log viewer for Windows, similar to the Unix tail utility. This series of articles details my rewrite of the application from the ground up.
Continue reading ‘Ripsaw Library Implementation’ »
Share
More fun with one of my favorite languages: A barcode generator written in JavaScript that will create an EAN-13 barcode. The page is completely self-contained and uses no graphics or server-side code.
I’ve only tested the page in Internet Explorer 6, Internet Explorer 7 beta, and Firefox 1.5. I’m not going to target older browsers, but I am interested in hearing about problems in current browsers other than those mentioned above.
Share
>Lisp is becoming a theme here, apparently. I suppose I’ve read so many Paul Graham essays that I’m becoming a fan of the language. In order to become more familiar with it, I decided to write a Lisp interpreter in JavaScript. It’s not quite complete, and the semantics are definitely not entirely correct, but it’s at least usable. The page is even partially scripted in Lisp, and as I debug the interpreter and add more to it (such as loop constructs) I’ll convert more (and eventually all) of the JavaScript to Lisp. Once you browse to the page, view the source and scroll down until you see a <script type="text/lisp"> block.
I have only tested the interpreter in Firefox and Internet Explorer 6, so I’d like to know how it works in other browsers. If you want to look over the interpreter code, download it and play around with it. If you make any additions, changes, or corrections, I’d love to hear about them so I can incorporate them into the code.
Share