- Pharo-dev - lists.pharo.org

Re: [Pharo-project] DuplicatedVariableError: styler is already defined in PluggableTextMorph

by Guillermo Polito

I think that Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfOmniBrowser'; load. (((Smalltalk at: #ConfigurationOfOmniBrowser) perform: #project) perform: #version with: '1.2.3') load should do it ;) On Wed, Jan 12, 2011 at 5:18 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > > On 12 Jan 2011, at 20:11, Guillermo Polito wrote: > > > There is a fix already submitted to PharoTaskForces. If you download the > last version from the metacello config, it should load well :). > > Thanks for the response, Guillermo. > > I will have to read up on Metacello, I keep postponing it, but there seems > to be no escape from it ;-) > > Sven > > >

Jan. 12, 2011

Re: [Pharo-project] Issue 3533 in pharo: add Dictionary>>at:ifAbsentValue:

by pharo＠googlecode.com

Comment #5 on issue 3533 by rydier: add Dictionary>>at:ifAbsentValue: http://code.google.com/p/pharo/issues/detail?id=3533 "you can't tell anything about nature of objects you are storing in dictionary, and when speed is essential" Do you have any specific use caees in mind?

Jan. 12, 2011

Re: [Pharo-project] DuplicatedVariableError: styler is already defined in PluggableTextMorph

by Sven Van Caekenberghe

On 12 Jan 2011, at 20:11, Guillermo Polito wrote: > There is a fix already submitted to PharoTaskForces. If you download the last version from the metacello config, it should load well :). Thanks for the response, Guillermo. I will have to read up on Metacello, I keep postponing it, but there seems to be no escape from it ;-) Sven

Jan. 12, 2011

Re: [Pharo-project] SUNit

by Lukas Renggli

> That I knew but my problem is that *all* resources are initialized *at once* > before running the test suite.Â I would need *only* the proper resource to > be initialized before running all tests in every TestCase subclass...Â My > problem lies in the fact that the resource I need is a singleton instance > that is initialized based on specific parameters, each time different from > one test case to another.Â So what happens is that all tests cases end up > using this singleton with the way it was last initialized before running the > test suite, which ain't good! Tests do not run in a predefined order, so you cannot make assumptions on that. What you can do, is to let your TestResource return different resources based on the context, i.e. the test class that requests it. MyTestCase>>singleton ^ MyTestResource current singletonFor: self MyTestResource>>singletonFor: aTestCase ^ singletonCache at: aTestCase class ifAbsentPut: [ aTestCase buildSingleton ] If you want to see an example of this pattern have a look at the tests of PetitParser. PPCompositeParserTest (and its subclasses) and PPParserResource do exactly follow that pattern. Lukas -- Lukas Renggli www.lukas-renggli.ch

Jan. 12, 2011

Re: [Pharo-project] SUNit

by Benoit St-Jean

That I knew but my problem is that *all* resources are initialized *at once* before running the test suite. I would need *only* the proper resource to be initialized before running all tests in every TestCase subclass... My problem lies in the fact that the resource I need is a singleton instance that is initialized based on specific parameters, each time different from one test case to another. So what happens is that all tests cases end up using this singleton with the way it was last initialized before running the test suite, which ain't good! ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein) ________________________________ From: Mariano Martinez Peck <marianopeck(a)gmail.com> To: Pharo-project(a)lists.gforge.inria.fr Sent: Wed, January 12, 2011 1:48:13 PM Subject: Re: [Pharo-project] SUNit On Wed, Jan 12, 2011 at 7:13 PM, Benoit St-Jean <bstjean(a)yahoo.com> wrote: Is there any way to initialize a TestCase subclass *once* and set up all the necessary stuff I need for all test cases in that subclass ? > >Let's say I want to test some socket stuff and connect only ONCE (and reuse that >socket over and over, leaving it open), how should I proceed? I don't want to >open and close the socket with #setUp and #tearDown each and every time so a >one-time initialization for the class (and a proper cleanup ) everytime I run >the test suite is what I am looking for. Suggestions? Is there any Sunit >version/fork/extension that would allow me to do that? > > As Lukas said, the best solution here is using TestResource. I did exaclty what you describe there for the SqueakDBX tests and the connections to the database. Did I miss something obvious and I have exactly what I need in front on me in my class browser right now or we can't do this with what's there now? > >If it's not there, does anyone think it would be worth we add such a feature ? >I volunteer to get it done! > >tia! > > ----------------- >Benoit St-Jean >Yahoo! Messenger: bstjean >A standpoint is an intellectual horizon of radius zero. >(Albert Einstein) > > > >

