yes, but the configurations should be also copied into the catalog repositories (I hate that, we need a better way).
also AFAIK, the new shiny way of loading Seaside is not to use ConfigurationOfSeaside30, but ConfigurationOfSeaside3 (which is confuse too... :( ) Esteban On Sep 25, 2013, at 8:01 AM, Stéphane Ducasse <stephane.duca...@inria.fr> wrote: > in fact grease should be loaded from > > SmHUB/Seaside/MetacelloConfigurations/ > > then the stable version loads version but still have dirty package because > the configurations do not load the package where > the trrimboth are removed from grease. > I reported that to Stefan Eggermont and waiting for his answer. > I thought that damien cassou addressed this because we had that problem in > Moose. > > > Stef > >> I can confirm the problem with #trimBoth, strange though that it does not >> simply override the system version but removes it. >> >> On 2013-09-24, at 19:35, Norbert Hartl <norb...@hartl.name> wrote: >> >>> Ok, the cause should be that a project I loaded pulled in Grease from >>> squeaksource/Seaside30. In the package Grease-Core-NickAger.70 there are >>> method extensions for String>>#trimBoth et al. For the current pharo these >>> are overrides. So probably seaside tried to update grease and thus removing >>> the methods from the system. As this is a image for playing I loaded all >>> kinds of stuff so I need some time to figure out which package it was. >>> >>> Norbert >>> >>> Am 25.09.2013 um 00:09 schrieb Camillo Bruni <camillobr...@gmail.com>: >>> >>>> Strange the build is green: >>>> >>>> https://ci.inria.fr/pharo-contribution/job/Seaside/ >>>> >>>> What kind of error do you get? >>>> Does it happen the same way when you download on of the images from >>>> Jenkins? >>>> >>>> On 2013-09-24, at 19:03, Norbert Hartl <norb...@hartl.name> wrote: >>>> >>>>> When loading seaside3 from the configuration browser it will break the >>>>> image badly. It isn't even possible to open a system browser after that. >>>>> What is the best way to load it manually? Or better is there something >>>>> new so the configuration browser can be directed to a better config? >>>>> >>>>> Norbert >>>> >>> >>> >> > >
