July 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] why "maximize" does not fills all the window in1.1?

by Geert Claes

Thanks Gary, that's great! -- View this message in context: http://forum.world.st/why-maximize-does-not-fills-all-the-window-in-1-1-tp2… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 27, 2010

Re: [Pharo-project] [ANN] Pharo 1.1 - Win32 Setup

by Adrian Lienhard

Thanks, Torsten! I updated the website. Adrian On Jul 26, 2010, at 22:48 , Torsten Bergmann wrote: > For those of you who want to use Pharo 1.1. on Win32 only > there is again an installer for the new release: > > https://gforge.inria.fr/frs/download.php/27305/setup_pharo1.1-11411-release… > > as an alternative to the one click download. > > Have fun > Torsten > -- > Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! > Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 27, 2010

Re: [Pharo-project] [ANN 1.1] One-Click 1.1 release

by Serge Stinckwich

I added the following methods: RBMacSpellChecker>>primitiveSetLanguage: data <primitive: 'primitiveSetLanguage' module: 'SpellingPlugin'> self primitiveFailed RBMacSpellChecker>>primitiveGetLanguage <primitive:'primitiveGetLanguage' module: 'SpellingPlugin'> self primitiveFailed I do not understand why : checker := RBMacSpellChecker new. checker primitiveSetLanguage: 'fr'. result := checker check: 'How are you ?'. checker primitiveSetLanguage: 'en'. result returns an OrderedCollection() and : checker := RBMacSpellChecker new. checker primitiveSetLanguage: 'fr'. checker primitiveGetLanguage. result := checker check: 'How are you ?'. checker primitiveSetLanguage: 'en'. result returns the correct answer: an OrderedCollection('How' 'you') Any ideas ? Something wrong with the SpellingPlugin ? On Mon, Jul 26, 2010 at 3:46 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > On Mon, Jul 26, 2010 at 2:05 PM, Serge Stinckwich > <serge.stinckwich(a)gmail.com> wrote: >> 2010/7/25 Mariano Martinez Peck <marianopeck(a)gmail.com>: >>> >>> >>> On Sun, Jul 25, 2010 at 4:02 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: >>>> >>>> Hm, the link doesn't work for me. I just get an empty response... >>>> >>> >>> https://gforge.inria.fr/frs/download.php/27303/Pharo-1.1-OneClick.zip >>> >>> works ok here >> >> Works ok for me also. >> >> 9764 tests, 9693 passes, 53 expected failures, 17 failures, 1 error >> on Mac OS X 10.6.4. Most of the failures reported are inside RBSpellingRuleTest. >> Tests like: >> >> testPerfectSentence >> Â Â Â Â | result | >> Â Â Â Â result := self checker >> Â Â Â Â Â Â Â Â check: 'This is an english sentence without problems.'. >> Â Â Â Â self assert: result isCollection. >> Â Â Â Â self assert: result isEmpty >> >> could not work on my machine, because by default i'm using the french >> speller ... >> I made some modifications to switch the speller to english and came >> back to the original language after the tests. I put my modifications >> here: http://code.google.com/p/pharo/issues/detail?id=2714 >> >> After that all RBSpellingRuleTest are green. > > Hum in fact no ... there is still some problems. > > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

July 27, 2010

Re: [Pharo-project] Bytecode reference ...

by James Ladd

Hi Javier, Thanks for the reference. I have the Blue Book but wanted to check if this reference was still valid. Glad it is. Rgs, James.

July 27, 2010

[Pharo-project] How to interactively add items to a tree widget?

by Rob Rothwell

This is probably a pretty newbie question, but can anyone point me towards creating some code to right click on a tree item and add a pop-up menu so I can prompt for some input and create a new child of that node? I figured out how to change the contents of the tree in UITheme exampleBasicControls by creating a Dictionary with some child Dictionaries containing some objects, but now I seem to have a few challenges: 1. The items are not being highlighted when I click on them (they aren't in the example either). 2. I need a nudge in the right direction to capture the right click. 3. If I do that and successfully add a new child to a node, I don't know how to tell the tree to refresh itself... Thank you, Rob

July 27, 2010

Re: [Pharo-project] Unwanted blank lines

by Schwab,Wilhelm K

I *think* the problem originated when I post-processed the .sif file to remove Dolphin conventions that confuse Monticello. Rather than set the encoding, I simply put the write stream in binary mode and all was (reasonably) well. I still had to eventually mess with the encoding because I needed to edit the file, but I did that with a save-as from gedit. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Henrik Johansen [henrik.s.johansen(a)veloxit.no] Sent: Monday, July 26, 2010 11:13 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Unwanted blank lines Figure out the line ending used by the file, then specify that AS the lineEndingConvention on the stream before you import. Cheers, Henry Den 26. juli 2010 kl. 16:58 skrev "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> > Hello all, > > In recent weeks, the code that I have exported from Dolphin and imported in Pharo (both via SIF) has ended up double spaced. In small amounts, it's not a big problem, but I just exported 980k of code and don't look forward to fixing that up after the fact. This could turn out to be due to cr/lf/lf sequences or something (looking at the .sif file using a hex editor comes to mind). > > Any suggestions for where you might look for the problem or a workaround? > > Bill > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 27, 2010

Re: [Pharo-project] Pool dictionaries

by Schwab,Wilhelm K

Gary, I found SharedPool, but it was not clear to me how it was supposed to work. By initializers, do you mean a class-side #initialize that sets the values of the class variables? How many class variables can a class have? There are quite a few constants in/for the offending gizmo =:0 I could create multiple pools, which might make things more readable, but the real goal is to just make it work. Thanks, Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Gary Chambers [gazzaguru2(a)btinternet.com] Sent: Monday, July 26, 2010 2:20 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Pool dictionaries See SharedPool and subclasses... No longer dictionaries as such, explained in the class comment. Subclass SharedPool with the name you want and add class vars and initialisers. Regards, Gary ----- Original Message ----- From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Monday, July 26, 2010 6:51 PM Subject: [Pharo-project] Pool dictionaries > What is the current status of pool dictionaries? I have some code that > uses one, and for pretty good reason. What do I need to do? > > Bill > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 27, 2010

Re: [Pharo-project] Bytecode reference ...

by Eliot Miranda

On Mon, Jul 26, 2010 at 5:00 PM, Martin McClure <martin(a)hand2mouse.com>wrote: > On 07/26/2010 04:52 PM, Eliot Miranda wrote: > > For a cogent but somewhat out-of-date account read the 4th part of >> Smalltalk-80: The Language and its Implementation on the wayback >> machine. Dwight Hughes digitised the last section of the blue book and >> put it up on his site, but its long gone and you'll have to find it on >> the wayback machine (if that still exists; I juts visited and got a 404). >> > > The entire (I believe) Blue Book is available in PDF form here: > > > http://stephane.ducasse.free.fr/FreeBooks/BlueBook/ > which has full text, so search for "Formal Specification of the Interpreter" on page 593 > > > Regards, > > -Martin >

July 27, 2010

Re: [Pharo-project] Bytecode reference ...

by Martin McClure

On 07/26/2010 04:52 PM, Eliot Miranda wrote: > For a cogent but somewhat out-of-date account read the 4th part of > Smalltalk-80: The Language and its Implementation on the wayback > machine. Dwight Hughes digitised the last section of the blue book and > put it up on his site, but its long gone and you'll have to find it on > the wayback machine (if that still exists; I juts visited and got a 404). The entire (I believe) Blue Book is available in PDF form here: http://stephane.ducasse.free.fr/FreeBooks/BlueBook/ Regards, -Martin

July 27, 2010

Re: [Pharo-project] Bytecode reference ...

by Eliot Miranda

2010/7/26 James Ladd <james_ladd(a)hotmail.com> > Hi All, > > I'm wondering if you can help me just a little with some information. > > With Pharo I can dump the human readable form of Smalltalk bytecodes, like > this: > > 21 <41> pushLit: ContextPart > 22 <D0> send: primitiveFailToken > 23 <7C> returnTop > > Can someone please point me to a document that outlines what each bytecode > means? > ie: <41> <D0> <7C> > For an up-to-date reference look at InstructionStream>>interpretNextInstructionFor: & InstructionStream>>interpretExtension:in:for: and the implementations of the selectors it sends in MethodContext and ContextPart. For a cogent but somewhat out-of-date account read the 4th part of Smalltalk-80: The Language and its Implementation on the wayback machine. Dwight Hughes digitised the last section of the blue book and put it up on his site, but its long gone and you'll have to find it on the wayback machine (if that still exists; I juts visited and got a 404). HTH Eliot > I can essentially see from the dump, but a proper reference would really > help. > > Rgs, James. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 26, 2010

Re: [Pharo-project] Bytecode reference ...

by Javier PimÃ¡s

Hi, I think you'll find ultimate guide for bytecodes in smalltalk's blue book at chapter 28, it gives you all the details: http://stephane.ducasse.free.fr/FreeBooks/BlueBook/Bluebook.pdf if you want just a quick reference, look at InstructionStream>>#interpretNextInstructionFor: and Interpreter class>>#initializeBytecodeTable (Interpreter class is downloaded when installing VMMaker). Regards, Javier. 2010/7/26 James Ladd <james_ladd(a)hotmail.com> > Hi All, > > I'm wondering if you can help me just a little with some information. > > With Pharo I can dump the human readable form of Smalltalk bytecodes, like > this: > > 21 <41> pushLit: ContextPart > 22 <D0> send: primitiveFailToken > 23 <7C> returnTop > > Can someone please point me to a document that outlines what each bytecode > means? > ie: <41> <D0> <7C> > > I can essentially see from the dump, but a proper reference would really > help. > > Rgs, James. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Javier PimÃ¡s Ciudad de Buenos Aires

July 26, 2010

[Pharo-project] [Pharo 1.1 OneClick] Errors launching the one click distrib on Linux

by Nicolas Petton

Hi guys, I just tried the one click distribution on Linux. Some files seem to miss execution rights: pharo.sh cannot be executed $ chmod +x ./pharo.sh $ ./pharo.sh exec: 12: ./Contents/Linux/squeakvm: Permission denied easily fixed too: $ chmod +x ./Contents/Linux/squeakvm I don't know if this problem only happens on my system though. Cheers, Nico

July 26, 2010

[Pharo-project] Bytecode reference ...

by James Ladd

Hi All, I'm wondering if you can help me just a little with some information. With Pharo I can dump the human readable form of Smalltalk bytecodes, like this: 21 <41> pushLit: ContextPart 22 <D0> send: primitiveFailToken 23 <7C> returnTop Can someone please point me to a document that outlines what each bytecode means? ie: <41> <D0> <7C> I can essentially see from the dump, but a proper reference would really help. Rgs, James.

July 26, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.1 released

by GermÃ¡n Arduino

Excellent news! Thanks by the effort to all the people involved. GermÃ¡n. 2010/7/26 Adrian Lienhard <adi(a)netstyle.ch>: > Hi all, > > I'm excited to announce our second release of Pharo! > > Please check out the updated website at www.pharo-project.org. > > This release contains many bug fixes, improvements, performance optimizations, and new features that didn't get into version 1.0. Specific information about what is new in this release can be found on > www.pharo-project.org/pharo-download/release-1-1. > > Thanks everyone who has contributed and helped to bring Pharo one step further! > > Please help to spread the word... > > Cheers, > Adrian > > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > -- ================================================= GermÃ¡n S. ArduinoÂ <gsa @ arsol.net>Â Â Twitter: garduino Arduino Software & Web HostingÂ Â http://www.arduinosoftware.com PasswordsProÂ http://www.passwordspro.com =================================================

July 26, 2010

Re: [Pharo-project] Primitives ? (Michael Haupt)

by James Ladd

Yes Michael, there will be content on http://redline.st as soon as I can possibly manage it.

July 26, 2010

Re: [Pharo-project] Primitives ?

by Mariano Martinez Peck

2010/7/26 James Ladd <james_ladd(a)hotmail.com> > Hi All, > > I'm looking at some low level details of Pharo Smalltalk and I am > wondering, > when I see a primitive in the bytecode, is it safe to assume that before > the primitive is executed, the receiver and any args to the method are > pushed > onto the stack? > As far as I understand, yes. Check in VMMaker package, look in Interpreter class and check some primitives. But I am not a VMMaker expert.... cheers mariano > > > Rgs, James. > > ------------------------------ > Australia's #1 job site If It Exists, You'll Find it on SEEK<http://clk.atdmt.com/NMN/go/157639755/direct/01/> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 26, 2010

Re: [Pharo-project] how do I turn off "smart" quotes in Pharo Seaside one-click image

by Martin McClure

On 07/19/2010 07:44 AM, Schwab,Wilhelm K wrote: > Stef, > > I will admit that eCompletion is the first thing I disable in any new image, Me too (well, the smartCharacters anyway). > but if the point is that it is useful if one selects and then types, could it simply apply the smart characters only when there is a slection as the character is typed? In that case, typing [ would do just that, typing [ when there is a selection would wrap the selection in []. Just a thought. I like this idea -- smartCharacters might be useful if it only took effect with a non-null selection. As it is, trying to type 'foo' is just too annoying to leave it on. Regards, -Martin

July 26, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.1 released

by Miguel Enrique CobÃ¡ MartÃnez

El lun, 26-07-2010 a las 22:22 +0200, Adrian Lienhard escribiÃ³: > Hi all, > > I'm excited to announce our second release of Pharo! > > Please check out the updated website at www.pharo-project.org. > > This release contains many bug fixes, improvements, performance optimizations, and new features that didn't get into version 1.0. Specific information about what is new in this release can be found on > www.pharo-project.org/pharo-download/release-1-1. > > Thanks everyone who has contributed and helped to bring Pharo one step further! > > Please help to spread the word... > > Cheers, > Adrian Very good news! Good job! Cheers > > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users -- Miguel CobÃ¡ http://miguel.leugim.com.mx

July 26, 2010

[Pharo-project] PluggableThemedOverflowPanelMorph(Object)>>doesNotUnderstand: #statusColor

by Mariano Martinez Peck

Just try open a TestRunner. You will get a DNU and that won't let you even debug the error. Pharo core version: PharoCore-1.2-12061 I attach PharoDebug.log PluggableThemedOverflowPanelMorph(Object)>>doesNotUnderstand: #statusColor Issue: http://code.google.com/p/pharo/issues/detail?id=2717 Cheers Mariano

July 26, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.1 released

by laurent laffont

On Mon, Jul 26, 2010 at 10:22 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Hi all, > > I'm excited to announce our second release of Pharo! > > Please check out the updated website at www.pharo-project.org. > > This release contains many bug fixes, improvements, performance > optimizations, and new features that didn't get into version 1.0. Specific > information about what is new in this release can be found on > www.pharo-project.org/pharo-download/release-1-1. > > Thanks everyone who has contributed and helped to bring Pharo one step > further! > > Please help to spread the word... > > Cheers, > Adrian > What a good day ! Thank you all ! Laurent > > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >

July 26, 2010

[Pharo-project] [ANN] Pharo 1.1 - Win32 Setup

by Torsten Bergmann

For those of you who want to use Pharo 1.1. on Win32 only there is again an installer for the new release: https://gforge.inria.fr/frs/download.php/27305/setup_pharo1.1-11411-release… as an alternative to the one click download. Have fun Torsten -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail

July 26, 2010

Re: [Pharo-project] [ANN] Pharo 1.1 released

by Alexandre Bergel

This is really cool! Congrat to all of you! Alexandre On 26 Jul 2010, at 22:22, Adrian Lienhard wrote: > Hi all, > > I'm excited to announce our second release of Pharo! > > Please check out the updated website at www.pharo-project.org. > > This release contains many bug fixes, improvements, performance optimizations, and new features that didn't get into version 1.0. Specific information about what is new in this release can be found on > www.pharo-project.org/pharo-download/release-1-1. > > Thanks everyone who has contributed and helped to bring Pharo one step further! > > Please help to spread the word... > > Cheers, > Adrian > > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 26, 2010

[Pharo-project] [ANN] Pharo 1.1 released

by Adrian Lienhard

Hi all, I'm excited to announce our second release of Pharo! Please check out the updated website at www.pharo-project.org. This release contains many bug fixes, improvements, performance optimizations, and new features that didn't get into version 1.0. Specific information about what is new in this release can be found on www.pharo-project.org/pharo-download/release-1-1. Thanks everyone who has contributed and helped to bring Pharo one step further! Please help to spread the word... Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/

July 26, 2010

Re: [Pharo-project] cog-based image crashes on mac

by Lukas Renggli

2010/7/26 Eliot Miranda <eliot.miranda(a)gmail.com>: > There's an update in svn that could fix crashes. No sorry, still the same (if I remember correctly I've never seen the bunch of error messages before the last two though) with the latest svn code: 26.07.10 20:39:33 [0x0-0x1d3dd3c].com.teleplace.Teleplace[4514] mprotect(x,y,PROT_READ | PROT_WRITE): Cannot allocate memory 26.07.10 20:39:33 [0x0-0x1d3dd3c].com.teleplace.Teleplace[4514] mprotect(x,y,PROT_READ | PROT_WRITE): Invalid argument 26.07.10 20:39:33 [0x0-0x1d3dd3c].com.teleplace.Teleplace[4514] squeak: could not load plugin `MiscPrimitivePlugin' 26.07.10 20:39:33 [0x0-0x1d3dd3c].com.teleplace.Teleplace[4514] squeak: could not load plugin `DropPlugin' 26.07.10 20:39:33 [0x0-0x1d3dd3c].com.teleplace.Teleplace[4514] squeak: could not load plugin `FilePlugin' 26.07.10 20:39:33 [0x0-0x1d3dd3c].com.teleplace.Teleplace[4514] squeak: could not load plugin `SecurityPlugin' 26.07.10 20:39:33 [0x0-0x1d3dd3c].com.teleplace.Teleplace[4514] squeak: could not load plugin `BitBltPlugin' 26.07.10 20:39:33 [0x0-0x1d3dd3c].com.teleplace.Teleplace[4514] squeak: could not load plugin `LargeIntegers' 26.07.10 20:39:33 [0x0-0x1d3dd3c].com.teleplace.Teleplace[4514] squeak: could not load plugin `B2DPlugin' 26.07.10 20:39:33 [0x0-0x1d3dd3c].com.teleplace.Teleplace[4514] squeak: could not load plugin `InternetConfigPlugin' 26.07.10 20:39:33 [0x0-0x1d3dd3c].com.teleplace.Teleplace[4514] squeak: could not load plugin `SocketPlugin' 26.07.10 20:40:03 [0x0-0x1d3dd3c].com.teleplace.Teleplace[4514] squeak: could not load plugin `DSAPrims' 26.07.10 20:40:06 [0x0-0x1d3dd3c].com.teleplace.Teleplace[4514] squeak: could not load plugin `JPEGReadWriter2Plugin' 26.07.10 20:41:33 [0x0-0x1d3dd3c].com.teleplace.Teleplace[4514] nanosleep: Invalid argument 26.07.10 20:41:33 com.apple.launchd.peruser.501[200] ([0x0-0x1d3dd3c].com.teleplace.Teleplace[4514]) Exited with exit code: 1 Lukas -- Lukas Renggli www.lukas-renggli.ch

July 26, 2010

Re: [Pharo-project] Pool dictionaries

by Gary Chambers

See SharedPool and subclasses... No longer dictionaries as such, explained in the class comment. Subclass SharedPool with the name you want and add class vars and initialisers. Regards, Gary ----- Original Message ----- From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Monday, July 26, 2010 6:51 PM Subject: [Pharo-project] Pool dictionaries > What is the current status of pool dictionaries? I have some code that > uses one, and for pretty good reason. What do I need to do? > > Bill > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 26, 2010

Re: [Pharo-project] cog-based image crashes on mac

by Eliot Miranda

There's an update in svn that could fix crashes. I had some logging code that looks like static unsigned long long useclog[LOGSIZE]; static int ulogidx = (unsigned int)-1; # define logusecs(usecs) do { sqLowLevelMFence(); \ if (logClock) useclog[++ulogidx % LOGSIZE] = (usecs); \ } while (0) which blows up when ulogidx wraps around. It the sign of -ve % +ve is undefined in C. The fix is simple; make the index unsigned: static unsigned long long useclog[LOGSIZE]; static unsigned int ulogidx = (unsigned int)-1; # define logusecs(usecs) do { sqLowLevelMFence(); \ if (logClock) useclog[++ulogidx % LOGSIZE] = (usecs); \ } while (0) I doubt this is your problem since it should take many hours for the clock log to wrap. But updating and rebuilding is still probably worthwhile. HTH Eliot On Mon, Jul 26, 2010 at 4:32 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > >>> The image I got is based on the sources from 27.06.2010. > >> > >> You may be missing some image-side changes. The CogVM was open sourced > on > >> 20.06.2010. > > > > Actually, where should I get the complete image-side changes from? I have > > those prepared by Lukas a while ago. > > Yeah, these are the complete ones from the repository adapted to Pharo. > > Maybe these same socket related crashes that randomly appear with > Seaside images? > > nanosleep: Invalid argument > Exited with exit code: 1 > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 26, 2010

[Pharo-project] Pool dictionaries

by Schwab,Wilhelm K

What is the current status of pool dictionaries? I have some code that uses one, and for pretty good reason. What do I need to do? Bill

July 26, 2010

Re: [Pharo-project] What is correct way to save image automatically in background?

by Norbert Hartl

On 23.07.2010, at 17:11, David T. Lewis wrote: > Yes, it really is true. That said, I would expect the practical impact > to vary depending on how busy the main image is. > > If you are running a Squeak/Pharo image that is not busy, such as your > own personal desktop image or a Seaside image that is not currently > receiving requests, then the additional system memory used by the > forked background image is extremely small (it's pretty amazing > actually, try watching it on a system monitor such as xosview). > However, I would expect that if you were to do this with a busy > Seaside image, then that image would be doing a lot of updates to > memory and possibly garbage collection, so that will force the OS > to use more memory. > What you are saying depends on the environment underneath. In theory it is pretty easy. The fork doubles the process memory when forking. Systems like linux have something called "memory overcommit". They don't allocate the reserved memory unless something is written. I think that is what you meant by saying "... is extremely small...". Why I am saying this? Because especially for seaside images the situation could be different. It is very common nowadays to use OS virtualization to install things like seaside images. Virtualizers disable "memory overcommitment" because otherwise one virtual instance could have side effects on other instances. So you are back with doubling process memory. You need to be careful if you have a small virtual machine or if you try to fork from several images at the same time. hope this adds anything, Norbert > Unfortunately this means that the busier your image is, the less > benefit you get from a memory usage point of view. But even at that, > you still get the advantage of doing the image save in a background > OS process running at lower OS scheduling priority. > > I do not actually run any Seaside server images, so someone would > need to try this on a real system to find out how much benefit it > delivers in practice. I would be interested to know the results. > > Dave > > > On Fri, Jul 23, 2010 at 02:12:14PM +0200, Lukas Renggli wrote: >> David, is what is said about memory management really true? I thought >> that saving the image triggered a garbage collect what forces to copy >> the whole memory anyway. >> >> Lukas >> >> On 23 July 2010 14:00, David T. Lewis <lewis(a)mail.msen.com> wrote: >>> On Fri, Jul 23, 2010 at 09:49:46AM +0200, Lukas Renggli wrote: >>>>> But How I can do that without fork? I track changes in another process and >>>>> when I do update I save image in this process. >>>>> How I can initiate image saving from ui process? >>>> >>>> I don't understand what you are saying. >>>> >>>> The thing is that using #fork to save the image has no effect (other >>>> than wrecking the image), because #snapshot:andQuit: is eventually >>>> calling a primitive that locks the complete VM anyway. >>>> >>>> If you want to fork while saving the image you need to use an OS-level >>>> fork, not a Smalltalk-level fork. You can do this with OSProcess for >>>> example (check the Seaside mailing-list archive). >>> >>> "UnixProcess saveImageInBackgroundNicely" >>> >>> Explained in the method comment: >>> >>> UnixProcess class>>saveImageInBackground: savedImageName nice: niceFlag >>> ? ? ? ?"When Squeak is used as a server it is sometimes desirable to periodically >>> ? ? ? ?save image snapshots. This method forks a headless Squeak to perform a >>> ? ? ? ?snapshot without impacting the server Squeak. Very little additional memory >>> ? ? ? ?is required to do this because Unix copy-on-write memory management allows >>> ? ? ? ?the two Squeak images to share object memory while the save is performed. >>> ? ? ? ?The saved image is given a time stamped name, and the image name of >>> ? ? ? ?the main server Squeak remains unchanged. If niceFlag is true, the >>> ? ? ? ?background OS process runs at lowered scheduling priority." >>> >>> Dave >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 26, 2010

Re: [Pharo-project] [SPAM] New Features for Hudson Build Tools

by Lukas Renggli

Thanks for the feedback, I pushed out a new version that produces a slightly cleaner and smaller build. The root directory now only contains 3 files: - for Windows a .lnk file with the correct icon - for Linux a .sh file with the correct icon after the first start (probably works on Gnome only) - readme.txt I tested it on OS X 10.6, Ubuntu 10, and Windows XP. Lukas -- Lukas Renggli www.lukas-renggli.ch On 20 July 2010 20:42, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi Lukas, > > This is really great. > > Cheers, > Doru > > > On 20 Jul 2010, at 13:07, Sven Van Caekenberghe wrote: > >> Lukas, >> >> This is really very impressive stuff. >> Thanks for setting all this up and sharing it with us. >> I am learning a lot from it. >> >> Sven >> >> On 20 Jul 2010, at 10:26, Lukas Renggli wrote: >> >>> I've added some new functionality to the Hudson Build Toos for Pharo: >>> >>> 1. I've added a script build-oneclick.sh that builds OneClick >>> distributions. This means that with every successful build there will >>> be a new OneClick distribution. >>> >>> For example, the latest PetitParser OneClick distribution is available >>> from: >>> http://hudson.lukas-renggli.ch/job/PetitParser/lastSuccessfulBuild/artifact…. >>> >>> 2. I've changes build.sh to automatically find and fetch dependent >>> images. This makes the configuration in Hudson much simpler, as no >>> images need to be copied around. >>> >>> For example, the Hudson configuration of PetitParser looks as follows: >>> >>> build.sh -i omnibrowser -s petitparser -o petitparser >>> build.sh -i petitparser -s testrunner -s petitparser-tests -o >>> petitparser-tests >>> build-oneclick.sh -i petitparser -o PetitParser-OneClick -t >>> PetitParser -c PetitParser -n petitparser >>> >>> As usual all the code is available from: >>> >>> http://github.com/renggli/builder >>> >>> Lukas >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

July 26, 2010

Re: [Pharo-project] [ANN 1.1] One-Click 1.1 release

by Lukas Renggli

On 26 July 2010 09:06, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > Why Pier.icns, PetitParser.icns and Seaside.icns files are included in > the Contents/Resources directory ? Wow, if this is the biggest concern :-) Anyway, I pushed out a new version that does not include these generic build-artifacts. Also it cleans up the root directory, it only contains three files now: - for Windows a .lnk file with the correct icon - for Linux a .sh file with the correct icon (probably works for Gnome only, and only appears after the first start) - readme.txt Lukas -- Lukas Renggli www.lukas-renggli.ch

July 26, 2010

Re: [Pharo-project] Unwanted blank lines

by Henrik Johansen

Figure out the line ending used by the file, then specify that AS the lineEndingConvention on the stream before you import. Cheers, Henry Den 26. juli 2010 kl. 16:58 skrev "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> > Hello all, > > In recent weeks, the code that I have exported from Dolphin and imported in Pharo (both via SIF) has ended up double spaced. In small amounts, it's not a big problem, but I just exported 980k of code and don't look forward to fixing that up after the fact. This could turn out to be due to cr/lf/lf sequences or something (looking at the .sif file using a hex editor comes to mind). > > Any suggestions for where you might look for the problem or a workaround? > > Bill > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 26, 2010

[Pharo-project] Unwanted blank lines

by Schwab,Wilhelm K

Hello all, In recent weeks, the code that I have exported from Dolphin and imported in Pharo (both via SIF) has ended up double spaced. In small amounts, it's not a big problem, but I just exported 980k of code and don't look forward to fixing that up after the fact. This could turn out to be due to cr/lf/lf sequences or something (looking at the .sif file using a hex editor comes to mind). Any suggestions for where you might look for the problem or a workaround? Bill

July 26, 2010

Re: [Pharo-project] why "maximize" does not fills all the window in1.1?

by Gary Chambers

For Mariano's side note... http://code.google.com/p/pharo/issues/detail?id=2716 Regards, Gary ----- Original Message ----- From: Mariano Abel Coca To: Pharo-project(a)lists.gforge.inria.fr Sent: Thursday, July 08, 2010 9:01 PM Subject: Re: [Pharo-project] why "maximize" does not fills all the window in1.1? What would be great is not using the squeak menu inside the world, but drawing it on the system window. More like mac's, that is integrated in the global menu. In Linux there is a GlobalMenuApplet for Gnome Panels that works like mac's Global Menu, and removes the menu from the windows and merges on the pannel. It's a nice advance to a mac interface. (That and CairoDock, of course) I don't have a clue about how to do it, but dreaming is free. :) Cheers, Mariano. 2010/7/8 Mariano Martinez Peck <marianopeck(a)gmail.com> On Thu, Jul 8, 2010 at 10:30 AM, Geert Claes <geert.wl.claes(a)gmail.com> wrote: Carla F. Griggio wrote: > > Hahaha, good point, Wilhelm :P > > It kind of bothered me at first, but then I noticed it was more > confortable to open the World Menu, although I thought "maybe there's > another way to open the World menu where I don't need the background to be > visible". Is there? > > If not, I agree that there should be a way to do it without depending on > the background. But in the meantime, not maximizing the windows to full > screen helps. > I was thinking that a while ago as well. How about a top menu-bar like the Apple Menu like this (see screen mockup)? http://forum.world.st/file/n2281990/World_Menu.png This is cool. You did it? is it working ? because we have HostMenus-Mac, but it is only MacOS. Cheers Mariano On a side note, there's another small thing which has been bothering me is that even though I really like the Mac theme and look and feel the Red/Yellow/Green Close/Min/Max buttons don't indicate which one is which on a mouse-over so you need to know which color does what. I liked the windows button I saw in one of the Smalltalk Medicine Show video's. It still had a nice look-n-feel but the icons actually had more meaning. http://forum.world.st/file/n2281990/Better_Window_Icons.png -- View this message in context: http://forum.world.st/why-maximize-does-not-fills-all-the-window-in-1-1-tp2… Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ------------------------------------------------------------------------------ _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 26, 2010

Re: [Pharo-project] Autotest, proof-of-concept [was: About TDD and Pharo]

by laurent laffont

On Mon, Jul 26, 2010 at 8:01 AM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Ideally, we should not tag long tests. The system should be smart enough to > characterize a test as long. If it takes more than 200ms, then it is long. > Autotest should then offer me to include long test or not in the automatic > test execution. > > Using tags means that I have to go over each method test and tag them. This > is a costly effort that is likely to not work in practice. > > We have > -=-=-=-=-=-=-=-=-=-=-=-= > TestCase class>>newTestDictionary > ^ Dictionary new at: #timeStamp put: TimeStamp now; > at: #passed put: Set new; > at: #failures put: Set new; > at: #errors put: Set new; > yourself > -=-=-=-=-=-=-=-=-=-=-=-= > > Maybe it should be extended with > -=-=-=-=-=-=-=-=-=-=-=-= > at: #long put: Set new > -=-=-=-=-=-=-=-=-=-=-=-= > > I guess the tweak in SUnit to identify long tests should not be that hard > to implement. > Indeed I also want to log for each test: - min / max / mean execution time - time to first failure - % of errors/failures/success - run count so with these datas we know long tests. I think about wrapping run test methods with an object which then can collect these datas. Would you go this way ? (Another way is to modify TestResult / TestCase, but it's more intrusive). I also think that execution time is not the only criteria. For example, Autotest can have a "feedback deadline" of 2 seconds. That means it can run: - 2 tests of 1 second - 20 tests of 100 ms So knowing execution times, Autotest can run as many tests as it can, starting from fastest to lowest. It seems that JUnitMax do this way. Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ > > Cheers, > Alexandre > > > On 26 Jul 2010, at 07:44, laurent laffont wrote: > > > > > On Sat, Jul 24, 2010 at 10:16 AM, Alexandre Bergel <alexandre(a)bergel.eu> > wrote: > > I have been using Autotest for a while already. I greatly reduce the > window switching. This is cool. > > However, I have to disable Autotest when the tests take time to execute. > > > > > > An idea is to be able to tag tests with pragmas to put them in > categories. So we can have a LongRunning category which is not run by > default. Like NUnit (http://www.nunit.org/index.php?p=category&r=2.2) > > > > Then SUnit could be enhanced to show these categories. Useful to quickly > select all tests related to a project for example; or run only performance > tests. > > > > > > How would you name the tag ? Where the implementation should go ? > (TestCase ?) > > > > > > Laurent. > > > > > > Alexandre > > > > > > On 15 Jun 2010, at 21:41, laurent laffont wrote: > > > > > Hi Alexandre, > > > > > > I've reorganized Autotest to write tests. The tests now run in a thread > with lower priority. Thanks for feedback. > > > > > > Cheers, > > > > > > Laurent Laffont > > > > > > http://pharocasts.blogspot.com/ > > > http://magaloma.blogspot.com/ > > > > > > > > > On Mon, Jun 14, 2010 at 4:52 PM, Alexandre Bergel <alexandre(a)bergel.eu> > wrote: > > > Hi Laurent, > > > > > > I tried to program while having AutoTest running. > > > More importantly than the interface, I experienced some problem with > long executing tests. Basically, these tests should not be executed while I > am programming. Or at least in a thread of a lesser priority. Am I the only > one to experience this? > > > > > > Cheers, > > > Alexandre > > > > > > > > > On 11 Jun 2010, at 09:02, laurent laffont wrote: > > > > > > > On Fri, Jun 11, 2010 at 2:29 PM, Alexandre Bergel < > alexandre(a)bergel.eu> wrote: > > > > Hi Laurent, > > > > > > > > I like Autotest. It is true that I always execute the test after > modifying it. > > > > There are three horizontal panes. Why so? Is it just to open a > debugger when necessary? > > > > > > > > I want to be able to open a debugger from autotest. I agree the GUI > is crap now. > > > > > > > > > > > > We could imagine one standalone button instead with a green color to > say the test I just edited is green, and yellow or red when it fails. In > that case, clicking on the button open a debugger. > > > > > > > > I just feel the window of autotest takes a lot of space in the > screen, without having a real benefit. > > > > > > > > Yes it's true. I'm still thinking on a good GUI. But I'm learning how > to make GUI now :) > > > > > > > > If you look at Autotest package, AutotestView is just the GUI, so we > can implement several GUI and see the best solution. I need to take the time > to do it, repository is read / write so feel free to commit :) > > > > > > > > What I want to have is a dashboard docked on one side of the screen > which acts like you're driving a car. It's always visible, you have to be > able to look quickly at it as when you check the speed of your car, adjust > your drive, .... > > > > > > > > Also another problem with the current version if that if a test > fails, change it and fails again, you don't see it has run (nothing moves in > the GUI). > > > > > > > > Finally, another problem is that you see that a test has failed, but > you don't know why (SUnit TestRunner has the same problem). I want to > display the exception message too. > > > > > > > > Thanks a lot for feedback. > > > > > > > > Laurent Laffont > > > > > > > > http://pharocasts.blogspot.com/ > > > > http://magaloma.blogspot.com/ > > > > > > > > > > > > > > > > Cheers, > > > > Alexandre > > > > > > > > > > > > On 3 Jun 2010, at 17:11, laurent laffont wrote: > > > > > > > > > Hi, > > > > > > > > > > I've written a proof-of-concept for Autotest. Draft/crappy code and > no tests (exploration mode :) but it loads on PharoCore-1.1-11383-beta > image. > > > > > > > > > > Load it: > > > > > Gofer new > > > > > squeaksource: 'Autotest'; > > > > > package: 'Autotest'; > > > > > load > > > > > > > > > > Open it: > > > > > AutotestView open > > > > > (there's en entry in WorldMenu > Tools) > > > > > > > > > > And change a tested method to see the results. > > > > > > > > > > There's a bug I need to find, maybe someone knows: > > > > > - Change Bag>>occurrencesOf: > > > > > - Autotest gives: > > > > > > > > > > 284 run, 281 passes, 0 expected failures, 1 failures, 2 errors, 0 > unexpected passes > > > > > Failures: > > > > > CollectionRootTest>>#test0FixtureIterateTest > > > > > > > > > > Errors: > > > > > CollectionRootTest>>#testBasicCollect > > > > > CollectionRootTest>>#testDoWithout > > > > > > > > > > but in SUnit CollectionRootTest gives > > > > > 0 run, 0 passes, 0 expected failures, 0 failures, 0 errors, 0 > unexpected passes ?? > > > > > > > > > > > > > > > Cheers, > > > > > > > > > > Laurent Laffont > > > > > > > > > > http://pharocasts.blogspot.com/ > > > > > http://magaloma.blogspot.com/ > > > > > > > > > > > > > > > On Thu, Jun 3, 2010 at 6:09 PM, Alexandre Bergel < > alexandre(a)bergel.eu> wrote: > > > > > The idea is excellent. > > > > > > > > > > Cheers, > > > > > Alexandre > > > > > > > > > > > > > > > On 3 Jun 2010, at 10:22, laurent laffont wrote: > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jun 3, 2010 at 3:42 PM, Alexandre Bergel < > alexandre(a)bergel.eu> wrote: > > > > > > > You may have a lot of noise. > > > > > > > > > > > > > > I guess that Ruby uses files as a unit of > development/deployment. The closest Smalltalk/Pharo has is the class and the > package. > > > > > > > > > > > > > > I would suggest that TestCase which would use this feature use > some pragma/method to identify/declare which classes/packages this test > depends upon. Then the "autotest" framework would register such tests and > listen for changes in the given classes/packages, launching required tests > whenever a change happen. > > > > > > > > > > > > > > Additionally, one could declare such a pragma on a single test > method, when this test should be run for a specific class. > > > > > > > > > > > > > > Of course, you also to take care of long running tests, which > you probably want to exclude from auto-testing. > > > > > > > > > > > > I see autotest in Pharo in a slighly different way: When I press > save in the Monticello browser, I have a popup menu which asks me whether > (i) I want to run all the tests or (ii) only the tests that cover that I > changed from the last version. > > > > > > > > > > > > Does this make sense? > > > > > > > > > > > > Please no popup :) What I like in ruby autotest is that I can > quickly look at test results if I want (or not) without stop writing. Often > you want to see your tests failing, as you type / save code. I don't have to > stop writing, click a button, wait test results, go again.... testing is > done in background and I just see notifications whether it's OK or not. > > > > > > > > > > > > So test log in a Transcript is OK for me. > > > > > > > > > > > > > > > > > > For autotest unit of work is file: it runs the test file which > has the same name as the code file, but you can customize this behavior. For > autotest-rails: > > > > > > "A simplified version of Autotest heuristics in this mode would > be: > > > > > > When changing a test file, only this file is run (e.g. > test/unit/foo_test.rb âtest/unit/foo_test.rb). > > > > > > When changing a model file, only associated unit test file is run > (e.g.app/models/foo.rb â test/unit/foo_test.rb). > > > > > > When changing a controller file, associated functional test file > is run (e.g.app/controllers/foo_controller.rb > âtest/functional/foo_controller_test.rb). > > > > > > When changing a fixture file, associated unit test and functional > test are run (e.g.app/fixtures/foos.yml â test/unit/foo_test.rb > +test/functional/foo_controller_test.rb). > > > > > > When changing a helper file, associated functional test file is > run (e.g.app/helpers/foo_helper.rb âtest/functional/foo_controller_test.rb). > > > > > > When changing application_helper.rb file all functional test > files are run (e.g.application_helper.rb â test/functional/*_test.rb). > > > > > > When changing a file under the config directory, all tests are > run." > > > > > > > > > > > > Laurent > > > > > > > > > > > > > > > > > > > > > > > > Cheers, > > > > > > Alexandre > > > > > > -- > > > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > > > Alexandre Bergel http://www.bergel.eu > > > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Pharo-project mailing list > > > > > > Pharo-project(a)lists.gforge.inria.fr > > > > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > > > > > _______________________________________________ > > > > > > Pharo-project mailing list > > > > > > Pharo-project(a)lists.gforge.inria.fr > > > > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > > > -- > > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > > Alexandre Bergel http://www.bergel.eu > > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Pharo-project mailing list > > > > > Pharo-project(a)lists.gforge.inria.fr > > > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > > > _______________________________________________ > > > > > Pharo-project mailing list > > > > > Pharo-project(a)lists.gforge.inria.fr > > > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > -- > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > Alexandre Bergel http://www.bergel.eu > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Pharo-project mailing list > > > > Pharo-project(a)lists.gforge.inria.fr > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > _______________________________________________ > > > > Pharo-project mailing list > > > > Pharo-project(a)lists.gforge.inria.fr > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > Alexandre Bergel http://www.bergel.eu > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 26, 2010

Re: [Pharo-project] cog-based image crashes on mac

by Lukas Renggli

>>> The image I got is based on the sources from 27.06.2010. >> >> You may be missing some image-side changes. The CogVM was open sourced on >> 20.06.2010. > > Actually, where should I get the complete image-side changes from? I have > those prepared by Lukas a while ago. Yeah, these are the complete ones from the repository adapted to Pharo. Maybe these same socket related crashes that randomly appear with Seaside images? nanosleep: Invalid argument Exited with exit code: 1 Lukas -- Lukas Renggli www.lukas-renggli.ch

July 26, 2010

Re: [Pharo-project] cog-based image crashes on mac

by Tudor Girba

Hi, On 25 Jul 2010, at 17:32, Levente Uzonyi wrote: > On Sun, 25 Jul 2010, Tudor Girba wrote: > >> Hi, >> >> I have been using the Cog VM exclusively for several months now, >> and from > > Did you get a VM from Teleplace before it was open sourced? No. I directly got the sources from SVN and compile them for Mac. Is there an official Cog VM compiled for Mac? >> time to time it crashes on me without leaving any trace in debug log. >> >> One frequent cause for the crash that I noticed is dealing with >> Monticello (both reading and writing). Does anyone experience >> similar things? Am I doing something wrong? > > IIRC this issue was fixed in VMMaker-oscog.17. I am not sure what this means :). >> The image I got is based on the sources from 27.06.2010. > > You may be missing some image-side changes. The CogVM was open > sourced on 20.06.2010. Actually, where should I get the complete image-side changes from? I have those prepared by Lukas a while ago. Cheers, Doru > Levente > >> >> Perhaps a more general idea: given that this VM brings an important >> improvement, do we want to have a more concerted effort to beta- >> test it? >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "It's not how it is, it is how we see it." >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done."

July 26, 2010

[Pharo-project] [update 1.2] #12066

by Marcus Denker

12066 ----- Issue 2712: Once Issue 2715: remove three methods from Object: evaluateUnloggedForSelf, stringRepresentation, stringForReadout Issue 2529: FreeTypeFont>>veryDeepCopyWith: -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 26, 2010

[Pharo-project] Reporting error to end users

by Alexandre Bergel

Hi! I feel that Object>>error: is a bit too low level. I tried to write a method errorEndUser: -=-=-=-=-=-=-=-=-=-=-=-= Object>>errorEndUser: aString "Open a end user friendly error notification" | answer | answer := UIManager default confirm: aString, String cr, String cr, 'Do you want to open a debugger?'. answer ifTrue: [ self error: aString ] ifFalse: [ Processor terminateActive ] -=-=-=-=-=-=-=-=-=-=-=-= But doing a Processor terminateActive freezes the image. I need to do a cmd-. to make it live again. Any idea how I can simply interrupt the current process without opening a debugger? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 26, 2010

Re: [Pharo-project] Comparing floats

by Alexandre Bergel

Excellent! Thanks! Cheers, Alexandre On 26 Jul 2010, at 10:29, Marcus Denker wrote: > > On Jul 26, 2010, at 10:24 AM, Alexandre Bergel wrote: > >> Hi! >> >> In one of my test, I want to check the equality of an array of floats. >> The following goes yellow: >> self assert: (service outgoingLinks collect: #bandwidth) asArray = #(0.876846926482685 14.7478812578828). >> >> But this one goes green: >> self assert: (service outgoingLinks collect: #bandwidth) asArray printString = '#(0.876846926482685 14.7478812578828)' . >> >> Any idea how I can avoid a conversion to strings? >> > > > there is a method #closeTo: on Float that compares in a way that should be ok for tests like this. > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 26, 2010

Re: [Pharo-project] [ANN 1.1] One-Click 1.1 release

by Serge Stinckwich

On Mon, Jul 26, 2010 at 2:05 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > 2010/7/25 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >> >> On Sun, Jul 25, 2010 at 4:02 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: >>> >>> Hm, the link doesn't work for me. I just get an empty response... >>> >> >> https://gforge.inria.fr/frs/download.php/27303/Pharo-1.1-OneClick.zip >> >> works ok here > > Works ok for me also. > > 9764 tests, 9693 passes, 53 expected failures, 17 failures, 1 error > on Mac OS X 10.6.4. Most of the failures reported are inside RBSpellingRuleTest. > Tests like: > > testPerfectSentence > Â Â Â Â | result | > Â Â Â Â result := self checker > Â Â Â Â Â Â Â Â check: 'This is an english sentence without problems.'. > Â Â Â Â self assert: result isCollection. > Â Â Â Â self assert: result isEmpty > > could not work on my machine, because by default i'm using the french > speller ... > I made some modifications to switch the speller to english and came > back to the original language after the tests. I put my modifications > here: http://code.google.com/p/pharo/issues/detail?id=2714 > > After that all RBSpellingRuleTest are green. Hum in fact no ... there is still some problems. -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

July 26, 2010

Re: [Pharo-project] Books for summer (was: Time Machine)

by Geoffroy Couprie

2010/7/26 laurent laffont <laurent.laffont(a)gmail.com> > > > On Sat, Jul 24, 2010 at 10:59 AM, Patrick Barroca < > patrick.barroca(a)gmail.com> wrote: > >> I've ordered "Why programs fail" by Andreas Zeller. >> It will be my summer holidays book ;) >> > > So I'll borrow it once read :) > > I've ordered > "Your Brain at Work: Strategies for Overcoming Distraction, Regaining > Focus, and Working Smarter All Day Long" - David Rock > > "The 10-day MBA: A Step-by-Step Guide to Mastering the Skills Taught in Top > Business Schools" - Steven Silbiger (recommended in "Passionate Programmer" > by Chad Fowler). > > And you dear Pharoers, what will you read this summer regarding your > computing/business activity ? > > The blue book :)

July 26, 2010

Re: [Pharo-project] Comparing floats

by Marcus Denker

On Jul 26, 2010, at 10:24 AM, Alexandre Bergel wrote: > Hi! > > In one of my test, I want to check the equality of an array of floats. > The following goes yellow: > self assert: (service outgoingLinks collect: #bandwidth) asArray = #(0.876846926482685 14.7478812578828). > > But this one goes green: > self assert: (service outgoingLinks collect: #bandwidth) asArray printString = '#(0.876846926482685 14.7478812578828)' . > > Any idea how I can avoid a conversion to strings? > there is a method #closeTo: on Float that compares in a way that should be ok for tests like this. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 26, 2010

[Pharo-project] Comparing floats

by Alexandre Bergel

Hi! In one of my test, I want to check the equality of an array of floats. The following goes yellow: self assert: (service outgoingLinks collect: #bandwidth) asArray = #(0.876846926482685 14.7478812578828). But this one goes green: self assert: (service outgoingLinks collect: #bandwidth) asArray printString = '#(0.876846926482685 14.7478812578828)' . Any idea how I can avoid a conversion to strings? In JUnit, there is assertEquals(double, double, delta). Where delta is an approximation. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 26, 2010

Re: [Pharo-project] [ANN 1.1] One-Click 1.1 release

by Marcus Denker

On Jul 26, 2010, at 9:06 AM, Serge Stinckwich wrote: > Why Pier.icns, PetitParser.icns and Seaside.icns files are included in > the Contents/Resources directory ? > Because the one-click is based on Lukas' setup for Hudson auto-build... We should fix that for 1.2 Marcus > > On Sun, Jul 25, 2010 at 9:02 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> On Jul 25, 2010, at 12:05 PM, Marcus Denker wrote: >> >>> >>> >>> https://gforge.inria.fr/frs/download.php/27302/Pharo-1.1-OneClick.zip >> >> >> due to a small glicht (used the wrong zip, added macos meta data...) >> >> Sadly the gforge can not replace files and keep the same path... >> >> https://gforge.inria.fr/frs/download.php/27303/Pharo-1.1-OneClick.zip >> >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 26, 2010

Re: [Pharo-project] [ANN 1.1] One-Click 1.1 release

by Serge Stinckwich

Why Pier.icns, PetitParser.icns and Seaside.icns files are included in the Contents/Resources directory ? On Sun, Jul 25, 2010 at 9:02 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jul 25, 2010, at 12:05 PM, Marcus Denker wrote: > >> >> >> Â Â Â https://gforge.inria.fr/frs/download.php/27302/Pharo-1.1-OneClick.zip > > > due to a small glicht (used the wrong zip, added macos meta data...) > > Sadly the gforge can not replace files and keep the same path... > > https://gforge.inria.fr/frs/download.php/27303/Pharo-1.1-OneClick.zip > > > -- > Marcus Denker Â -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

July 26, 2010

Re: [Pharo-project] [ANN 1.1] One-Click 1.1 release

by Serge Stinckwich

2010/7/25 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > On Sun, Jul 25, 2010 at 4:02 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: >> >> Hm, the link doesn't work for me. I just get an empty response... >> > > https://gforge.inria.fr/frs/download.php/27303/Pharo-1.1-OneClick.zip > > works ok here Works ok for me also. 9764 tests, 9693 passes, 53 expected failures, 17 failures, 1 error on Mac OS X 10.6.4. Most of the failures reported are inside RBSpellingRuleTest. Tests like: testPerfectSentence | result | result := self checker check: 'This is an english sentence without problems.'. self assert: result isCollection. self assert: result isEmpty could not work on my machine, because by default i'm using the french speller ... I made some modifications to switch the speller to english and came back to the original language after the tests. I put my modifications here: http://code.google.com/p/pharo/issues/detail?id=2714 After that all RBSpellingRuleTest are green. Regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

July 26, 2010

Re: [Pharo-project] Autotest, proof-of-concept [was: About TDD and Pharo]

by Alexandre Bergel

Ideally, we should not tag long tests. The system should be smart enough to characterize a test as long. If it takes more than 200ms, then it is long. Autotest should then offer me to include long test or not in the automatic test execution. Using tags means that I have to go over each method test and tag them. This is a costly effort that is likely to not work in practice. We have -=-=-=-=-=-=-=-=-=-=-=-= TestCase class>>newTestDictionary ^ Dictionary new at: #timeStamp put: TimeStamp now; at: #passed put: Set new; at: #failures put: Set new; at: #errors put: Set new; yourself -=-=-=-=-=-=-=-=-=-=-=-= Maybe it should be extended with -=-=-=-=-=-=-=-=-=-=-=-= at: #long put: Set new -=-=-=-=-=-=-=-=-=-=-=-= I guess the tweak in SUnit to identify long tests should not be that hard to implement. Cheers, Alexandre On 26 Jul 2010, at 07:44, laurent laffont wrote: > > On Sat, Jul 24, 2010 at 10:16 AM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > I have been using Autotest for a while already. I greatly reduce the window switching. This is cool. > However, I have to disable Autotest when the tests take time to execute. > > > An idea is to be able to tag tests with pragmas to put them in categories. So we can have a LongRunning category which is not run by default. Like NUnit (http://www.nunit.org/index.php?p=category&r=2.2) > > Then SUnit could be enhanced to show these categories. Useful to quickly select all tests related to a project for example; or run only performance tests. > > > How would you name the tag ? Where the implementation should go ? (TestCase ?) > > > Laurent. > > > Alexandre > > > On 15 Jun 2010, at 21:41, laurent laffont wrote: > > > Hi Alexandre, > > > > I've reorganized Autotest to write tests. The tests now run in a thread with lower priority. Thanks for feedback. > > > > Cheers, > > > > Laurent Laffont > > > > http://pharocasts.blogspot.com/ > > http://magaloma.blogspot.com/ > > > > > > On Mon, Jun 14, 2010 at 4:52 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > > Hi Laurent, > > > > I tried to program while having AutoTest running. > > More importantly than the interface, I experienced some problem with long executing tests. Basically, these tests should not be executed while I am programming. Or at least in a thread of a lesser priority. Am I the only one to experience this? > > > > Cheers, > > Alexandre > > > > > > On 11 Jun 2010, at 09:02, laurent laffont wrote: > > > > > On Fri, Jun 11, 2010 at 2:29 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > > > Hi Laurent, > > > > > > I like Autotest. It is true that I always execute the test after modifying it. > > > There are three horizontal panes. Why so? Is it just to open a debugger when necessary? > > > > > > I want to be able to open a debugger from autotest. I agree the GUI is crap now. > > > > > > > > > We could imagine one standalone button instead with a green color to say the test I just edited is green, and yellow or red when it fails. In that case, clicking on the button open a debugger. > > > > > > I just feel the window of autotest takes a lot of space in the screen, without having a real benefit. > > > > > > Yes it's true. I'm still thinking on a good GUI. But I'm learning how to make GUI now :) > > > > > > If you look at Autotest package, AutotestView is just the GUI, so we can implement several GUI and see the best solution. I need to take the time to do it, repository is read / write so feel free to commit :) > > > > > > What I want to have is a dashboard docked on one side of the screen which acts like you're driving a car. It's always visible, you have to be able to look quickly at it as when you check the speed of your car, adjust your drive, .... > > > > > > Also another problem with the current version if that if a test fails, change it and fails again, you don't see it has run (nothing moves in the GUI). > > > > > > Finally, another problem is that you see that a test has failed, but you don't know why (SUnit TestRunner has the same problem). I want to display the exception message too. > > > > > > Thanks a lot for feedback. > > > > > > Laurent Laffont > > > > > > http://pharocasts.blogspot.com/ > > > http://magaloma.blogspot.com/ > > > > > > > > > > > > Cheers, > > > Alexandre > > > > > > > > > On 3 Jun 2010, at 17:11, laurent laffont wrote: > > > > > > > Hi, > > > > > > > > I've written a proof-of-concept for Autotest. Draft/crappy code and no tests (exploration mode :) but it loads on PharoCore-1.1-11383-beta image. > > > > > > > > Load it: > > > > Gofer new > > > > squeaksource: 'Autotest'; > > > > package: 'Autotest'; > > > > load > > > > > > > > Open it: > > > > AutotestView open > > > > (there's en entry in WorldMenu > Tools) > > > > > > > > And change a tested method to see the results. > > > > > > > > There's a bug I need to find, maybe someone knows: > > > > - Change Bag>>occurrencesOf: > > > > - Autotest gives: > > > > > > > > 284 run, 281 passes, 0 expected failures, 1 failures, 2 errors, 0 unexpected passes > > > > Failures: > > > > CollectionRootTest>>#test0FixtureIterateTest > > > > > > > > Errors: > > > > CollectionRootTest>>#testBasicCollect > > > > CollectionRootTest>>#testDoWithout > > > > > > > > but in SUnit CollectionRootTest gives > > > > 0 run, 0 passes, 0 expected failures, 0 failures, 0 errors, 0 unexpected passes ?? > > > > > > > > > > > > Cheers, > > > > > > > > Laurent Laffont > > > > > > > > http://pharocasts.blogspot.com/ > > > > http://magaloma.blogspot.com/ > > > > > > > > > > > > On Thu, Jun 3, 2010 at 6:09 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > > > > The idea is excellent. > > > > > > > > Cheers, > > > > Alexandre > > > > > > > > > > > > On 3 Jun 2010, at 10:22, laurent laffont wrote: > > > > > > > > > > > > > > > > > > > On Thu, Jun 3, 2010 at 3:42 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > > > > > > You may have a lot of noise. > > > > > > > > > > > > I guess that Ruby uses files as a unit of development/deployment. The closest Smalltalk/Pharo has is the class and the package. > > > > > > > > > > > > I would suggest that TestCase which would use this feature use some pragma/method to identify/declare which classes/packages this test depends upon. Then the "autotest" framework would register such tests and listen for changes in the given classes/packages, launching required tests whenever a change happen. > > > > > > > > > > > > Additionally, one could declare such a pragma on a single test method, when this test should be run for a specific class. > > > > > > > > > > > > Of course, you also to take care of long running tests, which you probably want to exclude from auto-testing. > > > > > > > > > > I see autotest in Pharo in a slighly different way: When I press save in the Monticello browser, I have a popup menu which asks me whether (i) I want to run all the tests or (ii) only the tests that cover that I changed from the last version. > > > > > > > > > > Does this make sense? > > > > > > > > > > Please no popup :) What I like in ruby autotest is that I can quickly look at test results if I want (or not) without stop writing. Often you want to see your tests failing, as you type / save code. I don't have to stop writing, click a button, wait test results, go again.... testing is done in background and I just see notifications whether it's OK or not. > > > > > > > > > > So test log in a Transcript is OK for me. > > > > > > > > > > > > > > > For autotest unit of work is file: it runs the test file which has the same name as the code file, but you can customize this behavior. For autotest-rails: > > > > > "A simplified version of Autotest heuristics in this mode would be: > > > > > When changing a test file, only this file is run (e.g. test/unit/foo_test.rb âtest/unit/foo_test.rb). > > > > > When changing a model file, only associated unit test file is run (e.g.app/models/foo.rb â test/unit/foo_test.rb). > > > > > When changing a controller file, associated functional test file is run (e.g.app/controllers/foo_controller.rb âtest/functional/foo_controller_test.rb). > > > > > When changing a fixture file, associated unit test and functional test are run (e.g.app/fixtures/foos.yml â test/unit/foo_test.rb +test/functional/foo_controller_test.rb). > > > > > When changing a helper file, associated functional test file is run (e.g.app/helpers/foo_helper.rb âtest/functional/foo_controller_test.rb). > > > > > When changing application_helper.rb file all functional test files are run (e.g.application_helper.rb â test/functional/*_test.rb). > > > > > When changing a file under the config directory, all tests are run." > > > > > > > > > > Laurent > > > > > > > > > > > > > > > > > > > > Cheers, > > > > > Alexandre > > > > > -- > > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > > Alexandre Bergel http://www.bergel.eu > > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Pharo-project mailing list > > > > > Pharo-project(a)lists.gforge.inria.fr > > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > > > _______________________________________________ > > > > > Pharo-project mailing list > > > > > Pharo-project(a)lists.gforge.inria.fr > > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > -- > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > Alexandre Bergel http://www.bergel.eu > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Pharo-project mailing list > > > > Pharo-project(a)lists.gforge.inria.fr > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > _______________________________________________ > > > > Pharo-project mailing list > > > > Pharo-project(a)lists.gforge.inria.fr > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > Alexandre Bergel http://www.bergel.eu > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 26, 2010

Re: [Pharo-project] Autotest, proof-of-concept [was: About TDD and Pharo]

by laurent laffont

On Sat, Jul 24, 2010 at 10:16 AM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > I have been using Autotest for a while already. I greatly reduce the window > switching. This is cool. > However, I have to disable Autotest when the tests take time to execute. > An idea is to be able to tag tests with pragmas to put them in categories. So we can have a LongRunning category which is not run by default. Like NUnit (http://www.nunit.org/index.php?p=category&r=2.2) Then SUnit could be enhanced to show these categories. Useful to quickly select all tests related to a project for example; or run only performance tests. How would you name the tag ? Where the implementation should go ? (TestCase ?) Laurent. > > Alexandre > > > On 15 Jun 2010, at 21:41, laurent laffont wrote: > > > Hi Alexandre, > > > > I've reorganized Autotest to write tests. The tests now run in a thread > with lower priority. Thanks for feedback. > > > > Cheers, > > > > Laurent Laffont > > > > http://pharocasts.blogspot.com/ > > http://magaloma.blogspot.com/ > > > > > > On Mon, Jun 14, 2010 at 4:52 PM, Alexandre Bergel <alexandre(a)bergel.eu> > wrote: > > Hi Laurent, > > > > I tried to program while having AutoTest running. > > More importantly than the interface, I experienced some problem with long > executing tests. Basically, these tests should not be executed while I am > programming. Or at least in a thread of a lesser priority. Am I the only one > to experience this? > > > > Cheers, > > Alexandre > > > > > > On 11 Jun 2010, at 09:02, laurent laffont wrote: > > > > > On Fri, Jun 11, 2010 at 2:29 PM, Alexandre Bergel <alexandre(a)bergel.eu> > wrote: > > > Hi Laurent, > > > > > > I like Autotest. It is true that I always execute the test after > modifying it. > > > There are three horizontal panes. Why so? Is it just to open a debugger > when necessary? > > > > > > I want to be able to open a debugger from autotest. I agree the GUI is > crap now. > > > > > > > > > We could imagine one standalone button instead with a green color to > say the test I just edited is green, and yellow or red when it fails. In > that case, clicking on the button open a debugger. > > > > > > I just feel the window of autotest takes a lot of space in the screen, > without having a real benefit. > > > > > > Yes it's true. I'm still thinking on a good GUI. But I'm learning how > to make GUI now :) > > > > > > If you look at Autotest package, AutotestView is just the GUI, so we > can implement several GUI and see the best solution. I need to take the time > to do it, repository is read / write so feel free to commit :) > > > > > > What I want to have is a dashboard docked on one side of the screen > which acts like you're driving a car. It's always visible, you have to be > able to look quickly at it as when you check the speed of your car, adjust > your drive, .... > > > > > > Also another problem with the current version if that if a test fails, > change it and fails again, you don't see it has run (nothing moves in the > GUI). > > > > > > Finally, another problem is that you see that a test has failed, but > you don't know why (SUnit TestRunner has the same problem). I want to > display the exception message too. > > > > > > Thanks a lot for feedback. > > > > > > Laurent Laffont > > > > > > http://pharocasts.blogspot.com/ > > > http://magaloma.blogspot.com/ > > > > > > > > > > > > Cheers, > > > Alexandre > > > > > > > > > On 3 Jun 2010, at 17:11, laurent laffont wrote: > > > > > > > Hi, > > > > > > > > I've written a proof-of-concept for Autotest. Draft/crappy code and > no tests (exploration mode :) but it loads on PharoCore-1.1-11383-beta > image. > > > > > > > > Load it: > > > > Gofer new > > > > squeaksource: 'Autotest'; > > > > package: 'Autotest'; > > > > load > > > > > > > > Open it: > > > > AutotestView open > > > > (there's en entry in WorldMenu > Tools) > > > > > > > > And change a tested method to see the results. > > > > > > > > There's a bug I need to find, maybe someone knows: > > > > - Change Bag>>occurrencesOf: > > > > - Autotest gives: > > > > > > > > 284 run, 281 passes, 0 expected failures, 1 failures, 2 errors, 0 > unexpected passes > > > > Failures: > > > > CollectionRootTest>>#test0FixtureIterateTest > > > > > > > > Errors: > > > > CollectionRootTest>>#testBasicCollect > > > > CollectionRootTest>>#testDoWithout > > > > > > > > but in SUnit CollectionRootTest gives > > > > 0 run, 0 passes, 0 expected failures, 0 failures, 0 errors, 0 > unexpected passes ?? > > > > > > > > > > > > Cheers, > > > > > > > > Laurent Laffont > > > > > > > > http://pharocasts.blogspot.com/ > > > > http://magaloma.blogspot.com/ > > > > > > > > > > > > On Thu, Jun 3, 2010 at 6:09 PM, Alexandre Bergel < > alexandre(a)bergel.eu> wrote: > > > > The idea is excellent. > > > > > > > > Cheers, > > > > Alexandre > > > > > > > > > > > > On 3 Jun 2010, at 10:22, laurent laffont wrote: > > > > > > > > > > > > > > > > > > > On Thu, Jun 3, 2010 at 3:42 PM, Alexandre Bergel < > alexandre(a)bergel.eu> wrote: > > > > > > You may have a lot of noise. > > > > > > > > > > > > I guess that Ruby uses files as a unit of development/deployment. > The closest Smalltalk/Pharo has is the class and the package. > > > > > > > > > > > > I would suggest that TestCase which would use this feature use > some pragma/method to identify/declare which classes/packages this test > depends upon. Then the "autotest" framework would register such tests and > listen for changes in the given classes/packages, launching required tests > whenever a change happen. > > > > > > > > > > > > Additionally, one could declare such a pragma on a single test > method, when this test should be run for a specific class. > > > > > > > > > > > > Of course, you also to take care of long running tests, which you > probably want to exclude from auto-testing. > > > > > > > > > > I see autotest in Pharo in a slighly different way: When I press > save in the Monticello browser, I have a popup menu which asks me whether > (i) I want to run all the tests or (ii) only the tests that cover that I > changed from the last version. > > > > > > > > > > Does this make sense? > > > > > > > > > > Please no popup :) What I like in ruby autotest is that I can > quickly look at test results if I want (or not) without stop writing. Often > you want to see your tests failing, as you type / save code. I don't have to > stop writing, click a button, wait test results, go again.... testing is > done in background and I just see notifications whether it's OK or not. > > > > > > > > > > So test log in a Transcript is OK for me. > > > > > > > > > > > > > > > For autotest unit of work is file: it runs the test file which has > the same name as the code file, but you can customize this behavior. For > autotest-rails: > > > > > "A simplified version of Autotest heuristics in this mode would be: > > > > > When changing a test file, only this file is run (e.g. > test/unit/foo_test.rb âtest/unit/foo_test.rb). > > > > > When changing a model file, only associated unit test file is run > (e.g.app/models/foo.rb â test/unit/foo_test.rb). > > > > > When changing a controller file, associated functional test file is > run (e.g.app/controllers/foo_controller.rb > âtest/functional/foo_controller_test.rb). > > > > > When changing a fixture file, associated unit test and functional > test are run (e.g.app/fixtures/foos.yml â test/unit/foo_test.rb > +test/functional/foo_controller_test.rb). > > > > > When changing a helper file, associated functional test file is run > (e.g.app/helpers/foo_helper.rb âtest/functional/foo_controller_test.rb). > > > > > When changing application_helper.rb file all functional test files > are run (e.g.application_helper.rb â test/functional/*_test.rb). > > > > > When changing a file under the config directory, all tests are > run." > > > > > > > > > > Laurent > > > > > > > > > > > > > > > > > > > > Cheers, > > > > > Alexandre > > > > > -- > > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > > Alexandre Bergel http://www.bergel.eu > > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Pharo-project mailing list > > > > > Pharo-project(a)lists.gforge.inria.fr > > > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > > > _______________________________________________ > > > > > Pharo-project mailing list > > > > > Pharo-project(a)lists.gforge.inria.fr > > > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > -- > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > Alexandre Bergel http://www.bergel.eu > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Pharo-project mailing list > > > > Pharo-project(a)lists.gforge.inria.fr > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > _______________________________________________ > > > > Pharo-project mailing list > > > > Pharo-project(a)lists.gforge.inria.fr > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > Alexandre Bergel http://www.bergel.eu > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 26, 2010

Re: [Pharo-project] Books for summer (was: Time Machine)

by laurent laffont

On Sat, Jul 24, 2010 at 10:59 AM, Patrick Barroca <patrick.barroca(a)gmail.com > wrote: > I've ordered "Why programs fail" by Andreas Zeller. > It will be my summer holidays book ;) > So I'll borrow it once read :) I've ordered "Your Brain at Work: Strategies for Overcoming Distraction, Regaining Focus, and Working Smarter All Day Long" - David Rock "The 10-day MBA: A Step-by-Step Guide to Mastering the Skills Taught in Top Business Schools" - Steven Silbiger (recommended in "Passionate Programmer" by Chad Fowler). And you dear Pharoers, what will you read this summer regarding your computing/business activity ? Laurent > > On Thu, Jul 22, 2010 at 11:52 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > http://www.st.cs.uni-saarland.de/dd/ > > you can get some papers but also the slides that go with the book > > Stef > > > > On Jul 22, 2010, at 11:36 PM, laurent laffont wrote: > > > >> > >> On Thu, Jul 22, 2010 at 11:34 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> did you read delta debugging from andreas Zeller? > >> > >> No. Where ? > >> > >> Laurent > >> > >> > >> > >> Stef > >> > >> On Jul 22, 2010, at 11:11 PM, laurent laffont wrote: > >> > >> > Hi, > >> > > >> > From a discussion I had with Kent Beck about Continuous Testing / > Autotest (see > http://pharocasts.blogspot.com/2010/07/live-testing-with-autotest.html ), > I would like to add a kind of Time Machine for Smalltalk code in Autotest. > >> > > >> > When a test fails, what I really want to know is why. Sometimes a test > fails and I don't know why. So I have to go through a debugging session > which distracts me from what I've been coding. > >> > > >> > So an idea is to diff backtrace before and after the test fails: > >> > - revert to last green > >> > - replay the test and save the trace > >> > - forward to current test and run (test fails) > >> > - compare execution paths in order to see the consequence of last > change > >> > > >> > How would you do this ? Where should I look for materials which can > help me coding this ? > >> > > >> > Cheers, > >> > > >> > Laurent Laffont > >> > > >> > http://pharocasts.blogspot.com/ > >> > http://magaloma.blogspot.com/ > >> > _______________________________________________ > >> > Pharo-project mailing list > >> > Pharo-project(a)lists.gforge.inria.fr > >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > Patrick Barroca > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 26, 2010

Re: [Pharo-project] Primitives ?

by Michael Haupt

James, from the caller perspective, a primitive looks just like a method, so the VM, when executing the primitive, finds the arguments on the stack. Look at any of the primitive implementations in the VM source and how arguments are retrieved. HTH, Michael P.S. Will there eventually be content on redline.st? ;-) Am 26.07.2010 um 00:52 schrieb James Ladd <james_ladd(a)hotmail.com>: > Hi All, > > I'm looking at some low level details of Pharo Smalltalk and I am wondering, > when I see a primitive in the bytecode, is it safe to assume that before > the primitive is executed, the receiver and any args to the method are pushed > onto the stack? > > Rgs, James. > > Australia's #1 job site If It Exists, You'll Find it on SEEK > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 26, 2010