March 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Moose-dev] Re: numerical method in smalltalk
by Serge Stinckwich March 20, 2012

March 20, 2012

2012/3/20 Steffen MÃ¤rcker <merkste(a)web.de>: > It can imagine that it would be useful for the ST community to have this > cross dialect. Are there any plans in this direction? Yes in a perfect world, but having already something working on Pharo is a first step. After that people could adapt to other flavors if they want. Regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

1 0

[Pharo-project] Object>>deprecated:on:in: doesn't respect state of Deprecation class>>showWarning:
by Martin Sandiford March 20, 2012

March 20, 2012

Hi all, Kind of new to Pharo, so not sure if this is intended behaviour or not, but "Object>>deprecated:on:in:" doesn't respect the current state of the "Deprecation class>>showWarning" setting. This was unexpected for me --- in a headless setting the warning dialog causes the VM to exit. To reproduce (in 1.4 14399): Deprecation showWarning: false. true and: [ true ] and: [ true ]. "Boolean>>and:and: sends deprecated:on:in:" Fix seems straightforward: wrap the current contents of "deprecated:on:in:" in "Deprecation showWarning ifTrue: [...]". If there are no objections, I'll raise a bug in the tracker. Cheers, Martin

2 3

Re: [Pharo-project] [Moose-dev] Re: numerical method in smalltalk
by Serge Stinckwich March 20, 2012

March 20, 2012

2012/3/20 Steffen MÃ¤rcker <merkste(a)web.de>: > Hi, > > There's a package "Numerical Methods" in Cincoms Public Repository which is > - I think - based on the book "Object-Oriented Implementation of Numerical > Methods". Is this package already ported? If not, it might be a good > starting point. But it needs more documentation... Yes there is already the same version for Pharo/Squeak on Squeaksource. There is actually a lot of code dispersed in several projects with some duplication also. The idea is to consolidate everything. Regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

2 1

[Pharo-project] [update 1.4] #14404
by Marcus Denker March 20, 2012

March 20, 2012

14404 ----- Issue 5522: Remove a code duplication in Browser http://code.google.com/p/pharo/issues/detail?id=5522 Issue 5511: recategorize CompiledMethod>>hasBreakpoint and Object>>break http://code.google.com/p/pharo/issues/detail?id=5511 Issue 5509: DNU #renameAs: in FileList http://code.google.com/p/pharo/issues/detail?id=5509 Issue 5508: #asText should be packaged along with Collections-Text http://code.google.com/p/pharo/issues/detail?id=5508 -- Marcus Denker -- http://marcusdenker.de

1 0

Re: [Pharo-project] [Moose-dev] failing tests
by Tudor Girba March 20, 2012

March 20, 2012

Hi, The problem is that the new implementation of union: and intersection: makes reference to class directly. Instead, they should use species. I opened a an issue: http://code.google.com/p/pharo/issues/detail?id=5523 and created the corresponding slice: Name: SLICE-Issue-5523-Collection-union-and-intersection-should-use-species-TudorGirba.1 Author: TudorGirba Time: 20 March 2012, 7:25:55 am UUID: b3944736-b2d8-4c30-ad24-3c39c2a18cf9 Ancestors: Dependencies: Collections-Abstract-TudorGirba.158 use species instead of class for Collection>>union: and intersection: Cheers, Doru On 19 Mar 2012, at 20:10, StÃ©phane Ducasse wrote: > > On Mar 18, 2012, at 10:08 PM, Alexandre Bergel wrote: > >> I am a bit puzzled. How comes that a new version of #union: break down so many tests. >> #union: is a simple operation. > > Yes I would like to know it too. > Do you have one single case that we can understand? > > Stef > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com If you can't say why something is relevant, it probably isn't.

2 1

[Pharo-project] International Workshop on Smalltalk Technologies 2011
by Alain Plantec March 20, 2012

March 20, 2012

Dear smalltakers, We are now pleased to inform you that the IWST 2011 proceedings are currently on-line. here is the IWST link: http://dl.acm.org/citation.cfm?id=2166929&picked=prox&cfid=71182337&cftoken… From this page, you will be able to acces all papers. Regards, LoÃ¯c Lagadec & Alain Plantec IWST 2011 co-chairs

1 0

[Pharo-project] MVP - presenters as factories; some models; CODE!!!
by Schwab,Wilhelm K March 20, 2012

March 20, 2012

Hello all, I am a strong believer in "say it once," and I find Polymorph's lists, and especially trees, very cumbersome to use. One is led to create a slot to hold selections and accessors. That work should be done by by a reusable presenter with some help from ListModel and TreeModel. Attached is the current state (of confusion) of the framework. The factory concept (presenters create morph-model pairs, the views are all morphs) is new, in some sense a concession to reality. I would prefer other layout means (see the various "obsolete" parts of the package), but have not been able to make them work. Using polymorph rows and columns, I can get close enough to what I need, at least with a suitable user base. The GUI is nothing special, but the way it is built is, I think, worthy of some attention. Try CartoonPersonalityBrowser new asMorph openInWorld. for a few laughs. For those not familiar with it, the Rocky and Bullwinkle Show was *not* for kids. Kids will enjoy it, but it was in fact beautiful cold-war satire. The road runner and coyote are more likely to be familiar to you, and are just good (great) slapstick with a few comments on life (everything works fine until the roadrunner appears...). The list and tree scream for a #selectionChanging: event, which I had not appreciated until I created the above example. In short, you can edit the fields, but they are not saved. Punching the presenters onto the tree elements would be a little tricky, but one should be able to know that the selection is changing, react to it (saving current contents) and then even veto the change. More work... Please comment freely. Bill

1 1

Re: [Pharo-project] Object>>deprecated:on:in: doesn't respect state of Deprecation class>>showWarning:
by Fernando Olivero March 19, 2012

March 19, 2012

Hi Martin, no objections! please create the issue, and attach the fix. Fernando On Mon, Mar 19, 2012 at 10:47 PM, Martin Sandiford <ms(a)mcdev.com.au> wrote: > Hi all, > > Kind of new to Pharo, so not sure if this is intended behaviour or > not, but "Object>>deprecated:on:in:" doesn't respect the current state > of the "Deprecation class>>showWarning" setting. > > This was unexpected for me --- in a headless setting the warning > dialog causes the VM to exit. > > To reproduce (in 1.4 14399): > > Deprecation showWarning: false. > true and: [ true ] and: [ true ]. "Boolean>>and:and: sends deprecated:on:in:" > > Fix seems straightforward: wrap the current contents of > "deprecated:on:in:" in "Deprecation showWarning ifTrue: [...]". > > If there are no objections, I'll raise a bug in the tracker. > > Cheers, > Martin >

2 1

[Pharo-project] "Browse class" : Nautilus class DNU #newOnClass:
by Alexis Parseghian March 19, 2012

March 19, 2012

Fix by implementing it and have it call Nautilus class>>openOnClass: http://code.google.com/p/pharo/issues/detail?id=5505

2 1

[Pharo-project] Pharo Kernel Reload Tests-Unix - Build # 20 - Still unstable!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr March 19, 2012

March 19, 2012

1 1