September 2013 - Pharo-users

Re: [Pharo-users] Snapshotcello & Pharo 20: issues...

by Yuriy Tymchuk

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 <tudor(a)tudorgirba.com> wrote: > Ok, asEnglishPlural is now removed. > > Doru > > > On Thu, Sep 26, 2013 at 9:45 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Moose-o-cello :P > > On 26 Ð²ÐµÑ. 2013, at 22:43, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> 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 <yuriy.tymchuk(a)me.com> 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. >> >> uko >> >> On 26 Ð²ÐµÑ. 2013, at 21:46, Tudor Girba <tudor(a)tudorgirba.com> 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 <yuriy.tymchuk(a)me.com> wrote: >> > >> >> Hi, >> >> >> >> so what are we going to do with 'asEnglishPlural' missing from the ByteString? >> >> >> >> Uko >> >> >> >> On 26 Ð²ÐµÑ. 2013, at 09:52, Tudor Girba <tudor(a)tudorgirba.com> 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 <stephane.ducasse(a)inria.fr> 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-re…, 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." >> > >> > >> > >> > >> >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Sept. 27, 2013

Re: [Pharo-users] Snapshotcello & Pharo 20: issues...

by phil＠highoctane.be

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

Sept. 27, 2013

Re: [Pharo-users] Snapshotcello & Pharo 20: issues...

by Tudor Girba

Ok, asEnglishPlural is now removed. Doru On Thu, Sep 26, 2013 at 9:45 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Moose-o-cello :P > > On 26 Ð²ÐµÑ. 2013, at 22:43, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > 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 <yuriy.tymchuk(a)me.com>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. >> >> uko >> >> On 26 Ð²ÐµÑ. 2013, at 21:46, Tudor Girba <tudor(a)tudorgirba.com> 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 <yuriy.tymchuk(a)me.com> >> wrote: >> > >> >> Hi, >> >> >> >> so what are we going to do with 'asEnglishPlural' missing from the >> ByteString? >> >> >> >> Uko >> >> >> >> On 26 Ð²ÐµÑ. 2013, at 09:52, Tudor Girba <tudor(a)tudorgirba.com> 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 < >> stephane.ducasse(a)inria.fr> 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-re…, >> 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." >> > >> > >> > >> > >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 27, 2013

Re: [Pharo-users] Scoped Senders

by Sean P. DeNigris

-------- Original message -------- From: "Camillo Bruni-3 [via Smalltalk]" <ml-node+s1294792n4710572h20(a)n4.nabble.com> Date: 09/26/2013 10:45 AM (GMT-05:00) To: "Sean P. DeNigris" <sean(a)clipperadams.com> Subject: Re: Scoped Senders => create a refactoring scope (I don't know the menu entry, but the shortcut is: CMD-B CMD-R CMD-R (browse restricted regular expression) Thank you, perfect! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Scoped-Senders-tp4710563p4710676.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 27, 2013

Re: [Pharo-users] Snapshotcello & Pharo 20: issues...

by Yuriy Tymchuk

Moose-o-cello :P On 26 Ð²ÐµÑ. 2013, at 22:43, Tudor Girba <tudor(a)tudorgirba.com> wrote: > 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 <yuriy.tymchuk(a)me.com> 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. > > uko > > On 26 Ð²ÐµÑ. 2013, at 21:46, Tudor Girba <tudor(a)tudorgirba.com> 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 <yuriy.tymchuk(a)me.com> wrote: > > > >> Hi, > >> > >> so what are we going to do with 'asEnglishPlural' missing from the ByteString? > >> > >> Uko > >> > >> On 26 Ð²ÐµÑ. 2013, at 09:52, Tudor Girba <tudor(a)tudorgirba.com> 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 <stephane.ducasse(a)inria.fr> 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-re…, 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." > > > > > > > > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Sept. 26, 2013

Re: [Pharo-users] Snapshotcello & Pharo 20: issues...

by Tudor Girba

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 <yuriy.tymchuk(a)me.com> 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. > > uko > > On 26 Ð²ÐµÑ. 2013, at 21:46, Tudor Girba <tudor(a)tudorgirba.com> 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 <yuriy.tymchuk(a)me.com> wrote: > > > >> Hi, > >> > >> so what are we going to do with 'asEnglishPlural' missing from the > ByteString? > >> > >> Uko > >> > >> On 26 Ð²ÐµÑ. 2013, at 09:52, Tudor Girba <tudor(a)tudorgirba.com> 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 < > stephane.ducasse(a)inria.fr> 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-re…, > 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." > > > > > > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 26, 2013

Re: [Pharo-users] Snapshotcello & Pharo 20: issues...

by Yuriy Tymchuk

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 <tudor(a)tudorgirba.com> 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 <yuriy.tymchuk(a)me.com> wrote: > >> Hi, >> >> so what are we going to do with 'asEnglishPlural' missing from the ByteString? >> >> Uko >> >> On 26 Ð²ÐµÑ. 2013, at 09:52, Tudor Girba <tudor(a)tudorgirba.com> 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 <stephane.ducasse(a)inria.fr> 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-re…, 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." > > > >

Sept. 26, 2013

Re: [Pharo-users] Snapshotcello & Pharo 20: issues...

by Tudor Girba

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 <yuriy.tymchuk(a)me.com> wrote: > Hi, > > so what are we going to do with 'asEnglishPlural' missing from the ByteString? > > Uko > > On 26 Ð²ÐµÑ. 2013, at 09:52, Tudor Girba <tudor(a)tudorgirba.com> 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 <stephane.ducasse(a)inria.fr> 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-re…, 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."

Sept. 26, 2013

Re: [Pharo-users] Snapshotcello & Pharo 20: issues...

by Yuriy Tymchuk

Hi, so what are we going to do with 'asEnglishPlural' missing from the ByteString? Uko On 26 Ð²ÐµÑ. 2013, at 09:52, Tudor Girba <tudor(a)tudorgirba.com> 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 <stephane.ducasse(a)inria.fr> 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-re…, 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"

Sept. 26, 2013

Re: [Pharo-users] Scoped Senders

by Goubier Thierry

Le 26/09/2013 16:58, Goubier Thierry a Ã©crit : > In AltBrowser, double click on the package you want, in the resulting > package-scoped browser, choose the method and select sendersOf in the > context menu :) > > (It may not be working completely at the moment) > > By hand, write the following. > > Create a RBEnvironment: > > | rbp | > rbp := RBBrowserEnvironment new forPackages: { }. > > Then do the senders search on it: > > rbp referencesTo: aSelector in: rbp Sorry, should be rbp referencesTo: aSelector Thierry > > Thierry > > Le 26/09/2013 16:39, Sean P. DeNigris a Ã©crit : >> How do I find the senders of a message, but just in a certain set of >> packages? >> >> Thanks. >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Scoped-Senders-tp4710563.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> >> > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 26, 2013