- Pharo-dev - lists.pharo.org

Re: [Pharo-project] problem with metacello in 1.2

by Dale Henrichs

Stef, I've wrapped my head around this one a little more ... the only stack that I saw, showed a 'Error: file is too short' error which is probably coming from the ZipArchive code ... this usually means that there was a network failure when trying to read a file from an HTTP repository. Perhaps SqueakSource was being saturated? Dale On 10/25/2010 11:44 AM, Dale Henrichs wrote: > Stef, > > I'm not sure what problem you are referring to. I haven't released a new > version of Metacello since the beginning of September.... > > Dale > > On 10/24/2010 09:55 AM, StÃ©phane Ducasse wrote: >> Dale >> >> did something change on the server side? >> >> This is strange >> >> 199 - Issue 3048: MC method cache fix. Thanks Igor Stasenko >> 200 - Issue 2653: Editor cursor fix: remove autoclose in texteditor. >> - Issue 3128: AuthorRequestImprovement. Thanks Alain Plantec - Issue 3099: Create method in the debugger does not provides getter/setters implementors. Thanks Hernan Wilkinson >> 201 - Issue 1800: MenuIcons and ThemeIcons should be merged. Big thanks to alain plantec!!! >> 202 - Issue 3070: weird replacements in TextEditor. Thanks Alain Plantec!!! >> 203 - Issue 654: inconsistent highlight color. Thanks Alain Plantec >> - Issue 3101: Wrong Monticello packages initialization order. Thanks Pavel Krivanek >> 204 - Issue 2868: allClassesUsingPool: allClassesUsingPoolVariable: for systemNavigation >> - Issue 3046: BUG: LineMorph class>>from:to:color:width: returns a PolygonMorph >> - Issue 3130: MethodReference>> #isLocalSelector should not be part of Monticello package >> - Issue 3095: Character isLiteral is in wrong category >> - Issue 3134: Cleaning uniclasses from smartRefStream >> Jannik can you check with the Utilities trick I sent you to try >> >> Utilities readServer: Utilities serverUrls updatesThrough: 12200 saveLocally: false updateImage: true >> >> 199 >> 200 >> 201 >> 202 >> 203 >> 204 >> >> so that we try to identify the problem >> >> Stef >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 25, 2010

Re: [Pharo-project] problem with metacello in 1.2

by Dale Henrichs

Stef, I'm not sure what problem you are referring to. I haven't released a new version of Metacello since the beginning of September.... Dale On 10/24/2010 09:55 AM, StÃ©phane Ducasse wrote: > Dale > > did something change on the server side? > > This is strange > > 199 - Issue 3048: MC method cache fix. Thanks Igor Stasenko > 200 - Issue 2653: Editor cursor fix: remove autoclose in texteditor. > - Issue 3128: AuthorRequestImprovement. Thanks Alain Plantec - Issue 3099: Create method in the debugger does not provides getter/setters implementors. Thanks Hernan Wilkinson > 201 - Issue 1800: MenuIcons and ThemeIcons should be merged. Big thanks to alain plantec!!! > 202 - Issue 3070: weird replacements in TextEditor. Thanks Alain Plantec!!! > 203 - Issue 654: inconsistent highlight color. Thanks Alain Plantec > - Issue 3101: Wrong Monticello packages initialization order. Thanks Pavel Krivanek > 204 - Issue 2868: allClassesUsingPool: allClassesUsingPoolVariable: for systemNavigation > - Issue 3046: BUG: LineMorph class>>from:to:color:width: returns a PolygonMorph > - Issue 3130: MethodReference>> #isLocalSelector should not be part of Monticello package > - Issue 3095: Character isLiteral is in wrong category > - Issue 3134: Cleaning uniclasses from smartRefStream > Jannik can you check with the Utilities trick I sent you to try > > Utilities readServer: Utilities serverUrls updatesThrough: 12200 saveLocally: false updateImage: true > > 199 > 200 > 201 > 202 > 203 > 204 > > so that we try to identify the problem > > Stef > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 25, 2010

Re: [Pharo-project] what happened with Shout colors in Pharo 1.1?

by Ramon Leon

