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

Re: [Pharo-dev] The interrupt semaphore

by Guillermo Polito

In any case, I'd understand why, but we still have that semaphore installed in the special objects array, and code in the VM for handling it... On Fri, Jun 7, 2013 at 4:31 PM, Guillermo Polito <guillermopolito(a)gmail.com>wrote: > We are not using it? > > Why interruption is made by the event fetcher process? > > Guille >

June 7, 2013

The interrupt semaphore

by Guillermo Polito

We are not using it? Why interruption is made by the event fetcher process? Guille

June 7, 2013

Re: [Pharo-dev] Necessity of TDD with Smalltalk

by btc＠openinworld.com

June 7, 2013

For 2.0: links point to latest build on pharp-project.org

by Marcus Denker

Hi, I changed all links to point to the latest 2.0 build on files.pharo.org Reason: -> We are fixing bugs, yet people downloading 2.0 do not see the fix -> We had multiple times that people wasted quite some effort re-reporting bugs that are already fixed. Notes -> the file name "latest.zip" is not good for the image. It should encode that it is the image only and the version number maybe? -> I did not change any VM related download links, but I think we should do the same there. Marcus

June 7, 2013

Re: [Pharo-dev] Moving PostgresV2 from SS to Shub. Any objection?

by StÃ©phane Ducasse

On Jun 7, 2013, at 2:44 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi guys, > > I was going to commit something on PostgresV2 in SS but then I though it is a good opportunity to moved it to SmalltalkHub. > > Any objection? Pleasssssssseeeeeeeeeee You can put it in Pharo Extras Setf > > Thanks, > > -- > Mariano > http://marianopeck.wordpress.com

June 7, 2013

Re: [Pharo-dev] Moving PostgresV2 from SS to Shub. Any objection?

by phil＠highoctane.be

If we could get a full DBXTalk solution for Pharo 2.0, it would be awesome. Phil On Fri, Jun 7, 2013 at 3:07 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 07 Jun 2013, at 14:44, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > Hi guys, > > > > I was going to commit something on PostgresV2 in SS but then I though it > is a good opportunity to moved it to SmalltalkHub. > > > > Any objection? > > Nope. Good idea ;-) > > > Thanks, > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > >

June 7, 2013

[update 3.0] #30185

by StÃ©phane Ducasse

30185 ----- 10828 Cleaning Morphic https://pharo.fogbugz.com/f/cases/10828 10830 Cleaning Morphic (stringMorph enabled) https://pharo.fogbugz.com/f/cases/10830 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-StephaneDucasse.… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-StephaneDuc… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-StephaneDucasse.…

June 7, 2013

Re: [Pharo-dev] Moving PostgresV2 from SS to Shub. Any objection?

by Sven Van Caekenberghe

On 07 Jun 2013, at 14:44, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi guys, > > I was going to commit something on PostgresV2 in SS but then I though it is a good opportunity to moved it to SmalltalkHub. > > Any objection? Nope. Good idea ;-) > Thanks, > > -- > Mariano > http://marianopeck.wordpress.com

June 7, 2013

Re: [Pharo-dev] Necessity of TDD with Smalltalk

by Rafael Luque

Dennis, It would be great to receive your ideas about how to use mocks in this case. Feel free to add any comment directly in the screencast at Vimeo (http://vimeo.com/19591202) Thank you! 2013/6/7 Dennis Schetinin <chaetal(a)gmail.com> > As for me, the StringCalculator kata is a very good (or better to say > nearly perfect) demo of a classic TDD approach: small and fast steps, live > objectsâ¦ really nice! > > Though I see (feel?) some issuesâ¦ mostly about factoring-out new classes > without tests (yes, that was refactoringâ¦ but still), I believe, that's > beyond classic approach and only top-down TDD with mocks may help to keep > TDD pure here. (I've scheduled a task for detailed exploration of how mocks > can be used here to provide "seamless" TDD in this case.) > > So, this screencast is a great lesson on TDD in Smalltalk. > > > > -- > > Best regards, > > > Dennis Schetinin > > > 2013/6/7 Rafael Luque <rafael.luque.leiva(a)gmail.com> > >> Hi Dennis, >> >> What do you think about the approach shown in this screencast: >> http://www.pharocasts.com/2011/02/stringcalculator-kata.html ? >> >> I'm far away from being an Smalltalk developer, but I tried to show a TDD >> process to solve this simple kata. >> >> Rafael Luque >> >> >> 2013/6/7 Dennis Schetinin <chaetal(a)gmail.com> >> >>> I don't remember exactly where and when, but I think we've discussed the >>> Laser Game tutorial already. I told this before, and I (after reviewing the >>> tutorial again) should repeat it again: actually, this tutorial doesn't >>> show TDD. I can explain my opinion in detail if someone's interested, but >>> in general, that's simply an up-front design approach with some automatic >>> testing. It's not even "Test-First" approach most of time. >>> >>> Disclaimer: I don't mean the tutorial and/or the design approach used >>> there are bad. I like this tutorial. It's really very good: it shows many >>> aspects for Smalltalk programing, it shows how to use debugger and >>> inspectors properly. I borrowed many ideas from there for my Smalltalk >>> programming courseâ¦ It's just not TDD, not "pure" TDD at least. >>> >>> >>> >>> -- >>> >>> Best regards, >>> >>> >>> Dennis Schetinin >>> >>> >>> 2013/6/7 <btc(a)openinworld.com> >>> >>> Paul Davidowitz wrote: >>>> >>>>> It seems to me that a big reason for developing via writing tests first >>>>> (Test Driven Development) is that the tests serve as a debugging tool >>>>> -- >>>>> if a test breaks, then the last piece of (non-test) code that change is >>>>> likely the culprit. But with the powerful debugging environment that >>>>> comes with Smalltalk, I am wondering of the utility of TDD (TDD is big >>>>> in the Ruby camp perhaps for a reason). After all, writing and >>>>> re-writing the tests becomes quite a non-trivial chore (not to mention >>>>> that the tests themselves could be buggy). So my question: Is it ok in >>>>> Smalltalk to write tests afterwards? Is it even perhaps recommended? >>>>> >>>>> - Paul >>>>> >>>>> >>>>> >>>>> >>>> Actually some Smalltalk'ers consider the debugger a major facilitator >>>> of TDD by mostly coding from within the debugger. >>>> 1. Before writing any application code, write a test. >>>> 2. Execute that test straight away. Of course it fails because you >>>> haven't written any application code. >>>> 3. Up comes the debugger - now "from within the debugger" add the >>>> application code needed to satisfy the test. >>>> 4. Repeat. >>>> >>>> A good demonstration of this is Stephan Wessels' Laser Game tutorial >>>> [1] (but you'll temporarily need to revert to Squeak 3.9 to do it) >>>> cheers -ben >>>> >>>> >>>> >>> >> >

June 7, 2013

Re: [Pharo-dev] SmalltalkHub misleading stats?

by Esteban A. Maringolo

And, IMHO, I would report "projects" instead of "packages". Regards, Esteban A. Maringolo 2013/6/7 Damien Cassou <damien.cassou(a)gmail.com> > please report an issue > > On Fri, Jun 7, 2013 at 2:40 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > > > > On Jun 7, 2013, at 2:07 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > >> Hi guys. > >> In my own instance of shub that I am running, the number of "packages > uploaded" shown in the home of smalltalkhub looked like 10k, while I only > have around 10 packages. > >> In public smalltalkhub it says 60997. > >> So I wonder....what they actually are? can they actually be package > VERSIONS uploaded and not just packages? > >> > > They are *Versions*, it is very misleading. > > > > Marcus > > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

June 7, 2013