..and after all is loaded do:

"Register Pier2 on Seaside" PRPierFrame registerAsApplication: 'pier' kernel: (PRKernel instanceNamed: 'pier')

"Start Comanche server" WAComancheAdaptor startOn: 8080.

Successfully tested with updated-to-now Squeak4.2-10160-alpha image.

Nikolay

On Wed, Jul 21, 2010 at 10:11 AM, Tobias Pape Das.Linux@gmx.de wrote:

Hi,

I would like to have that a tiny bit more concise:

Am 2010-07-21 um 07:47 schrieb Nikolay Suslov:

...

Hello,

This should work for loading Seaside3 | Magritte2 | Pier2 into Squeak 4.1

image.

...

In Workspace:

"1. Load Metacello"

(Installer repository: '

http://www.squeaksource.com/MetacelloRepository')

...

    install: 'ConfigurationOfMetacello'.

(Smalltalk at: #ConfigurationOfMetacello) perform: #loadLatestVersion.

Metacello is kept recent by any of the following loads, thus, not needed explicitely.

...

"2. Load Seaside3"

(Installer repository: 'http://www.squeaksource.com/MetacelloRepository') install: 'ConfigurationOfSeaside30'. (Smalltalk at: #ConfigurationOfSeaside30) perform: #load.

Installer squeaksource poroject: 'MetacelloRepository'; install: 'ConfigurationOfSeaside30'.

Thus, this is not having to put in an URL. Don't know, but it feels more smalltalkish to me.

...

"3. Load Magritte2"

(Installer repository: 'http://www.squeaksource.com/MetacelloRepository') install: 'ConfigurationOfMagritte2'. (Smalltalk at: #ConfigurationOfMagritte2) perform: #load.

idem.

...

"4. Load Pier2"

(Installer repository: 'http://www.squeaksource.com/MetacelloRepository') install: 'ConfigurationOfPier2'. (Smalltalk at: #ConfigurationOfPier2) perform: #load.

idem.

so long, -Tobias

Tobias,

To have Pier2 application enabled, you should manually (in workspace) register it for now (the same in official Seaside-3.0rc Pharo based image). Just check PRPierFrame class, where there is no #initialize method yet, meaning that after doing (WADispatcher resetAll) you will lose Pier2 app.

Looking at Seaside-3.0rc Pharo based image, Kom is the default. Thanks for pointing to the Seaside's control panel, yes it's better to use.

Also, after loading all Seaside stuff, the default system browser is changed to OmniBrowser (which is default for Pharo). So, this could be changed to default Squeak system browser manually in Window menu.

Regards, Nikolay

On Wed, Jul 21, 2010 at 2:27 PM, Tobias Pape Das.Linux@gmx.de wrote:

Hi,

Am 2010-07-21 um 11:02 schrieb Nikolay Suslov:

...

..and after all is loaded do:

"Register Pier2 on Seaside" PRPierFrame registerAsApplication: 'pier' kernel: (PRKernel

instanceNamed: 'pier')

...

"Start Comanche server" WAComancheAdaptor startOn: 8080.

However, this is a bit ‘short-sighted’[1]

There is the Seaside control panel in the ‘Open…’ menu, that manages all Adaptors currently reigstered etc.pp.

I’d propose to include this way to the Seaside control panel instead of the startOn: doit. (if more than one Kom is started, it will fail anyways). Isn‘t Swazoo more common as default adaptor now?

So Long, -Tobias

[1] does this exist in English?

On 7/21/2010 5:01 AM, Tobias Pape wrote:

There may be more questions that will arise from that point. E.g. OB does not make use of the Squeak4.1 default shout, hence, this may be confusing for some people

Let's try it. Here is a starting point:

http://ftp.squeak.org/various_images/seaside/Squeak4.1/Seaside3.0.zip

Improvements, fixes, enhancements, etc. are all welcome. Also, does anyone have instructions for how to create a Seaside 2.8 based image?

Cheers, - Andreas

On 2010/07/21 21:31, Andreas Raab wrote:

On 7/21/2010 5:01 AM, Tobias Pape wrote:

...

There may be more questions that will arise from that point. E.g. OB does not make use of the Squeak4.1 default shout, hence, this may be confusing for some people

Let's try it. Here is a starting point:

http://ftp.squeak.org/various_images/seaside/Squeak4.1/Seaside3.0.zip

Improvements, fixes, enhancements, etc. are all welcome. Also, does anyone have instructions for how to create a Seaside 2.8 based image?

Looks good! Download, run, and it works!

frank

On 7/21/10 4:26 AM, Nikolay Suslov wrote:

Tobias,

To have Pier2 application enabled, you should manually (in workspace) register it for now (the same in official Seaside-3.0rc Pharo based image). Just check PRPierFrame class, where there is no #initialize method yet, meaning that after doing (WADispatcher resetAll) you will lose Pier2 app.

Looking at Seaside-3.0rc Pharo based image, Kom is the default. Thanks for pointing to the Seaside's control panel, yes it's better to use.

Also, after loading all Seaside stuff, the default system browser is changed to OmniBrowser (which is default for Pharo). So, this could be changed to default Squeak system browser manually in Window menu.

Regards, Nikolay

I had a nasty time trying to figure out why the browser's behavior changed as each package in a series was loaded. Is there a discussion somewhere as to why certain features were left out of OmniBrowser?

Also, I've noticed that within OmniBrowser, the features seem inconsistent. Compare how the browser displays PRDistribution vs Object for example...

Lawson

On Wed, Jul 21, 2010 at 2:27 PM, Tobias Pape <Das.Linux@gmx.de mailto:Das.Linux@gmx.de> wrote:

Hi,

Am 2010-07-21 um 11:02 schrieb Nikolay Suslov:

> ..and after all is loaded do:
>
> "Register Pier2 on Seaside"
> PRPierFrame registerAsApplication: 'pier' kernel: (PRKernel
instanceNamed: 'pier')
>
> "Start Comanche server"
> WAComancheAdaptor startOn: 8080.

However, this is a bit ‘short-sighted’[1]

There is the Seaside control panel in the ‘Open…’ menu,
that manages all Adaptors currently reigstered etc.pp.

I’d propose to include this way to the Seaside control panel
instead of the startOn: doit. (if more than one Kom is started,
it will fail anyways). Isn‘t Swazoo more common as default
adaptor now?

So Long,
       -Tobias



[1] does this exist in English?

Yep. Exactly the same phrase.