how to use google cdn for scriptaculous and prototype googleapis

Basically include this script


but then if you want the submodules, it’s like this:

There are no minified versions, but apparently they’ll be gzipped which is practically already as good. ref:¬†!topic/prototype-scriptaculous/_faqKXu9kJY

Another option that might work is to load your javascript [in rails] with like javascript_include_tag :defaults, :async => true

though I guess that async flag might screw things up LOL

or possibly use :defer instead of :async


postgres initdb createuser woe

c:\installs\postgres95_installed>usr\local\pgsql\bin\psql -h localhost -p 5555 template1
psql: FATAL: role “packrd” does not exist


meant “when it runs initdb, it creates by default a table named postgres, user <current user>”

What you’re typing there means, by default, “connect as user packrd, to table packrd” which don’t work so hot.


postgres extension building mingw woe

At first I thought the comments meant “install postgres on windows to a folder without spaces in it” then I realized that isn’t even enough.

According to this¬†basically postgres binary distributiosn in windows are “MSVC only” so you have to go that route. yikes.

Actually, if you install a “mingw” build of postgres for windows then you can use the normal

make PG_CONFIG=C:\installs\postgres95_installed\usr\local\pgsql\bin\pg_config.exe
make: Nothing to be done for `all’.

c:\dev\downloads\pg_partman>make PG_CONFIG=C:\installs\postgres95_installed\usr\local\pgsql\bin\pg_config.exe install
/bin/mkdir -p ‘c:/installs/POSTGR~2/usr/local/pgsql/share/extension’
/bin/mkdir -p ‘c:/installs/POSTGR~2/usr/local/pgsql/share/extension’
/bin/mkdir -p ‘c:/installs/postgres95_installed/usr/local/pgsql/share/doc/extension’
/bin/mkdir -p ‘c:/installs/POSTGR~2/usr/local/pgsql/bin’
/usr/bin/install -c -m 644 pg_partman.control ‘c:/installs/POSTGR~2/usr/local/pgsql/share/extension/’
/usr/bin/install -c -m 644 updates/pg_partman–0.1.0–0.1.1.sql updates/pg_partman–0.1.1–0.1.2.sql updates/pg_partman–0.1.2–0.2.0.sql updates/pg_partman–0.2.0–0.3.0.sql updates/pg_partman–0.3.0–0.3.1.sql updates/pg_partman–0.3.1–0.3.2.sql updates/pg_partman–0.3.2–0.4.0.sql updates/pg_partman–0.4.0–0.4.1.sql updates/pg_partman–0.4.1–0.4.2.sql updates/pg_partman–0.4.2–1.0.0.sql updates/pg_partman–1.0.0–1.1.0.sql updates/pg_partman–1.1.0–1.2.0.sql updates/pg_partman–1.2.0–1.3.0.sql updates/pg_partman–1.3.0–1.4.0.sql updates/pg_partman–1.4.0–1.4.1.sql updates/pg_partman–1.4.1–1.4.2.sql updates/pg_partman–1.4.2–1.4.3.sql updates/pg_partman–1.4.3–1.4.4.sql updates/pg_partman–1.4.4–1.4.5.sql updates/pg_partman–1.4.5–1.5.0.sql updates/pg_partman–1.5.0–1.5.1.sql updates/pg_partman–1.5.1–1.6.0.sql updates/pg_partman–1.6.0–1.6.1.sql updates/pg_partman–1.6.1–1.7.0.sql updates/pg_partman–1.7.0–1.7.1.sql updates/pg_partman–1.7.1–1.7.2.sql sql/pg_partman–1.7.2.sql ‘c:/installs/POSTGR~2/usr/local/pgsql/share/extension/’
/usr/bin/install -c -m 644 doc/ ‘c:/installs/postgres95_installed/usr/local/pgsql/share/doc/extension/’
/usr/bin/install -c -m 755 bin/ bin/ bin/ bin/ ‘c:/installs/POSTGR~2/usr/local/pgsql/bin/’


and it just works (builds at least, and installs), woot!

wicket how to unit test with deployment configuration

in your unit test, don’t use Application

instead use something liket his:

private static class DeploymentApplication extends Application {
public org.apache.wicket.RuntimeConfigurationType getConfigurationType() {
return RuntimeConfigurationType.DEPLOYMENT; // some freaky wicket bug where if you are in DEVELOPMENT you can’t have any duplicate label values [we do TODO get rid of duplicates, then remove this weirdo (inspired by