- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [pharo-project/pharo-core]

by Goubier Thierry

Hi Alexandre, I use SmalltalkHub, GitHub and professionally hosted git repositories for my Pharo developments, and I have slowly moved my SmalltalkHub hosted applications to GitHub, so yes, you can use GitHub to store applications. As Dale said, I'm adding a Monticello way to use a git repository to store pharo packages, trying to hide as much as possible the command line (you still have to do 'git clone', 'git pull' and 'git push' on the command line...) while being as close as possible to a mcz-based repository (which means going back and forth between smalltalkhub and github is possible). Overall, I find git to be a bit less of a hassle to connect to than smalltalkhub (authentification by public key is a real plus), and github tools and web interface a lot more powerfull than smalltalkhub at the moment. Some of git operations, however, are not very compatible with pharo code and packages, so its not perfect (yet). I do believe SmalltalkHub could use a git repository to store packages, yes. Synchronize that git to a github repo, why not as well? Thierry Le 23/07/2013 20:01, Alexandre Bergel a Ã©crit : > Hi! > > What this all business with Pharo on github is about? > I checked https://github.com/pharo-project and not much is said. > > Can one store its application in Github? > > About git, can Smalltalkhub be a nice facade of github? I mean, I do not want to use command line to save my code in a repository, but I would be more than happy that non-pharoers are aware of the very cool language Pharo by just glancing projects on github. Can Smalltalkhub instead use github for all the storing? > > Cheers, > Alexandre > > > On Jul 23, 2013, at 7:23 AM, GitHub <noreply(a)github.com> wrote: > >> Branch: refs/tags/30294 >> Home: https://github.com/pharo-project/pharo-core >> > -- 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

July 24, 2013

14 issues in need of a quick check

by Marcus Denker

Hi, there are 14 issues in the status where they need to be checked. https://pharo.fogbugz.com/f/filters/36/Review

July 24, 2013

Re: [Pharo-dev] [Moose-dev] Re: Re: [ann] snapshotcello

by Tudor Girba

Hi, On Jul 24, 2013, at 8:48 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Jul 23, 2013, at 11:51 PM, Dale K. Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > >> Stef, >> >> I haven't completely wrapped my brain around what SnapshotCello does so I don't have an informed opinion ... the fact that you found a need to invent SnapshotCello does speak volumes to the fact that there is a need that is going unmet:). >> >> However, I don't like the fact that you end up sending a non-spec message to make this work (#populateSpec:with:). Tools like Versioner will not be able to rewrite a method like this correctly so it is a less than satisfactory workaround to the method literal limit. > Indeed. May be in the future we could recreate a simple compliant spec driven method by interpreting the > existing configuration trees but this requires some work. I do not understand this point. What do you mean by "interpreting the configuration trees"? Doru >> >> With that said it _is_ performing a useful function ... >> >> I have recently come up with an approach to addressing the method literal limit from a slightly different angle and I would assume that SnapshotCello could be recast to use this "approved approach" when the new techinique becomes available. At that time it would make sense to roll the SnapshotCello funtionality into the MetacelloToolBox... >> >> Dale >> >> [1] http://forum.world.st/Loading-problem-in-Seaside-tp4699965p4700161.html >> ----- Original Message ----- >> | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> >> | To: "Moose-related development" <moose-dev(a)iam.unibe.ch> >> | Cc: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>, "Pharo Development List" >> | <pharo-dev(a)lists.pharo.org> >> | Sent: Tuesday, July 23, 2013 2:17:50 PM >> | Subject: [Moose-dev] Re: [ann] snapshotcello >> | >> | Nice to see SnapshotCello coming to live. May be it should be >> | integrated to Metacello. >> | Because everybody may need this cool feature. >> | >> | Stef >> | >> | On Jul 23, 2013, at 10:43 PM, Tudor Girba <tudor(a)tudorgirba.com> >> | wrote: >> | >> | > Hi, >> | > >> | > Stef and I developed Snapshotcello, a little utility that enables >> | > you to freeze a snapshot of a given configuration based on what is >> | > already loaded in your current image. >> | > >> | > The idea is simple. You develop against the latest versions of all >> | > packages, and commit your changes for each package. When you are >> | > ready for a release, you assemble your image, and generate a >> | > snapshot version that can be reloaded later. >> | > >> | > Here is an example of how it can work to take a snapshot of a >> | > development version: >> | > Snapshotcello new >> | > configurationClass: ConfigurationOfMoose; >> | > configurationVersion: #development; >> | > publishVersion: '4.8-snapshot' >> | > >> | > You can find more details here: >> | > http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-re… >> | > >> | > You can get the code at: >> | > Gofer new >> | > smalltalkhubUser: 'girba' project: 'Snapshotcello'; >> | > package: 'ConfigurationOfSnapshotcello'; >> | > load. >> | > (Smalltalk globals at: #ConfigurationOfSnapshotcello) >> | > loadDevelopment >> | > >> | > Cheers, >> | > Doru >> | > >> | > -- >> | > www.tudorgirba.com >> | > >> | > "Every successful trip needs a suitable vehicle." >> | > >> | > >> | > >> | > >> | > >> | > _______________________________________________ >> | > Moose-dev mailing list >> | > Moose-dev(a)iam.unibe.ch >> | > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> | >> | >> | _______________________________________________ >> | Moose-dev mailing list >> | Moose-dev(a)iam.unibe.ch >> | https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> | >> > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "From an abstract enough point of view, any two things are similar."

July 24, 2013

Re: [Pharo-dev] [Moose-dev] [ann] snapshotcello

by Tudor Girba

Hi, On Jul 24, 2013, at 8:49 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Jul 24, 2013, at 12:09 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> Nice :) >> >> Random Question: Do you have a way to file out a whole configuration as a fuel file? > > Do you mean the packages? or the configuration itself? > What snapshotcello does is that it walks the configurations and gather the packages and their repository > and generate a list. I think he means all packages. I like the idea. >> or would it be considerably easier to so with your Snappy tool? > > probably because you get a linear list of packages. It actually does not depend that much on Snapshotcello, given that Snapshotcello actually uses Metacello for anything meaningful. But, it could be cheaper to simply traverse the snapshotted list of packages and dump them in fuel. Cheers, Doru > Stef > >> >> On 2013-07-23, at 23:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> Nice to see SnapshotCello coming to live. May be it should be integrated to Metacello. >>> Because everybody may need this cool feature. >>> >>> Stef >>> >>> On Jul 23, 2013, at 10:43 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>>> Hi, >>>> >>>> Stef and I developed Snapshotcello, a little utility that enables you to freeze a snapshot of a given configuration based on what is already loaded in your current image. >>>> >>>> The idea is simple. You develop against the latest versions of all packages, and commit your changes for each package. When you are ready for a release, you assemble your image, and generate a snapshot version that can be reloaded later. >>>> >>>> Here is an example of how it can work to take a snapshot of a development version: >>>> Snapshotcello new >>>> configurationClass: ConfigurationOfMoose; >>>> configurationVersion: #development; >>>> publishVersion: '4.8-snapshot' >>>> >>>> You can find more details here: >>>> http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-re… >>>> >>>> You can get the code at: >>>> Gofer new >>>> smalltalkhubUser: 'girba' project: 'Snapshotcello'; >>>> package: 'ConfigurationOfSnapshotcello'; >>>> load. >>>> (Smalltalk globals at: #ConfigurationOfSnapshotcello) loadDevelopment >>>> >>>> Cheers, >>>> Doru >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Every successful trip needs a suitable vehicle." >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)iam.unibe.ch >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >> >> > > -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

July 24, 2013

Re: [Pharo-dev] [Pharo-users] [Moose-dev] Re: [ann] snapshotcello

by Tudor Girba

