How should I load Seaside/Bootstrap in Pharo 7 ?
Hi, [ Max replied on the Seaside ML where I originally posted:
We don't have a build for Pharo 7 yet. Loading from github would be the recommended way. A quick look makes me think that it will require a bit of work to get the baseline set up correctly. I can't promise anything before next weekend.
I think it is important that Seaside works on Pharo 7, it is an important use case and test during development, and very necessary as well. ] I am stuck trying to move my main development to Pharo 7 because I have trouble loading Seaside (which I normally do indirectly by loading the Bootstrap project). Here is my dependency: project: 'Bootstrap' with: [ spec className: 'ConfigurationOfBootstrap'; repository: 'http://smalltalkhub.com/mc/TorstenBergmann/Bootstrap/main/'; versionString: #stable ] I also tried the following: Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load. What is the right/recommended way to do it ? Thx, Sven
Nobody (trying to use|using) Seaside on Pharo 7 ??
On 6 Nov 2017, at 09:51, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Hi,
[
Max replied on the Seaside ML where I originally posted:
We don't have a build for Pharo 7 yet. Loading from github would be the recommended way. A quick look makes me think that it will require a bit of work to get the baseline set up correctly. I can't promise anything before next weekend.
I think it is important that Seaside works on Pharo 7, it is an important use case and test during development, and very necessary as well.
]
I am stuck trying to move my main development to Pharo 7 because I have trouble loading Seaside (which I normally do indirectly by loading the Bootstrap project). Here is my dependency:
project: 'Bootstrap' with: [ spec className: 'ConfigurationOfBootstrap'; repository: 'http://smalltalkhub.com/mc/TorstenBergmann/Bootstrap/main/'; versionString: #stable ]
I also tried the following:
Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load.
What is the right/recommended way to do it ?
Thx,
Sven
On 7 Nov 2017, at 21:17, stephan <stephan@stack.nl> wrote:
On 07-11-17 21:11, Sven Van Caekenberghe wrote:
Nobody (trying to use|using) Seaside on Pharo 7 ??
I already did one pull request.
OK, thanks, let's hope things keep moving forward. I am ready to test and help.
That is not enough because of the flattening of traits
Yes, that is a though one for external libraries.
Stephan
On 7 Nov 2017, at 17:22, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 7 Nov 2017, at 21:17, stephan <stephan@stack.nl> wrote:
On 07-11-17 21:11, Sven Van Caekenberghe wrote:
Nobody (trying to use|using) Seaside on Pharo 7 ??
I already did one pull request.
OK, thanks, let's hope things keep moving forward. I am ready to test and help.
That is not enough because of the flattening of traits
Yes, that is a though one for external libraries.
why? (not putting it in doubt, just wanting to know ;) ) Esteban
Stephan
On 07-11-17 21:25, Esteban Lorenzano wrote:
On 7 Nov 2017, at 17:22, Sven Van Caekenberghe <sven@stfx.eu> wrote: Yes, that is a though one for external libraries.
why? (not putting it in doubt, just wanting to know ;) )
Ah, well, it just means that we'll want to replace some code written for pharo 3 or 4 and add it there. Just unplanned work to keep up with Pharo changes. And would have been better handled as a rewrite rule, I think. Stephan
On 7 Nov 2017, at 21:25, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 7 Nov 2017, at 17:22, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 7 Nov 2017, at 21:17, stephan <stephan@stack.nl> wrote:
On 07-11-17 21:11, Sven Van Caekenberghe wrote:
Nobody (trying to use|using) Seaside on Pharo 7 ??
I already did one pull request.
OK, thanks, let's hope things keep moving forward. I am ready to test and help.
That is not enough because of the flattening of traits
Yes, that is a though one for external libraries.
why? (not putting it in doubt, just wanting to know ;) )
Like I said in another email, for example STON adds methods to Class, MetaClass and ClassDescription *Traits*. Now it has to add to the classes itself (right ?). So a single code base cannot deal with Pharo 7 and older version without splitting. I like to keep simple projects like STON simple (Seaside is huge in comparison and deals with this stuff all the time and already has the complex infrastructure for it).
Esteban
Stephan
Hi Sven 2017-11-07 21:35 GMT+01:00 Sven Van Caekenberghe <sven@stfx.eu>:
Like I said in another email, for example STON adds methods to Class, MetaClass and ClassDescription *Traits*. Now it has to add to the classes itself (right ?). So a single code base cannot deal with Pharo 7 and older version without splitting. I like to keep simple projects like STON simple (Seaside is huge in comparison and deals with this stuff all the time and already has the complex infrastructure for it).
I think it should not be problem for compatibility. Because with flattening you will just has duplication of code for classes and traits but classes and traits existed in Pharo all the time. So flattened version of STON will correctly work in older Pharo's.
On 7 Nov 2017, at 22:59, Denis Kudriashov <dionisiydk@gmail.com> wrote:
Hi Sven
2017-11-07 21:35 GMT+01:00 Sven Van Caekenberghe <sven@stfx.eu>:
Like I said in another email, for example STON adds methods to Class, MetaClass and ClassDescription *Traits*. Now it has to add to the classes itself (right ?). So a single code base cannot deal with Pharo 7 and older version without splitting. I like to keep simple projects like STON simple (Seaside is huge in comparison and deals with this stuff all the time and already has the complex infrastructure for it).
I think it should not be problem for compatibility. Because with flattening you will just has duplication of code for classes and traits but classes and traits existed in Pharo all the time. So flattened version of STON will correctly work in older Pharo's.
I didn't look careful enough to realise you made your own fork. Still, trying Metacello new baseline:'Seaside3'; repository: 'github://pavel-krivanek/Seaside:minimalPharo/repository'; load. In full Pharo 7, 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. Thanks for helping out. Sven
hmm, I suppose it is related to the latest Metacello update. -- Pavel 2017-11-07 23:45 GMT+01:00 Sven Van Caekenberghe <sven@stfx.eu>:
On 7 Nov 2017, at 22:59, Denis Kudriashov <dionisiydk@gmail.com> wrote:
Hi Sven
2017-11-07 21:35 GMT+01:00 Sven Van Caekenberghe <sven@stfx.eu>:
Like I said in another email, for example STON adds methods to Class, MetaClass and ClassDescription *Traits*. Now it has to add to the classes itself (right ?). So a single code base cannot deal with Pharo 7 and older version without splitting. I like to keep simple projects like STON simple (Seaside is huge in comparison and deals with this stuff all the time and already has the complex infrastructure for it).
I think it should not be problem for compatibility. Because with flattening you will just has duplication of code for classes and traits but classes and traits existed in Pharo all the time. So flattened version of STON will correctly work in older Pharo's.
I didn't look careful enough to realise you made your own fork.
Still, trying
Metacello new baseline:'Seaside3'; repository: 'github://pavel-krivanek/Seaside:minimalPharo/repository'; load.
In full Pharo 7, 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.
Thanks for helping out.
Sven
I successfully loaded Seaside into minimal Pharo 7 image: http://forum.world.st/Seaside-on-minimal-Pharo-7-0-td4979763.html -- Pavel 2017-11-07 21:11 GMT+01:00 Sven Van Caekenberghe <sven@stfx.eu>:
Nobody (trying to use|using) Seaside on Pharo 7 ??
On 6 Nov 2017, at 09:51, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Hi,
[
Max replied on the Seaside ML where I originally posted:
We don't have a build for Pharo 7 yet. Loading from github would be the recommended way. A quick look makes me think that it will require a bit of work to get the baseline set up correctly. I can't promise anything before next weekend.
I think it is important that Seaside works on Pharo 7, it is an important use case and test during development, and very necessary as well.
]
I am stuck trying to move my main development to Pharo 7 because I have trouble loading Seaside (which I normally do indirectly by loading the Bootstrap project). Here is my dependency:
project: 'Bootstrap' with: [ spec className: 'ConfigurationOfBootstrap'; repository: 'http://smalltalkhub.com/mc/TorstenBergmann/Bootstrap/ main/'; versionString: #stable ]
I also tried the following:
Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load.
What is the right/recommended way to do it ?
Thx,
Sven
On 07-11-17 22:34, Pavel Krivanek wrote:
I successfully loaded Seaside into minimal Pharo 7 image:
http://forum.world.st/Seaside-on-minimal-Pharo-7-0-td4979763.html
Well, loading code that adds methods to the still existing traits works. But if those traits are no longer used, that might result in silent failure. That actually needs a quality rule (or rewrite to also flatten) Stephan
participants (5)
-
Denis Kudriashov -
Esteban Lorenzano -
Pavel Krivanek -
stephan -
Sven Van Caekenberghe