On 10/25/2010 11:04 AM, Simon Denier wrote: > Uhuh, that's indeed the old theme, but as said before I now prefer the > current theme with some adaptations: it's less aggressive to the eye. And several of us have said, we like the old theme, very much because it's so aggressive to the eye. It's easy to identify things. The new theme is much less useful. The new style has removed colors and italics and has too much stuff looking the same; it's just bland. The old style is simply better because it visually separates different kinds of variables and scopes with color and font style. Local variables don't look like arguments, etc. -- Ramon Leon http://onsmalltalk.com

Oct. 25, 2010

Re: [Pharo-project] what happened with Shout colors in Pharo 1.1?

by Simon Denier

Uhuh, that's indeed the old theme, but as said before I now prefer the current theme with some adaptations: it's less aggressive to the eye. To apply, call SHTextStylerST80 initialize after changing the style table SHTextStylerST80 styleTable: #( "(symbol color [emphasisSymbolOrArray [textStyleName [pixelHeight]]])" (default ( black ) ) (invalid ( red ) ) (excessCode ( red ) ) (comment ( green muchDarker ) ) (unfinishedComment ( green muchDarker ) ) (#'$' ( magenta muchDarker) ) (character ( magenta muchDarker) ) (integer ( magenta muchDarker) ) (number ( magenta muchDarker) ) (#- ( magenta muchDarker) ) (symbol ( magenta muchDarker) ) (stringSymbol ( magenta muchDarker) ) (literalArray ( magenta muchDarker) ) (string ( magenta muchDarker) ) (unfinishedString ( magenta muchDarker) ) (assignment ( black ) ) (ansiAssignment ( black ) ) (literal ( black ) ) (keyword ( black ) ) (binary ( black ) ) (unary ( black ) ) (incompleteKeyword ( red ) ) (incompleteBinary ( red ) ) (incompleteUnary ( red ) ) (undefinedKeyword ( red ) ) (undefinedBinary ( red ) ) (undefinedUnary ( red ) ) (patternKeyword ( black ) bold ) (patternBinary ( black ) bold ) (patternUnary ( black ) bold ) (#self ( cyan muchDarker ) ) (#super ( cyan muchDarker ) ) (#true ( cyan muchDarker ) ) (#false ( cyan muchDarker ) ) (#nil ( cyan muchDarker ) ) (#thisContext ( cyan muchDarker ) ) (#return ( black ) ) (patternArg ( blue muchDarker ) ) (methodArg ( blue muchDarker ) ) (blockPatternArg ( blue muchDarker ) ) (blockArg ( blue muchDarker ) ) (argument ( blue muchDarker ) ) (blockArgColon black ) (leftParenthesis black ) (rightParenthesis black ) (leftParenthesis1 black ) (rightParenthesis1 black ) (leftParenthesis2 black ) (rightParenthesis2 black ) (leftParenthesis3 black ) (rightParenthesis3 black ) (leftParenthesis4 black ) (rightParenthesis4 black ) (leftParenthesis5 black ) (rightParenthesis5 black ) (leftParenthesis6 black ) (rightParenthesis6 black ) (leftParenthesis7 black ) (rightParenthesis7 black ) (blockStart black ) (blockEnd black ) (blockStart1 black ) (blockEnd1 black ) (blockStart2 black ) (blockEnd2 black ) (blockStart3 black ) (blockEnd3 black ) (blockStart4 black ) (blockEnd4 black ) (blockStart5 black ) (blockEnd5 black ) (blockStart6 black ) (blockEnd6 black ) (blockStart7 black ) (blockEnd7 black ) (arrayStart black ) (arrayEnd black ) (arrayStart1 black ) (arrayEnd1 black ) (byteArrayStart black ) (byteArrayEnd black ) (byteArrayStart1 black ) (byteArrayEnd1 black ) (leftBrace black ) (rightBrace black ) (cascadeSeparator black ) (statementSeparator black ) (externalCallType black ) (externalCallTypePointerIndicator black ) (primitiveOrExternalCallStart black ) (primitiveOrExternalCallEnd black ) (methodTempBar black ) (blockTempBar black ) (blockArgsBar black ) (primitive gray ) (externalFunctionCallingConvention gray ) (module gray ) (blockTempVar ( blue muchDarker ) ) (blockPatternTempVar ( blue muchDarker ) ) (instVar ( brown darker) ) (workspaceVar ( blue muchDarker ) ) (undefinedIdentifier ( red ) ) (incompleteIdentifier ( red ) ) (tempVar ( blue muchDarker ) ) (patternTempVar ( blue muchDarker ) ) (poolConstant ( black ) bold ) (classVar ( brown darker ) ) (globalVar ( black ) bold ) ) On 25 oct. 2010, at 19:36, Mariano Martinez Peck wrote: > Thanks Ramon. So, we have to options. > > 1) We commit this change to Shout repository > 2) We add this method in ConfigurationOfPharo and we call it while building the dev image. > > opinions? > > cheers > > mariano > > On Mon, Oct 25, 2010 at 7:12 PM, Ramon Leon <ramon.leon(a)allresnet.com> wrote: > On 10/23/2010 10:11 AM, Mariano Martinez Peck wrote: > Exactly. > > Can you or Simon provide a script to set back the original colors?? So > that we can apply this for next PharoDev images? (or at least for my > own images) > > Thanks > > Mariano > > I just went back in the package history and found the point where Damien changed the colors and grabbed the previous version. I have a ConfigurationOfDevelopment class that loads all my local packages, so I just added a method to it to reload the old colors. Here it is... > > -- Simon

