- Pharo-dev - lists.pharo.org

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

by Alexandre Bergel

> ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS * Worked hard on Deep into Pharo * Make significant progress on Roassal 3d (Thanks to Ronie and Milton). Screenshots are available on https://twitter.com/ObjectProfile * Packaged Sunburst, video available on http://bit.ly/sunburstDemo * Many fix and improvement integration of Roassal. New release is in the pipeline > > ### What's next, until 2013-08-31 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION * Working on memory profiling * Doing a new pass on Deep into Pharo * Integrate the foreword by Dave Thomas in Deep into Pharo * Help the Object Profile crew with their presentations for ESUG :-) Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 19, 2013

WhatsUp from: 2013-08-19 until: 2013-08-31

by seaside＠rmod.lille.inria.fr

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-08-31 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

Aug. 19, 2013

Re: [Pharo-dev] About SqNumberParser

by Nicolas Cellier

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. 18, 2013

Re: [Pharo-dev] PharoSound load error in Pharo 2.0

by jannik.laval

I tried again and again without understandingâ¦ Now, what I have: If I inspect: " (ConfigurationOfPhratch project version: '1.0-baseline') record.", the version recorded is 5.4 (I am hoping to have 5.3) === a MetacelloNullRecordingMCSpecLoader(linear load : linear load : 1.0-baseline [ConfigurationOfPhratch] load : ConfigurationOfOSProcess linear load : 1.0-baseline [ConfigurationOfPhratch] load : ConfigurationOfPharoSound linear load : 1.0-baseline [ConfigurationOfPhratch] linear load : 5.4 [ConfigurationOfPharoSound] load : Sound-StephaneDucasse.76 load : Settings-Sound-HenrikSperreJohansen.2 load : SoundScores-StephaneDucasse.6 load : SoundMorphicUserInterface-StephaneDucasse.29 [â¦] load : Phratch) === BUT, if I inspect "(ConfigurationOfPhratch project version: '1.0-baseline') ignoreImage: true; record.", It works fine. === a MetacelloNullRecordingMCSpecLoader(linear load : linear load : 1.0-baseline [ConfigurationOfPhratch] load : ConfigurationOfOSProcess linear load : 1.0-baseline [ConfigurationOfPhratch] load : ConfigurationOfPharoSound linear load : 1.0-baseline [ConfigurationOfPhratch] linear load : 5.3 [ConfigurationOfPharoSound] load : Sound-StephaneDucasse.75 load : Settings-Sound-HenrikSperreJohansen.2 load : SoundScores-StephaneDucasse.6 load : Collections-Arithmetic-GuillermoPolito.4 load : SoundMorphicUserInterface-StephaneDucasse.27 [â¦] load : Phratch) === Why the ignoreImage change the behavior ? Jannik On Aug 18, 2013, at 10:27 AM, jannik.laval <jannik.laval(a)gmail.com> wrote: > > On Aug 18, 2013, at 10:18 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> >> On Aug 18, 2013, at 8:42 AM, jannik.laval <jannik.laval(a)gmail.com> wrote: >> >>> Hum, I do not understand. >>> When I load it with your script it works (it loads the version 75 of Sound). >>> Now, with Phratch it tries to load the version 76 of Sound. >>> >>> Here is my configuration: >>> >>> === >>> baseline10: spec >>> <version:'1.0-baseline'> >>> spec for: #common do: [ >>> spec blessing: #baseline. >>> spec repository: 'http://smalltalkhub.com/mc/JLaval/Phratch/main'. >>> spec project: 'Sound' with: [ >>> spec >>> repository: 'http://smalltalkhub.com/mc/PharoExtras/Sound/main'; >>> versionString: #stable; >>> className: 'ConfigurationOfPharoSound']. >>> spec package: 'Phratch' with: [ >>> spec requires: 'Sound'. >>> ]. >>> ]. >>> === >>> >> >> did you try with '5.3'? to see > > Yes, I tried and I have the same behavior. > There is something I do not understand, and the chapter about Metacello does not help me :( > > Jannik > > >> >>> And I load it with : >>> (ConfigurationOfPhratch project latestVersion: #baseline) load. >>> >>> So, why does it not take the stable version of PharoSound ? >> >> >> I do not know. we should ask dale. >> >>> >>> Thanks for the help. >>> Jannik >>> >>> >>> >>> On Aug 17, 2013, at 7:03 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>>> jannik >>>> >>>> >>>> (ConfigurationOfPharoSound project version: '5.3') load >>>> >>>> loads perfectly in 2.0 >>>> >>>> >>>> stable: spec >>>> <symbolicVersion: #stable> >>>> >>>> spec for: #'pharo1.0.x' version: '1.0'. >>>> spec for: #'pharo1.1.x' version: '3.0'. >>>> spec for: #'pharo1.2.x' version: '3.0'. >>>> spec for: #'pharo1.4.x' version: '5.0'. >>>> spec for: #'pharo2.0.x' version: '5.3'. >>>> spec for: #'pharo3.0.x' version: '5.4'. >>>> >>>> (ConfigurationOfPharoSound project version: '5.3') load >>>> loads perfectly on a freshly downloaded 2.0 image >>>> >>>> So tell me more. >>>> >>>> Stef >>>> >>>> >>> >>> >> >> >

Aug. 18, 2013

Re: [Pharo-dev] Anyone in St Petersburg?

by ÐÐ»Ð°Ð´Ð¸Ð¼Ð¸Ñ ÐÑÑÑÐ»Ð°Ð¹Ð½ÐµÐ½

Hi! I live in Saint-Petersburg andÂ I should be glad to meet with you! regards Vladimir Musulainen ÐÐ¾ÑÐºÑÐµÑÐµÐ½ÑÐµ, 18 Ð°Ð²Ð³ÑÑÑÐ° 2013, 13:45 +02:00 Ð¾Ñ Alexandre Bergel <alexandre.bergel(a)me.com>: >Hi! > >I am spending the week in Russia to attend ESEC/FSE. Just wondering whether some of the Russian crew here are up to a drink this week. > >Cheers, >Alexandre >-- >_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >Alexandre Bergel http://www.bergel.eu >^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- ÐÐ»Ð°Ð´Ð¸Ð¼Ð¸Ñ ÐÑÑÑÐ»Ð°Ð¹Ð½ÐµÐ½

Aug. 18, 2013

Re: [Pharo-dev] I would prefer to see the diff from Smalltalkhub than Git commits

by Alexandre Bergel

I have a (probably) naive question. What is stored on Github? How good the git support is in Pharo? Do I still need to use command lines to commit an application? Cheers, Alexandre On Aug 17, 2013, at 8:27 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > nope, the smalltalk hub diffs are clearly minor > > - they are auto generate, no manual intervention needed to send them > - they are only sent if the build succeeds > - they include valuable information > - the github repository is the place where you go to find changes, it's simply impossible to figure out when something broke on smalltalkhub since you cannot compare multiple packages over multiple times > > and... I thought we agree that I send the diff from github. > Usually the diff gets send along with the update, but since there was a strange update that didn't change any code, the export script failed, so I catch up with the export. > > > On 2013-08-16, at 17:02, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi >> >> could we avoid to get the github commits. I would prefer to get diff from Smalltalkhub. >> >> Stef > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 18, 2013

Anyone in St Petersburg?

by Alexandre Bergel

Hi! I am spending the week in Russia to attend ESEC/FSE. Just wondering whether some of the Russian crew here are up to a drink this week. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 18, 2013

Re: [Pharo-dev] I would prefer to see the diff from Smalltalkhub than Git commits

by Camillo Bruni

I just care for a solution that works now, in the present and needs no interaction, no hypothetical thingy. In any case, I redirected the messages to my account. If anybody is interested let me know... On 2013-08-18, at 11:33, Stephan Eggermont <stephan(a)stack.nl> wrote: > Camillo wrote: >> - they are auto generate, no manual intervention needed to send them > > So they should go to the issue tracker list > >> - the github repository is the place where you go to find changes, it's simply impossible to figure out when >> something broke on smalltalkhub since you cannot compare multiple packages over multiple times > > Sounds like it's time to migrate Torch.

Aug. 18, 2013

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

by Sven Van Caekenberghe

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. 18, 2013

Re: [Pharo-dev] I would prefer to see the diff from Smalltalkhub than Git commits

by Stephan Eggermont

Camillo wrote: >- they are auto generate, no manual intervention needed to send them So they should go to the issue tracker list >- the github repository is the place where you go to find changes, it's simply impossible to figure out when > something broke on smalltalkhub since you cannot compare multiple packages over multiple times Sounds like it's time to migrate Torch. Stephan

Aug. 18, 2013