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

Re: [Pharo-project] Latest pharo issue with Eliot's latest Cog

by Esteban Lorenzano

Well.. looks like there is a misunderstanding here. I suggested use a CogVM. yes, but one of our builds, not Eliot's. PharoVM was born two weeks ago. Before that, we were producing CogVM and NBCogVM regularly. I suggested to use one of those, IÂ´m sorry if it was not clear. The right VMs can be found here: http://pharo.gforge.inria.fr/ci/vm/nbcog/ (yes, the whole vm thing is a mess, we will clean it eventually, but it will take some time...) Esteban On Mar 12, 2013, at 5:31 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I understand and encourage the streamlining of efforts. And I have no problem with dealing with the bumps of living on the latest version, be it the VM or the image. > > But, please consider the point of view of the one that offers the feedback. Right now, it sounds as if you are shooting down an unreasonable request from Stephan, but in this case, Esteban suggested that we should use the Cog VM instead of the Pharo VM to develop Moose, given that the Pharo VM is basically broken for us. > > So, Stephan did exactly that: he used the Cog VM. He reported that the tests do not crash the VM, which I think should be a relevant input, and he also reported other problems while running on the Cog VM. These errors indeed seem to be related to FileSystem, and this just shows that using the Cog VM as a temporary solution does not work. So, we have to focus on the Pharo VM. > > And now, I am back to the original question: What other tests or experiments would you like us to do to help with identifying the problem? > > Cheers, > Doru > > > On Tue, Mar 12, 2013 at 4:53 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > FileDialogs apparently make use of the new FileSystem values, so yes, > the update-our-VM-warning is there for a good reason! > > On 2013-03-12, at 16:47, Stephan Eggermont <stephan(a)stack.nl> wrote: > > > The problem is not just with the MOOSE image, > > Pharo 20598 and Cog.app 2071 doesn't allow a > > file dialog to be opened. > > > > FileDialogWindow new open > > > > Stephan > > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

March 12, 2013

Re: [Pharo-project] Latest pharo issue with Eliot's latest Cog

by Tudor Girba

Hi, I understand and encourage the streamlining of efforts. And I have no problem with dealing with the bumps of living on the latest version, be it the VM or the image. But, please consider the point of view of the one that offers the feedback. Right now, it sounds as if you are shooting down an unreasonable request from Stephan, but in this case, Esteban suggested that we should use the Cog VM instead of the Pharo VM to develop Moose, given that the Pharo VM is basically broken for us. So, Stephan did exactly that: he used the Cog VM. He reported that the tests do not crash the VM, which I think should be a relevant input, and he also reported other problems while running on the Cog VM. These errors indeed seem to be related to FileSystem, and this just shows that using the Cog VM as a temporary solution does not work. So, we have to focus on the Pharo VM. And now, I am back to the original question: What other tests or experiments would you like us to do to help with identifying the problem? Cheers, Doru On Tue, Mar 12, 2013 at 4:53 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > FileDialogs apparently make use of the new FileSystem values, so yes, > the update-our-VM-warning is there for a good reason! > > On 2013-03-12, at 16:47, Stephan Eggermont <stephan(a)stack.nl> wrote: > > > The problem is not just with the MOOSE image, > > Pharo 20598 and Cog.app 2071 doesn't allow a > > file dialog to be opened. > > > > FileDialogWindow new open > > > > Stephan > > > > > -- www.tudorgirba.com "Every thing has its own flow"

March 12, 2013

[Pharo-project] Kiln Harmony

by phil＠highoctane.be

http://blog.fogcreek.com/announcing-kiln-harmony-the-future-of-dvcs/ Guess as we are on FogBugz, it is worth a look :-) Phil

March 12, 2013

Re: [Pharo-project] beta 1.4 documentation online

by phil＠highoctane.be

