Toxic Elephant

Don't bury it in your back yard!

We don't need another Arial

Posted by matijs 16/09/2007 at 13h00

Some time ago, RedHat released the Liberation set of fonts. They are intended as metrically identical replacements for Microsoft’s Arial, Times New Roman and Courier New fonts.

Sounds great, doesn’t it?

Well, apart from the license issues, there’s another problem: Metric equivalence isn’t everything. Arial is already the metrically equivalent substitute for Helvetica, and look at it: Arial is basically Helvetica’s ugly twin sister. So, will Liberation be any better?

Linux already has a set of fonts that are not only metrically equivalent to, but actually look like Helvetica, Times Roman and Courier: The URW
fonts
. To see them on the screen, instead of the ugly jagged bitmap versions, you’ll need to make them available to X, and turn off bitmap fonts in fontconfig1.

But the URW fonts themselves look ugly too, because their hinting is bad. Liberation would solve that, wouldn’t it? No it wouldn’t, because
Liberation’s hinting isn’t done yet:

The first release is a set of fully usable fonts, but they will lack the fully [sic] hinting capability […] provided by TrueType/FreeType technology.

So why not spend the effort on providing good hinting for the URW fonts, so we can have actual nice looking real Helvetica on our Linux screens?

1 On Debian, and probably Ubuntu, that’s

sudo aptitude install gsfonts-x11

and

sudo dpkg-reconfigure fontconfig-config

respectively. Answer no to using bitmapped fonts.

Tags no comments no trackbacks

Disqualified by Advertising

Posted by matijs 23/08/2007 at 16h36

I was enthousiastic about noobkit for about a week. Finally an alternative to the rough style of Ruby’s standard API documentation.

Until I actually wanted to use it.

Most pages have a full width block of Google ads above the main content. This is just too much. For some methods, the text is one line. The ad block then is five times as big.

I’ll go back to using the old version, thanks.

[Also, the search function is not geared towards API documentation, but instead uses a generic Google-like method. Why not highlight the search results that actually describe the method or methods with the searched name?]

Tags no comments no trackbacks

Zurich

Posted by matijs 27/06/2007 at 21h12

So, I’m reading Steve Yegge’s latest, and he drops some not so suble hints to the reader that they should apply at Google. I talk about that to my wife, how working at Google would definitely be nice, but that it would mean moving from Amsterdam (the Netherlands) to Zurich (Switzerland), because that’s where Google is in Europe. And then she says:

Zurich has the best zoo in Europe.

Tags 1 comment no trackbacks

People Ready

Posted by matijs 25/06/2007 at 20h27

First, what the hell does Microsoft’s slogan people ready even mean? The campaign’s site seems to think it means you need people to run a business. Well, I don’t see any businesses around run by small rodents, so I guess they’re right. That’s some vision

So, what’s this about? Some bloggers got paid for writing about people ready, and people got upset.
Now, some defend themselves saying they didn’t endorse anything, and some defend themselves saying of course it’s an ad box (whatever an ad box is).

Well, I don’t think this looks like an ad, and it may not be an endorsement of a Microsoft product, but it is an endorsement of a Microsoft campaign. Oh, and look at the right of the page. It says “Click here to submit your own People Ready Business story”. So, that pretty much suggests that the content on the left was also submitted the same way. But of course, it wasn’t.

Luckily, at least one of the entries seems to have been written while drunk.

People readiness is something only people that are ready for people to be ready can be ready for.

All this via Mark’s translation.

Finally, back to the meaning: “people ready” means ready for people, right? Just like HD ready means ready for HD. Well, sort of anyway. But no, it means the people are ready. See?

Campaign lame.

Tags , no comments no trackbacks

A song

Posted by matijs 21/06/2007 at 23h38

Today, at seven months and nineteen days of age, Sophia spontaneously performed her first song. It went like this:

Ba ba baa ba baa, ba ba baa ba baa.