Hi, On Jul 23, 2013, at 11:51 PM, "Dale K. Henrichs" <dale.henrichs(a)gemtalksystems.com> wrote: > Stef, > > I haven't completely wrapped my brain around what SnapshotCello does so I don't have an informed opinion ... the fact that you found a need to invent SnapshotCello does speak volumes to the fact that there is a need that is going unmet:). What is not clear? I would be interested in describing our scenario in more details because I think this is a development pattern. But, I need some concrete questions to start from. > However, I don't like the fact that you end up sending a non-spec message to make this work (#populateSpec:with:). Tools like Versioner will not be able to rewrite a method like this correctly so it is a less than satisfactory workaround to the method literal limit. I still do not understand why Versionner would be affected by the current versions given that we are only generating versions that should be immutable hence no need for management. > With that said it _is_ performing a useful function ... > > I have recently come up with an approach to addressing the method literal limit from a slightly different angle and I would assume that SnapshotCello could be recast to use this "approved approach" when the new techinique becomes available. At that time it would make sense to roll the SnapshotCello funtionality into the MetacelloToolBox... Having a different way to store the information should be no problem. I am curious about your ideas. Cheers, Doru > Dale > > [1] http://forum.world.st/Loading-problem-in-Seaside-tp4699965p4700161.html > ----- Original Message ----- > | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > | To: "Moose-related development" <moose-dev(a)iam.unibe.ch> > | Cc: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>, "Pharo Development List" > | <pharo-dev(a)lists.pharo.org> > | Sent: Tuesday, July 23, 2013 2:17:50 PM > | Subject: [Moose-dev] Re: [ann] snapshotcello > | > | Nice to see SnapshotCello coming to live. May be it should be > | integrated to Metacello. > | Because everybody may need this cool feature. > | > | Stef > | > | On Jul 23, 2013, at 10:43 PM, Tudor Girba <tudor(a)tudorgirba.com> > | wrote: > | > | > Hi, > | > > | > Stef and I developed Snapshotcello, a little utility that enables > | > you to freeze a snapshot of a given configuration based on what is > | > already loaded in your current image. > | > > | > The idea is simple. You develop against the latest versions of all > | > packages, and commit your changes for each package. When you are > | > ready for a release, you assemble your image, and generate a > | > snapshot version that can be reloaded later. > | > > | > Here is an example of how it can work to take a snapshot of a > | > development version: > | > Snapshotcello new > | > configurationClass: ConfigurationOfMoose; > | > configurationVersion: #development; > | > publishVersion: '4.8-snapshot' > | > > | > You can find more details here: > | > http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-re… > | > > | > You can get the code at: > | > Gofer new > | > smalltalkhubUser: 'girba' project: 'Snapshotcello'; > | > package: 'ConfigurationOfSnapshotcello'; > | > load. > | > (Smalltalk globals at: #ConfigurationOfSnapshotcello) > | > loadDevelopment > | > > | > Cheers, > | > Doru > | > > | > -- > | > www.tudorgirba.com > | > > | > "Every successful trip needs a suitable vehicle." > | > > | > > | > > | > > | > > | > _______________________________________________ > | > Moose-dev mailing list > | > Moose-dev(a)iam.unibe.ch > | > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > | > | > | _______________________________________________ > | Moose-dev mailing list > | Moose-dev(a)iam.unibe.ch > | https://www.iam.unibe.ch/mailman/listinfo/moose-dev > | > -- www.tudorgirba.com "Live like you mean it."

July 24, 2013

Re: [Pharo-dev] [Moose-dev] [ann] snapshotcello

by StÃ©phane Ducasse

On Jul 24, 2013, at 12:09 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > Nice :) > > Random Question: Do you have a way to file out a whole configuration as a fuel file? Do you mean the packages? or the configuration itself? What snapshotcello does is that it walks the configurations and gather the packages and their repository and generate a list. > or would it be considerably easier to so with your Snappy tool? probably because you get a linear list of packages. Stef > > On 2013-07-23, at 23:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Nice to see SnapshotCello coming to live. May be it should be integrated to Metacello. >> Because everybody may need this cool feature. >> >> Stef >> >> On Jul 23, 2013, at 10:43 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> Hi, >>> >>> Stef and I developed Snapshotcello, a little utility that enables you to freeze a snapshot of a given configuration based on what is already loaded in your current image. >>> >>> The idea is simple. You develop against the latest versions of all packages, and commit your changes for each package. When you are ready for a release, you assemble your image, and generate a snapshot version that can be reloaded later. >>> >>> Here is an example of how it can work to take a snapshot of a development version: >>> Snapshotcello new >>> configurationClass: ConfigurationOfMoose; >>> configurationVersion: #development; >>> publishVersion: '4.8-snapshot' >>> >>> You can find more details here: >>> http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-re… >>> >>> You can get the code at: >>> Gofer new >>> smalltalkhubUser: 'girba' project: 'Snapshotcello'; >>> package: 'ConfigurationOfSnapshotcello'; >>> load. >>> (Smalltalk globals at: #ConfigurationOfSnapshotcello) loadDevelopment >>> >>> Cheers, >>> Doru >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every successful trip needs a suitable vehicle." >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> > >

July 24, 2013

Re: [Pharo-dev] [Moose-dev] Re: [ann] snapshotcello

