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

Re: [Pharo-project] about communication and collaboration

by phil＠highoctane.be

A bad consultant with good marketing beats a good consultant with bad marketing. Looks like it works for a lot of things in life, light being faster than sound. (Oh, shiny!) "(S)he looked nice until (s)he opened his/her mouth". Phil 2013/3/12 Serge Stinckwich <serge.stinckwich(a)gmail.com>: > 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 ? > > 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 phil＠highoctane.be

### Here's what I've been up to since the last WhatsUp: * Trying out new image and messing around, reporting bugs in the process * Reporting issues with the iOS VM build * Getting the iOS VM to recognize a bluetooth keyboard * Getting the VM to build for debian 6 amd64 ### What's next, until 2013-03-24 (*): * Finishing up keyboard mapping for iOS VM * Understanding how to have amber working with Pharo through AidaWeb * Trying out new stuff coming my way * Getting the InterpreterSimulator running into the image Phil

March 12, 2013

Re: [Pharo-project] about communication and collaboration

by Esteban Lorenzano

I just sent my list of issues as an example... yes, is some kind like a remote-standup meeting. Esteban 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 ? > > 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 Camillo Bruni

On 2013-03-12, at 16:53, 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: - Jenkins: - new nodes - new matrix builds for Pharo2.0 - new matrix builds for http://ci.inria.fr/pharo-contribution - A nice NativeBoost paper - Pharo Online Documentation Generator > ### What's next, until 2013-03-24 (*): - NativeBoost Paper - Finish Pharo Online Documentation System

March 12, 2013

Re: [Pharo-project] beta 1.4 documentation online

by phil＠highoctane.be

Oh, thank you! Didn't notice that. Phil 2013/3/12 Sven Van Caekenberghe <sven(a)stfx.eu>: > 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 Camillo Bruni

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 Camillo Bruni

On 2013-03-12, at 16:48, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > That already exists no ? > > $ ./vm.sh Pharo.image save Foo exactly! :) I usally use: ./vm.sh Pharo.image save MyProject --delete-old so I have less mess around > 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 I think I will sit with Benjamin this weekend to hack on a per-project documentation solution: ./vm.sh MyProject.image docment --output-dir=doc MyPackage-Foo "MyPackage-Bar.*" and you will get a nice doc folder with a more or less ready to ship pharo documentation a la javadoc :) but with a source code navigation that rocks!

March 12, 2013

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

by Damien Pollet

Well, that took some timeâ¦ So that's the mail Stef was writing about. Tell us what you think! On 12 March 2013 16:08, <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 > > ### What's next, until 2013-03-24 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION > > (*) we'll be expecting results by then ;) > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

March 12, 2013

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

by Camillo Bruni

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 >

March 12, 2013

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

by Sven Van Caekenberghe

Stephan, On 12 Mar 2013, 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 Although it would certainly be nice that Pharo 2.0 ran on the regular Cog VM ( I want that too ), it is not a bug if it does not. The Pharo VM is the reference VM, it is as simple as that. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

March 12, 2013