Sep 092007
 

I’ve used Motorola mobile phones since I’ve had a mobile phone, starting with the V60i back in 2002 (as a customer of the original AT&T Wireless), followed with a V551 (with Cingular), which was in turn replaced with a RAZR V3 (upon its untimely demise).

The latter two phones had nearly identical software; but I was (and still am) a sucker for the RAZR’s form factor and construction.

  • I keep my phone in my pocket, so I like thin.
  • Antenna nubs are annoying. They’re pretty much a thing of the past on GSM phones; but when the RAZR was introduced, most clamshell phones had them.
  • There’s something satisfying about a cool-to-the-touch metal case.
  • The RAZR’s construction is solid. The hinge mechanism has a nice stiff feel to it with very little play. Mine has held up well through a couple of years of use.

The RAZR is not without its flaws, though. My chief annoyance was the weak phone book. This weakness is by no means unique to the RAZR. Most Motorola phones share a lot of the same software; and the phone book appears basically unchanged on models as recent as the KRZR. The number one, what-the-hell-were-they-thinking problem with the this phone book has to be: the single name field; i.e., no means of distinguishing between first and last names. So if you want to sort your phone book by last names, you need to put the last name first in each field. And then when you go to use synchronization software, you’re generally screwed because it doesn’t know about the scheme you’ve superimposed. A lot could be forgiven if this one problem were fixed. But there is plenty more wrong:

  • Rather than let you attach multiple phone numbers to a single entry, the Motorola phone book instead makes you create multiple entries with the same name, then gives you the option to visually merge the identically-named entries and treat one as primary. While this mostly works, it can at times be cumbersome to use.
  • That single name field is, on the RAZR at least, way too short.
  • The phone book accommodates storing phone number and e-mail addresses—nothing else.

So while I have preferred the Motorola clamshell phones, my wife has preferred Nokia candybar format phones. No question about it, Nokia’s UI is consistently superior—particularly its phone book. But there’s something about the ergonomics of opening a clamshell phone to answer it that I’ve always found attractive. And until relatively recently, Nokia’s suite of clamshell phones available in the US was quite weak.

That’s changed lately, which brings me to the N75. This phone uses a more recent version of the S60 software driving Gina’s 6682, so I was reasonably sure I’d be satisfied with the phone on this account. Indeed, the phone sports an extremely capable address book. It knows about first names and last names. It also knows about entries for which there should just be a company name. It can even store physical addresses—a feature I’ve been wishing for in a phone for quite some time.

The N75 has fared so-so in reviews. The major strikes against it seem to be that it is a battery hog and that it takes merely so-so pictures. My demands of a phone-bound camera are quite low; and coming from the RAZR’s VGA camera, even a mediocre 2 megapixel camera is a significant upgrade. I haven’t tried the camera much; but picture quality issues aside, I am quite pleased with the traditional camera-style ergonomics for the camera controls. Camera lenses on some phones seem to be designed to be obscured by a finger; that’s no problem here, even with my large paws. (The nice large keypad on this phone is also very accommodating of large fingers.)

As for the battery issue, I seem to be getting about two days on a charge. That may improve in the future, once I’m opening the phone to edit the address book less.

The construction of this phone feels reasonably solid; but it’s not up to the level of the RAZR in this regard. Nokia could learn a thing or two from Motorola with regard to hinge construction. Mind you, the N75 certainly isn’t bad in this regard. But the opening mechanism isn’t even as satisfying as my old V551; and it’s really nowhere near the nice feel of the RAZR. Apart from the hinge area, the body of the N75 is a matte black plastic. It seems likely to hide scratches reasonably well. But it doesn’t have the nice cool-to-the-touch feel of the RAZR’s metal case. Closed, the phone has almost the same footprint as the RAZR; but it’s about 30% thicker. While not terribly thick, the N75 isn’t really a “thin” phone by modern standards.

All in all, I’m pretty satisfied with the N75.

 Posted by at 10:04 pm
Jul 222007
 

I didn’t want to like Python. I’m still not sure that I do. But I have to admit that it is starting to grow on me. I’m beginning to get used to its goofy ideas about whitespace. And its double-underscore-emblazoned special identifiers are starting to hurt my eyes less.

I have been learning to use Blender. I can’t count the number of times in the past I had started the application, messed around for a few minutes, and then closed it in frustration. But a few days ago, I got it to do something I wanted.

Cool.

So I’ve continued to play around with it. And, slowly, I think Blender is managing to bend my will to its own.