And it is not even true <imageName> defaults to `Squeak.image'. as I get a file dialog when such an image is in the folder. (Duly created with the save command) Phil 2013/3/12 Camillo Bruni <camillobruni(a)gmail.com>: > > On 2013-03-12, at 16:51, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> These are the standard installed handlers: >> >> $ ../vm.sh Pharo.image --list >> Currently installed Command Line Handlers: >> st Loads and executes .st source files >> Fuel Loads fuel files >> config Install and inspect Metacello Configurations from the command line >> save Rename the image and changes file >> test A command line test runner >> update Load updates >> printVersion Print image version >> eval Directly evaluates passed in one line scripts >> >> for each of them you can do --help >> >> $ ../vm.sh Pharo.image save --help >> Usage: save <imageBaseName> [--delete-old] >> <imageName> a base name for the image >> --delete-old remove the old image and changes file >> >> Documentation: >> Saves the image and changes file under a new name. >> >> Examples: >> # create a 'bar.image' and 'foo.changes' >> $PHAROVM Foo.image saveAs bar >> # create the same file as in the previous example but delete Foo.image and Foo.changes >> $PHAROVM Foo.image saveAs bar --delete-old >> >> Sven > > ups, typos, typos: saveAs => save :/ > I'll open an issue > > >> On 12 Mar 2013, at 16:48, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> That already exists no ? >>> >>> $ ./vm.sh Pharo.image save Foo >>> >>> will do a 'Save As..' to Foo.[image|changes] >>> >>> On 12 Mar 2013, at 16:45, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >>> >>>> BTW, an interesting additional ./vm.sh command would be: >>>> >>>> $./vm.sh clone Pharo WebDocExperiment >>>> >>>> which would do a copy of Pharo.image and Pharo.changes to the >>>> WebDoc.image and WebDoc.changes >>>> >>>> Phil >>>> 2013/3/12 Martin Dias <tinchodias(a)gmail.com>: >>>>> impressive!! >>>>> >>>>> On Tue, Mar 12, 2013 at 3:06 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >>>>>> http://pharo.gforge.inria.fr/doc/1.4/doc/package/undefined >>>>>> >>>>>> RSArrayNode. >>>>>> >>>>>> 2013/3/12 Camillo Bruni <camillobruni(a)gmail.com>: >>>>>>> >>>>>>> On 2013-03-12, at 14:49, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >>>>>>> >>>>>>>> On Tue, Mar 12, 2013 at 2:18 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: >>>>>>>> >>>>>>>>> finally, after the 100th attempt I managed to export the documentation on >>>>>>>>> 1.4 >>>>>>>>> >>>>>>>>> http://pharo.gforge.inria.fr/doc/1.4 >>>>>>>>> >>>>>>>>> this weekend I will tackle 2.0 :) and of course, it still needs some love! >>>>>>>>> >>>>>>>>> >>>>>>>> - How can I export it myself too? >>>>>>> >>>>>>> currently work in progress, but there is a configuration for it: >>>>>>> >>>>>>> Gofer new >>>>>>> url: 'http://smalltalkhub.com/mc/dh83/webdoc/main' >>>>>>> configurationOf: 'WebDoc'; >>>>>>> loadDevelopment. >>>>>>> >>>>>>> And I think you have to manually start up a seaside adapter, once that is done: >>>>>>> >>>>>>> http://localhost:8080/doc >>>>>>> >>>>>>> should do the trick. >>>>>>> >>>>>>> >>>>>>>> - We should report issues about it in the foogzbuz (or whatever it is >>>>>>>> called I cannot reproduce yet :P). >>>>>>> >>>>>>> yes, maybe let's wait until next weekend :) since it doesn't run under >>>>>>> 2.0 yet :P. I won't work on during the day :P that is reserved for Guido and >>>>>>> the paper... >>>>>> >>>>> >>>> >>> >> > >

March 12, 2013

Re: [Pharo-project] beta 1.4 documentation online

by phil＠highoctane.be

<imageName> defaults to `Squeak.image'. WHAT?! PhilMac:~/Documents/Smalltalk/2-MyWorkspaces/workspaceZeroConf20130312 philippeback$] ./vm.sh --help unknown option: --help Usage: [<option>...] [<imageName> [<argument>...]] [<option>...] -- [<argument>...] Common <option>s: -help print this help message, then exit -memory <size>[mk] use fixed heap size (added to image size) -headless run in headless (no window) mode (default: false) Notes: <imageName> defaults to `Squeak.image'. If `-memory' is not specified then the heap will grow dynamically. <argument>s are ignored, but are processed by the Squeak image. The first <argument> normally names a Squeak `script' to execute. Precede <arguments> by `--' to use default image. 2013/3/12 Camillo Bruni <camillobruni(a)gmail.com>: > > On 2013-03-12, at 16:51, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> These are the standard installed handlers: >> >> $ ../vm.sh Pharo.image --list >> Currently installed Command Line Handlers: >> st Loads and executes .st source files >> Fuel Loads fuel files >> config Install and inspect Metacello Configurations from the command line >> save Rename the image and changes file >> test A command line test runner >> update Load updates >> printVersion Print image version >> eval Directly evaluates passed in one line scripts >> >> for each of them you can do --help >> >> $ ../vm.sh Pharo.image save --help >> Usage: save <imageBaseName> [--delete-old] >> <imageName> a base name for the image >> --delete-old remove the old image and changes file >> >> Documentation: >> Saves the image and changes file under a new name. >> >> Examples: >> # create a 'bar.image' and 'foo.changes' >> $PHAROVM Foo.image saveAs bar >> # create the same file as in the previous example but delete Foo.image and Foo.changes >> $PHAROVM Foo.image saveAs bar --delete-old >> >> Sven > > ups, typos, typos: saveAs => save :/ > I'll open an issue > > >> On 12 Mar 2013, at 16:48, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> That already exists no ? >>> >>> $ ./vm.sh Pharo.image save Foo >>> >>> will do a 'Save As..' to Foo.[image|changes] >>> >>> On 12 Mar 2013, at 16:45, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >>> >>>> BTW, an interesting additional ./vm.sh command would be: >>>> >>>> $./vm.sh clone Pharo WebDocExperiment >>>> >>>> which would do a copy of Pharo.image and Pharo.changes to the >>>> WebDoc.image and WebDoc.changes >>>> >>>> Phil >>>> 2013/3/12 Martin Dias <tinchodias(a)gmail.com>: >>>>> impressive!! >>>>> >>>>> On Tue, Mar 12, 2013 at 3:06 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >>>>>> http://pharo.gforge.inria.fr/doc/1.4/doc/package/undefined >>>>>> >>>>>> RSArrayNode. >>>>>> >>>>>> 2013/3/12 Camillo Bruni <camillobruni(a)gmail.com>: >>>>>>> >>>>>>> On 2013-03-12, at 14:49, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >>>>>>> >>>>>>>> On Tue, Mar 12, 2013 at 2:18 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: >>>>>>>> >>>>>>>>> finally, after the 100th attempt I managed to export the documentation on >>>>>>>>> 1.4 >>>>>>>>> >>>>>>>>> http://pharo.gforge.inria.fr/doc/1.4 >>>>>>>>> >>>>>>>>> this weekend I will tackle 2.0 :) and of course, it still needs some love! >>>>>>>>> >>>>>>>>> >>>>>>>> - How can I export it myself too? >>>>>>> >>>>>>> currently work in progress, but there is a configuration for it: >>>>>>> >>>>>>> Gofer new >>>>>>> url: 'http://smalltalkhub.com/mc/dh83/webdoc/main' >>>>>>> configurationOf: 'WebDoc'; >>>>>>> loadDevelopment. >>>>>>> >>>>>>> And I think you have to manually start up a seaside adapter, once that is done: >>>>>>> >>>>>>> http://localhost:8080/doc >>>>>>> >>>>>>> should do the trick. >>>>>>> >>>>>>> >>>>>>>> - We should report issues about it in the foogzbuz (or whatever it is >>>>>>>> called I cannot reproduce yet :P). >>>>>>> >>>>>>> yes, maybe let's wait until next weekend :) since it doesn't run under >>>>>>> 2.0 yet :P. I won't work on during the day :P that is reserved for Guido and >>>>>>> the paper... >>>>>> >>>>> >>>> >>> >> > >

March 12, 2013

Re: [Pharo-project] about communication and collaboration

by stephane ducasse

On Mar 12, 2013, at 4:48 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > On Tue, Mar 12, 2013 at 4:02 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Dear Pharoers >> >> last january I visited another lab and I realised that the Pharo Team was not good at systematically telling what we were doing. >> I got quite frustrated by that situation, especially because we are working hard to build a better system. >> So we brainstormed when I came back and we want to apply the same ideas that what we do for our research team. >> >> For our research team every monday we get a simple mail that tell us to say to the others what we did and what we >> plan to do. Simple, easy. >> Then after people of the rmod team can discuss if they want more. > > It looks like quite an interesting idea in a research team. Do you a > have a description somewhere how it works ? > This is similar to a standup meeting ? we tried but a stand up meeting failed with us. So we just have a mail what you have done what you will do Stfe > > Regards, > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ >

March 12, 2013

Re: [Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24

by stephane ducasse

On Mar 12, 2013, at 4:08 PM, seaside(a)rmod.lille.inria.fr wrote: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS - working with Damien Cassou on the pier extensions: missing figures but else the html is - migrating XMLParser - migrating XMLWriter - migrating Soup - migrating other moosish collections - first release of the ZeroConf chapter - migrating sound - Pharo 2.0 list of actions - producing issues for 3.0 :) - learn with igor on resources management and weakregistry bugs :) > ### What's next, until 2013-03-24 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION > > (*) we'll be expecting results by then ;) - Retrospective planning - Continue to migrate projects to Smalltalkhub game moose projects look for orphan squeaksource important project - Finish block chapter for the book - Add discussion about tests in default group the metacello chapter! - Prepare and plan 3.0 features introduction Stef

