[Glass] Install last master branch of Seaside

Tue Sep 25 23:31:45 PDT 2018

> Hi Dario,
> 
> Since Pillar was extracted from Pier and extended, some of those extensions use traits in Pharo, so it’s no longer a smalltalk community project - rather Pharo only for now.

It's possible to move methods from Pharo Traits to the proper Pier superclass (or Object class) and everything should be fine IMHO.
But yes, it's some work, you can make a porting work on the Pharo side and then export final work to the Gemstone, or hack package loader on Gemstone side or something like this (even more work)...

If I understood it well, something new about project loading/managing is baking at Gemstone - new Tonel format etc etc. It would be nice if Gemstone were ready for new things (Traits) coming from Pharo and make needed conversions automatically  - lot of stuff/libraries comes from Pharo and the gap expands...

pf

> 
> I had a go at porting it to GemStone some time back, and getting Pier to work in GS3.4.x and Seaside 3.2 with some success, but I haven’t had a project that needed it so it hasn’t been revisited in a while.
> 
> You can find it at:
> 
> https://github.com/JupiterSmalltalk/Pier <https://github.com/JupiterSmalltalk/Pier>
> https://github.com/JupiterSmalltalk/Pillar <https://github.com/JupiterSmalltalk/Pillar>
> 
> You should be able to load the Pier configuration and it will find the right dependencies - sorry I’m not able to test that now for you but I’ll give it a go next weekend.
> 
> Cheers,
> 
> J
> 
> > On 26 Sep 2018, at 3:42 am, Dale Henrichs via Glass <glass at lists.gemtalksystems.com> wrote:
> > 
> > 
> > 
> > On 09/21/2018 03:43 AM, Trussardi Dario Romano via Glass wrote:
> >> Ciao Dale, Jupiter,
> >> 
> >> 
> >> 	Now i need to load the Magritte support and Pier CMS in Gemstone.
> > Dario,
> > 
> > If you are going to use Pier, then I think that you need to consider the fact that Pier probably does not work on top of the latest Seaside version ... so you probably need to install Pier and then let the Pier baseline drive which version of Magritte and Seaside are needed ...
> > 
> > Poking around on my machine I found that I hav a Pier stone for GemStone 3.2.11 from 2015 ... and I ran the tODE install and it loaded successfully ... here's the relevant entries from the project list (you can see which versions of things it is using...:
> > 
> > --------------------
> > |+ Seaside3|               2984ce1 [gs_master]               filetree://$GS_HOME/shared/repos/Seaside31/repository              
> > GsDevKit_home              6434a73 [issue_200]               $GS_HOME
> > FastCGI Project            0.237 [release]                  http://seaside.gemtalksystems.com/ss/MetacelloRepository <http://seaside.gemtalksystems.com/ss/MetacelloRepository>
> > |FileTree|                 e53944d [gemstone_24_dev]         filetree:///export/foos1/users/dhenrich/dev/_home/shared/repos/filetree/repository
> > Gofer                      1.0.5.4 [release]                 http://seaside.gemtalksystems.com/ss/metacello <http://seaside.gemtalksystems.com/ss/metacello>
> > |Grease|                   c4715e9 [dev]                     filetree:///export/foos1/users/dhenrich/dev/_home/shared/repos/Grease/repository
> > |Metacello|                2f5cd0f [dev]                     filetree:///export/foos1/users/dhenrich/dev/_home/shared/repos/metacello-work/repository
> > |Pier3|                    3.0.0 [release]                   http://www.squeaksource.com/MetacelloRepository <http://www.squeaksource.com/MetacelloRepository>
> > |Ston|                     25aace1 ^ ad9d4bc [gemstone_dev]  filetree:///export/foos1/users/dhenrich/dev/_home/shared/repos/ston/repository
> > |Tode|                     de2b1a9 ^ 28c92f2 [dev]           filetree:///export/foos1/users/dhenrich/dev/_home/shared/repos/tode/repository
> > |GsApplicationTools|       898232b [master]                  filetree://$GS_HOME/shared/repos/gsApplicationTools/repository
> > |RB|                       f67b448 ^ 5e8b88c [dev]           filetree:///export/foos1/users/dhenrich/dev/_home/shared/repos/rb/repository
> > |GLASS1|                   ca1ef30 [dev]                     filetree:///export/foos1/users/dhenrich/dev/_home/shared/repos/glass/repository
> > |Magritte3|                daf2b1d [master]                  filetree://$GS_HOME/shared/repos/Magritte3/repository
> > Swazoo2                    2.2.0.7 [release]                 http://smalltalkhub.com/mc/Swazoo/Swazoo/main <http://smalltalkhub.com/mc/Swazoo/Swazoo/main>
> > |ZincHTTPComponents|       36265f1 [dev]                     filetree:///export/foos1/users/dhenrich/dev/_home/shared/repos/zinc/repository
> > |XMLSupport|               1.2.2.1                          http://seaside.gemtalksystems.com/ss/MetacelloRepository <http://seaside.gemtalksystems.com/ss/MetacelloRepository>
> > 
> > It looks like Pier is using Seaside3.1 ... I haven't run the tests, but I assume that I created this stone because these were versions of projects that were "know to work together" ... I haven't tried this on a later version of GemStone ... we could probably make it work on later versions of GemStone, but I think you should perhaps evaluate the Pier environment in a 3.2.11 stone using the tode install scripts that I used ...
> > 
> > If you are happy with the 3.2.11 setup, then we can work together to make sure that this environment works in a recent version of GemStone ...
> > 
> > I also don't know if there is a later version of Pier available or not ... if there is we can work together to get it ported/running in GemStone as well ...
> > 
> > Let me know if you want to try loading up Pier 3.0.0 using my tODE scripts and I'll package them up for you...
> > 
> > Dale
> > _______________________________________________
> > Glass mailing list
> > Glass at lists.gemtalksystems.com
> > http://lists.gemtalksystems.com/mailman/listinfo/glass
> 

> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass