July 2013 - Pharo-dev - lists.pharo.org

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

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

by Dale K. Henrichs

Alex, I can't speak about SmalltalkHub, but using FileTree one can store Monticello packages on disk in a form that one can use git for the heavy lifting of source code versioning. With FileTree, you need to do manual git commands. Thierry Groubier is actively working on providing image-level support for Git based on using OsProcess[1]. Camillo Bruni, Stefan Marr[6] and Max Leske[5] have worked on a couple different approaches to interfacing to the Git C api from Smalltalk ... The Metacello Preview[2] has Metacello level support for interacting with FileTree and GithHub repositories, but I am still in the process of fine tuning the Metacello Scripting API. So at the moment I would say that using GitHub for Smalltalk is only for those interested in being on the bleeding edge. I do virtually all of my work using GitHub on a daily basis. GitHub is my primary repository for Metacello[2], FileTree[3] and tODE[4]. Slow but steady progress _is_ being made towards making git/github as easy to use as any other Monticello repository, we're just not quite there... Dale [1] https://github.com/dalehenrich/filetree/tree/pharo2.0/repository/Monticello… [2] https://github.com/dalehenrich/metacello-work [3] https://github.com/dalehenrich/filetree [4] https://github.com/dalehenrich/tode [5] http://smalltalkhub.com/mc/MaxLeske/FileSytem-Git/main [6] https://github.com/smarr/LibGit ----- Original Message ----- | From: "Alexandre Bergel" <alexandre.bergel(a)me.com> | To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> | Sent: Tuesday, July 23, 2013 11:01:18 AM | Subject: Re: [Pharo-dev] [pharo-project/pharo-core] | | 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 | > | | -- | _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | Alexandre Bergel http://www.bergel.eu | ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | | | | |

July 23, 2013

[ann] snapshotcello

by Tudor Girba

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."

July 23, 2013

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

by Alexandre Bergel

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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 23, 2013

Re: [Pharo-dev] [rmod] Post on how to install pharo

by StÃ©phane Ducasse

sure! You can have a look at the github repos and the readme. https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/120/artifa… I just finished it :) On Jul 23, 2013, at 2:53 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Next week you can show me gutenberg so next time I do it myself :P > > > On Tue, Jul 23, 2013 at 2:50 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Ok will port your blog to gutenberg and we can compare and you let me know if the html is ok > after I can generate the stuff for the code. > > stef > > >> So far, the HTML tags supported are these: >> >> http://en.support.wordpress.com/code/#html-tags >> >> and the code should be exported as this: >> >> http://en.support.wordpress.com/code/posting-source-code/ >> >> For syntax coloring I'm using ruby, just like >> >> [code language="ruby"] >> self bla: 1 + super ble. >> [/code] >> >> >> >> On Tue, Jul 23, 2013 at 12:33 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >> >> >> On Tue, Jul 23, 2013 at 12:24 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Guilermo >> >> I would like to turn your blog entry into Gutenberg. I will do it while reading it as a kata exercise. >> >> Nice! >> >> Now I'm thinking that I could write a outputer for Gutenberg to produce the blog contents. >> What is the format used to edit your blog? >> >> I'm writing in wordpress :/... It allows to write a post using a WYSIWYG and to write it in a kind of HTML. However, for embedding images and writing code it uses tags between brackets. I cannot find a cool description on what is exactly the format :(. >> >> Because like that we could change edit gutenberg file and get: >> latex >> html >> blog >> >> Nick Ager didn't show that pier can import wordpress? maybe he can tell better :) >> >> >> Stef >> >> On Jul 23, 2013, at 11:03 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >>> Hi guys, >>> >>> I've written a small post on the current mechanisms for download and deploy pharo images and vms. Of course it may not be complete, just wanted to make noise :). So, feedback and retweets are welcome ;). >>> >>> http://playingwithobjects.wordpress.com/2013/07/23/installing-pharo-in-many… >>> >>> Guille >> >> >> > >

July 23, 2013