I must say that Pharo has a come a long way and the community support for the
newer tools is great...
To solve my problem, I just had to read the opening text in the Pharo Image and
do:
DEVImageWorkspaces openExternalProjectWorkspace.
Reading that, I learned about how MetaCello is being used, and was able to do:
Gofer new
squeaksource: 'MetacelloRepository';
package: 'ConfigurationOfSeaside28';
load.
((Smalltalk at: #ConfigurationOfSeaside28) project latestVersion) load.
Then I loaded my code in. With only a minor fixup to changes with the MIME*
subsystem, I'm up and running on a new image with a CogVM.
- Brian
On Oct 27, 2011, at 11:38 AM, Brian Brown wrote:
> Hello all,
>
> It's been a while since I showed my digital face around here ;)
>
>
> I've got a number of Seaside based web applications that I would like to move
> into newer pharo images and take advantage of the VM advances that have been
> made.
>
> My stuff is all running under Seaside 2.8/Kom/Dynamic Bindings, etc.... which
> presents several problems when trying to load into a 1.3 Pharo Core.
>
> For example, Dynamic Bindings extends BlockContext, but now BlockClosure is
> the class that is receiving messages previously intended for BlockContext.
> I'm sure there will be many more issues like this, so I'm looking for advice
> on how to proceed.
>
> Is there a new Kom/DynamicBindings that works with the newer closure images?
> Have folks gone to a different web server, and if so, can it work with 2.8?
>
> If I can get this all running in a newer image, then my next step would be to
> port it Seaside 3, but I'm playing serious catchup in the incredible amount
> of changes since I was using Seaside/Pharo.
>
> Thanks for any advice you can give me!
>
>
> - Brian
