[Seaside] Re: [ANN] Seaside 3.0.3 release
dhenrich at vmware.com
Tue Dec 21 01:22:20 UTC 2010
I was probably being a little too aggressive in "requiring" the latest
version of OmniBrowser when I updated the ConfigurationOfSeaside30 (I
don't remember specifically), so I'll take the blame on this one:)
Pharo, Metacello, and Seaside30 are all changing at different rates over
time so I tend to go with what works for me (which is usually later
versions of the packages) rather than testing the large number of
potential package versions ...
While there is no tool support at the moment, you _can_ find out what
Metacello will load _before_ actually doing the load (and you can look
at what was actually loaded ... without having to scan through the
Transcrtip), but without being familiar with which packages go with
which projects, it may not be that useful..
On 12/20/2010 04:42 PM, Fritz Schenk wrote:
> Indeed, when I close the old browser and open a new one, the new one works.
> I wish there was some warning of this 'feature'.
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside