- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Updating the Pharo Contributors listing

by Esteban Lorenzano

PharoContributor new name: 'Esteban Lorenzano'; id: 'estebanlm'; email: 'estebanlm(a)gmail.com'; website: 'http://smallworks.eu'; description: 'Pharo core team. Contributor of several projects, including Kernel, DBXTalk, Voyage, Mars, etc. Also I work on the VM.'; image: 'http://www.gravatar.com/avatar/193af464509ae8fbcc04abad70b72fc0?s=120'; yourself On Aug 18, 2013, at 12:39 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi Jannik, > > On 16 Aug 2013, at 21:23, jannik.laval <jannik.laval(a)gmail.com> wrote: > >> PharoContributor new >> name: 'Jannik Laval'; >> id: 'jannik.laval'; >> email: 'jannik.laval(a)gmail.com'; >> website: 'http://www.jannik-laval.eu'; >> description: 'Software Researcher at Mines Douai'; >> image: 'http://www.jannik-laval.eu/assets/images/DSC02023%20-%20Version%202.jpg'; >> yourself > > Updated: > > http://contributors.pharo.org#janniklaval > > Thanks. > > Sven > >> On Aug 12, 2013, at 5:12 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> Dear Fellow Pharoers, >>> >>> As some of you may know, we have a page listing Pharo Contributors >>> >>> http://www.pharo-project.org/community/contributors >>> >>> This page was manually constructed and urgently needs an update. >>> Based on the code behind the Pharo Consultants page >>> >>> http://consultants.pharo.org >>> >>> we want a similar data driven, statically generated page for Pharo Contributors >>> >>> http://contributors.pharo.org >>> >>> the new page is based on some of the old data, but needs updating. Many people are missing as well. So please, please, edit the template and send me your new or up to date information. >>> >>> PharoContributor new >>> name: 'StÃ©phane Ducasse'; >>> id: 'stephaneducasse'; >>> email: 'stephane.ducasse(a)inria.fr'; >>> website: 'http://stephane.ducasse.free.fr/'; >>> description: 'Research director at INRIA Lille leading the RMoD Team. Pharo board member and president of ESUG.'; >>> image: 'http://stephane.ducasse.free.fr/StefFingerOnNose128.jpg'; >>> yourself >>> >>> PharoContributor new >>> name: 'Camillo Bruni'; >>> email: 'camillobruni(a)gmail.com'; >>> description: 'Cosmopolitan Swiss Hacker, currently at INRIA'; >>> yourself >>> >>> Some notes: >>> >>> - id is only needed when your name contains non-ascii characters >>> - email will default to pharo-dev(a)lists.pharo.org if missing >>> - website will default to a Google search for your name if a URL is missing >>> - image can be omitted if you have a Gravatar, else it becomes a smiley >>> - images will be rescaled to fit in 128x128, the URL needs to remain accessible >>> - description is a pure text String, no markup is allowed >>> - the description does not have to be too formal >>> - the page is statically generated, only then do changes take effect >>> >>> Regards, >>> >>> Sven, on behalf of the Pharo Board. >>> >>> PS: If you are curious, the code for generating this page can be found at >>> >>> http://www.smalltalkhub.com/#!/~Pharo/PharoPeople >>> >>> >> > >

Aug. 19, 2013

Re: [Pharo-dev] WhatsUp from: 2013-08-19 until: 2013-08-31

by Tudor Girba

Hi, ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS > - Significant Moose cleaning and preparation for the release - Strenghtening Snapshotcello (a new release is available for Pharo 2.0) - Working on a robust and configurable object traverser - Working with Andrei on some exciting new debuggers (yes, you read right: we are working on multiple debuggers that can be customized and interchanged. it's so cool) - Continue work on a new Coder design - Wrote more blog posts about using Moose for solving specific problems ( http://humane-assessment.com) ### What's next, until 2013-08-31 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION > - Release Moose - Finish the object traverser Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Aug. 19, 2013

Re: [Pharo-dev] WhatsUp from: 2013-08-19 until: 2013-08-31

by Alexandre Bergel

> - More PWM What is that? > - See how to merge my NBXLib fork with existing one. A two sentence description of these forks? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 19, 2013

Re: [Pharo-dev] WhatsUp from: 2013-08-19 until: 2013-08-31

by laurent laffont

> > ### Here's what I've been up to since the last WhatsUp: > - Learn NativeBoost to bind XLib - Write a chapter on the subject for "Pharo for the enterprise" book, see https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… - Start an X11 window manager using Pharo > ### What's next, until 2013-08-31 (*): > - Improve the chapter - More PWM - See how to merge my NBXLib fork with existing one. Laurent

Aug. 19, 2013

Re: [Pharo-dev] why can we interrupt the UI thread?

by Esteban Lorenzano

I do not understand. Can you elaborate a bit? On Aug 15, 2013, at 10:21 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >

Aug. 19, 2013

Re: [Pharo-dev] WhatsUp from: 2013-08-19 until: 2013-08-31

by Esteban Lorenzano

On Aug 19, 2013, at 7:00 AM, 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: - mainly fighting with the VM, its plugins and jenkins jobs. - broadcast system for consortium/association -pharo bugs and integrations. > > ### What's next, until 2013-08-31 (*): - more VM hit and run :) - maybe, just maybe, finish milestone 1 of broadcast. - fix RPackage and Traits (broken now) - ... no idea what else will emerge.

Aug. 19, 2013

Re: [Pharo-dev] WhatsUp from: 2013-08-19 until: 2013-08-31

by Damien Cassou

### Here's what I've been up to since the last WhatsUp: - CI jobs for Pier, Magritte and Grease (https://ci.inria.fr/pharo-contribution/) - Fix Magritte so its job is green - Improve code and add features in Pharo to make a better PharoLauncher (http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher) ### What's next, until 2013-08-31 (*): Fix Grease and Pier so their jobs are green Make use of the improvements in Pharo for the PharoLauncher Finish the Deep Into Pharo book -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Aug. 19, 2013

[update 3.0] #30337

by Marcus Denker

30337 ----- 11394 Needed support for traits in ClassFactoryForTestCase https://pharo.fogbugz.com/f/cases/11394 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/SUnit-Tests-MarcusDenker.23.d… http://smalltalkhub.com/mc/Pharo/Pharo30/main/SUnit-Core-MarcusDenker.92.di…

Aug. 19, 2013

Re: [Pharo-dev] WhatsUp from: 2013-08-19 until: 2013-08-31

by StÃ©phane Ducasse

On Aug 19, 2013, at 7:00 AM, 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: - cleaning, integrating fixes. - toooooook far too much time. - working on textEditor with igor - working on AutomaticMethodCategorizer - working on SystemLogger > ### What's next, until 2013-08-31 (*): - finish first version of SystemLogger - finish first version of AutomaticMethodCategorizer

Aug. 19, 2013

Re: [Pharo-dev] About SqNumberParser

by StÃ©phane Ducasse

thanks! Stef > I think just because 1.0s was explicitely not supported in Squeak? > There should be some related tests... > It should be rather simple to change. > > > 2013/8/13 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi nicolas > > We would really like to have only one number parser in Pharo as well as handling the 1.0s syntax > marcus raised a question that I could not answer. > Do you habve nfrmation to share with us so that we can take a decision? > > Stef > > > so the strange thing is that this is *explicitly* implemented in SqNumberParser to not allow 2.0s > > - do not allow single s without following digits as ScaledDecimal > > It is not explained why this is a good idea. > > In general, we need to merge the whole NumberParser hierarchy into one class, i don't understand why we have three classes now. >

Aug. 19, 2013