Boxer

Developer diary: plans and progress reports.

Another beta, and a peek behind the curtain Saturday 18th July 2009

Boxer 0.86 20090718-1 has been released, which fixes a couple of bugs and tweaks some interface strings. This version is also up on the Boxer betacast and will appear as an automatic update for previous betas.

At the same time, I figured some users might be interested in a peek at the iterative rewriting process that Boxer’s interfaces go through.

First, a little background

In the newest 0.86 betas, Boxer will ask you after game installation if you’d like to import the original installation files into your new gamebox. These files then become available to the game as a fake CD-ROM drive. This is necessary for games that still need access to those files after installation: usually, CD-based games that only install part of their total files. Boxer 0.8 and up would already offer to do this after installing from a physical CD: but now Boxer offers to after installing from any installation source, such as a regular folder of files copied from a CD.

Round and round we go

The first released version of the interface for that choice looked like this:

This is unsatisfactory: the window tells you broadly what would happen (the installation files would be imported), but not why you would need to do so, nor what effect this would have on the game.

After a few iterations, it became this:

This is better: the window now specifies why you would choose to import the files (because games that check for a CD will need them), and what effect it would have (the files would become a new CD for the game).

However, the wording is clunky and ambiguous: users could mistakenly think that Boxer would burn a physical CD from those files. The buttons also refer to two separate concepts: “importing” and “making a CD.”

A few more iterations later, and we have this:

Clearer still: the text flows better and does away with the distracting “importing” verb, instead focusing on the more familiar notion of “making a CD.” It also clarifies that the CD will be “fake”, as opposed to a real, physical CD. (This is a sufficient description, as the user doesn’t need to know how Boxer handles fake CDs: just that they won’t need to burn a real one.)

However in the quest for brevity, the text no longer indicates a connection between the fake CD and the game itself. The brevity is also deceptive, since the folder label (“DFCD”) could be much longer and would then wrap to a third line anyway. So we can spend a few more words to clear this up:

This is the final window used by the new 20090718-1 beta. We’ll see how long it lasts before being rewritten again.

Commentary

  1. The dialog box doesn't seem to come up, Alun. I did the trash the old version as well.

    BJ

  2. What game are you installing with it?

  3. Does the dialog work for installing games from mounted game BIN/CUE or ISO files?

  4. Boxer recognises and can import both physical CDs and disc images of CDs. The import alert for CDs and disc images is slightly different from the one above (it refers to “importing the CD so that you won't need it in the drive to play”) but performs the same function.

    However, Boxer's game installation and importing process doesn't work with BIN/CUE images, since the image needs to be mountable in OS X (not just DOSBox) so that Boxer can access its filesystem. Thus, it currently only works with images in ISO and CDR format.

    (As far as I know, there are no tools that can mount BIN/CUE volumes in OS X—but if you find one, then Boxer will happily install from and import the mounted disk.)

  5. When prompted for a file to run all files are grayed out. I have to cancel and run form commandline. No other version on Boxer on this 10.5.6 machine.

  6. Does is have Growl ? (not that I'm going to use in on Tiger, but I'm just curious) or was I too late to reply? ;P

  7. Jef: This version doesn't support Growl in 10.4, the next beta will however :)

    MTX: After my email to you yesterday, I found that I had accidentally reintroduced that everything-greyed-out bug in a recent beta. It'll be fixed again in the next beta, for which you will receive an automatic update notification.

  8. As far as which game I was trying to install, I was trying to install my GOG version of Descent 2 again so I could make the darn thing work!! The dialog box that you described in your post did NOT come up, and it probably should have. Just sayin'.

    BJ

  9. The reason it didn't come up in that case is because Boxer detected that Descent 2 was already fully installed. In these cases, Boxer simply imports the entire game folder and makes it into a new gamebox. So in short, it's already done what the dialog would have asked you, because there's nothing else for it to do.

    (If the resulting Descent 2 gamebox isn't working, then that's an entirely separate problem I’ll need to look into - although I’ve done that with GOG's Descent 2 folder in earlier versions of Boxer and it's worked fine.)

  10. The latest automatic update works great, Alun! Thank you very much. Daggerfall is running beautifully on my old white Macbook.

    Re: the blog post. Perhaps using the words "disk image" or "CD image file" instead of "fake CD" may be worth considering?

  11. Glad to hear the update cleared up the problem!

    Regarding the terms: something along those lines could work, but the term "image" properly refers to a specific type of discrete file. Boxer's fake CDs are nothing more than folders with the .cdrom extension, and they don't behave in other respects like what people would think of as a disk image.

    That said, it might be appropriate for Boxer to actually import the data as a new ISO image, instead of copying it as a folder. I'll give that some thought and see what advantages there would be.

  12. That said, it might be appropriate for Boxer to actually import the data as a new ISO image, instead of copying it as a folder. I'll give that some thought and see what advantages there would be.

    Has my vote too! But I don't know if it's possible in vanilla AppleScript (maybe UNIX has some tricks up its sleeve)... I don't know about ISO but maybe there are other file formats (with compressions?) that have more advantages. As long as DOSBox can read it they should work fine wouldn't they...

  13. Boxer can make an ISO out of a folder just by feeding it to hdiutil on the commandline. One downside to that is that vanilla Applescript lacks the chops to parse and present a progress indicator from a commandline process, so Boxer would appear to be doing nothing for up to a minute.

  14. Ah, I see, I haven't thought about that, I'm being used to AppleScript Studio.

  15. Haha, I read it ! You left your drawing thingie at work :) -probably everyone reading this will say I'm nuts because they don't know what I'm talking about-

    I've seen that the newest beta has OS X' keys again, are you going to DOSBox' source again?

  16. Er, what do you mean it has OS X's keys? Nothing should have changed in regard to the way keyboard shortcuts operate, I just added a couple more for the screencapture functions.

  17. Cmd + q, cmd+f etc...

  18. Just wanted to send my thanks for actively developing this! Great frontend and much needed for people that, like me, just ain't technical. Thanks!

Design by 40watt.