(The bas are short, the baas are long). The piece was performed at a constant pitch. I’m still working on the correct rhythmic notation; it’s pretty complex.

Years from now, we will say: We were there at her first performance.

Tags no comments no trackbacks

How to compile TV output into the latest X.org ati drivers on Ubuntu

Posted by matijs 21/06/2007 at 12h58

The Problem

You have built a home server slash PVR that you want to hook up to your twenty-year-old television. You have gone to several shops to buy a graphics card that actually has open-source drivers for its TV output functionality (i.e., the ATI Radeon A9250). You have dodged salesmen trying to sell you something else (“No, but here is its successor the NVidia so-and-so.” “Uhm, no thanks.”). You finally succeeded by ordering it over the Interweb (and probably should have done that in the first place). Now you want to patch the driver shipped by Ubuntu to actually get TV output working.

Tags , 11 comments no trackbacks

Subversion and tagging

Posted by matijs 18/06/2007 at 14h50

I’ve been using svk for a while now, but I keep bumping into problems with the whole concept of tags being just copies.

The problem is this: In my mind, a tag should be a symbolic name for a particular revision on a particular branch. In subversion (and hence, svk), it’s not. To use a tag in place of a revision, you first have to do svn info to find the corresponding revision number, and then use that in your svn diff or svn merge or whatever.

Subversion should have had a smarter client from the start, one that emulates tags and branches and hides the implementation detail that they are ‘really the same thing’ from the user.

As it stands, subversion has no tagging.

It’s all very annoying.

Tags 1 comment 1 trackback

Outage

Posted by matijs 18/06/2007 at 13h13

Last week, I did some work on my website, upgrading to the latest Typo trunk and Rails 1.2, and changing from mod_fcgid to a Mongrel cluster.

Last Friday or so, I rebooted my server. Unfortunately, I had neglected to make the Mongrel cluster start at boot. So for the past weekend, all you have seen here is a Service Temporarily Unavailable message.

Sorry.

Tags no comments no trackbacks

A DSL for making SQL-like DSLs

Posted by matijs 14/04/2007 at 14h42

Setting the stage

Some time ago, I came across SQLDSL, a DSL for building SQL queries. The benefit of using a DSL over plain old string concatenation is that syntax is checked before the database server is hit. Unfortunately, SQLDSL does not deliver. It will happily accept

q = Insert.into[“frot”][“zop”][“blob”].values(“kng”).values[“kgn”]

resulting in

q.to_sql
  1. => “insert into ‘frot’ (zop) (blob) values (‘kng’) values () (kgn)”

which is hardly acceptable SQL.

A metasolution

The problem is that each chained call operates on the same class, so the calls can be repeated, even when that’s not appropriate. Instead, each step in the building of the query should return an object of a different class, having only methods appropriate at that stage. Something like this:

class Insert
  1. […]
    def [](*fields)
    return InsertIntoFields.new(@table, fields)
    end
    end
class InsertIntoFields
  1. […]
    def values
    InsertIntoFieldsValuesPre.new(@table, @fields)
    end
    end
  1. etc.

Of course, this quickly becomes tedious, with all the initialize methods having to be made, etc. Boring, boring. Let’s do some metaprogramming.

First, I need a quick way to create a class with a certain number of instance variables, that are set in the call to new(). That sounds like Struct, but the classes that creates have too many methods that would conflict with a DSL for SQL (like values()). So instead, I took a small, simplified part of Mauricio Fernandez alternative: SuperClass (specifically, I didn’t want any accessors for the fields, or named parameters):

module SuperClass def self.new(*fields, &blk) k = Class.new do

defined_instance_variables = fields.clone class << self; attr_reader :defined_instance_variables end define_method(:initialize) do |*a| if fields.size != a.size raise ArgumentError, "wrong number of arguments (#{a.size} for #{fields.size})" else fields.each_with_index {|f,i| instance_variable_set("#{f}", a[i])}
end
end
end
k.instance_eval &blk if blk
k
end
end