Oct. 25, 2010

Re: [Pharo-project] what happened with Shout colors in Pharo 1.1?

by Mariano Martinez Peck

Thanks Ramon. So, we have to options. 1) We commit this change to Shout repository 2) We add this method in ConfigurationOfPharo and we call it while building the dev image. opinions? cheers mariano On Mon, Oct 25, 2010 at 7:12 PM, Ramon Leon <ramon.leon(a)allresnet.com>wrote: > On 10/23/2010 10:11 AM, Mariano Martinez Peck wrote: > >> Exactly. >> >> Can you or Simon provide a script to set back the original colors?? So >> that we can apply this for next PharoDev images? (or at least for my >> own images) >> >> Thanks >> >> Mariano >> > > I just went back in the package history and found the point where Damien > changed the colors and grabbed the previous version. I have a > ConfigurationOfDevelopment class that loads all my local packages, so I just > added a method to it to reload the old colors. Here it is... > > setColors > SHTextStylerST80 styleTable: > #( > "(symbol color [emphasisSymbolOrArray > [textStyleName [pixelHeight]]])" > (default > black ) > (invalid > red ) > (excessCode > red ) > (comment > (green muchDarker) italic) > (unfinishedComment (red > muchDarker) italic) > (#'$' > (red muchDarker) ) > (character > (red muchDarker) ) > (integer > (red muchDarker) ) > (number (red > muchDarker) ) > (#- > (red muchDarker) ) > (symbol > (blue muchDarker) bold) > (stringSymbol > (blue muchDarker) bold) > (literalArray > (blue muchDarker) bold) > (string > (magenta muchDarker) normal) > (unfinishedString red > normal ) > (assignment > nil bold ) > (ansiAssignment nil > bold) > (literal > nil italic) > (keyword > (blue muchDarker) ) > (binary > (blue muchDarker) ) > (unary > (blue muchDarker) ) > (incompleteKeyword > (gray muchDarker) underlined) > (incompleteBinary > (gray muchDarker) underlined) > (incompleteUnary > (gray muchDarker) underlined) > (undefinedKeyword red > ) > (undefinedBinary red > ) > (undefinedUnary red > ) > > (patternKeyword nil > bold) > (patternBinary nil > bold) > (patternUnary nil > bold) > (#self > (red muchDarker) bold) > (#super > (red muchDarker) bold) > (#true > (red muchDarker) bold) > (#false > (red muchDarker) bold) > (#nil > (red muchDarker) bold) > (#thisContext (red > muchDarker) bold) > (#return > (red muchDarker) bold) > (patternArg > (blue muchDarker) italic) > (methodArg > (blue muchDarker) italic) > (blockPatternArg > (blue muchDarker) italic) > (blockArg > (blue muchDarker) italic) > (argument > (blue muchDarker) italic) > (blockArgColon > black ) > (leftParenthesis > black ) > (rightParenthesis > black ) > (leftParenthesis1 > (green muchDarker) ) > (rightParenthesis1 > (green muchDarker) ) > (leftParenthesis2 > (magenta muchDarker) ) > (rightParenthesis2 > (magenta muchDarker) ) > (leftParenthesis3 (red > muchDarker) ) > (rightParenthesis3 (red > muchDarker) ) > (leftParenthesis4 > (green darker) ) > (rightParenthesis4 > (green darker) ) > (leftParenthesis5 > (orange darker) ) > (rightParenthesis5 > (orange darker) ) > (leftParenthesis6 > (magenta darker) ) > (rightParenthesis6 > (magenta darker) ) > (leftParenthesis7 blue > ) > (rightParenthesis7 blue > ) > (blockStart > black ) > (blockEnd > black ) > (blockStart1 > (green muchDarker) ) > (blockEnd1 > (green muchDarker) ) > (blockStart2 > (magenta muchDarker) ) > (blockEnd2 > (magenta muchDarker) ) > (blockStart3 > (red muchDarker) ) > (blockEnd3 > (red muchDarker) ) > (blockStart4 > (green darker) ) > (blockEnd4 > (green darker) ) > (blockStart5 > (orange darker) ) > (blockEnd5 > (orange darker) ) > (blockStart6 > (magenta darker) ) > (blockEnd6 > (magenta darker) ) > (blockStart7 > blue ) > (blockEnd7 > blue ) > > > > > > (arrayStart > black ) > (arrayEnd > black ) > (arrayStart1 > black ) > (arrayEnd1 > black ) > (leftBrace > black ) > (rightBrace > black ) > (cascadeSeparator > black ) > (statementSeparator > black ) > (externalCallType > black ) > (externalCallTypePointerIndicator black ) > (primitiveOrExternalCallStart black bold ) > (primitiveOrExternalCallEnd black bold > ) > (methodTempBar gray > ) > (blockTempBar gray > ) > (blockArgsBar gray > ) > (primitive > (green muchDarker) bold) > (pragmaKeyword (green > muchDarker) bold) > (pragmaUnary > (green muchDarker) bold) > (pragmaBinary > (green muchDarker) bold) > > (externalFunctionCallingConvention (green muchDarker) > bold) > (module > (green muchDarker) bold) > (blockTempVar gray > italic) > (blockPatternTempVar gray > italic) > (instVar > black bold) > (workspaceVar > black bold) > (undefinedIdentifier red > bold) > (incompleteIdentifier (gray > darker) (italic underlined)) > (tempVar > (gray darker) italic) > (patternTempVar (gray > darker) italic) > (poolConstant > (gray darker) italic) > (classVar > (gray darker) bold) > (globalVar > black bold) ) > > > -- > Ramon Leon > http://onsmalltalk.com > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 25, 2010

Re: [Pharo-project] what happened with Shout colors in Pharo 1.1?

by Ramon Leon

On 10/23/2010 10:11 AM, Mariano Martinez Peck wrote: > Exactly. > > Can you or Simon provide a script to set back the original colors?? So > that we can apply this for next PharoDev images? (or at least for my > own images) > > Thanks > > Mariano I just went back in the package history and found the point where Damien changed the colors and grabbed the previous version. I have a ConfigurationOfDevelopment class that loads all my local packages, so I just added a method to it to reload the old colors. Here it is... setColors SHTextStylerST80 styleTable: #( "(symbol color [emphasisSymbolOrArray [textStyleName [pixelHeight]]])" (default black ) (invalid red ) (excessCode red ) (comment (green muchDarker) italic) (unfinishedComment (red muchDarker) italic) (#'$' (red muchDarker) ) (character (red muchDarker) ) (integer (red muchDarker) ) (number (red muchDarker) ) (#- (red muchDarker) ) (symbol (blue muchDarker) bold) (stringSymbol (blue muchDarker) bold) (literalArray (blue muchDarker) bold) (string (magenta muchDarker) normal) (unfinishedString red normal ) (assignment nil bold ) (ansiAssignment nil bold) (literal nil italic) (keyword (blue muchDarker) ) (binary (blue muchDarker) ) (unary (blue muchDarker) ) (incompleteKeyword (gray muchDarker) underlined) (incompleteBinary (gray muchDarker) underlined) (incompleteUnary (gray muchDarker) underlined) (undefinedKeyword red ) (undefinedBinary red ) (undefinedUnary red ) (patternKeyword nil bold) (patternBinary nil bold) (patternUnary nil bold) (#self (red muchDarker) bold) (#super (red muchDarker) bold) (#true (red muchDarker) bold) (#false (red muchDarker) bold) (#nil (red muchDarker) bold) (#thisContext (red muchDarker) bold) (#return (red muchDarker) bold) (patternArg (blue muchDarker) italic) (methodArg (blue muchDarker) italic) (blockPatternArg (blue muchDarker) italic) (blockArg (blue muchDarker) italic) (argument (blue muchDarker) italic) (blockArgColon black ) (leftParenthesis black ) (rightParenthesis black ) (leftParenthesis1 (green muchDarker) ) (rightParenthesis1 (green muchDarker) ) (leftParenthesis2 (magenta muchDarker) ) (rightParenthesis2 (magenta muchDarker) ) (leftParenthesis3 (red muchDarker) ) (rightParenthesis3 (red muchDarker) ) (leftParenthesis4 (green darker) ) (rightParenthesis4 (green darker) ) (leftParenthesis5 (orange darker) ) (rightParenthesis5 (orange darker) ) (leftParenthesis6 (magenta darker) ) (rightParenthesis6 (magenta darker) ) (leftParenthesis7 blue ) (rightParenthesis7 blue ) (blockStart black ) (blockEnd black ) (blockStart1 (green muchDarker) ) (blockEnd1 (green muchDarker) ) (blockStart2 (magenta muchDarker) ) (blockEnd2 (magenta muchDarker) ) (blockStart3 (red muchDarker) ) (blockEnd3 (red muchDarker) ) (blockStart4 (green darker) ) (blockEnd4 (green darker) ) (blockStart5 (orange darker) ) (blockEnd5 (orange darker) ) (blockStart6 (magenta darker) ) (blockEnd6 (magenta darker) ) (blockStart7 blue ) (blockEnd7 blue ) (arrayStart black ) (arrayEnd black ) (arrayStart1 black ) (arrayEnd1 black ) (leftBrace black ) (rightBrace black ) (cascadeSeparator black ) (statementSeparator black ) (externalCallType black ) (externalCallTypePointerIndicator black ) (primitiveOrExternalCallStart black bold ) (primitiveOrExternalCallEnd black bold ) (methodTempBar gray ) (blockTempBar gray ) (blockArgsBar gray ) (primitive (green muchDarker) bold) (pragmaKeyword (green muchDarker) bold) (pragmaUnary (green muchDarker) bold) (pragmaBinary (green muchDarker) bold) (externalFunctionCallingConvention (green muchDarker) bold) (module (green muchDarker) bold) (blockTempVar gray italic) (blockPatternTempVar gray italic) (instVar black bold) (workspaceVar black bold) (undefinedIdentifier red bold) (incompleteIdentifier (gray darker) (italic underlined)) (tempVar (gray darker) italic) (patternTempVar (gray darker) italic) (poolConstant (gray darker) italic) (classVar (gray darker) bold) (globalVar black bold) ) -- Ramon Leon http://onsmalltalk.com

Oct. 25, 2010

[Pharo-project] [update 1.2] #12215

by Marcus Denker

[update 1.2] #12215 12215 ----- Issue 3158: Deprecate translation support protocol Issue 3157: Text entry dialog window badly compute minimumWidth Issue 3025: SystemVersionTest>>testDowngrade use a deprecated method Issue 3029: The Menus of the Source panes reverted to the old complex ones... Issue 3025: SystemVersionTest>>testDowngrade use a deprecated method -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Oct. 25, 2010

Re: [Pharo-project] export information to PDF

by Schwab,Wilhelm K

This would be most welcome. But it should be useful for more than just morphs. In particular, I am thinking of printing where one has to paginate and sometimes represent things differently than would be done on screen. A post script canvas or similar entry points should do it. -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Monday, October 25, 2010 1:14 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] export information to PDF if it works yes and if it does not pollutes everything. So Esteban if you can package this behavior into a package we are interested. Probably look in 3.9 but I'm not sure that it was working there. On Oct 25, 2010, at 12:42 AM, Esteban Lorenzano wrote: > Some time ago, there was a functionality to export a morph as a .ps file, I don't remember in which pharo version that function was lost...maybe it is in a package, and can be loaded, I really don't know, but it should be nice :) > > Cheers, > Esteban > > On 2010-10-24 09:58:09 -0300, name name <onor16(a)gmail.com> said: > >> Hello, >> Could you tell me how can I export (or where I can found ) information that >> I can get with a getter into a .pdf file? >> Thanks >> > ass=3D"text-cell">=A0=A0=A0=A0 Hello, Could you tell me how can I ex= >> port (or where I can found )=20 >> =A0information that I can get with a getter into a .pdf file? >> Thanks >> =09 >> =09 >> =09 >> >> _______________________________________________ >> 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

