- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] I cannot merge 10828 and 10830 because the system does not find

by Esteban Lorenzano

no idea :( you can try copying it into inbox, but this is weird. Esteban On Jun 7, 2013, at 11:51 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> Subject: I cannot merge 10828 and 10830 because the system does not find >> Date: June 7, 2013 11:49:47 AM GMT+02:00 >> To: Esteban Lorenzano <estebanlm(a)gmail.com> >> >> Morphic-Base-EstebanLorenzano.3 >> I do not understand why > > especially since the file is in main. > >> >> Stef >

June 7, 2013

I cannot merge 10828 and 10830 because the system does not find

by StÃ©phane Ducasse

> From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: I cannot merge 10828 and 10830 because the system does not find > Date: June 7, 2013 11:49:47 AM GMT+02:00 > To: Esteban Lorenzano <estebanlm(a)gmail.com> > > Morphic-Base-EstebanLorenzano.3 > I do not understand why especially since the file is in main. > > Stef

June 7, 2013

Re: [Pharo-dev] FogBugz (Case [Issue]10840) Collection - WeakSet>>#size utterly broken

by Camille Teruel

On 7 juin 2013, at 11:19, Pharo Issue Tracker wrote: > A FogBugz case was edited by Stephane Ducasse. > > Case ID: 10840 > Title: WeakSet>>#size utterly broken > Status: Resolved (Fix Review Needed) > Category: Bug > Project: Collection > Area: Misc > Priority: 3 - Must Fix > Milestone: Pharo3.0: 30/03/2014 > Assigned To: Camille Teruel > > URL: https://pharo.fogbugz.com/f/cases/10840 > > Last message: > Please can you send a mail to the mailing-list so that we all discuss this problems. Hello everyone, WeakSet>>#size is broken as demonstrated by the following snippet: set := WeakSet new. set add: Object new. Smalltalk garbageCollect. set size. "answers 1 instead of 0" That is because a WeakSet has no mean to know when its items get garbage collected, and thus the tally cannot be updated. So we need to override #size in Weak, I propose: size | counter | counter := 0. self do: [ :e | counter := counter + 1 ]. ^ counter But that it rather inefficient for such a simple query. Any proposition? The bug entry is: https://pharo.fogbugz.com/f/cases/10840 > > > If you do not want to receive automatic notifications anymore, change your preferences in the Options screen. (https://pharo.fogbugz.com/default.asp?pg=pgPrefs)

June 7, 2013

Re: [Pharo-dev] 30181 Kernel package Dirty

by Damien Cassou

On Thu, Jun 6, 2013 at 7:19 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > 1. Download a fresh 30181 > 2. In MC Browser, view "Changes" on Kernel > > The package will show a handful of changes and be marked dirty which repository are you comparing against? You must always compare against the Pharo30 repository (not Pharo30Inbox) -- 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

[update 3.0] #30182

by StÃ©phane Ducasse

30182 ----- 10115 MCClassTraitDefinition DNU printDefinitionOn: https://pharo.fogbugz.com/f/cases/10115 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-StephaneDucasse.80…

June 7, 2013

Re: [Pharo-dev] Problem with setting class comments

by Marcus Denker

On Jun 7, 2013, at 11:00 AM, phil(a)highoctane.be wrote: > Just got a bite from that bug. > > https://pharo.fogbugz.com/default.asp?10860 > > Now, how can get I my fileIns to work? > I do not think that these are related. The *only* thing the classComment: thing brings is that the meta-data for the class comment is not recorded. This has to be a completely unreleased error. > > On Fri, Jun 7, 2013 at 8:17 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jun 6, 2013, at 5:54 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > Hi guys. > > > > I think I found a problem with class comments. The default method #classComment: in TClassAndTraitDescription does the following: > > > > classComment: aString > > "Store the comment, aString or Text or RemoteString, associated with the class we are orgainzing. Empty string gets stored only if had a non-empty one before." > > ^ self classComment: aString stamp: '<historical>' > > > > Why it puts a '<historical>' stamp instead of say "Author changeStamp" ? > > > > Nautilus uses this message. So as a consequence, when you edit and save a class comment with Nautilus, to get a <historical> stamp.... > > > > I am using Pharo 2.0. > > > > Bug? > > > > Yes! > > Marcus > > >

June 7, 2013

Re: [Pharo-dev] Problem with setting class comments

by phil＠highoctane.be

Just got a bite from that bug. https://pharo.fogbugz.com/default.asp?10860 Now, how can get I my fileIns to work? On Fri, Jun 7, 2013 at 8:17 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Jun 6, 2013, at 5:54 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > Hi guys. > > > > I think I found a problem with class comments. The default method > #classComment: in TClassAndTraitDescription does the following: > > > > classComment: aString > > "Store the comment, aString or Text or RemoteString, associated > with the class we are orgainzing. Empty string gets stored only if had a > non-empty one before." > > ^ self classComment: aString stamp: '<historical>' > > > > Why it puts a '<historical>' stamp instead of say "Author changeStamp" ? > > > > Nautilus uses this message. So as a consequence, when you edit and save > a class comment with Nautilus, to get a <historical> stamp.... > > > > I am using Pharo 2.0. > > > > Bug? > > > > Yes! > > Marcus > > >

June 7, 2013

Fwd: Release Artefact 1.0, the PDF framework

by Guillaume Larcheveque

Thanks a lot about your return!!! About format, we will add your format but can you please inform us about all commons US formats (please fileOut what you have implemented). In a short future, we will split the project in many packages and grant to everybody the right to contribute for format, composite elements, fonts... 2013/6/6 Chris Cunningham <cunningham.cb(a)gmail.com> > Hi. > > I'm using your Artefact project, and really enjoying it. But, of, course, > there is a little problem. > > I'm in the US, so naturally, I want to use US size paper. Looking at you > formats, your PDFLetterFormat is actually sized for Legal - if you could > change the class to be PDSLegalFormat, and add a new PDFLetterFormat where > the #defaultSize is "^612 point @ 792 point", that would make me super > happy. > > Or, of course, you could grant me access,and I could make the change (user > id cbc). I've already done this locally to move ahead. > > Thanks, > Chris > > > On Fri, May 31, 2013 at 6:30 AM, Guillaume Larcheveque < > guillaume.larcheveque(a)gmail.com> wrote: > >> We are proud to announce that Artefact is available in 1.0 version. >> >> You can download it from: http://smalltalkhub.com/#!/~RMoD/Artefact >> >> Artefact is a framework to generate PDF documents. It is fully written in >> Smalltalk and doesn't require any native library. Artefact is light, >> platform independant and offer to users a high level of abstraction in >> order to easily creating PDF documents. >> >> * completely written in Smalltalk (and only Smalltalk), >> * complete freedom about the order of creation for pages, elements... >> (no need to follow the document order) >> * multi format and orientation for pages >> * page composition based on reusables PDF elements, >> * extensibility by offering a composition standard to create your own >> high level elements >> * styleSheet that can be reused in many documents and avoid wasting time >> and place with duplication >> * image support with the JPEG format >> * pre-defined high level elements like datagrid >> * support PDF compression to produce compact files >> >> A basic documentation is available in the help browser. Many examples are >> implemented in the PDFDemos class. >> >> -- >> *Olivier Auverlot and Guillaume Larcheveque* >> >> > -- *Guillaume Larcheveque* -- *Guillaume Larcheveque*

June 7, 2013

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

by Rafael Luque

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

Thanks for the participation to Pharo web days

by StÃ©phane Ducasse

Hi guys I wanted to thank you for the effort you did: coming to lille and presenting your great product. Thanks again. Stef

June 7, 2013