Well, I got past most of the RB and OB issues by doing this:
 
Gofer new
 squeaksource: 'MetacelloRepository';
 package: 'ConfigurationOfMetacello';
load.
 
((Smalltalk at: #ConfigurationOfMetacello) project version: #stable) load.
 
Gofer new
 squeaksource: 'MetacelloRepository';
 package: 'ConfigurationOfSeaside30';
load.
 
((Smalltalk at: #ConfigurationOfSeaside30) project version: #stable) load.
 
Apparently, it's just a good idea to upgrade Metacello before doing anything else.  Being new and using the One-Click Pharo image, I was just following the instructions that pop up when you evaluate 'DEVImageWorkspaces openExternalProjectWorkspace.'  It would maybe be a good idea if the instructions were updated to recommend upgrading Metacello before doing anything else.
 
Now, however, I'm getting this from ConfigurationOfOmniBrowser version122:
 
SmallInteger(Object)>>doesNotUnderstand: #add:
 
 

From: Dale Henrichs [via Smalltalk] [ml-node+[hidden email]]
Sent: Wednesday, October 12, 2011 10:53 AM
To: Joel E. Wilson
Subject: Re: Loading Seaside 3.0 cripples System browser

Tangaloor,

The OB dependency in Seaside3.0 is only for the one package Seaside-Tools-OmniBrowser which gives you a window to control your adaptors. Without Seaside-Tools-OmniBrowser you need to use an expression like the following to start the web service:

  WAKomEncoded startOn: 8080

There is no 'load everything except this package' function in Metacello (maybe I'll add that) so to get all of Seaside excluding the one package means that you have to explicitly load the other packages ... this is the step that I need to spend some time on ... the best answer is to add a group to the config...

Dale


View this message in context: RE: Loading Seaside 3.0 cripples System browser
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.