- Pharo-dev - lists.pharo.org

[Pharo-project] pharo-2.0-tests Â» win - Build # 334 - Failure!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 7, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 333 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 7, 2012

[Pharo-project] pharo-2.0-tests Â» linux - Build # 333 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 7, 2012

[Pharo-project] pharo-2.0-tests Â» mac - Build # 333 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 7, 2012

Re: [Pharo-project] git support

by Camillo Bruni

On 2012-09-07, at 15:29, Dale Henrichs <dhenrich(a)vmware.com> wrote: > Does FsGit run in Pharo1.4 or is ti Pharo2.0 only ... if it ran in Pharo1.4 I would start using it in my daily work:) so that's a motivation to get it up and running in 1.4 :P With FileSystem being backported I don't see any immediate problems ahead... > ----- Original Message ----- > | From: "Camillo Bruni" <camillobruni(a)gmail.com> > | To: Pharo-project(a)lists.gforge.inria.fr > | Sent: Friday, September 7, 2012 6:22:44 AM > | Subject: Re: [Pharo-project] git support > | > | > | On 2012-09-07, at 15:13, Dale Henrichs <dhenrich(a)vmware.com> wrote: > | > Cami, > | > > | > What kind of work needs to be done for the Cypress-compatible > | > format? I've done a couple of different implementations already:) > | > So I can definitely do one more ... If you give me the name of the > | > class that is the entry point for read/write then I can take it > | > from there ... > | > | Since you ported it to the new FileSystem I don't have to change much > | :) > | The git stuff works on top of the new FileSystem, thus completely > | transparent to > | whatever FileOperations you used. > | > | - load filetree > | - use filetree instead of my own git exporter > | - use filetree for recreating mc snapshots > | > | I will try to hook that up this weekend, then I need busy testers :P > | > | > | > Metacello integration is also among the "missing" from the > | > perspective that I want some real users using the Metacello > | > Preview[1] and giving me feedback[2] before I make a general > | > release. > | > | I guess we could push some work to Versionner? That would then have > | to interact > | with the low-level git filesystem to set the tags / commits > | > | > Also keep in mind that we will need to be inventing the Smalltalk > | > workflow for git... > | > | yes :) I hope to get closer to that once I have a running > | implementation in pharo.. > | > | > Dale > | > > | > [1] > | > https://github.com/dalehenrich/metacello-work/blob/master/README.md > | > [2] https://groups.google.com/group/metacello/ > | > > | > ----- Original Message ----- > | > | From: "Camillo Bruni" <camillobruni(a)gmail.com> > | > | To: "Pharo-project(a)lists.gforge.inria.fr Development" > | > | <pharo-project(a)lists.gforge.inria.fr> > | > | Sent: Friday, September 7, 2012 4:15:46 AM > | > | Subject: [Pharo-project] git support > | > | > | > | who will help? > | > | > | > | max and I, stimulated by ESUG, worked on the latest version of > | > | FS-Git > | > | to make it stable again. > | > | we are very close to have a complete set of git tools written in > | > | pharo ready! > | > | > | > | missing > | > | ======= > | > | - a better mc integration > | > | - a cypress compatible fileout format > | > | - complete interaction with the git protocol > | > | - a direct way to commit stuff > | > | > | > | as always my time is somewhat limited as well and we're the only > | > | two > | > | developers working on it... > | > | > | > | The current work is available here: > | > | http://ss3.gemstone.com/ss/FSGit-Experimental.html > | > | https://github.com/dalehenrich/FSGit > | > | > | > | best > | > | cami > | > | > | > > | > | > | >

Sept. 7, 2012

Re: [Pharo-project] git support

by Dale Henrichs