by StÃ©phane Ducasse

On Jul 23, 2013, at 11:51 PM, Dale K. Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > Stef, > > I haven't completely wrapped my brain around what SnapshotCello does so I don't have an informed opinion ... the fact that you found a need to invent SnapshotCello does speak volumes to the fact that there is a need that is going unmet:). > > However, I don't like the fact that you end up sending a non-spec message to make this work (#populateSpec:with:). Tools like Versioner will not be able to rewrite a method like this correctly so it is a less than satisfactory workaround to the method literal limit. Indeed. May be in the future we could recreate a simple compliant spec driven method by interpreting the existing configuration trees but this requires some work. > > With that said it _is_ performing a useful function ... > > I have recently come up with an approach to addressing the method literal limit from a slightly different angle and I would assume that SnapshotCello could be recast to use this "approved approach" when the new techinique becomes available. At that time it would make sense to roll the SnapshotCello funtionality into the MetacelloToolBox... > > Dale > > [1] http://forum.world.st/Loading-problem-in-Seaside-tp4699965p4700161.html > ----- Original Message ----- > | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > | To: "Moose-related development" <moose-dev(a)iam.unibe.ch> > | Cc: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>, "Pharo Development List" > | <pharo-dev(a)lists.pharo.org> > | Sent: Tuesday, July 23, 2013 2:17:50 PM > | Subject: [Moose-dev] Re: [ann] snapshotcello > | > | Nice to see SnapshotCello coming to live. May be it should be > | integrated to Metacello. > | Because everybody may need this cool feature. > | > | Stef > | > | On Jul 23, 2013, at 10:43 PM, Tudor Girba <tudor(a)tudorgirba.com> > | wrote: > | > | > Hi, > | > > | > Stef and I developed Snapshotcello, a little utility that enables > | > you to freeze a snapshot of a given configuration based on what is > | > already loaded in your current image. > | > > | > The idea is simple. You develop against the latest versions of all > | > packages, and commit your changes for each package. When you are > | > ready for a release, you assemble your image, and generate a > | > snapshot version that can be reloaded later. > | > > | > Here is an example of how it can work to take a snapshot of a > | > development version: > | > Snapshotcello new > | > configurationClass: ConfigurationOfMoose; > | > configurationVersion: #development; > | > publishVersion: '4.8-snapshot' > | > > | > You can find more details here: > | > http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-re… > | > > | > You can get the code at: > | > Gofer new > | > smalltalkhubUser: 'girba' project: 'Snapshotcello'; > | > package: 'ConfigurationOfSnapshotcello'; > | > load. > | > (Smalltalk globals at: #ConfigurationOfSnapshotcello) > | > loadDevelopment > | > > | > Cheers, > | > Doru > | > > | > -- > | > www.tudorgirba.com > | > > | > "Every successful trip needs a suitable vehicle." > | > > | > > | > > | > > | > > | > _______________________________________________ > | > Moose-dev mailing list > | > Moose-dev(a)iam.unibe.ch > | > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > | > | > | _______________________________________________ > | Moose-dev mailing list > | Moose-dev(a)iam.unibe.ch > | https://www.iam.unibe.ch/mailman/listinfo/moose-dev > | >

July 24, 2013

Re: [Pharo-dev] [Moose-dev] [ann] snapshotcello

by Camillo Bruni

Nice :) Random Question: Do you have a way to file out a whole configuration as a fuel file? or would it be considerably easier to so with your Snappy tool? On 2013-07-23, at 23:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Nice to see SnapshotCello coming to live. May be it should be integrated to Metacello. > Because everybody may need this cool feature. > > Stef > > On Jul 23, 2013, at 10:43 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> Stef and I developed Snapshotcello, a little utility that enables you to freeze a snapshot of a given configuration based on what is already loaded in your current image. >> >> The idea is simple. You develop against the latest versions of all packages, and commit your changes for each package. When you are ready for a release, you assemble your image, and generate a snapshot version that can be reloaded later. >> >> Here is an example of how it can work to take a snapshot of a development version: >> Snapshotcello new >> configurationClass: ConfigurationOfMoose; >> configurationVersion: #development; >> publishVersion: '4.8-snapshot' >> >> You can find more details here: >> http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-re… >> >> You can get the code at: >> Gofer new >> smalltalkhubUser: 'girba' project: 'Snapshotcello'; >> package: 'ConfigurationOfSnapshotcello'; >> load. >> (Smalltalk globals at: #ConfigurationOfSnapshotcello) loadDevelopment >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Every successful trip needs a suitable vehicle." >> >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >

