Smalltalk › Frameworks & Tools › Seaside › Seaside Development

Seaside on Squeak

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

8 messages Options

Tobias Pape

Seaside on Squeak

Dear Seaside developers

I plan to make Seaside 3.0.x available for
the stable Squeak 4.4 and also Squeak Trunk.

I would like to adapt the Metacello configuration
for that, please tell me whether I should
* modifiy the existing release (3.0.7),
* create a new point release (3.0.7.2),
* or make it a new release (3.0.8)

Other than that, I made Seaside 3.1 load in
Squeak 4.4.

The respective configurations for Grease and Seaside
can be found at
> http://netshed.de/seaside/ConfigurationOfGrease-topa.191.mcz
> http://netshed.de/seaside/ConfigurationOfSeaside30-topa.415.mcz

Feel free to review and integrate them with your
development process.

Best
-Tobias
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Dale Henrichs

Re: Seaside on Squeak

Tobias,

I'm inclined to leave #released versions alone and open a new version ... then there is no confusion about which version works in Squeak4.4 ... if you claim that 3.0.7 should be used for Squeak4.4, I can find older versions of the mcz file that invalidate that claim.

So i'd recommend going with 3.0.7.2 using 3.0.7.1 as a starting point ...

Dale

----- Original Message -----
| From: "Tobias Pape" <[hidden email]>
| To: [hidden email]
| Sent: Wednesday, March 20, 2013 2:41:27 AM
| Subject: [Seaside-dev] Seaside on Squeak
|
| Dear Seaside developers
|
| I plan to make Seaside 3.0.x available for
| the stable Squeak 4.4 and also Squeak Trunk.
|
| I would like to adapt the Metacello configuration
| for that, please tell me whether I should
| * modifiy the existing release (3.0.7),
| * create a new point release (3.0.7.2),
| * or make it a new release (3.0.8)
|
| Other than that, I made Seaside 3.1 load in
| Squeak 4.4.
|
| The respective configurations for Grease and Seaside
| can be found at
| > http://netshed.de/seaside/ConfigurationOfGrease-topa.191.mcz
| > http://netshed.de/seaside/ConfigurationOfSeaside30-topa.415.mcz
|
| Feel free to review and integrate them with your
| development process.
|
| Best
| -Tobias
| _______________________________________________
| seaside-dev mailing list
| [hidden email]
| http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
|
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Tobias Pape

Re: Seaside on Squeak

Dear Dale
Am 20.03.2013 um 17:54 schrieb Dale Henrichs <[hidden email]>:

> Tobias,
>
> I'm inclined to leave #released versions alone and open a new version ... then there is no confusion about which version works in Squeak4.4 ... if you claim that 3.0.7 should be used for Squeak4.4, I can find older versions of the mcz file that invalidate that claim.
>
> So i'd recommend going with 3.0.7.2 using 3.0.7.1 as a starting point ...

I thought the very same but I wanted to be sure.
Thank you.

Best
-Tobias_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

DiegoLont

Configuration for Pharo 2.0

Hi all,

I am working on making a configuration for Pharo 2.0, that loads Magritte and Seaside Rest, and all that is needed for this.

Currently I am busy with the configuration for Seaside. I created a version 3.1.1, since it needs to load the current bleeding edge (so newer versions). I think I have the right configuration now and all correct versions, but I get an error because the version 3.1.0 is broken for Pharo 2.0 (it refers to the packages 'Seaside-Pharo-Core' and 'Seaside-Tests-Pharo-Core', that are not defined under #'pharo20').

I have the following questions:
1. Do you agree that I should create a version 3.1.1, or should it be 3.1.0.1?
2. What do I do with version 3.1.0, since this is broken?

Cheers,
Diego

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

DiegoLont

Configuration of Seaside Modifications

In reply to this post by Tobias Pape

Hi all,

Now that I am mailing about the configuration two more things:

Some libraries are not made Pharo 2.0 compatible, and since I do not need them I don't feel qualified to change them. I.E. the Swazoo2 that is referred in the Seaside configuration. What do I do with these. I thought I should refer to the new Pharo20 repo (http://ss3.gemstone.com/ss/MetaRepoForPharo20) and thus automatically generating an error if this option is used under pharo2.0.

I know the startup panel under Pharo 2.0 no longer works. I know there is a start by Stephan Eggermont at the ESUG to port this to spec, but this is not finished. I don't know what to do with this, I disabled loading it under Pharo 2.0.

Any suggestions for better solutions for this are welcome.

Cheers,
Diego

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

Johan Brichau-2

Re: Configuration of Seaside Modifications

Hi diego,
Hi everyone,

I barely followed the recent discussions on working metacello configurations for Seaside3.0 and Seaside3.1
but I could not find any working configuration to load Seaside 3.0.7.1 in Pharo2.0.

Because I needed to get something working fast, I adapted the configuration ConfigurationOfSeaside30-dkh.379 by adding the following section:

spec for: #'pharo2.x' do:[
spec removeProject: 'OB'.
spec group: 'Core' overrides: #('Base' 'Development' 'RSS-Core' 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' 'Seaside-FileSystem' )
].

Which removes loading 'OB'. This at least enables loading Seaside3.0 in Pharo2.0.
Just a couple of tests on file directories are failing but that was expected.

Except the filedirectory issue, the following issues remain:
- BlockContext>>renderOn: is not loadable (package: Seaside-Pharo-Core) -> is it safe to remove it?
- deprecation warnings regarding includesSubString: (easy to fix)

