[Seaside] Setup Pier environment
dtrussardi at tiscali.it
dtrussardi at tiscali.it
Wed Oct 22 12:52:43 UTC 2014
Ciao,
i have very difficulty to setup the environment for test Pier into Pharo using Seaside3.0.x
I do:
Gofer new
url:'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
package: 'ConfigurationOfSeaside3';
load.
((Smalltalk at: #ConfigurationOfSeaside3) project version: '3.0.15') load.
ConfigurationOfSeaside3 project currentVersion. > 3.0.1.5 OK
Gofer new
url:'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
package: 'ConfigurationOfMagritte3';
load.
( ConfigurationOfMagritte3 project version: '3.0') load.
ConfigurationOfMagritte3 project currentVersion. > 3.1.4 ( not 3.0 because ? )
Gofer new
url:'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
package: 'ConfigurationOfMagritte3AddOns';
load.
( ConfigurationOfMagritte3AddOns project version: '3.0.0') load.
ConfigurationOfMagritte3AddOns project currentVersion. > 3.0.0 OK
Gofer new
url:'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
package: 'ConfigurationOfPier3';
load.
( ConfigurationOfPier3 project version: '3.0.0') load.
ConfigurationOfPier3 project currentVersion. > 3.0.1 ( not 3.0.0 because ?
Gofer new
url:'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main';
package: 'ConfigurationOfPier3AddOns';
load.
( ConfigurationOfPier3AddOns project version: '3.0.3') load.
ConfigurationOfPier3AddOns project currentVersion. > 3.1.1 ( not 3.0.3 because ? )
At the end the piersetup don't work.
Some time ago i have similar problem into GLASS.
Dale proposed to load directly the package with the code:
GsDeployer
bulkMigrate: [
{#('Seaside3' '3.0.13' 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main').
#('ZincHTTPComponents' '1.1' 'http://www.squeaksource.com/ZincHTTPComponents').
#('Magritte3' '3.0' 'http://www.squeaksource.com/MetacelloRepository').
#('Magritte3AddOns' '3.0.0' 'http://www.squeaksource.com/MetacelloRepository').
#('Pier3' '3.0.0' 'http://www.squeaksource.com/MetacelloRepository').
#('Pier3AddOns' '3.0.3' 'http://www.squeaksource.com/MetacelloRepository')}
do: [ :ar |
| projectName version repository |
projectName := ar at: 1.
version := ar at: 2.
repository := ar at: 3.
Metacello new
configuration: projectName;
repository: repository;
get.
Metacello new
configuration: projectName;
version: version;
repository: repository;
onUpgrade: [ :ex :existing :new |
existing locked
ifTrue: [ ex disallow ]
ifFalse: [ ex allow ] ];
onConflict: [ :ex | ex disallow ];
load.
Metacello new
configuration: projectName;
version: version;
repository: repository;
lock ] ]
How i can do it into Pharo image?
Thanks,
Dario
> Johan,
>
>> Dario,
>>
>> In a previous email, I remarked that the Pier code does not seem to be ported to Seaside 3.1.x
>> If you want to use Pier, use Seaside 3.0.x
>
> But how i can load it?
>
> I do:
>
> Gofer it
> squeaksource: 'MetacelloRepository';
> package: 'ConfigurationOfPier3AddOns';
> load.
>
> ( ConfigurationOfPier3AddOns project version: '3.0.4') load.
>
> it load in any case Seaside 3.1.3.1
>
> Thanks,
>
> Dario
>
>
>> In the other case, you might want to check out the changelog and port Pier to Seaside 3.1.x [1,2]
>>
>> [1] https://code.google.com/p/seaside/wiki/Seaside310Changelog
>> [2] https://code.google.com/p/seaside/wiki/Seaside311Changelog
>>
>> On 22 Oct 2014, at 11:23, dtrussardi at tiscali.it wrote:
>>
>>> Ciao,
>>>
>>> Whereas the problems of my last e-mail are still open,
>>>
>>> (I wonder if others have the same problems)
>>>
>>> i add a few notes about the NAFileUpload support:
>>>
>>> 1) Some instance methods of NAFileUpload class, reference the WARenderCanvas class
>>>
>>> but WARenderCanvas is not in the system. ( Change it to WACanvas ? )
>>>
>>>
>>> 2) NAFileUploadConfigurator class method
>>>
>>> fileuploadPathRootDefault
>>>
>>> ^ FileDirectory default pathName, GRPlatform current pathSeparator, 'uploadedFiles'
>>>
>>> call pathName, but it's deprecate.
>>>
>>> I think to change it with fullName method.
>>>
>>>
>>>
>>> These are a few considerations that together with the previous does not allow me to test the Pier support into Pharo.
>>>
>>> If i right understand, this in any case is the area on which to work.
>>>
>>> Pier previous versions i believe are misaligned.
>>>
>>> It's right ?
>>>
>>> Thanks for any help, considerations,
>>>
>>> Dario
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> seaside mailing list
>>> seaside at lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20141022/6738d721/attachment.htm
More information about the seaside
mailing list