- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Necessity of TDD with Smalltalk
by Stephan Eggermont June 7, 2013

June 7, 2013

Paul 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? Test-driven development works well when you have some idea of where you want to go. If you don't know yet what your first test could look like, the powerful debugging environment of Smalltalk allows you to do some fast experiments. Then you might want to switch to TDD, as there are two ideas in TDD that are not covered by having a good debugging environment: - don't write more code than you have tests for, so the design is really driven by the tests - the tests provide insurance that you'll notice when something breaks. Writing and re-writing tests is what helps you get to a simple design. Tests need refactoring and DRY just as much as other code. Stephan

7 11

30181 Kernel package Dirty
by Sean P. DeNigris June 7, 2013

June 7, 2013

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 ----- Cheers, Sean -- View this message in context: http://forum.world.st/30181-Kernel-package-Dirty-tp4692004.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

3 3

[update 3.0] #30183
by Marcus Denker June 7, 2013

June 7, 2013

30183 ----- 10813 Update Opal to latest version in image https://pharo.fogbugz.com/f/cases/10813 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Tests-MarcusDenk… http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenke…

1 0

Class comments... we want them but, ... hard to convince the system at this point in time
by phil＠highoctane.be June 7, 2013

June 7, 2013

https://pharo.fogbugz.com/default.asp?10861 Still, this happens when doing a mcz load. Wondering... Phil

1 0

[update 3.0] #30182
by StÃ©phane Ducasse June 7, 2013

June 7, 2013

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

1 0

Problem with setting class comments
by Mariano Martinez Peck June 7, 2013

June 7, 2013

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? -- Mariano http://marianopeck.wordpress.com

3 3

Fwd: Release Artefact 1.0, the PDF framework
by Guillaume Larcheveque June 7, 2013

June 7, 2013

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*

1 0

June 7, 2013

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

1 0

Re: [Pharo-project] Adding a statement programmatically
by Marcus Denker June 7, 2013

June 7, 2013

On Mar 8, 2012, at 12:21 PM, Noury Bouraqadi wrote: > Hi Sean, > > Did you thought about: > -using method wrappers? > -object as methods. An object o put in a method dictionary instead of some method with selector #s. When #s is looked up, o receives the message > run: selector with: args in: originalReceiver > -proxies (look at Ghost) so you introduce an indirection to perform what ever action you want before performing the actual code > -> Compile the code to an RB AST, this then has all the interfaces needed to replace nodes or add nodes. You can then pretty print it back to source. Marcus -- Marcus Denker -- http://marcusdenker.de

3 6

Thanks
by Hilaire Fernandes June 7, 2013

June 7, 2013

Hi, I just want to say thanks you for the tips you gave me to migrate both DrGeo repo and its build scripts to SmalltalkHub. Smooth and clean. Hilaire -- Dr. Geo - http://www.drgeo.eu

1 0