Oct. 25, 2010

Re: [Pharo-project] About Adding/modifying in SUnit or not?

by Lukas Renggli

I am all in for improving SUnit, but there must be some compatibility mode that makes it easy not only to run, but also to write tests on the official SUnit. This is crucial for projects like Seaside, Magritte, Pier, PetitParser, ... that are supposed to work on various other Smalltalk platforms. Lukas On 25 October 2010 15:51, Niko Schwarz <niko.schwarz(a)googlemail.com> wrote: > Yea, well, it depends on whether we want to be compatible with camp > smalltalk's SUnit, as maintained by Niall Ross: > http://sunit.sourceforge.net/devel.htm. Pharo already is using > extensions, such as the possibility to mark tests as expected failures > at all (that is impossible in standard SUnit). > > My humble opinion is that we must control our testing environment, and > we already have an excellent cleanup of SUnit, namely akuhn/SUnit, > http://www.squeaksource.com/akuhn.html. And we have progress in the > form of Phexample, which builds ontop of SUnit. > http://smalltalkthoughts.blogspot.com/2009/11/phexample-because-examples-ex… > . I'd be more than happy if Pharo took a new SUnit as its standard > testing framework, and I'd even be thrilled if enough people found > Phexample useful enough, so that it could become standard over time. > > Niko > > 2010/10/25 Luc Fabresse <luc.fabresse(a)gmail.com>: >> Hi all, >> Â I am working on pushing environments in SystemNavigation. >> Â SystemNavigationTest previously used ClassFactoryForTestCase from SUnit for >> generating Â classes. >> Â Now I need an environment-awareÂ ClassFactoryForTestCase. >> Â Should I directly modifyÂ ClassFactoryForTestCase since a class generator >> should now be environment aware? >> Â Should I subclassÂ ClassFactoryForTestCase and put it in SUnit? >> Â Should I never changed SUnit and put it elsewhere? ;-) >> #Luc >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > http://scg.unibe.ch/staff/Schwarz > twitter.com/nes1983 > Tel: +41 076 235 8683 > > _______________________________________________ > 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

Oct. 25, 2010

Re: [Pharo-project] About Adding/modifying in SUnit or not?

by Niko Schwarz

Yea, well, it depends on whether we want to be compatible with camp smalltalk's SUnit, as maintained by Niall Ross: http://sunit.sourceforge.net/devel.htm. Pharo already is using extensions, such as the possibility to mark tests as expected failures at all (that is impossible in standard SUnit). My humble opinion is that we must control our testing environment, and we already have an excellent cleanup of SUnit, namely akuhn/SUnit, http://www.squeaksource.com/akuhn.html. And we have progress in the form of Phexample, which builds ontop of SUnit. http://smalltalkthoughts.blogspot.com/2009/11/phexample-because-examples-ex… . I'd be more than happy if Pharo took a new SUnit as its standard testing framework, and I'd even be thrilled if enough people found Phexample useful enough, so that it could become standard over time. Niko 2010/10/25 Luc Fabresse <luc.fabresse(a)gmail.com>: > Hi all, > Â I am working on pushing environments in SystemNavigation. > Â SystemNavigationTest previously used ClassFactoryForTestCase from SUnit for > generating Â classes. > Â Now I need an environment-awareÂ ClassFactoryForTestCase. > Â Should I directly modifyÂ ClassFactoryForTestCase since a class generator > should now be environment aware? > Â Should I subclassÂ ClassFactoryForTestCase and put it in SUnit? > Â Should I never changed SUnit and put it elsewhere? ;-) > #Luc > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- http://scg.unibe.ch/staff/Schwarz twitter.com/nes1983 Tel: +41 076 235 8683

Oct. 25, 2010