@Diego: I think it makes sense to remove Swazoo from the Pharo2.0 section, similar to removing OB.

Sorry if these things have been done before, but I could not find anything regarding this in the Seaside30 repository. Tell me if I need to look elsewhere.
In the meantime, I'm continuing the above.

regards
Johan

On 22 Mar 2013, at 11:24, Diego Lont <[hidden email]> wrote:

> Hi all,
>
> Now that I am mailing about the configuration two more things:
>
> Some libraries are not made Pharo 2.0 compatible, and since I do not need them I don't feel qualified to change them. I.E. the Swazoo2 that is referred in the Seaside configuration. What do I do with these. I thought I should refer to the new Pharo20 repo (http://ss3.gemstone.com/ss/MetaRepoForPharo20) and thus automatically generating an error if this option is used under pharo2.0.
>
> I know the startup panel under Pharo 2.0 no longer works. I know there is a start by Stephan Eggermont at the ESUG to port this to spec, but this is not finished. I don't know what to do with this, I disabled loading it under Pharo 2.0.
>
> Any suggestions for better solutions for this are welcome.
>
> Cheers,
> Diego
>
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

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

DiegoLont

Re: Configuration of Seaside Modifications

Johan,

I should have probably posted my result until now. I posted them on the Pharo list. There are more libraries that I did not test, not only swazoo.

These configs are working (at least loading Seaside-Welcome, Magritte and Rest)

Regards,
Diego

On Mar 24, 2013, at 10:42 AM, Johan Brichau wrote:

> Hi diego,
> Hi everyone,
>
> I barely followed the recent discussions on working metacello configurations for Seaside3.0 and Seaside3.1
> but I could not find any working configuration to load Seaside 3.0.7.1 in Pharo2.0.
>
> Because I needed to get something working fast, I adapted the configuration ConfigurationOfSeaside30-dkh.379 by adding the following section:
>
> spec for: #'pharo2.x' do:[
> spec removeProject: 'OB'.
> spec group: 'Core' overrides: #('Base' 'Development' 'RSS-Core' 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' 'Seaside-FileSystem' )
> ].
>
> Which removes loading 'OB'. This at least enables loading Seaside3.0 in Pharo2.0.
> Just a couple of tests on file directories are failing but that was expected.
>
> Except the filedirectory issue, the following issues remain:
> - BlockContext>>renderOn: is not loadable (package: Seaside-Pharo-Core) -> is it safe to remove it?
> - deprecation warnings regarding includesSubString: (easy to fix)
>
> @Diego: I think it makes sense to remove Swazoo from the Pharo2.0 section, similar to removing OB.
>
> Sorry if these things have been done before, but I could not find anything regarding this in the Seaside30 repository. Tell me if I need to look elsewhere.
> In the meantime, I'm continuing the above.
>
> regards
> Johan
>
>
> On 22 Mar 2013, at 11:24, Diego Lont <[hidden email]> wrote:
>
>> Hi all,
>>
>> Now that I am mailing about the configuration two more things:
>>
>> Some libraries are not made Pharo 2.0 compatible, and since I do not need them I don't feel qualified to change them. I.E. the Swazoo2 that is referred in the Seaside configuration. What do I do with these. I thought I should refer to the new Pharo20 repo (http://ss3.gemstone.com/ss/MetaRepoForPharo20) and thus automatically generating an error if this option is used under pharo2.0.
>>
>> I know the startup panel under Pharo 2.0 no longer works. I know there is a start by Stephan Eggermont at the ESUG to port this to spec, but this is not finished. I don't know what to do with this, I disabled loading it under Pharo 2.0.
>>
>> Any suggestions for better solutions for this are welcome.
>>
>> Cheers,
>> Diego
>>
>> _______________________________________________
>> seaside-dev mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

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

ConfigurationOfMyProject-DiegoLont.1.mcz (6K) Download Attachment

ConfigurationOfPetitParser-DiegoLont.30.mcz (9K) Download Attachment

ConfigurationOfGrease-DiegoLont.189.mcz (45K) Download Attachment

ConfigurationOfMagritte3-DiegoLont.27.mcz (9K) Download Attachment

ConfigurationOfSeaside30-DiegoLont.415.mcz (194K) Download Attachment

ConfigurationOfSeasideRest-DiegoLont.13.mcz (10K) Download Attachment

Philippe Marschall

Re: Configuration for Pharo 2.0

In reply to this post by DiegoLont

On Fri, Mar 22, 2013 at 11:15 AM, Diego Lont <[hidden email]> wrote:
> Hi all,
>
> I am working on making a configuration for Pharo 2.0, that loads Magritte and Seaside Rest, and all that is needed for this.
>
> Currently I am busy with the configuration for Seaside. I created a version 3.1.1, since it needs to load the current bleeding edge (so newer versions). I think I have the right configuration now and all correct versions, but I get an error because the version 3.1.0 is broken for Pharo 2.0 (it refers to the packages 'Seaside-Pharo-Core' and 'Seaside-Tests-Pharo-Core', that are not defined under #'pharo20').
>
> I have the following questions:
> 1. Do you agree that I should create a version 3.1.1, or should it be 3.1.0.1?
> 2. What do I do with version 3.1.0, since this is broken?

Change 3.1.0, my view is that 3.1.0 is work in progress until we have
a working configuration so it's fine to change it.

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