Actually - it looks like a caching thing - as in a clean image, if I use my reduced baseline (without the Tests) it loads (albeit with a deprecation warning).
Does anyone know what you have to clear to get it to honour the baseline code you actually have in your image - as its a faff to have to use a clean image? (This is a constant frustration in Smalltalk - caches are useful and all, but there isn’t a consistent way to reset frameworks - I really long for a pragma for reset, and a menu item somewhere that shows you a reset menu for all the frameworks you have loaded, so its easy to clear things and get to a consistent state…) Tim > On 21 Jun 2018, at 14:58, Tim Mackinnon <[email protected]> wrote: > > Hi guys - how did you load Seaside into Pharo 7 as part of a baseline? I’ve > hit a similar same problem and am getting a walkback error when trying to > load a baseline for a project I wanted to try on P7 which uses seaside. > > I get: MetacelloNameNotDefinedError: project group, or package named: > 'Seaside-Pharo-Development' not found when used in requires: or includes: > field of package: 'Seaside-Tests-Pharo-Development' for version: baseline of > BaselineOfSeaside3. > > My baseline has the following: > > setUpDependencies: spec > > spec > baseline: 'Seaside3' > with: [ spec > repository: > 'github://SeasideSt/Seaside:master/repository'; > loads: #('Seaside-Environment') ]. > > > If did have (copied from a Willow example) - and I’m wondering if something > is getting cached and that its not actually using the above - but I’m not > clear on how to ensure any caches are cleared? > > spec > baseline: 'Seaside3' > with: [ spec > repository: > 'github://SeasideSt/Seaside:v3.2.4/repository'; > loads: #('Seaside-Environment' 'JQuery' 'Zinc') > ]; > project: 'Seaside3-Tests' copyFrom: 'Seaside3' with: [ spec > loads: #('Seaside-Tests-Core') ]. > > Any tips gratefully received. > > Tim > >> On 24 May 2018, at 16:02, Sven Van Caekenberghe <[email protected]> wrote: >> >> Hi Torsten, >> >> Thanks for taking care. >> >> I can confirm, from a quick test, that Seaside loads/works fine in the >> latest Pharo 7. >> >> I had trouble opening the Seaside Control Panel, 10s of deprecation warnings >> opening for the icon base64 decoding, I had to comment out the #deprecated: >> message send in #mimeDecodeToBytes: >> >> I don't understand why the Grease stream tests are failing since they seem >> to be testing ReadWriteStream, a class that was not changed, at all. >> >> Sven >> >>> On 22 May 2018, at 22:01, Torsten Bergmann <[email protected]> wrote: >>> >>> Just as an info: after fixing the #mimeDecodeToBytes: issue with recent >>> image 70934 and later it is possible >>> to load Seaside again from GitHub using >>> >>> Metacello new >>> baseline:'Seaside3'; >>> repository: 'github://SeasideSt/Seaside:master/repository'; >>> load >>> >>> >>> into a recent Pharo 7.0 (load instruction as recommended on >>> https://github.com/SeasideSt/Seaside). >>> >>> For the deprecated warnings you either "Proceed" or disable them for the >>> time being. >>> >>> 799 of 806 Seaside tests passes >>> 470 of 457 Grease tests passes >>> >>> primarily failing to to non-compatible streams. Seaside and Grease tests >>> seem to test >>> some ANSI related things - who fail now. >>> >>> _______________________________________________ >>> seaside-dev mailing list >>> [email protected] >>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev >> >> > >
