.
I wrote a small Gofer script (attached) which does what I need except I was surprised that class initializations appear to occur in the reverse order in which the packages are loaded? The script loads PostgresV2, ROE, Magritte-Roe and, my favorite bit of contributed code, Moe.
The problem is that Magritte-Roe attempts to connect to PostgreSQL before meaningful connection arguments can be entered, so it bombs out. This causes all of the remaining initializations not to execute, which leaves PostgresV2 unable to connect at all until PGPacket is manually initialized.
So I added a bit of code to MAConnectionPool's initialization to prompt for the correct arguments to be entered before MAConnectionPool attempts to startup. It is a bit ugly, using a half a dozen FillInTheBlankMorphs to get the required info. Before doing it that way, I added Magritte descriptions to PGConnectionArgs so as to bring up a nice morphic dialog (see MAConnectionPool class>>initializeConnectionArgsMorphic), but two problems with that are:
1) Magritte-Morphic is not loaded in the standard Pharo 1.0 image? (I guess I could add that to the Gofer script)