Re: [Pharo-users] About deprecation and unit testing
On 04 Dec 2013, at 08:57, Damien Cassou damien.cas...@gmail.com 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.fogbugz.com/f/cases/11423
Re: [Pharo-users] About deprecation and unit testing
On Wed, Dec 4, 2013 at 9:18 AM, Marcus Denker marcus.den...@inria.fr 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.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. Winston Churchill
Re: [Pharo-users] About deprecation and unit testing
On 04 Dec 2013, at 09:33, Damien Cassou damien.cas...@gmail.com wrote: On Wed, Dec 4, 2013 at 9:18 AM, Marcus Denker marcus.den...@inria.fr 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. 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. -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. Winston Churchill
Re: [Pharo-users] About deprecation and unit testing
On Wed, Dec 4, 2013 at 9:50 AM, Sven Van Caekenberghe s...@stfx.eu 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 #raiseWarning: is true, a test sending a deprecated message fails - when the preference #raiseWarning: is false, a test sending a deprecated message succeeds Implemented in: Name: SLICE-Issue-11423-Running-unit-tests-that-raise-deprecation-warnings-makes-them-fail-incomprehensibly-DamienCassou.1 Author: DamienCassou Time: 4 December 2013, 9:56:07.727774 am UUID: bc043b07-b57b-4b5c-b140-8805a4397d31 Ancestors: Dependencies: SUnit-Tests-DamienCassou.31, SUnit-Core-DamienCassou.107 - when the preference #raiseWarning: is true, a test sending a deprecated message fails - when the preference #raiseWarning: is false, a test sending a deprecated message succeeds -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. Winston Churchill
[Pharo-users] openFullscreen a WindowModel
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] openFullscreen a WindowModel
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 prova...@hotmail.it wrote: 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
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 that no class below Object redefines the method. Stephan
Re: [Pharo-users] About deprecation and unit testing
On 04 Dec 2013, at 11:47, Stephan Eggermont step...@stack.nl 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 images) fail silently. In Slice 12324 I added a test checking that no class below Object redefines the method. this is true for all meta kind of selectors… e.g. #layout… (there is an issue related to that) Marcus
Re: [Pharo-users] command line command from pharo image
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 thisOSProcess You can remove the send of #thisOSProcess and it will still work. Also, if you don't care about output, you can use NB without installing anything. In Pharo 3.0, it works on Windows, will work on Mac with Igor's latest changes... not sure about Linux... HTH Cheers, Sean -- If you reply to this email, your message will be added to the discussion below: http://forum.world.st/command-line-command-from-pharo-image-tp4727022p4727098.html To start a new topic under Pharo Smalltalk Users, email ml-node+s1294792n1310670...@n4.nabble.com To unsubscribe from command line command from pharo image, click herehttp://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=4727022code=c2FiaW5lLmtub2VmZWxAZ21haWwuY29tfDQ3MjcwMjJ8MTA0OTM5MTYx . NAMLhttp://forum.world.st/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://forum.world.st/command-line-command-from-pharo-image-tp4727022p4727311.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Re: [Pharo-users] About deprecation and unit testing
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 that no class below Object redefines the method. I do not think that it can be correct because ClassDecription defines it and it is under Object
Re: [Pharo-users] About deprecation and unit testing
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]) isEmpty. It found the 5 (not 4, I missed one) extra implementations. Stephan
[Pharo-users] Lectures at Prague
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 30 alpha. More importantly I will give an overview of all the partners and shows that Pharo is composed of a really strong community of academic partners, research groups and companies. In addition I will stress that Pharo is YOUR open-source platform and that if you start to consider it as it then suddenly you realise that you want to improve it and that you can get an impact and influence Pharo's future and your future. I will finish by an key example showing the essence of object-oriented programming and prove to the audience that this is because of such example that Pharo is one of the best system to understand deeply object-oriented programming from its roots. Bio: Stephane leads the RMoD (http://rmod.lille.inria.fr) team. He is expert in two domains: object-oriented language design and reengineering. He worked on traits, composable groups of methods, and this work got some impact. Traits have been introduced in AmbiantTalk, and Squeak/Pharo, Perl, PHP and under a variant into Scala, Fortress of SUN Microsystems. He is one of the developer of Pharo http://www.pharo.org/ a new dynamic language used in industry and academia. He is also expert on software quality, program understanding, program visualizations, reengineering and metamodeling. He is one of the developer of Moose, an open-source software analysis platform http://www.moosetechnology.org/. He is working with http://www.synectique.eu/ a company building dedicated tools for advanced software analysis. He wrote several books: Pharo by Example and Deep into Pharo. He is president of ESUG http://www.esug.org Lecture: Prague Monday 9 December at The lecture starts at 4:15pm in the new Czech National Technical Library There will be a workshop wednesday / thursday afternoon Stef