Does FsGit run in Pharo1.4 or is ti Pharo2.0 only ... if it ran in Pharo1.4 I would start using it in my daily work:) Dale ----- Original Message ----- | From: "Camillo Bruni" <camillobruni(a)gmail.com> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Friday, September 7, 2012 6:22:44 AM | Subject: Re: [Pharo-project] git support | | | On 2012-09-07, at 15:13, Dale Henrichs <dhenrich(a)vmware.com> wrote: | > Cami, | > | > What kind of work needs to be done for the Cypress-compatible | > format? I've done a couple of different implementations already:) | > So I can definitely do one more ... If you give me the name of the | > class that is the entry point for read/write then I can take it | > from there ... | | Since you ported it to the new FileSystem I don't have to change much | :) | The git stuff works on top of the new FileSystem, thus completely | transparent to | whatever FileOperations you used. | | - load filetree | - use filetree instead of my own git exporter | - use filetree for recreating mc snapshots | | I will try to hook that up this weekend, then I need busy testers :P | | | > Metacello integration is also among the "missing" from the | > perspective that I want some real users using the Metacello | > Preview[1] and giving me feedback[2] before I make a general | > release. | | I guess we could push some work to Versionner? That would then have | to interact | with the low-level git filesystem to set the tags / commits | | > Also keep in mind that we will need to be inventing the Smalltalk | > workflow for git... | | yes :) I hope to get closer to that once I have a running | implementation in pharo.. | | > Dale | > | > [1] | > https://github.com/dalehenrich/metacello-work/blob/master/README.md | > [2] https://groups.google.com/group/metacello/ | > | > ----- Original Message ----- | > | From: "Camillo Bruni" <camillobruni(a)gmail.com> | > | To: "Pharo-project(a)lists.gforge.inria.fr Development" | > | <pharo-project(a)lists.gforge.inria.fr> | > | Sent: Friday, September 7, 2012 4:15:46 AM | > | Subject: [Pharo-project] git support | > | | > | who will help? | > | | > | max and I, stimulated by ESUG, worked on the latest version of | > | FS-Git | > | to make it stable again. | > | we are very close to have a complete set of git tools written in | > | pharo ready! | > | | > | missing | > | ======= | > | - a better mc integration | > | - a cypress compatible fileout format | > | - complete interaction with the git protocol | > | - a direct way to commit stuff | > | | > | as always my time is somewhat limited as well and we're the only | > | two | > | developers working on it... | > | | > | The current work is available here: | > | http://ss3.gemstone.com/ss/FSGit-Experimental.html | > | https://github.com/dalehenrich/FSGit | > | | > | best | > | cami | > | | > | | |

Sept. 7, 2012

[Pharo-project] after object create callback?

by sergio_101

hey, all.. i was wondering how to implement an 'after_create' callback in smalltalk.. the idea is, immediately after creating an object, some predefined methods get called. any ideas? thanks! -- ---- peace, sergio photographer, journalist, visionary http://www.ThoseOptimizeGuys.com http://www.CodingForHire.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Sept. 7, 2012

Re: [Pharo-project] Building a run loop that can continue after an unhanded exception

by Joe Rickerby

I'm actually doing forkAndWait on the timer actions to prevent any synchronisation problems, and to prevent me spawning too many processes and bringing down the system :/ On 7 Sep 2012, at 13:02, Frank Shearar <frank.shearar(a)gmail.com> wrote: > On 7 September 2012 12:29, Joe Rickerby <joe.rickerby(a)square-i.net> wrote: >> I have a solution however! Each timer on the run loop runs its action in a fork. This way any exception raised cannot unroll the stack to outside my run loop code. > > Right. That's effectively identical to using a delimited continuation: > that marks the stack such that when you cut the continuation you can't > capture past the stack marker. [1] > > The problem you might have is that the actions, being forked, run in a > separate Process. That means you have to worry about synchronising - > accessing common state from two actions (that are, of course, now > running in parallel). > > frank > > [1] http://okmij.org/ftp/continuations/green-fork.html > >> On 7 Sep 2012, at 12:24, Joe Rickerby <joe.rickerby(a)squaregroup.co.uk> >> wrote: >> >>> Not really. Proceed would take me back to where the exception was signalled. I want to resume at the point of the catch of the exception, no matter what happens regarding the exception. >>> >>> On 7 Sep 2012, at 09:40, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: >>> >>>> On 07.09.2012 10:17, Joe Rickerby wrote: >>>>> Hi all, >>>>> >>>>> I'm having a problem trying to build a run loop. If an exception is signalled within one of the run loop tasks, the exception escapes through the loop and terminates the process. >>>>> >>>>> I know I can catch the exception, and do something like print the message on the Transcript, but I was hoping to build something that was more helpful in development, allowing me to look through the stack, but if I press 'abandon' on that dialog, the run loop would continue from where I caught the exception. >>>>> >>>>> >>>> Isn't that exactly what happens if you don't handle the error, and use the proceed button in (pre and normal) debugger windows? >>>> >>>> Cheers, >>>> Henry >>> >> >> >> > >

Sept. 7, 2012

Re: [Pharo-project] git support

by Camillo Bruni

On 2012-09-07, at 15:13, Dale Henrichs <dhenrich(a)vmware.com> wrote: > Cami, > > What kind of work needs to be done for the Cypress-compatible format? I've done a couple of different implementations already:) So I can definitely do one more ... If you give me the name of the class that is the entry point for read/write then I can take it from there ... Since you ported it to the new FileSystem I don't have to change much :) The git stuff works on top of the new FileSystem, thus completely transparent to whatever FileOperations you used. - load filetree - use filetree instead of my own git exporter - use filetree for recreating mc snapshots I will try to hook that up this weekend, then I need busy testers :P > Metacello integration is also among the "missing" from the perspective that I want some real users using the Metacello Preview[1] and giving me feedback[2] before I make a general release. I guess we could push some work to Versionner? That would then have to interact with the low-level git filesystem to set the tags / commits > Also keep in mind that we will need to be inventing the Smalltalk workflow for git... yes :) I hope to get closer to that once I have a running implementation in pharo.. > Dale > > [1] https://github.com/dalehenrich/metacello-work/blob/master/README.md > [2] https://groups.google.com/group/metacello/ > > ----- Original Message ----- > | From: "Camillo Bruni" <camillobruni(a)gmail.com> > | To: "Pharo-project(a)lists.gforge.inria.fr Development" <pharo-project(a)lists.gforge.inria.fr> > | Sent: Friday, September 7, 2012 4:15:46 AM > | Subject: [Pharo-project] git support > | > | who will help? > | > | max and I, stimulated by ESUG, worked on the latest version of FS-Git > | to make it stable again. > | we are very close to have a complete set of git tools written in > | pharo ready! > | > | missing > | ======= > | - a better mc integration > | - a cypress compatible fileout format > | - complete interaction with the git protocol > | - a direct way to commit stuff > | > | as always my time is somewhat limited as well and we're the only two > | developers working on it... > | > | The current work is available here: > | http://ss3.gemstone.com/ss/FSGit-Experimental.html > | https://github.com/dalehenrich/FSGit > | > | best > | cami > | >

Sept. 7, 2012

Re: [Pharo-project] git support

by Dale Henrichs

Cami, What kind of work needs to be done for the Cypress-compatible format? I've done a couple of different implementations already:) So I can definitely do one more ... If you give me the name of the class that is the entry point for read/write then I can take it from there ... Metacello integration is also among the "missing" from the perspective that I want some real users using the Metacello Preview[1] and giving me feedback[2] before I make a general release. Also keep in mind that we will need to be inventing the Smalltalk workflow for git... Dale [1] https://github.com/dalehenrich/metacello-work/blob/master/README.md [2] https://groups.google.com/group/metacello/ ----- Original Message ----- | From: "Camillo Bruni" <camillobruni(a)gmail.com> | To: "Pharo-project(a)lists.gforge.inria.fr Development" <pharo-project(a)lists.gforge.inria.fr> | Sent: Friday, September 7, 2012 4:15:46 AM | Subject: [Pharo-project] git support | | who will help? | | max and I, stimulated by ESUG, worked on the latest version of FS-Git | to make it stable again. | we are very close to have a complete set of git tools written in | pharo ready! | | missing | ======= | - a better mc integration | - a cypress compatible fileout format | - complete interaction with the git protocol | - a direct way to commit stuff | | as always my time is somewhat limited as well and we're the only two | developers working on it... | | The current work is available here: | http://ss3.gemstone.com/ss/FSGit-Experimental.html | https://github.com/dalehenrich/FSGit | | best | cami |

Sept. 7, 2012