Of course, it wasn’t too long before I needed to use the VRML exporter. And I found that it didn’t play nicely with meshes to which the “Bevel Center” script had been applied. So, a few hours of staring at the export script (in Python, like a significant chunk of Blender’s functionality) and asking around on #blendercoders later, I had a fix.

And now I know some Python.

 Posted by at 2:41 am
Jun 182007
 

My word… was it really all the way back in 2001 that I first latched onto the idea of replacing OpenVRML‘s ANTLR-based parser with one written using Spirit?

I guess I shouldn’t be so surprised; I was immediately taken with Spirit upon discovering it. Though back in 2001 Spirit still had a good deal of growing up to do; it’s come a long way since then. And given that Joel de Guzman and his cohorts are hard at work on Spirit 2, I get the idea that it will yet go a good deal farther. But I digress.

It’s the middle of 2007 and I’ve gotten serious about writing a VRML parser for OpenVRML using Spirit. Why now? Well, ANTLR certainly hasn’t gotten to be any less of an annoying dependency over the years. But another factor is that a new major version of ANTLR has been released (3.0). I think my efforts are better spent moving away from ANTLR entirely than on upgrading to the new version (which I understand to include nontrivial changes to the grammar format).

Now, I don’t want to come across as disliking ANTLR. It’s a really nice tool. In fact, it’s the nicest parser generator I’ve ever used. Functionality is very discoverable and I found, for the most part, the general behavior of ANTLR parsers to be very intuitive. But it has its downsides:

  • It’s a code generator, and thus it has the caveats that go with any code generation.
  • It’s a Java program, and thus it has the caveats that go with any Java program.
  • Even though it can generate code for a number of languages that are Not Java, the Not Java language backends are maintained by persons other than the primary author of ANTLR; thus, these languages wind up being second class citizens. (For example, ANTLR 3.0 has been released without C++ support since the maintainer of the C++ backend for ANTLR 2.x didn’t have time to port it to the new version.)

I actually started in earnest on this project at the end of last summer. I made a good deal of headway, getting as far as developing a good understanding of how to use Spirit’s stored_rule to create a grammar with productions that get modified as part of the parse. This solved the somewhat tricky issue of parsing node field values. But then I got side-tracked with getting the stand-alone viewer (openvrml-player) working reliably; that took much, much longer than I’d anticipated. But now I’ve picked up pretty much where I left off. As of this writing, I can parse nodes, EXTERNPROTOs, and PROTOs, except for IS mappings. I still have to do ROUTEs; though they will be pretty easy now that I’ve got DEF working.

As with the ANTLR-based parser, I’m doing a good deal of semantic checking; this parser will be just as aggressive about rejecting code that’s Not Quite Right as OpenVRML’s current parser. But unlike OpenVRML’s current parser, I’m using very little of OpenVRML’s runtime machinery to accomplish this checking. The idea is to make this parser much more reusable than OpenVRML’s current parser. The current parser isn’t really exposed; users can read the file into the runtime and then inspect the node tree created for the runtime. It turns out, though, that a good deal of OpenVRML’s users (and prospective users) don’t care one bit about a VRML/X3D runtime—they just want to read a VRML or X3D file and do something with the data. So, the new parser will have

  • Pluggable semantic actions
  • Minimal dependencies on the rest of libopenvrml—ideally, linking with libopenvrml won’t be required at all for someone just using the parser

This will all be possible through the magic of Spirit and C++ templates.

 Posted by at 12:21 am
May 302007
 

After years of sitting on the sidelines, I’ve taken the plunge and gotten a digital audio player.

iPods don’t interest me. While I appreciate their slick interface, I’m not the least bit interested in iTunes (or other online music services). And the fact that they don’t play Ogg is a deal-breaker for me. I use a Linux desktop (GNOME) and Ogg is easy for me to use, high quality, and completely unencumbered.

The requirement for Ogg narrows the field quite a bit. Narrowing it further, I’m interested in a flash-based device. So for some weeks I’ve been considering the Cowon D2 or the iRiver Clix. But ultimately the iRiver S10 won me over. The multimedia capabilities of the D2 and Clix don’t interest me; and the S10’s form factor is quite attractive.

I received my S10 yesterday. The functionality and quality are top-notch. And Nautilus makes it easy for me to convert selections from my library of FLACs to Oggs on the S10.