March 12, 2013

Re: [Pharo-project] beta 1.4 documentation online

by phil＠highoctane.be

Ah, one critter less! 2013/3/12 Camillo Bruni <camillobruni(a)gmail.com>: > > On 2013-03-12, at 16:51, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> These are the standard installed handlers: >> >> $ ../vm.sh Pharo.image --list >> Currently installed Command Line Handlers: >> st Loads and executes .st source files >> Fuel Loads fuel files >> config Install and inspect Metacello Configurations from the command line >> save Rename the image and changes file >> test A command line test runner >> update Load updates >> printVersion Print image version >> eval Directly evaluates passed in one line scripts >> >> for each of them you can do --help >> >> $ ../vm.sh Pharo.image save --help >> Usage: save <imageBaseName> [--delete-old] >> <imageName> a base name for the image >> --delete-old remove the old image and changes file >> >> Documentation: >> Saves the image and changes file under a new name. >> >> Examples: >> # create a 'bar.image' and 'foo.changes' >> $PHAROVM Foo.image saveAs bar >> # create the same file as in the previous example but delete Foo.image and Foo.changes >> $PHAROVM Foo.image saveAs bar --delete-old >> >> Sven > > ups, typos, typos: saveAs => save :/ > I'll open an issue > > >> On 12 Mar 2013, at 16:48, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> That already exists no ? >>> >>> $ ./vm.sh Pharo.image save Foo >>> >>> will do a 'Save As..' to Foo.[image|changes] >>> >>> On 12 Mar 2013, at 16:45, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >>> >>>> BTW, an interesting additional ./vm.sh command would be: >>>> >>>> $./vm.sh clone Pharo WebDocExperiment >>>> >>>> which would do a copy of Pharo.image and Pharo.changes to the >>>> WebDoc.image and WebDoc.changes >>>> >>>> Phil >>>> 2013/3/12 Martin Dias <tinchodias(a)gmail.com>: >>>>> impressive!! >>>>> >>>>> On Tue, Mar 12, 2013 at 3:06 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >>>>>> http://pharo.gforge.inria.fr/doc/1.4/doc/package/undefined >>>>>> >>>>>> RSArrayNode. >>>>>> >>>>>> 2013/3/12 Camillo Bruni <camillobruni(a)gmail.com>: >>>>>>> >>>>>>> On 2013-03-12, at 14:49, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >>>>>>> >>>>>>>> On Tue, Mar 12, 2013 at 2:18 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: >>>>>>>> >>>>>>>>> finally, after the 100th attempt I managed to export the documentation on >>>>>>>>> 1.4 >>>>>>>>> >>>>>>>>> http://pharo.gforge.inria.fr/doc/1.4 >>>>>>>>> >>>>>>>>> this weekend I will tackle 2.0 :) and of course, it still needs some love! >>>>>>>>> >>>>>>>>> >>>>>>>> - How can I export it myself too? >>>>>>> >>>>>>> currently work in progress, but there is a configuration for it: >>>>>>> >>>>>>> Gofer new >>>>>>> url: 'http://smalltalkhub.com/mc/dh83/webdoc/main' >>>>>>> configurationOf: 'WebDoc'; >>>>>>> loadDevelopment. >>>>>>> >>>>>>> And I think you have to manually start up a seaside adapter, once that is done: >>>>>>> >>>>>>> http://localhost:8080/doc >>>>>>> >>>>>>> should do the trick. >>>>>>> >>>>>>> >>>>>>>> - We should report issues about it in the foogzbuz (or whatever it is >>>>>>>> called I cannot reproduce yet :P). >>>>>>> >>>>>>> yes, maybe let's wait until next weekend :) since it doesn't run under >>>>>>> 2.0 yet :P. I won't work on during the day :P that is reserved for Guido and >>>>>>> the paper... >>>>>> >>>>> >>>> >>> >> > >

March 12, 2013

[Pharo-project] Getting SoundRecorder to work: how?

by phil＠highoctane.be

sr := SoundRecorder new. sr startRecording. sr stopRecording. sr playback. doesn't seem to do anything properly and gives me a DNU inside the playback... Clues? Phil

March 12, 2013

Re: [Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24

by Damien Pollet

> > ### Here's what I've been up to since the last WhatsUp: > - adapt our weekly script to send this right here - start hacking a new LaTeX class for Pharo by Example sequels (Pharo Strikes Back, Pharo Episode IV: a new OOP, further titles undisclosed) - generally try to pair-program with the guys here: some FS-Git mostly ### What's next, until 2013-03-24 (*) - get a first reasonably complete document class - continue on FS-Git, maybe PetitMarkdown -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

March 12, 2013