Snapshotcello & Pharo 20: issues...
Locked
Snapshotcello & Pharo 20: issues...
 
|
I am giving a shot at Snapshotcello since it looks like a superb solution for creating images properly from a complex configuration.
From http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-ready, I tried to craft a call for my configuration.
I've loaded ConfigurationOfSnapshotcello #development in Pharo20. Then tried the calls and there were some API changes (from the tests, I found out the incantation).
Snapshotcello new configurationClass: ConfigurationOfHOWebStack; sourceVersion: #development;
targetVersion: '0.3-snapshot'; snapshot. But then I faced a problem with a DNU on 'asEnglishPlural' for a categorization. No big deal, I commented that out as I could live with that.
But then I faced something more difficult (the compileSnapshotWithCurrentPackages: aNumber worked in the self generateSnapshotWithCurrentPackages: aNumber...
It took a lot of time to get the whole config loaded... (so, the progressbars worked and worked)
Then, it failed on giving: "PostMortem: MNU: nil>>ancestry" self workingCopiesFromConfiguration do: [ :each |
codeStream tab; tab;
nextPutAll: '#(';
nextPut: $';
nextPutAll: each ancestry ancestorString;
nextPutAll: '.mcz';
nextPut: $';
nextPutAll: ' ';
nextPut: $';
nextPutAll: (self repositoryNameForWorkingCopy: each);
nextPut: $';
nextPutAll: ' ';
nextPut: $';
nextPutAll: each package name;
nextPut: $';
nextPutAll: ' ) ' ]
separatedBy: [ codeStream cr ].
codeStream
cr;
tab;
nextPutAll: ')'.
^ codeStream contents Oops. each is nil... Anyone having faced that? Debugging...
Phil |
Re: Snapshotcello & Pharo 20: issues...
|
|
this is strange since I could snapshot moose and synectique using it.
I'm about to write a boring report so I'm not allowed to open Pharo right now.
|
Re: Snapshotcello & Pharo 20: issues...
|
|
Strange. I've never encountered this. each should be a MCWorkingCopy. I will try to take a look, but it might take a while.
In the meantime, can you locate the package in your configuration? Is it possible that something went wrong with Monticello? Cheers, Doru On Wed, Sep 25, 2013 at 9:29 PM, Stéphane Ducasse <[hidden email]> wrote:
"Every thing has its own flow"
|
|
|
Hi, so what are we going to do with 'asEnglishPlural' missing from the ByteString? Uko On 26 вер. 2013, at 09:52, Tudor Girba <[hidden email]> wrote:
|
Re: Snapshotcello & Pharo 20: issues...
|
|
I am not sure I understand. Why is this question relevant for the present discussion?
Doru On Sep 26, 2013, at 7:36 PM, Yuriy Tymchuk <[hidden email]> wrote: > Hi, > > so what are we going to do with 'asEnglishPlural' missing from the ByteString? > > Uko > > On 26 вер. 2013, at 09:52, Tudor Girba <[hidden email]> wrote: > >> Strange. I've never encountered this. >> >> each should be a MCWorkingCopy. >> >> I will try to take a look, but it might take a while. >> >> In the meantime, can you locate the package in your configuration? Is it possible that something went wrong with Monticello? >> >> Cheers, >> Doru >> >> >> >> >> On Wed, Sep 25, 2013 at 9:29 PM, Stéphane Ducasse <[hidden email]> wrote: >> this is strange since I could snapshot moose and synectique using it. >> >> I'm about to write a boring report so I'm not allowed to open Pharo right now. >> >>> I am giving a shot at Snapshotcello since it looks like a superb solution for creating images properly from a complex configuration. >>> >>> From http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-ready, I tried to craft a call for my configuration. >>> >>> I've loaded ConfigurationOfSnapshotcello #development in Pharo20. >>> >>> Then tried the calls and there were some API changes (from the tests, I found out the incantation). >>> >>> Snapshotcello new >>> configurationClass: ConfigurationOfHOWebStack; >>> sourceVersion: #development; >>> targetVersion: '0.3-snapshot'; >>> snapshot. >>> >>> But then I faced a problem with a DNU on 'asEnglishPlural' for a categorization. No big deal, I commented that out as I could live with that. >>> >>> But then I faced something more difficult (the compileSnapshotWithCurrentPackages: aNumber worked in the self generateSnapshotWithCurrentPackages: aNumber... >>> >>> >>> It took a lot of time to get the whole config loaded... (so, the progressbars worked and worked) >>> >>> Then, it failed on giving: "PostMortem: MNU: nil>>ancestry" >>> >>> >>> >>> >>> >>> self workingCopiesFromConfiguration do: [ :each | >>> codeStream tab; tab; >>> nextPutAll: '#('; >>> nextPut: $'; >>> nextPutAll: >>> each ancestry ancestorString >>> ; >>> nextPutAll: '.mcz'; >>> nextPut: $'; >>> nextPutAll: ' '; >>> nextPut: $'; >>> nextPutAll: (self repositoryNameForWorkingCopy: each); >>> nextPut: $'; >>> nextPutAll: ' '; >>> nextPut: $'; >>> nextPutAll: each package name; >>> nextPut: $'; >>> nextPutAll: ' ) ' ] >>> separatedBy: [ codeStream cr ]. >>> codeStream >>> cr; >>> tab; >>> nextPutAll: ')'. >>> ^ codeStream contents >>> >>> >>> Oops. each is nil... >>> >>> >>> >>> >>> >>> Anyone having faced that? >>> >>> Debugging... >>> >>> Phil >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" > -- www.tudorgirba.com "Obvious things are difficult to teach." |
|
|
Because atm when you load Snapshotcello into Pharo 2.0 and run snapshotting, you get an exception that ByteString does no understand 'asEnglishPlural' and Phil mentioned it his letter.
uko On 26 вер. 2013, at 21:46, Tudor Girba <[hidden email]> wrote: > I am not sure I understand. Why is this question relevant for the present discussion? > > Doru > > > On Sep 26, 2013, at 7:36 PM, Yuriy Tymchuk <[hidden email]> wrote: > >> Hi, >> >> so what are we going to do with 'asEnglishPlural' missing from the ByteString? >> >> Uko >> >> On 26 вер. 2013, at 09:52, Tudor Girba <[hidden email]> wrote: >> >>> Strange. I've never encountered this. >>> >>> each should be a MCWorkingCopy. >>> >>> I will try to take a look, but it might take a while. >>> >>> In the meantime, can you locate the package in your configuration? Is it possible that something went wrong with Monticello? >>> >>> Cheers, >>> Doru >>> >>> >>> >>> >>> On Wed, Sep 25, 2013 at 9:29 PM, Stéphane Ducasse <[hidden email]> wrote: >>> this is strange since I could snapshot moose and synectique using it. >>> >>> I'm about to write a boring report so I'm not allowed to open Pharo right now. >>> >>>> I am giving a shot at Snapshotcello since it looks like a superb solution for creating images properly from a complex configuration. >>>> >>>> From http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-ready, I tried to craft a call for my configuration. >>>> >>>> I've loaded ConfigurationOfSnapshotcello #development in Pharo20. >>>> >>>> Then tried the calls and there were some API changes (from the tests, I found out the incantation). >>>> >>>> Snapshotcello new >>>> configurationClass: ConfigurationOfHOWebStack; >>>> sourceVersion: #development; >>>> targetVersion: '0.3-snapshot'; >>>> snapshot. >>>> >>>> But then I faced a problem with a DNU on 'asEnglishPlural' for a categorization. No big deal, I commented that out as I could live with that. >>>> >>>> But then I faced something more difficult (the compileSnapshotWithCurrentPackages: aNumber worked in the self generateSnapshotWithCurrentPackages: aNumber... >>>> >>>> >>>> It took a lot of time to get the whole config loaded... (so, the progressbars worked and worked) >>>> >>>> Then, it failed on giving: "PostMortem: MNU: nil>>ancestry" >>>> >>>> >>>> >>>> >>>> >>>> self workingCopiesFromConfiguration do: [ :each | >>>> codeStream tab; tab; >>>> nextPutAll: '#('; >>>> nextPut: $'; >>>> nextPutAll: >>>> each ancestry ancestorString >>>> ; >>>> nextPutAll: '.mcz'; >>>> nextPut: $'; >>>> nextPutAll: ' '; >>>> nextPut: $'; >>>> nextPutAll: (self repositoryNameForWorkingCopy: each); >>>> nextPut: $'; >>>> nextPutAll: ' '; >>>> nextPut: $'; >>>> nextPutAll: each package name; >>>> nextPut: $'; >>>> nextPutAll: ' ) ' ] >>>> separatedBy: [ codeStream cr ]. >>>> codeStream >>>> cr; >>>> tab; >>>> nextPutAll: ')'. >>>> ^ codeStream contents >>>> >>>> >>>> Oops. each is nil... >>>> >>>> >>>> >>>> >>>> >>>> Anyone having faced that? >>>> >>>> Debugging... >>>> >>>> Phil >>> >>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >> > > -- > www.tudorgirba.com > > "Obvious things are difficult to teach." > > > > |
Re: Snapshotcello & Pharo 20: issues...
|
|
Oh, I see. Thanks for clarifying. The method exists in the Moose image, so I have to fix it :) Doru On Thu, Sep 26, 2013 at 8:50 PM, Yuriy Tymchuk <[hidden email]> wrote: Because atm when you load Snapshotcello into Pharo 2.0 and run snapshotting, you get an exception that ByteString does no understand 'asEnglishPlural' and Phil mentioned it his letter. "Every thing has its own flow"
|
|
|
Moose-o-cello :P On 26 вер. 2013, at 22:43, Tudor Girba <[hidden email]> wrote:
|
Re: Snapshotcello & Pharo 20: issues...
|
|
Ok, asEnglishPlural is now removed. Doru On Thu, Sep 26, 2013 at 9:45 PM, Yuriy Tymchuk <[hidden email]> wrote:
"Every thing has its own flow"
|
Re: Snapshotcello & Pharo 20: issues...
|
|
Hello,
Question: how does Snapshotcello ensures the loading order? Doru, do you have any notes about that? I ask because I feel that what I get from a snapshot version isn't the same as what I get from the configuration.
Well, maybe I need to recheck all of the versions and stuff. Ah, time to look into Snapshotcello and MCXXXX classes... Thx Phil |
|
|
In reply to this post by Tudor Girba-2
Maybe we should add that to Pharo?
This kind of methods look useful for a lot of tasks. uko On 27 вер. 2013, at 08:51, Tudor Girba <[hidden email]> wrote:
|
Re: Snapshotcello & Pharo 20: issues...
|
|
In reply to this post by philippeback
On Sep 27, 2013, at 9:15 AM, [hidden email] wrote: > Hello, > > Question: how does Snapshotcello ensures the loading order? Doru, do you have any notes about that? Yes In fact it just ask the metacelloSpec for the order. If it fails it means that there is a missing dependency. > I ask because I feel that what I get from a snapshot version isn't the same as what I get from the configuration. > > Well, maybe I need to recheck all of the versions and stuff. Ah, time to look into Snapshotcello and MCXXXX classes… Stef > > Thx > > Phil > |
Re: Snapshotcello & Pharo 20: issues...
|
|
Exactly. Snapshotcello relies 100% on the loading order of Metacello. Doru On Fri, Sep 27, 2013 at 12:55 PM, Stéphane Ducasse <[hidden email]> wrote:
"Every thing has its own flow"
|
«
Return to Pharo Smalltalk Users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |