- Pharo-dev - lists.pharo.org

Bug (and fix?) with #doSilently: and FileLibrary

by Mariano Martinez Peck

Hi guys, I noticed that when we add files to FileLibrary using provided methods like both methods are created, #selectorsToInclude and whatever you have updated, say, #myCss. However, if you go to Monticello Browser, only #selectorsToInclude appears. Digging a bit, I found out that Seaside ends up using Grease for that. And Grease does: GRPharoPlatform >>compile: aString into: aClass classified: aSymbol self doSilently: [ aClass compile: aString classified: aSymbol ] And then, of course, the doSilently, ends up doing: GRPharoPlatform >> doSilently: aBlock "Deals with a different between Pharo1.x and Pharo2.x" ^ (Smalltalk includesKey: #SystemChangeNotifier) ifTrue:[(Smalltalk at: #SystemChangeNotifier) uniqueInstance doSilently: aBlock] ifFalse:[(Smalltalk at: #SystemAnnouncer) uniqueInstance suspendAllWhile: aBlock] So...first, I don't like that a method named like #compile:into:classified: does a silently compilation. Normally, we have the "silently" as part of the selector (or a boolean parameter). Second, why would we want to compile silently? the idea is that after, we commit the FileLibrary...so if the method is not there, it is a problem. So, should we change the #compile:into:classified: to NOT do the silently? Thanks, -- Mariano http://marianopeck.wordpress.com

Oct. 10, 2013

Re: [Pharo-dev] [Pharo-users] Start with a trivial improvement!

by Facundo Vozzi

I like it Marcus. Good start point. Thanks On Thu, Oct 10, 2013 at 12:25 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > good idea > yes for the blog entry > > On Oct 10, 2013, at 1:42 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Thank you, Marcus! > > Could you post this on the Pharo blog? > > Doru > > > On Thu, Oct 10, 2013 at 1:36 PM, Sven Van Caekenberghe <sven(a)stfx.eu>wrote: > >> +100 >> >> On 10 Oct 2013, at 13:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> > One nice way to get in the mood of doing (and at the same time testing >> the system) is to start >> > with trivial improvements. >> > >> > This is especially nice as a "starter" when you never contributed any >> change to Pharo. >> > >> > And by trivial I mean *really* mean trivial: >> > -> a typo in a comment >> > -> remove a temp not accessed >> > -> clean out some trivial dead code >> > -> do a simplistic refactoring of a bad smell, even inside a >> single method >> > -> document something >> > -> structure bad stuff better so it is easier to replace later >> > >> > Taken in itself, single changes like these have no influence, but: >> > >> > -> they get you in a mood of doing. >> > -> they make you feel that Pharo is "owned" by you. >> > -> take 1000 of those trivialities and they *do* make a >> difference. >> > -> next time something bothers you, you will have the context of >> "I can just fix it". >> > >> > The critic tools is one way of finding these places, another is to just >> note down every time >> > you see a triviality and later go through that list. The bug tracker >> can be source, too. >> > >> > >> > <wtfm.jpg> >> > >> > Marcus >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > >

Oct. 10, 2013

Re: [Pharo-dev] ShortRunArray not in Pharo 3.0 anymore, leading to problems with FFI-Kernel-tbn.25

by Esteban Lorenzano

yes, and we encourage people to try their stuff in Pharo3, to provide feedback, etc. bet definitively not for putting anything on production on it :) Esteban On Oct 10, 2013, at 5:20 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > philippeback wrote >> It is too complex for me to get things loaded in 3.0 and be delivering >> what >> we need to, so I am back to 2.0 now. > > I think that's the right decision even if you could get it loaded. I > wouldn't deploy on a beta version of Pharo (no matter how tempting all the > cool new features are!!)... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ShortRunArray-not-in-Pharo-3-0-anymore-leading-to-pro… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 10, 2013

Re: [Pharo-dev] New Image Command Line Handlers

by StÃ©phane Ducasse

excellent I will update the StartUp script chapter (except if somebody wants to do it). On Oct 10, 2013, at 7:48 PM, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > We (Cami, Ben, and I) added some command line options to control preference > loading, which seem useful e.g. for integrators and in my original use case > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/New-Image-Command-Line-Handlers-tp4713693.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 10, 2013

Re: [Pharo-dev] ShortRunArray not in Pharo 3.0 anymore, leading to problems with FFI-Kernel-tbn.25

by StÃ©phane Ducasse

On Oct 10, 2013, at 5:20 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > philippeback wrote >> It is too complex for me to get things loaded in 3.0 and be delivering >> what >> we need to, so I am back to 2.0 now. > > I think that's the right decision even if you could get it loaded. I > wouldn't deploy on a beta version of Pharo (no matter how tempting all the > cool new features are!!)â¦ we are alpha :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ShortRunArray-not-in-Pharo-3-0-anymore-leading-to-pro… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 10, 2013

Re: [Pharo-dev] Please contributors fill up this form...

by StÃ©phane Ducasse

thanks I love this list :) On Oct 10, 2013, at 9:18 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Hi Stef, > > here is mine. > > Thierry > > Le 09/10/2013 13:34, StÃ©phane Ducasse a Ã©crit : >> Hi guys >> >> I would like to get >> contributors.pharo.org a bit more representative of Pharo. >> >> We should have Previous contributors and enhance the current list. >> Can you please reply to this mail >> >> PharoContributor new >> name: 'Thierry Goubier'; >> id: 'ThierryGoubier'; >> email: 'thierry.goubier(a)cea.fr'; >> website: 'http://www-list.cea.fr'; >> description: 'Parsers, language design and analysis, alternative IDE, gitfiletree, SmaCC, code traces.'; >> image: 'http://www.gravatar.com/avatar/193af464509ae8fbcc04abad70b72fc0?s=120'; >> yourself >> >> >> Stef >> > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Oct. 10, 2013

Re: [Pharo-dev] New Image Command Line Handlers

by phil＠highoctane.be

Good news. If by default on Windows, it would be another default than pharo\ it would be great as it would be nicer with zeroconf fetching pharo-ui and pharo (headless) Are those changes going to find their way in Pharo 2.0? Phil On Thu, Oct 10, 2013 at 7:48 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > We (Cami, Ben, and I) added some command line options to control preference > loading, which seem useful e.g. for integrators and in my original use case > of running an image off a USB stick on a foreign computer and not wanting > to > pick up those preferences > > There are two new flags: > 1. --no-default-preferences = don't load from any of the default locations > 2. --preference-file [/full/path/to/file.st] = load this one > > They are independent, so there are four options now: > 1 | 2 | > - current behavior > x - don't load any preferences > x - load the defaults and this additional > x x - only load the specified file (not the defaults) > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/New-Image-Command-Line-Handlers-tp4713693.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Oct. 10, 2013

New Image Command Line Handlers

by Sean P. DeNigris

We (Cami, Ben, and I) added some command line options to control preference loading, which seem useful e.g. for integrators and in my original use case of running an image off a USB stick on a foreign computer and not wanting to pick up those preferences There are two new flags: 1. --no-default-preferences = don't load from any of the default locations 2. --preference-file [/full/path/to/file.st] = load this one They are independent, so there are four options now: 1 | 2 | - current behavior x - don't load any preferences x - load the defaults and this additional x x - only load the specified file (not the defaults) ----- Cheers, Sean -- View this message in context: http://forum.world.st/New-Image-Command-Line-Handlers-tp4713693.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 10, 2013

Re: [Pharo-dev] [OT] Git Internals PDF

by Camillo Bruni

nice indeed :) On 2013-10-10, at 17:25, Max Leske <maxleske(a)gmail.com> wrote: > Thanks Torsten, nice of you to think of us! > > On 10.10.2013, at 17:14, Torsten Bergmann <astares(a)gmx.de> wrote: > >> "A PDF by Scott Chacon about how the Git source code control system stores files and revisions." >> >> https://github.com/pluralsight/git-internals-pdf/releases >> >> Maybe thats interesting for the people working on Pharo & Git >> > >

Oct. 10, 2013

Re: [Pharo-dev] [OT] Git Internals PDF

by Max Leske

Thanks Torsten, nice of you to think of us! On 10.10.2013, at 17:14, Torsten Bergmann <astares(a)gmx.de> wrote: > "A PDF by Scott Chacon about how the Git source code control system stores files and revisions." > > https://github.com/pluralsight/git-internals-pdf/releases > > Maybe thats interesting for the people working on Pharo & Git >

Oct. 10, 2013