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

Re: [Pharo-project] SUNit
by Benoit St-Jean Jan. 24, 2011

Jan. 24, 2011

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) > > > >

4 6

[Pharo-project] Tabs and back button in browser?
by Janko MivÅ¡ek Jan. 24, 2011

Jan. 24, 2011

Hi Pharoers, Are you thinking about introducing tabs and back/forward button, like in web browsers? Just because of web we are now all accustomized and used of tabbed browsing and navigation with a back and forward buttons. This habit now demands all other tools to follow. Tabs are now everywhere, also in Smalltalk. Look at Visualworks, also Dolphin. Introducing tabs soon in Pharo will therefore greatly improve user experience, so if someone would spend some time on it, his contribution will be very valuable! Best regards Janko -- Janko MivÅ¡ek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si

3 2

[Pharo-project] What about a little rename in MouseEvent?
by Guillermo Polito Jan. 24, 2011

Jan. 24, 2011

I hate yellowButtonPressed and redButtonPressed and blueButtonPressed messages. Why not lefClick, rightClick and "middleClick"? Cheers, Guille

6 9

Re: [Pharo-project] default styler is shout
by Marcus Denker Jan. 24, 2011

Jan. 24, 2011

On Jan 24, 2011, at 2:19 AM, Guillermo Polito wrote: > But that imperfect solution won't be a good solution either, since we are not going to have shout styler anywhere :). > So how is that solved in1.1? We need, for 1.2, just a *usable* compromise. Then we can iterate in 1.3 Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

6 6

[Pharo-project] whisker browser
by Tudor Girba Jan. 24, 2011

Jan. 24, 2011

Hi, Does anybody have an image with a working Whisker Browser? I would be interested in learning from it. Cheers, Doru -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

2 1

[Pharo-project] doc on ob requests and commands
by Tudor Girba Jan. 24, 2011

Jan. 24, 2011

Hi, I am browsing OB to understand the design of the Requests and the commands. In particular, I am interested to understand why OBRequests are Notifications and how they link with the commands. Is there anywhere I can read about it? Cheers, Doru -- www.tudorgirba.com "What we can governs what we wish."

3 6

[Pharo-project] Graphics with Anti-Aliasing
by Udo Schneider Jan. 24, 2011

Jan. 24, 2011

All, does somebody has a pointer to a graphics lib/framework/engine for Pharo which works with Anti-Aliasing. My first tests with Balloon2D were disappointing (maybe I'm doing something wrong). But even setting aaLevel does not seem to bring any result. I.e. the line drawing code falls back to superclass code which simply draws the same jagged lines like always. Any pointers? CU, Udo

6 14

Re: [Pharo-project] for coral
by Marcus Denker Jan. 24, 2011

Jan. 24, 2011

On Jan 22, 2011, at 9:15 AM, StÃ©phane Ducasse wrote: > We should: > > - use this list > - have a plan Item 1: Hudson Project for Coral. :-) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 2

Re: [Pharo-project] [squeak-dev] Xtreams up to date
by mkobetic＠gmail.com Jan. 24, 2011

Jan. 24, 2011

"Hannes Hirzel"<hannes.hirzel(a)gmail.com> wrote: > I worked through it and understood it. I adapted the class names so > that it runs in the current Squeak 4.2 out of the box. In addition I > edited it slightly. I think it could be added as to the PEGParser > class. Maybe somebody else like to check it in addition .... Yes, wrote it with the intent to eventually turn it into documentation for the Parsing package. On VW side we keep these in package comments, that's the most obvious location for it IMO. I'm not convinced that using a class comment on Squeak/Pharo side is a good choice. I would have difficulty myself to pick the class for it, so the chances that a new user will find it are even lower. I'm intrigued by the help facilities that were mentioned on Pharo side quite a bit recently. Is that something people hope to turn into the primary resource for these things ? Sounds like it would be quite easy to package it as that. The package comment are already written using the google wiki syntax, so that they can be directly posted to the google project site. So the help facilities allowing wiki syntax sound particularly attractive. Is this something that could work on Squeak side too, or do we need to do something different there ? In the meantime I intend to at least keep the google project pages up to date. > Additional example: Wiki text parsing > > In the previous mail you mentioned that you'll add the fileout of the class > > PEGWikiGenerator Ah, I got caught up in the arithmetic example and forgot the attachments. They are attached now. Sorry about that. Thanks for the edited version of the example. I'll work on it some more and turn it into a doc page on the site. If we figure out how to package it in Squeak and Pharo so that people can find it easily, I'd be happy to add all the documentation we have on the site. Cheers, Martin

1 0

[Pharo-project] Issue 3588 in pharo: Monticello breaks when trying to load code with syntax errors
by pharo＠googlecode.com Jan. 24, 2011

Jan. 24, 2011

Status: New Owner: ---- New issue 3588 by elpochod...(a)gmail.com: Monticello breaks when trying to load code with syntax errors http://code.google.com/p/pharo/issues/detail?id=3588 Pharo image: Pharo Pharo core version: Pharo1.2rc1/Latest update: #12317 Virtual machine used: 'Squeak3.10.2 of 11 February 2010 [latest update: #9314]' (windows) Steps to reproduce: 1. Monticello browser->+Package named OpenGL 2. +Repository http: www.squeaksource.com/OpenGL 3. Open it, load OpenGL-clk.5.mcz ignoring warning because of missing classes. You get a syntax error because of underscore assignments, but it would fail the same for any syntax error, like assigning to a variable that is a parameter instead of a temporary, or anything that compiled with a previous compiler and doesn't compile anymore. The code can be modified by hand and (should be) accepted with ctrl+s, but then a monticello error is raised. The main thing is to fix the stack trace. Then, an accept/ignore and continue/cancel all button would be even better.

1 0