[Seaside] Re: I have installed the Seaside 'One Click Image' and
intrader.intrader at gmail.com
Sun May 2 21:52:43 UTC 2010
Mariano Martinez Peck <marianopeck <at> gmail.com> writes:
> On Sun, May 2, 2010 at 4:53 AM, Fritz Schenk <intrader.intrader <at>
> Running Pharo1.0 with saside-3.0a5
> I take the downloaded image and changes and stored it in the Pharo1.0 folder -
I change the pharo.sh script to point to the Seaside as given below:
> exec "$EXE/squeak" -plugins "$EXE" \
> -encoding latin1 \
> -vm-display-X11 \
> ###exec "$EXE/squeak" -plugins "$EXE" \
> ### -encoding latin1 \
> ### -vm-display-X11 \
> ### "$RES/Pharo-1.0.image"
> When I use the seaside image, there is no eCompletion and the source pane's
appearance does not change when I make changes.
> If I use the image from pharo, all works Ok, but Seaside is 2.8.
> This is correct: I will explain you: Pharo has 2 important things: a core
(those images are called PharoCore) and a set of tools to developers (those
images are called PharoDev).When you download Pharo from the pharo website, you
are downloading a PharoDev image that contains not only the core, but also all
the development tools (autocompletion, omnibrowser, refactorings, etc). The
image that you download from Seaside website, is based on Pharo, but in Pharo
core, and they install the tools they want. So, this may be a little different
from the PharoDev image. If you are used to Pharo, my suggestion is that you
download Pharo from the website and then install seaside. To do that, search in
the mailing for this day as Sean said.But basically, just evaluate: (Smalltalk
at: #Gofer) new squeaksource:
> package: 'ConfigurationOfSeaside'; load.and then:ConfigurationOfSeaside
> project latestVersion load: 'Seaside 3.0'.CheersMariano
> Please help
> seaside mailing listseaside <at>
> seaside mailing list
> seaside <at> lists.squeakfoundation.org
It looks like I need very basic help. First, which list should I go to answer
your post. I don't see a threaded list, the archives are not answerable (I see
my post there). the list at gmane is not where I initially posted the message.
Now to the meat of the problem - appears that Pharo is running Seaside2.8.
For example when I start the server via
WAComancheAdaptor startOn: 8080.
WAAdmin register: WebCounter asApplicationAt: 'webcounter'
and attempt to open http://localhost:8080/seaside I get the error:
Internal Server Error
WAError: My subclass should have overridden #handleFiltered:
KomHttpServer/7.1.2 (unix) Server at 'localhost' Port 8080
which indicates to me that 2.8 is active, and not 3.0
When I 'doit' the following recommended by Mariano:
(Smalltalk at: #Gofer) new squeaksource:
ConfigurationOfSeaside project latestVersion load: 'Seaside 3.0'
there is no error messages that I see, I sill get the 'Internal Server Error'
Now,when I open Monticello while on Pharo, and I see that Seaside Development
history says 'Ancestors: Seaside-Development lr.133, the repository frame of
Monticello says 'http://www.squeaksource.com/Seaside30.
Sorry for trouble, and I hope I can get past this problem
More information about the seaside