Hi Peter,
>> Gofer new
>> smalltalkhubUser: 'Pier' project: 'Pillar';
>> configuration;
>> loadDevelopment.
Loads perfectly, and (as expected) loads fine with the new Metacello api:
Metacello new
configuration: 'Pillar';
repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main’
<http://smalltalkhub.com/mc/Pier/Pillar/main%E2%80%99>;
version: #development;
load.
>> Gofer new
>> url:'http://www.smalltalkhub.com/mc/phm/PierLoadExperiment/main
>> <http://www.smalltalkhub.com/mc/phm/PierLoadExperiment/main>';
>> package: 'ConfigurationOfPierLoadExperiment';
>> load.
>> ((Smalltalk at: #ConfigurationOfPierLoadExperiment) project version:
>> #stable) load.
Fails for me with: Name not found: Seaside-Pharo-Development
However it does load with the new api:
Metacello new
configuration: 'PierLoadExperiment';
repository: 'http://www.smalltalkhub.com/mc/phm/PierLoadExperiment/main
<http://www.smalltalkhub.com/mc/phm/PierLoadExperiment/main>';
version: #stable;
load.
Haven’t looked into why the Gofer load isn’t working, but since it’s working
with the new API, I don’t think we need to worry.
>> Gofer new
>> url:'http://www.smalltalkhub.com/mc/phm/PierLoadExperimentChanges/main
>> <http://www.smalltalkhub.com/mc/phm/PierLoadExperimentChanges/main>';
>> package: 'ConfigurationOfPierLoadExperimentChanges';
>> load.
>> ((Smalltalk at: #ConfigurationOfPierLoadExperimentChanges) project
>> version: #stable) load.
I stuck with the new api and used:
Metacello new
configuration: 'PierLoadExperimentChanges';
repository:
'http://www.smalltalkhub.com/mc/phm/PierLoadExperimentChanges/main
<http://www.smalltalkhub.com/mc/phm/PierLoadExperimentChanges/main>';
version: #stable;
load.
Loads fine.
>> ZnZincServerAdaptor startOn: 8080.
>>
>> PRPierFrame registerAsApplication: 'pier' kernel: (PRKernel
>> instanceNamed: 'pier').
>>
>> (WAAdmin defaultDispatcher handlerAt: 'pier' ) exceptionHandler:
>> WADebugErrorHandler .
>>
>> Then visit http://localhost:8080/pier <http://localhost:8080/pier>
All looks good.
>> Does it work? Is it loading the right things? (I didn't check the
>> tests yet, and i don't really understand metacello or Pier, just
>> playing by trial and error :), but if it works, maybe someone with
>> more experience can turn it into a config that will load from catalog
>> in Pharo6. Thx.
>>
>
> Anyone check this? If it's correct, how do I get the changes into Pier?
I saw a few errors in the Pillar tests, but it’s been about a year since I last
looked at Pier/Pillar so I’m not sure what to expect right now.
I loaded the Magritte tests, then loaded Pier-Tests-Model, Pier-Tests-Security,
and Pier-Tests-Seaside-Model, and found 997 run, 993 passes, 0 skipped, 0
expected failures, 4 failures, 0 errors, 0 unexpected passes.
Will be on leave for xmas from the end of next week so I’ll have more time to
look into this.
Cheers,
J
PS. FYI Just realised I was running all this in Pharo6