July 23, 2013

Re: [Pharo-dev] [Moose-dev] Re: [ann] snapshotcello

by Dale K. Henrichs

Stef, I haven't completely wrapped my brain around what SnapshotCello does so I don't have an informed opinion ... the fact that you found a need to invent SnapshotCello does speak volumes to the fact that there is a need that is going unmet:). However, I don't like the fact that you end up sending a non-spec message to make this work (#populateSpec:with:). Tools like Versioner will not be able to rewrite a method like this correctly so it is a less than satisfactory workaround to the method literal limit. With that said it _is_ performing a useful function ... I have recently come up with an approach to addressing the method literal limit from a slightly different angle and I would assume that SnapshotCello could be recast to use this "approved approach" when the new techinique becomes available. At that time it would make sense to roll the SnapshotCello funtionality into the MetacelloToolBox... Dale [1] http://forum.world.st/Loading-problem-in-Seaside-tp4699965p4700161.html ----- Original Message ----- | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> | To: "Moose-related development" <moose-dev(a)iam.unibe.ch> | Cc: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>, "Pharo Development List" | <pharo-dev(a)lists.pharo.org> | Sent: Tuesday, July 23, 2013 2:17:50 PM | Subject: [Moose-dev] Re: [ann] snapshotcello | | Nice to see SnapshotCello coming to live. May be it should be | integrated to Metacello. | Because everybody may need this cool feature. | | Stef | | On Jul 23, 2013, at 10:43 PM, Tudor Girba <tudor(a)tudorgirba.com> | wrote: | | > Hi, | > | > Stef and I developed Snapshotcello, a little utility that enables | > you to freeze a snapshot of a given configuration based on what is | > already loaded in your current image. | > | > The idea is simple. You develop against the latest versions of all | > packages, and commit your changes for each package. When you are | > ready for a release, you assemble your image, and generate a | > snapshot version that can be reloaded later. | > | > Here is an example of how it can work to take a snapshot of a | > development version: | > Snapshotcello new | > configurationClass: ConfigurationOfMoose; | > configurationVersion: #development; | > publishVersion: '4.8-snapshot' | > | > You can find more details here: | > http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-re… | > | > You can get the code at: | > Gofer new | > smalltalkhubUser: 'girba' project: 'Snapshotcello'; | > package: 'ConfigurationOfSnapshotcello'; | > load. | > (Smalltalk globals at: #ConfigurationOfSnapshotcello) | > loadDevelopment | > | > Cheers, | > Doru | > | > -- | > www.tudorgirba.com | > | > "Every successful trip needs a suitable vehicle." | > | > | > | > | > | > _______________________________________________ | > Moose-dev mailing list | > Moose-dev(a)iam.unibe.ch | > https://www.iam.unibe.ch/mailman/listinfo/moose-dev | | | _______________________________________________ | Moose-dev mailing list | Moose-dev(a)iam.unibe.ch | https://www.iam.unibe.ch/mailman/listinfo/moose-dev |

July 23, 2013

Re: [Pharo-dev] [Moose-dev] [ann] snapshotcello

by StÃ©phane Ducasse

Nice to see SnapshotCello coming to live. May be it should be integrated to Metacello. Because everybody may need this cool feature. Stef On Jul 23, 2013, at 10:43 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Stef and I developed Snapshotcello, a little utility that enables you to freeze a snapshot of a given configuration based on what is already loaded in your current image. > > The idea is simple. You develop against the latest versions of all packages, and commit your changes for each package. When you are ready for a release, you assemble your image, and generate a snapshot version that can be reloaded later. > > Here is an example of how it can work to take a snapshot of a development version: > Snapshotcello new > configurationClass: ConfigurationOfMoose; > configurationVersion: #development; > publishVersion: '4.8-snapshot' > > You can find more details here: > http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-re… > > You can get the code at: > Gofer new > smalltalkhubUser: 'girba' project: 'Snapshotcello'; > package: 'ConfigurationOfSnapshotcello'; > load. > (Smalltalk globals at: #ConfigurationOfSnapshotcello) loadDevelopment > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every successful trip needs a suitable vehicle." > > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

July 23, 2013