From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Bastiaan Wakkie" <bastiaan(at)wakkie(dot)org> |
Cc: | "PgAdmin Hackers" <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Website |
Date: | 2006-01-13 11:31:36 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E40103D75D@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
________________________________
From: pgadmin-hackers-owner(at)postgresql(dot)org
[mailto:pgadmin-hackers-owner(at)postgresql(dot)org] On Behalf Of Dave Page
Sent: 13 January 2006 10:53
To: Bastiaan Wakkie
Cc: PgAdmin Hackers
Subject: Re: [pgadmin-hackers] Website
That's not allowed by the Google T&Cs unfortunately... though, I
wonder if I can do it with a little Javascript (you're not allowed to
modify the Google generated code at all, but it might not disallow
Javascript tweaking of form values).
Ah-ha - it seems there is a way to get the Google code generator to do
this - you select the sub domain in the sample output and it makes it
the default option in the generated code. If you subsequently press the
update code button it will reset it though. Oh, and Google don't seem to
have documented this!
So, the search is there and all without hacking any Google code, without
any Javascript, and without breaking any T&Cs :-)
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Bastiaan Wakkie | 2006-01-13 13:02:00 | Re: Website |
Previous Message | Dave Page | 2006-01-13 10:53:24 | Re: Website |