(Annoyingly, there’s no way to dynamically create methods with arbitrary arity, without resorting to eval-ing a string.)

The heart of this metaprogramming is this module:

module DSLChain def self.create(*fields, &blk) k = SuperClass.new(*fields) k.extend(DSLChain::Link) k.instance_eval &blk if blk k end module Link def add_step(func, field=nil)

div = defined_instance_variables
fields = div.clone
fields << field unless field.nil?
n = DSLChain.create(*fields)

define_method func do |a|
vals = []
fields.each do|f|
if div.include?(f)
vals << instance_variable_get(“@#{f}”)
end
end
vals << a if a.size > 0
n.new(
(vals))
end
n
end
end
end

Stepper::Step#add_step(func, field) adds a method called func that creates an object of a new anonymous class, optionally adding a field called field. It returns the new anonymous class, so theses calls can be chained.

This means we can do the following:

  1. Insert …
    Insert = DSLChain.create(:table) do
  2. Insert.into creates an instance of this class.
    def self.into(table)
    self.new(table)
    end
  1. Insert.into[fields].values[values]
    self.
    add_step(:[], :fields).
    add_step(:values).
    add_step(:[], :values).class_eval do
    def to_sql
    cn = table.column_names @fields.each {|f| cn.include?(f) or raise "Invalid field: #{f}"} raise "Incorrect number of values" unless @values.size == @fields.size res = "insert into #{table.to_s.downcase} ("
    res << @fields.join(", ")
    res << “) values (”
    res << @values.map{|v| v.to_sql}.join(", ")
    res << “)”
    res
    end
    end
    end

In the middle there, each call to add_step(func, field) creates a new intermediate anonymous class that results from a call to func on the previous one. The result is that after creating an Insert object with Insert.into, the call sequence is forced to be

Insert.into(SomeTable)[“some”, “column”, “names”]. values[“these”, “are”, “values”].to_sql

Aside One: For this to work, Insert.into takes some object that has a method column_names, like ActiveRecord objects. I’m also assuming appropriate to_sql methods to be defined on String and Numeric)

Aside Two: I changed the syntax a little bit from SQLDSL, since I like it better that way.

The original example then results in:

Insert.into(Frob)[“id”][“zonq”].values(“kng”).values[“kgn”]
  1. => undefined method `[]’ for #<#:0×30050220 @fields=[“id”], @table=Frob> (NoMethodError)

More examples

If you want two options, you can do this:

Sample2 = DSLChain.create(:one) do k = self.add_step(:foo, :two) k.add_step(:bar, :three).class_eval do def to_s “A bar: #{@one}, #{@two}, #{@three}” end end k.add_step(:baz, :four).class_eval do def to_s “A baz: #{@one}, #{@two}, #{@four}” end end end Sample2.new(“one”).foo(“two”).bar(“three”).to_s
  1. => A bar: one, two, three
    Sample2.new(“one”).foo(“two”).baz(“four”).to_s
  2. => A baz: one, two, four

Where to from here?

This was mainly a proof-of-concept, of course. There is now a DSL to make DSLs. I haven’t even begun to create the DSL for the select statement, and insert is far from complete. Doing the conditions of the where clause is yet another matter, although ez_where could prove useful for that.

On the other hand, I may not get round to adding all those parts. The metaprogramming was the best part, anyway.

On the gripping hand, wouldn’t it be nicer to have a DSL that actually looks like Ruby’s array operations, such as grep and map? That would be so much more beautiful.

Tags no comments no trackbacks

Who told you to come to this book store?

Posted by matijs 10/04/2007 at 22h22

Say you’re an online book store, and you have an affiliate program. Of course, affiliates come and go. So, what do you do when, say, slashdot stops being your affiliate, and someone clicks on an affiliate link left lying around in an old book review? Do you

  1. Show the book anyway, but not pay the affiliate? Or…
  2. Tell a potential customer to go elsewhere?

Hmm.

Tags 1 comment no trackbacks