[Seaside-dev] Configuration of Seaside Modifications

[Diego Lont]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ConfigurationOfMyProject-DiegoLont.1.mcz
Type: application/octet-stream
Size: 5126 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20130324/125ef9ed/ConfigurationOfMyProject-DiegoLont.1-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ConfigurationOfPetitParser-DiegoLont.30.mcz
Type: application/octet-stream
Size: 7058 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20130324/125ef9ed/ConfigurationOfPetitParser-DiegoLont.30-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ConfigurationOfGrease-DiegoLont.189.mcz
Type: application/octet-stream
Size: 34371 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20130324/125ef9ed/ConfigurationOfGrease-DiegoLont.189-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ConfigurationOfMagritte3-DiegoLont.27.mcz
Type: application/octet-stream
Size: 7127 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20130324/125ef9ed/ConfigurationOfMagritte3-DiegoLont.27-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ConfigurationOfSeaside30-DiegoLont.415.mcz
Type: application/octet-stream
Size: 145261 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20130324/125ef9ed/ConfigurationOfSeaside30-DiegoLont.415-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ConfigurationOfSeasideRest-DiegoLont.13.mcz
Type: application/octet-stream
Size: 7517 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20130324/125ef9ed/ConfigurationOfSeasideRest-DiegoLont.13-0001.obj
-------------- next part --------------

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 <diego.lont at delware.nl> 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
>> seaside-dev at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
> 
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev