|Programming||By Shamus||Sep 28, 2010||46 comments|
EDIT: Whoops. I’d intended to post this after today’s comic. The screenshots are spoiler-ish, so you might want to see today’s comic before reading further.
Some people expressed interest in what I was doing that led to yesterday’s post. I’m not one to miss an opportunity to talk about myself, so let’s do that.
Ever since DM of the Rings CXXXI I’ve used my own software for making comics. It’s 100% homebrew code. It looks thus:
Ok, I never have the window this small. I usually run it full-screen, so it looks like this:
That 308 you see in the lower left corner is the framerate counter, and should give you a pretty good idea of why I made the software in the first place. If you’ve ever opened a jumbo project in Photoshop, Comic Book creator, or some other graphic-artsy type program, you’ve probably noticed that they are not the smoothest things in the world. Zoom way in and pan around and watch your modern quad-core desktop computer choke and stutter like an old 486. Comic Press here is a champ and will maintain the smooth framerate no matter what you do. It’s rendering the comic using OpenGL, and this is a lightweight job even for graphics cards of a decade ago. It’s rendering maybe one or two hundred polygons. (Although the images are ginormous and likely wouldn’t fit in a turn of the century card.)
The word bubbles break against the panel borders automatically, so you can just slide them around the page and fiddle with how wide or tall they are and CP handles the rest. (Some artist-types do this sort of stuff in Photoshop by manually arranging words, drawing ovals, giving them borders, and cropping them as needed. Madness!) You can chain bubbles together, aim the tail, and alter the dialog in realtime. Just click and drag. I’m pretty proud of this.
The bubbles support a few bits of HTML markup, although that part needs work. You might remember the post from two years ago where I was frustrated with how slow and cumbersome Windows was when I generated the word bubbles. I managed to fix that, though.
Note that the program is only complete enough to serve my needs. It’s lacking crucial features and bug fixes that would be required if I were to ever try and release this to the public. There’s a dozen ways to crash it. I know about these issues and avoid them, so the program is stable for me. But it would be a minefield for the uninitiated.
Anyway, note the palette of controls on the right-hand side. That changes based on what you have selected. It’s the only part of the program that is Windows-specific. You couldn’t port this program to any other platform because you’d have to re-write the 3,000 lines of code that drive the interface widgets. (Windows code is very bulky.) It’s also kind of wasteful. There’s a ton of space wasted below the controls.
Last week I got to thinking it would be cool if the controls floated over the workspace like in this, which I just Photoshopped:
If the controls were part of the rendering, then they could be transparent. Also, it would no longer be driven by Microsoft-specific code, so it would be portable. I decided to try and find a library that would let me do this, which is how I lost my weekend to frustration and madness.