[Pharo-project] Installing and testing Seaside 2.8.4, Magritte and Pier in Pharo 1.1
Hi seasideers. I was loading all this stuff of PharoCore 1.1 and see if everything seems to be working. At this is the case :) However, I have 2 tests with errors and this is due to send to BlockClosure
fixTemps which is deprecated in Pharo 1.1 The fix is easy, just remove the send of fixTemps, but I am not sure the impact of this in other dialects. But would be cool not to have the deprecated warning when loading.
The places are Amb >> oneOf: aCollection and Amb >> valueOfOneOf: blockCollection Then I have two failing but I don't understand why: WABacktrackingTest >> testOrderedCollection I don't know why here, but after "original removeLast." snapshot has the elements "1" and "nil" instead of "1" and "2", and thus, it fails in self assert: original asArray = #(1 2) The other is: WABacktrackingTest >> testDictionary It is failing in "self assert: (original at: 1 ifAbsent: []) = #a." because original shows -> a Dictionary(2->#b 3->#d ) I know your effort is now in Seaside3 but having all green tests with Pharo 1.1 would be really cool :) Last thing, if you want to test it, just take a PharoCore 1.1 image, for example: https://gforge.inria.fr/frs/download.php/26995/PharoCore-1.1-11357-UNSTABLE.... And then evaluate: (Smalltalk at: #Gofer) new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside'; load. ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8'. and run tests :) Thanks Mariano
Seaside 2.8 and repective versions of Magritte and Pier are not actively developed anymore. I suugest to drop support for Pharo 1.1. Lukas On Sunday, May 16, 2010, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
Hi seasideers. I was loading all this stuff of PharoCore 1.1 and see if everything seems to be working. At this is the case :) However, I have 2 tests with errors and this is due to send to BlockClosure >> fixTemps which is deprecated in Pharo 1.1 The fix is easy, just remove the send of fixTemps, but I am not sure the impact of this in other dialects. But would be cool not to have the deprecated warning when loading.
The places are Amb >> oneOf: aCollection and Amb >> valueOfOneOf: blockCollection
Then I have two failing but I don't understand why:
WABacktrackingTest >> testOrderedCollection
I don't know why here, but after "original removeLast."Â snapshot has the elements "1" and "nil" instead of "1" and "2", and thus, it fails in self assert: original asArray = #(1 2)
The other is:
WABacktrackingTest >> testDictionary
It is failing in "self assert: (original at: 1 ifAbsent: []) = #a." because original shows ->Â Â a Dictionary(2->#b 3->#d )
I know your effort is now in Seaside3 but having all green tests with Pharo 1.1 would be really cool :)
Last thing, if you want to test it, just take a PharoCore 1.1 image, for example:
https://gforge.inria.fr/frs/download.php/26995/PharoCore-1.1-11357-UNSTABLE....
And then evaluate:
(Smalltalk at: #Gofer) new    squeaksource: 'MetacelloRepository';    package: 'ConfigurationOfSeaside';    load.
ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8'.
and run tests :)
Thanks
Mariano
-- Lukas Renggli www.lukas-renggli.ch
+1 We do not have the engineer force to support that many old versions. Stef On May 16, 2010, at 6:22 PM, Lukas Renggli wrote:
Seaside 2.8 and repective versions of Magritte and Pier are not actively developed anymore. I suugest to drop support for Pharo 1.1.
Lukas
On Sunday, May 16, 2010, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
Hi seasideers. I was loading all this stuff of PharoCore 1.1 and see if everything seems to be working. At this is the case :) However, I have 2 tests with errors and this is due to send to BlockClosure >> fixTemps which is deprecated in Pharo 1.1 The fix is easy, just remove the send of fixTemps, but I am not sure the impact of this in other dialects. But would be cool not to have the deprecated warning when loading.
The places are Amb >> oneOf: aCollection and Amb >> valueOfOneOf: blockCollection
Then I have two failing but I don't understand why:
WABacktrackingTest >> testOrderedCollection
I don't know why here, but after "original removeLast." snapshot has the elements "1" and "nil" instead of "1" and "2", and thus, it fails in self assert: original asArray = #(1 2)
The other is:
WABacktrackingTest >> testDictionary
It is failing in "self assert: (original at: 1 ifAbsent: []) = #a." because original shows -> a Dictionary(2->#b 3->#d )
I know your effort is now in Seaside3 but having all green tests with Pharo 1.1 would be really cool :)
Last thing, if you want to test it, just take a PharoCore 1.1 image, for example:
https://gforge.inria.fr/frs/download.php/26995/PharoCore-1.1-11357-UNSTABLE....
And then evaluate:
(Smalltalk at: #Gofer) new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside'; load.
ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8'.
and run tests :)
Thanks
Mariano
-- Lukas Renggli www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Sun, 16 May 2010, Lukas Renggli wrote:
Seaside 2.8 and repective versions of Magritte and Pier are not actively developed anymore. I suugest to drop support for Pharo 1.1.
It's a bit strange that the latest Seaside release is not supported anymore. Levente
Lukas
On Sunday, May 16, 2010, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
Hi seasideers. I was loading all this stuff of PharoCore 1.1 and see if everything seems to be working. At this is the case :) However, I have 2 tests with errors and this is due to send to BlockClosure >> fixTemps which is deprecated in Pharo 1.1 The fix is easy, just remove the send of fixTemps, but I am not sure the impact of this in other dialects. But would be cool not to have the deprecated warning when loading.
The places are Amb >> oneOf: aCollection and Amb >> valueOfOneOf: blockCollection
Then I have two failing but I don't understand why:
WABacktrackingTest >> testOrderedCollection
I don't know why here, but after "original removeLast."Â snapshot has the elements "1" and "nil" instead of "1" and "2", and thus, it fails in self assert: original asArray = #(1 2)
The other is:
WABacktrackingTest >> testDictionary
It is failing in "self assert: (original at: 1 ifAbsent: []) = #a." because original shows ->Â Â a Dictionary(2->#b 3->#d )
I know your effort is now in Seaside3 but having all green tests with Pharo 1.1 would be really cool :)
Last thing, if you want to test it, just take a PharoCore 1.1 image, for example:
https://gforge.inria.fr/frs/download.php/26995/PharoCore-1.1-11357-UNSTABLE....
And then evaluate:
(Smalltalk at: #Gofer) new    squeaksource: 'MetacelloRepository';    package: 'ConfigurationOfSeaside';    load.
ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8'.
and run tests :)
Thanks
Mariano
-- Lukas Renggli www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Sunday, May 16, 2010, Levente Uzonyi <leves@elte.hu> wrote:
On Sun, 16 May 2010, Lukas Renggli wrote:
Seaside 2.8 and repective versions of Magritte and Pier are not actively developed anymore. I suugest to drop support for Pharo 1.1.
It's a bit strange that the latest Seaside release is not supported anymore.
The latest Seaside release is Seaside 3.0a5. Lukas
Levente
Lukas
On Sunday, May 16, 2010, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
Hi seasideers. I was loading all this stuff of PharoCore 1.1 and see if everything seems to be working. At this is the case :) However, I have 2 tests with errors and this is due to send to BlockClosure >> fixTemps which is deprecated in Pharo 1.1 The fix is easy, just remove the send of fixTemps, but I am not sure the impact of this in other dialects. But would be cool not to have the deprecated warning when loading.
The places are Amb >> oneOf: aCollection and Amb >> valueOfOneOf: blockCollection
Then I have two failing but I don't understand why:
WABacktrackingTest >> testOrderedCollection
I don't know why here, but after "original removeLast."Â snapshot has the elements "1" and "nil" instead of "1" and "2", and thus, it fails in self assert: original asArray = #(1 2)
The other is:
WABacktrackingTest >> testDictionary
It is failing in "self assert: (original at: 1 ifAbsent: []) = #a." because original shows ->Â Â a Dictionary(2->#b 3->#d )
I know your effort is now in Seaside3 but having all green tests with Pharo 1.1 would be really cool :)
Last thing, if you want to test it, just take a PharoCore 1.1 image, for example:
https://gforge.inria.fr/frs/download.php/26995/PharoCore-1.1-11357-UNSTABLE....
And then evaluate:
(Smalltalk at: #Gofer) new    squeaksource: 'MetacelloRepository';    package: 'ConfigurationOfSeaside';    load.
ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8'.
and run tests :)
Thanks
Mariano
-- Lukas Renggli www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli www.lukas-renggli.ch
On Sun, 16 May 2010, Lukas Renggli wrote:
On Sunday, May 16, 2010, Levente Uzonyi <leves@elte.hu> wrote:
On Sun, 16 May 2010, Lukas Renggli wrote:
Seaside 2.8 and repective versions of Magritte and Pier are not actively developed anymore. I suugest to drop support for Pharo 1.1.
It's a bit strange that the latest Seaside release is not supported anymore.
The latest Seaside release is Seaside 3.0a5.
Doesn't 'a' mean alpha? Levente
Lukas
Levente
Lukas
On Sunday, May 16, 2010, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
Hi seasideers. I was loading all this stuff of PharoCore 1.1 and see if everything seems to be working. At this is the case :) However, I have 2 tests with errors and this is due to send to BlockClosure >> fixTemps which is deprecated in Pharo 1.1 The fix is easy, just remove the send of fixTemps, but I am not sure the impact of this in other dialects. But would be cool not to have the deprecated warning when loading.
The places are Amb >> oneOf: aCollection and Amb >> valueOfOneOf: blockCollection
Then I have two failing but I don't understand why:
WABacktrackingTest >> testOrderedCollection
I don't know why here, but after "original removeLast."Â snapshot has the elements "1" and "nil" instead of "1" and "2", and thus, it fails in self assert: original asArray = #(1 2)
The other is:
WABacktrackingTest >> testDictionary
It is failing in "self assert: (original at: 1 ifAbsent: []) = #a." because original shows ->Â Â a Dictionary(2->#b 3->#d )
I know your effort is now in Seaside3 but having all green tests with Pharo 1.1 would be really cool :)
Last thing, if you want to test it, just take a PharoCore 1.1 image, for example:
https://gforge.inria.fr/frs/download.php/26995/PharoCore-1.1-11357-UNSTABLE....
And then evaluate:
(Smalltalk at: #Gofer) new    squeaksource: 'MetacelloRepository';    package: 'ConfigurationOfSeaside';    load.
ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8'.
and run tests :)
Thanks
Mariano
-- Lukas Renggli www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli www.lukas-renggli.ch _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
participants (4)
-
Levente Uzonyi -
Lukas Renggli -
Mariano Martinez Peck -
Stéphane Ducasse