[Pharo-users] Lectures at Prague

2013-12-04 Thread Stéphane Ducasse
Alive and Kicking This presentation will discuss some successes stories around Smalltalk such AMD 64 bits, OOCL (http://www.oocl.com/), MediaGenix (www.mediagenix.tv), LAMRC (http://www.lamrc.com), netstyle.ch or yesplan.be. Then I will talk about Pharo and the recent advances in Pharo 20 and 3

Re: [Pharo-users] About deprecation and unit testing

2013-12-04 Thread Stephan Eggermont
Stef wrote >I do not think that it can be correct because ClassDecription defines it and >it is under Object I wasn’t precise enough. This is the current test. self assert: (Object allSubclasses select: [: each | (each class compiledMethodAt: #packages ifAbsent: [nil]) isNotNil]) isEmp

Re: [Pharo-users] About deprecation and unit testing

2013-12-04 Thread Stéphane Ducasse
> A related issue is the enforcing of protocol. Currently, the RPackage > implementation > doesn’t allow other class-side definitions of #packages. There was no test > for that, > so all images with Grease loaded (all Moose & Seaside based images) fail > silently. > In Slice 12324 I added a te

Re: [Pharo-users] command line command from pharo image

2013-12-04 Thread Sabine Knöfel
Hi Sean, thanks. I need it now, on Pharo 2.0 but I will change it when I move to 3.0. Which is the Class and the message in NB then? Sabine On Tue, Dec 3, 2013 at 5:40 PM, Sean P. DeNigris [via Smalltalk] < ml-node+s1294792n4727098...@n4.nabble.com> wrote: > Sabine Knöfel wrote > OSProcess

Re: [Pharo-users] About deprecation and unit testing

2013-12-04 Thread Marcus Denker
On 04 Dec 2013, at 11:47, Stephan Eggermont wrote: > A related issue is the enforcing of protocol. Currently, the RPackage > implementation > doesn’t allow other class-side definitions of #packages. There was no test > for that, > so all images with Grease loaded (all Moose & Seaside based ima

Re: [Pharo-users] About deprecation and unit testing

2013-12-04 Thread Stephan Eggermont
A related issue is the enforcing of protocol. Currently, the RPackage implementation doesn’t allow other class-side definitions of #packages. There was no test for that, so all images with Grease loaded (all Moose & Seaside based images) fail silently. In Slice 12324 I added a test checking tha

Re: [Pharo-users] openFullscreen a WindowModel

2013-12-04 Thread Benjamin
Add: WindowModel>>#openFullscreen self changed: #openFullscreen with: #() MorphicWindowAdapter>>#openFullscreen self widgetDo: [ :w | w openFullscreen ] And tada Ben On 04 Dec 2013, at 11:13, Picci Pharo wrote: > Hi Guys! > > One simple question: how can i open fullscreen

[Pharo-users] openFullscreen a WindowModel

2013-12-04 Thread Picci Pharo
Hi Guys! One simple question: how can i open fullscreen a WindowModel? As you know, the StandardWindow has got the message "openFullscreen", but it obviously doesn't work for the WindowModel.Any suggestion? Ciao!Paolo

Re: [Pharo-users] About deprecation and unit testing

2013-12-04 Thread Sven Van Caekenberghe
On 04 Dec 2013, at 09:56, Damien Cassou wrote: > On Wed, Dec 4, 2013 at 9:50 AM, Sven Van Caekenberghe wrote: >> No, I wouldn’t do that by default: that would defeat the whole purpose of >> deprecation. If you want to ignore deprecations, you should do it yourself >> in your own tests, at you

Re: [Pharo-users] About deprecation and unit testing

2013-12-04 Thread Damien Cassou
On Wed, Dec 4, 2013 at 9:50 AM, Sven Van Caekenberghe wrote: > No, I wouldn’t do that by default: that would defeat the whole purpose of > deprecation. If you want to ignore deprecations, you should do it yourself in > your own tests, at your own risk, IMHO. what about: - when the preference

Re: [Pharo-users] About deprecation and unit testing

2013-12-04 Thread Sven Van Caekenberghe
On 04 Dec 2013, at 09:33, Damien Cassou wrote: > On Wed, Dec 4, 2013 at 9:18 AM, Marcus Denker wrote: >> There is a related bug tracker entry: > > > I will try to propose a slice that ignores deprecation warnings while > running the tests. But this will make it harder for people to find > dep

Re: [Pharo-users] About deprecation and unit testing

2013-12-04 Thread Luc Fabresse
Hi All, I think that trapping Deprecations silently is not a good idea. As you said, people will not see them and it will be hard to upgrade code. Why not having a Preference? or another button in the TestRunner such as: "Run ignoring Deprecation"? #Luc 2013/12/4 Damien Cassou > On Wed,

Re: [Pharo-users] About deprecation and unit testing

2013-12-04 Thread Damien Cassou
On Wed, Dec 4, 2013 at 9:18 AM, Marcus Denker wrote: > There is a related bug tracker entry: I will try to propose a slice that ignores deprecation warnings while running the tests. But this will make it harder for people to find deprecated message sends. -- Damien Cassou http://damiencassou.s

Re: [Pharo-users] About deprecation and unit testing

2013-12-04 Thread Sven Van Caekenberghe
You could do: [ 'foobar' asFileReference ensureDeleted ] on: Deprecation do: [ :exception | exception resume ] On 04 Dec 2013, at 08:57, Damien Cassou wrote: > http://stackoverflow.com/questions/20369972/about-deprecation-and-unit-testing-in-pharo > > -- > Damien Cassou > http://damienc

Re: [Pharo-users] About deprecation and unit testing

2013-12-04 Thread Marcus Denker
On 04 Dec 2013, at 08:57, Damien Cassou wrote: > http://stackoverflow.com/questions/20369972/about-deprecation-and-unit-testing-in-pharo > There is a related bug tracker entry: 11423 Running unit tests that raise deprecation warnings makes them fail incomprehensibly https://pharo.fog