seaside on pharo 1.4 w/ zinc (ConfigurationOfSeaside30 mcz attached)

Hi, I don't know how many people have successfully run seaside on pharo 1.4 or even tried to, and I've not seen it documented anywhere. I have it running and while many of the unit tests don't pass :(  I can start up a zinc server and click through the example apps and some of my own apps fine. I've attached the .mcz file which excludes Comanche, Swazoo, and OmniBrowser from the default install group (OB is only used for the server manager I think, which is not very important, and I'm using nautilus on 1.4).

I understand that this patch might break earlier stuff so with any luck Dale will be able to give me some tips on how to make it more compatible.

Anyway, load up the mcz and then
ConfigurationOfSeaside30 project latestVersion load: #('default' 'Zinc-Seaside')

and to run a server
ZnZincServerAdaptor startOn: 8282

and you should be set.

note: I *just* got this "working" and it seems to work fine with my apps so far, but no promises that everything will go smoothly.

Pat



_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

2012/3/2 Pat Maddox <[hidden email]>:
> Hi, I don't know how many people have successfully run seaside on pharo 1.4 or even tried to, and I've not seen it documented anywhere. I have it running and while many of the unit tests don't pass :(

Which tests don't pass? I'm only aware of two [1] and they're not critical.

 [1] https://ci.lille.inria.fr/pharo/job/Seaside%20Pharo%201.4/

Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Pat,

I'm not sure what you're trying to do with the changes ... but it looks like you've excluded the load of Kom? the changes with tthe OmniBrowser and Swazoo groups probably don't affect what is loaded with your load expression, but removing 'Seaside-Adaptors-Comanche'  and the tests definitely does so presumably that was the important piece to get working for Pharo 1.4 ...

I have been trying to follow the wishes of Lukas, Philippe and Julian when it comes to defining the default behavior of the metacello configuration for seaside, but since it appears that none of the maintainers of seaside actually uses metacello there is tension between what they have told be to do and what is practical ...

The point of metacello goes something like this:

  developer gets project working on Pharo1.4 and records what works in metacello configuration

that way when a user of the project wants to load the project in Pharo1.4, they don't have to do anything but load the configuration ...

When a developer answers a question about why something doesn't work on Pharo1.4 with something along the lines of:

  - do xyz
  - I don't use w anymore, try q

The there is a clear indication that the relevant information has not been recorded in the configuration ...

I periodically visit the seaside project (usually around the time that I'm preparing to do Seaside work in GemStone) and pull in information that I can glean from the mcz files lying around in the various repositories and reconstruct what I think the seaside developers have in mind ... I then load the configuration of a variety of platforms (pharo1.0, squeak, etc.) and if the tests pass, I say my work is done ...

There has been continuous problems with OmniBrowser across multiple platforms (another example of a project where the maintainer doesn't use metacello) and that has caused problems in Seaside, because the seaside maintainers insist that OB be included in the core ... so I disagree with their decision, but it is their decision ...

There's only so much I can do...

Dale

----- Original Message -----
| From: "Pat Maddox" <[hidden email]>
| To: "Seaside - general discussion general discussion" <[hidden email]>, "Pharo mailing list list"
| <[hidden email]>
| Sent: Thursday, March 1, 2012 6:22:29 PM
| Subject: [Seaside] seaside on pharo 1.4 w/ zinc (ConfigurationOfSeaside30 mcz attached)
|
| Hi, I don't know how many people have successfully run seaside on
| pharo 1.4 or even tried to, and I've not seen it documented
| anywhere. I have it running and while many of the unit tests don't
| pass :(  I can start up a zinc server and click through the example
| apps and some of my own apps fine. I've attached the .mcz file which
| excludes Comanche, Swazoo, and OmniBrowser from the default install
| group (OB is only used for the server manager I think, which is not
| very important, and I'm using nautilus on 1.4).
|
| I understand that this patch might break earlier stuff so with any
| luck Dale will be able to give me some tips on how to make it more
| compatible.
|
| Anyway, load up the mcz and then
| ConfigurationOfSeaside30 project latestVersion load: #('default'
| 'Zinc-Seaside')
|
| and to run a server
| ZnZincServerAdaptor startOn: 8282
|
| and you should be set.
|
| note: I *just* got this "working" and it seems to work fine with my
| apps so far, but no promises that everything will go smoothly.
|
| Pat
|
|
|
| _______________________________________________
| seaside mailing list
| [hidden email]
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> There has been continuous problems with OmniBrowser across multiple platforms (another example of a project where the maintainer doesn't use metacello) and that has caused problems in Seaside, because the seaside maintainers insist that OB be included in the core ... so I disagree with their decision, but it is their decision ...

Uhh? No! Nothing in Seaside depends on OB.

We like OB and we use it in our development images. This is all.

Lukas

--
Lukas Renggli
www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

If you want to discuss configuration issues, I am all ears...

Dale

----- Original Message -----
| From: "Lukas Renggli" <[hidden email]>
| To: "Seaside - general discussion" <[hidden email]>
| Cc: "Pharo mailing list list" <[hidden email]>
| Sent: Monday, March 5, 2012 12:18:23 PM
| Subject: Re: [Seaside] seaside on pharo 1.4 w/ zinc (ConfigurationOfSeaside30 mcz attached)
|
| > There has been continuous problems with OmniBrowser across multiple
| > platforms (another example of a project where the maintainer
| > doesn't use metacello) and that has caused problems in Seaside,
| > because the seaside maintainers insist that OB be included in the
| > core ... so I disagree with their decision, but it is their
| > decision ...
|
| Uhh? No! Nothing in Seaside depends on OB.
|
| We like OB and we use it in our development images. This is all.
|
| Lukas
|
| --
| Lukas Renggli
| www.lukas-renggli.ch
| _______________________________________________
| seaside mailing list
| [hidden email]
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

If you have questions about metacello, I am willing to answer them...

Dale

----- Original Message -----
| From: "Lukas Renggli" <[hidden email]>
| To: "Seaside - general discussion" <[hidden email]>
| Cc: "Pharo mailing list list" <[hidden email]>
| Sent: Monday, March 5, 2012 12:18:23 PM
| Subject: Re: [Seaside] seaside on pharo 1.4 w/ zinc (ConfigurationOfSeaside30 mcz attached)
|
| > There has been continuous problems with OmniBrowser across multiple
| > platforms (another example of a project where the maintainer
| > doesn't use metacello) and that has caused problems in Seaside,
| > because the seaside maintainers insist that OB be included in the
| > core ... so I disagree with their decision, but it is their
| > decision ...
|
| Uhh? No! Nothing in Seaside depends on OB.
|
| We like OB and we use it in our development images. This is all.
|
| Lukas
|
| --
| Lukas Renggli
| www.lukas-renggli.ch
| _______________________________________________
| seaside mailing list
| [hidden email]
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

2012/3/5 Lukas Renggli <[hidden email]>:
>> There has been continuous problems with OmniBrowser across multiple platforms (another example of a project where the maintainer doesn't use metacello) and that has caused problems in Seaside, because the seaside maintainers insist that OB be included in the core ... so I disagree with their decision, but it is their decision ...
>
> Uhh? No! Nothing in Seaside depends on OB.
>
> We like OB and we use it in our development images. This is all.

Yes, but we don't use Metacello to build them.

I'm cool with switching the default adaptor to Zinc if that makes life easier.

Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On 06 Mar 2012, at 08:43, Philippe Marschall wrote:
This is a configuration issue.

From my point of view, as author of Zn, I can only say that I am very happy with the collaboration and openness of the Seaside developers to adopt Zn. They tried and used Zn as soon as it became available, it was included in builds and distributions, and there are enough abstraction in place to let people use whatever server they want.

What should be the default is not for me to say, although it would make some sense on certain Pharo builds.

Sven
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On 12-03-05 11:43 PM, Philippe Marschall wrote:
> Yes, but we don't use Metacello to build them.


Thats interesting.  How do you build them?  With Lukas's builder scripts?

Thanks for sharing

Paul
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Philippe,

Wouldn't it be more correct to say "we don't use Metacello"?

Dale
----- Original Message -----
| From: "Philippe Marschall" <[hidden email]>
| To: "Seaside - general discussion" <[hidden email]>
| Cc: "Pharo mailing list list" <[hidden email]>
| Sent: Monday, March 5, 2012 11:43:32 PM
| Subject: Re: [Seaside] seaside on pharo 1.4 w/ zinc (ConfigurationOfSeaside30 mcz attached)
|
| 2012/3/5 Lukas Renggli <[hidden email]>:
| >> There has been continuous problems with OmniBrowser across
| >> multiple platforms (another example of a project where the
| >> maintainer doesn't use metacello) and that has caused problems in
| >> Seaside, because the seaside maintainers insist that OB be
| >> included in the core ... so I disagree with their decision, but
| >> it is their decision ...
| >
| > Uhh? No! Nothing in Seaside depends on OB.
| >
| > We like OB and we use it in our development images. This is all.
|
| Yes, but we don't use Metacello to build them.
|
| I'm cool with switching the default adaptor to Zinc if that makes
| life easier.
|
| Cheers
| Philippe
| _______________________________________________
| seaside mailing list
| [hidden email]
| http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
|
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside