[squeak-dev] [Seaside] New catalog entry for Seaside 3.0.3
dhenrich at vmware.com
Tue Mar 5 23:23:56 UTC 2013
Nutty or not, the default installation of Seaside includes a dependency upon OmniBrowser (for starting and stopping the seaside server), plus a web server (used to be Kom and recently has moved to Zinc) ... the configuration describes all of the dependencies. The default configuration load includes just about everything that a developer might need to get up and running Seaside ...
If you want to duplicate the information from the configuration in SqueakMap, then I suggest you take a look at the configuration itself....
----- Original Message -----
| From: "Chris Muller" <asqueaker at gmail.com>
| To: "The general-purpose Squeak developers list" <squeak-dev at lists.squeakfoundation.org>
| Cc: "Seaside - general discussion" <seaside at lists.squeakfoundation.org>
| Sent: Tuesday, March 5, 2013 2:30:02 PM
| Subject: Re: [squeak-dev] [Seaside] New catalog entry for Seaside 3.0.3
| > (Smalltalk at: #WAServerAdaptorBrowser) open.
| > (Smalltalk at: #WAPharoServerAdaptorBrowser) open.
| > (Smalltalk at: #WAServerAdaptor) open.
| It may be you can't use that browser without OB which requires
| OCompletion. For a web-framework to require a fat-client UI framework
| seems nutty to me. :)
| But did you try working with Seaside itself, starting a server and
| opening a browser on it?
| > However none works. A note in the SqueakMap entry would be appreciated.
| > The note says: 'Seaside requires a web server; the most commonly used
| > is KomHttpServer'.
| > But there is no SqueakMap entry for that.
| Hm, check again, it's there. Maybe you need to update your SM Cache
| (via the "Update" button).
| seaside mailing list
| seaside at lists.squeakfoundation.org
More information about the seaside