Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Old revised version, and a new one
Date: Fri, 14 Nov 2003 08:29:09 -0000
Message-ID: <03AF4E498C591348A42FC93DEA9661B871FF86@mail.vale-housing.co.uk>
Thread-Topic: [pgsql-www] Old revised version, and a new one
thread-index: AcOqTpqMpfTXG0p+Sh6tw0Ef4Rj5xwAOkJRw
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "Michael Glaesemann" <grzm@myrealbox.com>
Cc: <webmaster@letzplay.de>, <pgsql-www@postgresql.org>

=20

> -----Original Message-----
> From: Michael Glaesemann [mailto:grzm@myrealbox.com]=20
> Sent: 14 November 2003 01:28
> To: Dave Page
> Cc: webmaster@letzplay.de; pgsql-www@postgresql.org
> Subject: Re: [pgsql-www] Old revised version, and a new one
>=20
> And I was running into problems with column width with words=20
> not fitting into the 120px columns defined by the ads. I do=20
> think 120px is a little narrow, making it harder to read=20
> longer descriptions (due to line breaks) or even using longer=20
> words in some cases. What are your thoughts on increasing the=20
> left and right borders on the ads to make the columns wider?

Ahh, a sense of d=E9j=E0 vu!!

The problem with increasing the left/right ad borders is that you then need=
 to do the top/bottom as well or it just looks wrong.

One this I did try previously that I seem to recall I liked but Marc wasn't=
 so keen on (though maybe not for this reason) was including a solid title =
bar just below the header, right the way across. It also had a thin white b=
order all round so it looked like a completely standalone entity. It gives =
just enough of a break that the columns no longer need to line up with the =
ads (though they should still look even).

Regards, Dave.