Introduction to Comic Book Millennium 2016

Introduction to Comic Book Millennium 2016

Comic Book Millennium is a program that can keep track of your comic book collection. You can enter the comics that you have and know how many comics you have and which ones. It can print reports of your collection. It can also report on missing issues that are in your collection of a particular title.

It was first offered for sale in 1999 or 1998 by my previous company, Cole Software Technologies. I believe I created the concept of the run with breaks because none of the comic book inventory software that I tried throughout the 90s had it. It was maddening. It was the reason that I wrote the original software because I didn't want to enter all of my comics in the database having to either enter one at a time, or just add one run at a time. So I wrote the first Comic Book Millennium. It was written in dBASE.

Around 2003, I decided to rewrite it in C++. So that was the second version of the program. It had some issues because I was trying to keep everything on a single form and .Net was in its infancy. It didn't work so well.

So I wrote Comic Book Millennium 3, 4, 5 before finally releasing an actual version of it as Comic Book Millennium V. I was feeling nostalgic for Roman Numerals.

Then I rewrote it again with version 6. It was a return to the multiple windows way of doing things. That was in 2008.

Since then I have probably rewritten it around 10 times but haven't released any because it wasn't good enough until now. Now with this version it is written in C# and wpf. But I'm not going to call it a version number at least in the title. Instead I'm going with the year. This is Comic Book Millennium 2016. The version number is 7 simply because I don't remember how many versions I've written and trashed. 

You'll see a lot of influence with the Windows 8/10 modern applications with it. However, this is a desktop application. I like having more control over what the application can do and distributing it.

It also should work well with a touch monitor since the menu and buttons that control the program are set up in such a way that I think a touch interface would be nice. Of course, I'm writing it on a computer without a touch display so I might be completely wrong.