I am very happy with it. But here are the few things I don’t like:

  • Unless you’re using a playlist, files play in the order of their FAT entries. I’d have preferred/expected alphanumeric order. The included software includes the facility to reorder the entries (and thus play order) however you like; however…
  • The included software only works on Windows. I realize that providing software that works on Linux is probably expecting too much; but I was expecting a Mac version. This software isn’t absolutely vital; but the FAT entry reordering is very useful and the software is the most convenient means I’ve found of creating playlists. (Though so far I haven’t found myself messing with playlists.)
  • The included software seems not to work at all unless it’s run by a user with Administrator privileges. Lame. Really lame.
  • No case was included; nor does anyone appear to make one. Hopefully that will change. An armband would be especially handy.
  • The “D-click” navigation is a pleasure to use; but it means that the player can’t really be operated while stored somewhere that’s at all a tight fit—like, for instance, pockets in jeans. If there is some way to lock the interface, I haven’t discovered it yet.
 Posted by at 9:59 pm
May 022007
 

My primary development box, hinge, has seen a bit of an overhaul lately. Most significantly, I snagged some Opteron 285s that were refurbished units (i.e., system pulls) from HP servers for $325 each. These replaced the 242s that I originally built hinge with. Twice the cores and a full 1 GHz faster—quite an improvement.

hinge is housed in a Lian-Li PC-V1200 case. I got the “Plus” version, which includes a blower fan. These blowers seem prone to get noisy after several months. I replaced the blower the first time this happened. Bad fans do happen. But recently the replacement got pretty loud, too. So, figuring these blowers are all destined to make noise, I’ve decided to see how the box fares without it. It does have two 120 mm intake fans; I figure it shouldn’t be that big of a deal for exhaust to be passive.

Unfortunately, I was faced with the realization that the machine was still pretty damn noisy. The primary culprit was the power supply—an Enermax EG651P-VE. The fans on the Cooler Master Vortex TX heat sinks I installed on the new CPUs were contributing to the problem as well. Another thing I really disliked about the Vortex TX heat sinks is that installing them required completely removing the motherboard—they don’t work with the stock mounting bracket for K8 CPUs.

I decided I’d listened to this thing long enough. I’ve now replaced the heat sinks with Hyper TXes; they’re quieter and they use the stock mounting bracket. And the power supply has been replaced with a PC Power & Cooling Silencer 610. Problem solved; this machine is now very quiet. But now the other machines in the room sound loud.

 Posted by at 6:36 am
Jan 082007
 

I spent most of the weekend laying tile in my basement. It amounts to Real Work. One 50 lb bag of thinset mix seems to stretch for about 16 of these 18″ tiles (give or take depending on how much I have to use to get a tile set level with respect to adjacent tiles). I went through two bags this weekend. I am perhaps 25% done with the job.

I am impressed with just how hard this tile is. At one point I lost control of a tile and it hit the floor right on the corner of the tile. It made a “bong” sound as the tile flexed in response to the impact where it took a chip out of the concrete slab floor. The tile? Nary a mark.

We’ve been remodeling our basement for a while now. When we moved into the house over two years ago, doing this was Part Of The Plan. The basement looked like it hadn’t been changed since the house was built in 1980. Sculpted brownish green carpet. Dark gray vinyl tile. Darkly stained wood paneling. And the best part? A large conglomeration of nailed-together lumber that seemed intended to be a bar. A disco dungeon of sorts.

But past the unfortunate decor, the basement is spacious and has a fireplace. It could become very comfortable living space. But salvaging it has not been an easy task. The bar was evicted. The wood paneling was replaced with drywall. A closet and built-in shelving were torn out. The sliding glass door to walk out to the back yard has been replaced. The carpet and vinyl tile were dispensed with. The walls and ceiling have been repainted. Even the fireplace doors have been upgraded.

And, of course, there were the unanticipated problems. A leak in the basement was sealed. (“So that’s why it smells like wet dog down here when we get a hard rain.”) The lopsided stairs were righted and their failing supports replaced.

So, at long last, I feel like we’ve reached the last leg of this project. But at this rate, I’ve got at least three more weekends of laying tile left to go. And I hurt.

 Posted by at 7:35 am
Jan 052007
 

Since going a season without posting here, I feel like I ought to provide some resolution to some of the things I mentioned here earlier in 2006.

Fall was pretty good for OpenVRML. The 0.16 series (which saw its first release back in August) yielded 0.16.3 by the end of the year—which seems to be a pretty usable release. Even the Mozilla plug-in seems to be basically usable, caveat a really annoying bug in the JPEG decoder. Also, I’ve started packaging OpenVRML for Fedora Extras.

Lately I’ve been spending most of my OpenVRML development time working on a stand-alone player. Like the Mozilla plug-in, it is simply a host to the openvrml-gtkplug out-of-process component. But it exercises openvrml-gtkplug in different ways—which accounts for most of my interest in writing the stand-alone player.

 Posted by at 10:48 pm