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

[Pharo-project] trait composition conflict autoresolution

by aizcorbe

Hi all, I'm doing some work with traits, and I found something like this case: Trait T1>>m1 ^self requirement Trait T2>>m1 doSomeStuff Class C1 uses: T1 + T2 [note, i'm not excluding m1 from T1 in the T1 + T2 composition.] And the resulting: C1>>m1 doSomeStuff It is just ok, since the other m1 is just a mark for a requiredMethod, but I find this a little weird, since do not follow the Trait definition. (at least the one I read, maybe it changed!). Wouldn't be better to automatically add the exclusion at the composition? Class C1 uses: T1 - {#m1} + T2 In this way the definition would be followed without any exception (and it will be explicit with what is going on). This is just a suggestion, anyway it works great! btw... why there are two requirement marks?: Object>>requirement self error: 'Implicitly required method' Object>>explicitRequirement self error: 'Explicitly required method' the question is, if I use #requirement, I'm explicitly requiring that method. Is there any situation where I should use #requirement? Cheers -- View this message in context: http://forum.world.st/trait-composition-conflict-autoresolution-tp2235790p2… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 29, 2010

Re: [Pharo-project] How do I install seaside in Pharo 1.0?

by magique poter

>> I have problem installing Seaside on Pharo 1.0. Evaluate >> ConfigurationOfSeaside >> workspace >> did not work. > > Hi! Hello! Thanks for your response, > In the Smalltalk world, when you see aClass >> aMmethod > it means that you are talking about the method aMethod from the class > aClass. > > Actually, what you CAN evaluate is something like this: > > AClass >> #aMethodName > > example > > ConfigurationOfSeaside >> #workspace There is no ConfigurationOfSeaside class in the Pharo 1.0 image. How can this work? >> I have also tryed this code: >> Gofer new >> Â squeaksource: 'MetacelloRepository'; >> Â package: 'ConfigurationOfSeaside'; >> Â load. >> ((Smalltalk at: #ConfigurationOfSeaside ) project latestVersion) load >> it did not work to. >> > > > Try: > > Gofer new > Â squeaksource: 'MetacelloRepository'; > Â package: 'ConfigurationOfSeaside30'; > Â load. > ((Smalltalk at: #ConfigurationOfSeaside30 ) project latestVersion) load Ok it works! >> Why does the code >> DEVImageWorkspaces openExternalProjectWorkspace >> did not show an easy way to install Seaside (it was the case before)? >> > > What is before and what is now? Before (in the late Pharo release), there was a code to evaluate like other external packages magma, aida, moose... like this: "Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. ((Smalltalk at: #ConfigurationOfSeaside30 ) project latestVersion) load" For both seaside2.8 and seaside 3.0. I have found this simple steps to install external packages very handy for starting programming in smaltalk, without have to deeply understand the Metacello packages system (I should start to understand it...). Thanks for your help! Sebovick > Mariano > >> >> Cordialy >> >> _______________________________________________ >> 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 >

May 29, 2010

Re: [Pharo-project] How do I install seaside in Pharo 1.0?

by Mariano Martinez Peck

On Sat, May 29, 2010 at 2:24 PM, magique poter <sebovick(a)gmail.com> wrote: > Hello, > > I have problem installing Seaside on Pharo 1.0. Evaluate > ConfigurationOfSeaside >> workspace > did not work. > Hi! In the Smalltalk world, when you see aClass >> aMmethod it means that you are talking about the method aMethod from the class aClass. If you refer to class side methods: aClass class >> aMethod So, in this case, it means you should see the method workspace of the class ConfigurationInSeaside, NOT to evaluate the code. Actually, what you CAN evaluate is something like this: AClass >> #aMethodName example ConfigurationOfSeaside >> #workspace if you evaluate this, it answer the compiled method of the selector #workspace. > I have also tryed this code: > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSeaside'; > load. > ((Smalltalk at: #ConfigurationOfSeaside ) project latestVersion) load > it did not work to. > > Try: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. ((Smalltalk at: #ConfigurationOfSeaside30 ) project latestVersion) load > Why does the code > DEVImageWorkspaces openExternalProjectWorkspace > did not show an easy way to install Seaside (it was the case before)? > > What is before and what is now? Thanks! Mariano > Cordialy > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 29, 2010

Re: [Pharo-project] SUnit Time out

by Lukas Renggli

We already have #should:notTakeMoreThan: and friends in TestCase. The complete TestCase can be protected by overriding #runCase, the individual test by wrapping the code of the test method. Lukas On 29 May 2010 16:43, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Stef, > > Time to expose some of my ignorance (don't worry, I have plenty more waiting where I found this): what is the tag concept? Â That sounds very Tweak-ish, and I am a real believer in doing things "with the language, not TO the language" whenever possible. Â That is not to say that frameworks are bad; in fact, it means that frameworks are good, language extensions are anywhere from suspect to evil. > > I have some code that I am still porting, but the basic idea is to be able to write > > [ > Â "code that might not complete" > > ] tryForSeconds:10 onTimeOut:[ > > ]. > > With a robust capability to do such things, it is probably not necessary (or even appropriate) for TestCase to enforce timeouts. Â The timeout block can simply raise an exception or assert false, and there is no need to disable timeouts where they do not belong. > > Bill > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Michael Roberts [mike(a)mjr104.co.uk] > Sent: Saturday, May 29, 2010 6:17 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] SUnit Time out > > yes think it's a good idea. I'm not sure the granularity that's > required though. > > mike > > On Saturday, May 29, 2010, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >> Hi guys >> >> in Squeak andreas introduced the idea of test time out >> Do you think that this is interesting? >> >> Stef >> >> SUnit >> ----- >> All test cases now have an associated timeout after which the test is considered failed. The purpose of the timeout is to catch issues like infinite loops, unexpected user input etc. in automated test environments. Timeouts can be set on an individual test basis using the <timeout: seconds> tag or for an entire test case by implementing the #defaultTimeout method. >> _______________________________________________ >> 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 > -- Lukas Renggli www.lukas-renggli.ch

May 29, 2010

Re: [Pharo-project] SUnit Time out

by StÃ©phane Ducasse

On May 29, 2010, at 4:43 PM, Schwab,Wilhelm K wrote: > Stef, > > Time to expose some of my ignorance (don't worry, I have plenty more waiting where I found this): what is the tag concept? probably a pragma > That sounds very Tweak-ish, and I am a real believer in doing things "with the language, not TO the language" whenever possible. That is not to say that frameworks are bad; in fact, it means that frameworks are good, language extensions are anywhere from suspect to evil. > > I have some code that I am still porting, but the basic idea is to be able to write > > [ > "code that might not complete" > > ] tryForSeconds:10 onTimeOut:[ > > ]. > > With a robust capability to do such things, it is probably not necessary (or even appropriate) for TestCase to enforce timeouts. The timeout block can simply raise an exception or assert false, and there is no need to disable timeouts where they do not belong. Yes this could be a nice extension now what is nice with the tag (I imagine I did not check is that this is orthogonal to the code and this is jyst an indication for the test runner and this is not intrusive. > > Bill > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Michael Roberts [mike(a)mjr104.co.uk] > Sent: Saturday, May 29, 2010 6:17 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] SUnit Time out > > yes think it's a good idea. I'm not sure the granularity that's > required though. > > mike > > On Saturday, May 29, 2010, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >> Hi guys >> >> in Squeak andreas introduced the idea of test time out >> Do you think that this is interesting? >> >> Stef >> >> SUnit >> ----- >> All test cases now have an associated timeout after which the test is considered failed. The purpose of the timeout is to catch issues like infinite loops, unexpected user input etc. in automated test environments. Timeouts can be set on an individual test basis using the <timeout: seconds> tag or for an entire test case by implementing the #defaultTimeout method. >> _______________________________________________ >> 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

May 29, 2010

Re: [Pharo-project] SUnit Time out

by Schwab,Wilhelm K

Stef, Time to expose some of my ignorance (don't worry, I have plenty more waiting where I found this): what is the tag concept? That sounds very Tweak-ish, and I am a real believer in doing things "with the language, not TO the language" whenever possible. That is not to say that frameworks are bad; in fact, it means that frameworks are good, language extensions are anywhere from suspect to evil. I have some code that I am still porting, but the basic idea is to be able to write [ "code that might not complete" ] tryForSeconds:10 onTimeOut:[ ]. With a robust capability to do such things, it is probably not necessary (or even appropriate) for TestCase to enforce timeouts. The timeout block can simply raise an exception or assert false, and there is no need to disable timeouts where they do not belong. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Michael Roberts [mike(a)mjr104.co.uk] Sent: Saturday, May 29, 2010 6:17 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] SUnit Time out yes think it's a good idea. I'm not sure the granularity that's required though. mike On Saturday, May 29, 2010, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > Hi guys > > in Squeak andreas introduced the idea of test time out > Do you think that this is interesting? > > Stef > > SUnit > ----- > All test cases now have an associated timeout after which the test is considered failed. The purpose of the timeout is to catch issues like infinite loops, unexpected user input etc. in automated test environments. Timeouts can be set on an individual test basis using the <timeout: seconds> tag or for an entire test case by implementing the #defaultTimeout method. > _______________________________________________ > 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

May 29, 2010

[Pharo-project] How do I install seaside in Pharo 1.0?

by magique poter

Hello, I have problem installing Seaside on Pharo 1.0. Evaluate ConfigurationOfSeaside >> workspace did not work. I have also tryed this code: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside'; load. ((Smalltalk at: #ConfigurationOfSeaside ) project latestVersion) load it did not work to. Why does the code DEVImageWorkspaces openExternalProjectWorkspace did not show an easy way to install Seaside (it was the case before)? Cordialy

May 29, 2010

Re: [Pharo-project] SUnit Time out

by Michael Roberts

yes think it's a good idea. I'm not sure the granularity that's required though. mike On Saturday, May 29, 2010, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > Hi guys > > in Squeak andreas introduced the idea of test time out > Do you think that this is interesting? > > Stef > > SUnit > ----- > All test cases now have an associated timeout after which the test is considered failed. The purpose of the timeout is to catch issues like infinite loops, unexpected user input etc. in automated test environments. Timeouts can be set on an individual test basis using the <timeout: seconds> tag or for an entire test case by implementing the #defaultTimeout method. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 29, 2010

[Pharo-project] SUnit Time out

by stephane ducasse

Hi guys in Squeak andreas introduced the idea of test time out Do you think that this is interesting? Stef SUnit ----- All test cases now have an associated timeout after which the test is considered failed. The purpose of the timeout is to catch issues like infinite loops, unexpected user input etc. in automated test environments. Timeouts can be set on an individual test basis using the <timeout: seconds> tag or for an entire test case by implementing the #defaultTimeout method.

May 29, 2010

[Pharo-project] [update 1.1] #11378

by StÃ©phane Ducasse

11378 ----- - Issue2458: ChooseColorDefaults - Issue 2182: Part one. http://code.google.com/p/pharo/issues/detail?id=2182 This slice adds a class ObsoleteTest that tests the various flavor of isObsolete (on classes, metaclasses and traits). Furthermore, it adds some very useful methods: Trait class>>named:, Class>>subclass:uses:

May 29, 2010