Jan. 12, 2011

Re: [Pharo-project] Updated ConfigurationsOf...scripts?

by HernÃ¡n Morales Durand

Ok if there are not, I think is a must, I spend a lot of time searching for the updated scripts or exporting/importing them in my images. What about creating a wiki page in the google project? HernÃ¡n 2011/1/11 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > Hi, > > Is there any page/tool where all the updated ConfigurationOf.... > installing scripts are found? > Best regards, > > -- > HernÃ¡n Morales > Information Technology Manager, > Institute of Veterinary Genetics. > National Scientific and Technical Research Council (CONICET). > La Plata (1900), Buenos Aires, Argentina. > Telephone: +54 (0221) 421-1799. > Internal: 422 > Fax: 425-7980 or 421-1799. >

Jan. 12, 2011

Re: [Pharo-project] Issue 3534 in pharo: LargePositiveInteger(Object)>>error

by pharo＠googlecode.com

Comment #1 on issue 3534 by Torsten....(a)astares.de: LargePositiveInteger(Object)>>error http://code.google.com/p/pharo/issues/detail?id=3534 The problem with this bug is that I was hit by it 7 or 8 times since using the Cog VM. Anytime when opening the world menu. Unfortunately it is hard to reproduce manually, I can open the world menu afterwards without any problem. The problem I see in the debugger is that instead of returning a Color instance (which would understand #pixelValueForDepth:) a large positive integer 4278190081 is returned from the expression "(colors at: i)" in the method ColorForm>>colormapIfNeededForDepth:

Jan. 12, 2011

Re: [Pharo-project] Issue 3533 in pharo: add Dictionary>>at:ifAbsentValue:

by pharo＠googlecode.com

Comment #4 on issue 3533 by siguctua: add Dictionary>>at:ifAbsentValue: http://code.google.com/p/pharo/issues/detail?id=3533 Of course, you can always use: dict at: x ifAbsent: y except that it is not always desirable to send #value message to 'y' argument, especially if you can't tell anything about nature of objects you are storing in dictionary, and when speed is essential, it would be good to have something like this: at: key ifAbsentValue: defaultValue "Answer the value associated with the key or, if key isn't found, answer the default value" ^((array at: (self findElementOrNil: key)) ifNil: [ ^ defaultValue ]) value Cog VM shows a significant difference in delivering an answer: | dict | dict := Dictionary new. dict at: #a put: 1. [ 1000000 timesRepeat: [ dict at: #foo ifAbsentValue: #bar ] ] timeToRun 236 234 239 [ 1000000 timesRepeat: [ dict at: #a ifAbsentValue: #bar ] ] timeToRun 241 234 236 237 [ 1000000 timesRepeat: [ dict at: #foo ifAbsent: [#bar] ] ] timeToRun 322 318 [ 1000000 timesRepeat: [ dict at: #a ifAbsent: [ #bar ] ] ] timeToRun 363 336 340

Jan. 12, 2011

Re: [Pharo-project] DuplicatedVariableError: styler is already defined in PluggableTextMorph

by Guillermo Polito

There is a fix already submitted to PharoTaskForces. If you download the last version from the metacello config, it should load well :). Cheers! On Wed, Jan 12, 2011 at 4:05 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > When trying to do: > > Gofer new renggli: 'omnibrowser'; > package: 'OmniBrowser'; > package: 'OB-Standard'; > package: 'OB-Morphic'; > package: 'OB-Shout'; > package: 'OB-Refactory'; > package: 'OB-Regex'; > package: 'OB-SUnitIntegration'; > load > > (Part of the build scripts of LR's builder scripting package) > > I get the following error: > > DuplicatedVariableError: styler is already defined in PluggableTextMorph > > while loading the definitiion of OBPluggableTextMorphWithShout in PharoCore > 1.2 #12294. > > I have seen some things flying around on the mailinglist related indirectly > to this issue. > > Is there a solution ? > > Thx, > > Sven > > >

Jan. 12, 2011

[Pharo-project] Dirty MC Packages in Pharo-1.1.1-OneClickCogVM

by Sven Van Caekenberghe

Yesterday I downloaded Pharo-1.1.1-OneClickCogVM from https://gforge.inria.fr/frs/download.php/27524/Pharo-1.1.1-OneClickCogVM.zip and I noticed it has two dirty MC packages (MethodWrappers and Tests). This is probably a glitch, but not nice and confusion for beginners. Sven

Jan. 12, 2011