January 2011 - Pharo-dev - lists.pharo.org

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

by laurent laffont

Isn't what you're looking for ? http://book.pharo-project.org/book/PharoTools/ Laurent On Wed, Jan 12, 2011 at 8:44 PM, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > 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

[Pharo-project] Issue 3536 in pharo: ZipArchive>>extractAllTo: leaves temporary directory on Mac

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3536 by sean.p.denigris: ZipArchive>>extractAllTo: leaves temporary directory on Mac http://code.google.com/p/pharo/issues/detail?id=3536 Pharo image: Pharo1.2beta Latest update: #12300 Steps to reproduce: 1. archive := ZipArchive new readFrom: '/Users/sean/Squeak/Fresh Images/PharoTrunk.zip'. archive extractAllTo: (FileDirectory on: '/Users/sean/Squeak/Fresh Images/a'). A temporary directory named __MACOSX will exist.

Jan. 12, 2011

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

by Mariano Martinez Peck

yes, that was a hack I had to do becuase at that moment Cog didn't support well objects as methods, used by MethodWrappers, and when running its tests, it crashed. we wanted to create a quick image so that people could start using cog and help testing it. this is not the case anymore in Pharo 1,2 so, if someone wants, the real solution is to create a new one click of 1.1.1 (without touching by hand method wrappers) and put new CogVMs. cheers mariano On Wed, Jan 12, 2011 at 8:10 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > 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

Re: [Pharo-project] [update 1.2] #12297

by Igor Stasenko

On 12 January 2011 16:56, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Wed, Jan 12, 2011 at 4:45 PM, Sven Van Caekenberghe <sven(a)beta9.be> > wrote: >> >> On 12 Jan 2011, at 16:30, StÃ©phane Ducasse wrote: >> >> > - Glamourous setting as default. >> >> Yes! Maybe a bit dull, but clean and professional, my favorite! >> > > But it is not about that. > As torsten said, there are books, screencasts, screnshots, tutorials, etc, > which are done with Watery2. so , you're an addict! :) Ubuntu changes its skin every single release.. and i am pretty sure that there are books, screencasts, screnshots, tutorials, etc for Ubuntu as well. (btw i think they established really good tradition, because people could quickly distinguish one version from another by simply taking a glance on the screen) Get used to live in ever changing world :) > you, and all Pharo advanced users can easily change the theme, and you > probbaly even have a script prepare that you run in each clean image to > adapt it to your taste. UIThemeWatery2 beCurrent. be my guest :) http://bit.ly/gi7vb7 > But I think we should make the life easier for new comers. > In addition, it was never discussed in the mailing list such change (at > least I didn't see it). > i agree, it is better to discuss broadly before changing. I like the glamourous theme because it is minimalistic and elegant. Still the colors are a bit wrong as to my taste, especially selection (light blue). > cheers > > mariano > -- Best regards, Igor Stasenko AKA sig.

Jan. 12, 2011

[Pharo-project] Auto completion and syntax highlighting options

by Schwab,Wilhelm K

I just downloaded the latest (#62) one click 1.2 and did the usual things: (1) turn off autocompletion (2) select win2k, enable fast drag (3) open a workspace, disable syntax highlighting I think Shout is the wonderful; it is very helpful in browsers and the debugger; I shut it off in workspaces because much of what I type there is not code. The snag: OCompletion is still popping up menus and disabling Shout in the workspace has no effect. Bill

Jan. 12, 2011

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