- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] TDD and BDD

by stepharo

>> refactor so that all those places use one implementation somewhere. > In fact, searching the sources for "beginsWith: 'test'", the logic is > duplicated quite a bit. So we should refactor it. > And someone even snuck your proposed change into > CompiledMethod>>#isTestMethod, so now we already have two conflicting > concepts of what a test selector is in Core. > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/TDD-and-BDD-tp4820612p4820673.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

April 20, 2015

Re: [Pharo-dev] Phaor 50: updating Metacello

by Dale Henrichs

Stef, While in development you should be doing builds with the most recent version on the github master branch ... that way if you hit problems and Christophe or I have bugfixes along the way, those fixes will be folded into the latest build ... I will add Pharo5.0 to my travis testing lineup shortly ... Dale On 04/20/2015 12:10 AM, stepharo wrote: > Hi > > I think that we should update metacello so that we get rid of problem > with Configuration not updated in the image. > > Stef >

April 20, 2015

Re: [Pharo-dev] TDD and BDD

by Sean P. DeNigris

Sean P. DeNigris wrote > refactor so that all those places use one implementation somewhere. In fact, searching the sources for "beginsWith: 'test'", the logic is duplicated quite a bit. And someone even snuck your proposed change into CompiledMethod>>#isTestMethod, so now we already have two conflicting concepts of what a test selector is in Core. ----- Cheers, Sean -- View this message in context: http://forum.world.st/TDD-and-BDD-tp4820612p4820673.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 20, 2015

Re: [Pharo-dev] TDD and BDD

by Sean P. DeNigris

demarey wrote > as it is something that is not specific to a project, I would prefer to > have it in the system. I agree that would be nice. I much prefer #shouldXyz. At the same time I don't mind so much having to override #testSelectors, and if we make this change, we must be ready for people to use it in Core, which IMHO might lead to better tests, but will clash a bit with current style. BTW if you have to change it in several places, the first step, whether we change the logic or not, would be to refactor so that all those places use one implementation somewhere. ----- Cheers, Sean -- View this message in context: http://forum.world.st/TDD-and-BDD-tp4820612p4820672.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 20, 2015

Re: [Pharo-dev] Roadmap

by Dmitri Zagidulin

I would love to see two things in Pharo 5: 1) Fix for mouse scrolling (at least on Mac OS X, though I think it does the same on Linux etc) in the class pane. While mouse-scrolling (either via a mouse wheel or two-finger scrolling on the touchpad) through the classes, the focus frequently and erratically jumps to the package pane, and the package pane starts scrolling instead. The focus also sometimes jumps when you reach the end of the class list (and, again, the package pane starts scrolling instead). 2) A button in the debugger that copies the error message to the clipboard (you can sort of do it currently by editing the title of the error window, but that's really awkward). I also have a question. Are there currently any roadmap plans for namespaces or modules for Pharo? I saw a brief discussion about it a few years back (http://forum.world.st/Pharo-and-Namespaces-td4636635.html ), and wanted to see if it's still on the table. On Mon, Apr 20, 2015 at 2:58 AM, stepharo <stepharo(a)free.fr> wrote: > Hi > > if you have suggestions please let us know. Now usually suggestions often > comes with time allocation ;) > We have definitively a list of points we want to see addressed. > > Stef > > Le 19/4/15 23:19, Torsten Bergmann a Ã©crit : > > Do we have a roadmap for Pharo 5 already? >> >> >> >> > >

April 20, 2015

Bug in SmalltalkHub?

by Jan Vrany

Hi, (Esteban), I'm trying to upload couple .mcz to Smalltalk hub using following script: ==== for f in $(cd mc && ls *.mcz); do echo -n "Uploading $f..." curl --user JanVrany:<my password here> --upload-file mc/$f http://smalltalkhub.com/mc/JanVrany/CalipeL-S/main/$f; echo done === and I'm getting following output: === Uploading CalipeL-S-Benchmarks-Game-JanVrany.ee1fd4a6e836.20150420125300.mcz...receiver of "asTimeStamp" is nil Uploading CalipeL-S-Benchmarks-Micro-JanVrany.ee1fd4a6e836.20150420125300.mcz...receiver of "asTimeStamp" is nil Uploading CalipeL-S-Core-JanVrany.ee1fd4a6e836.20150420125300.mcz...receiver of "asTimeStamp" is nil Uploading CalipeL-S-Tests-JanVrany.ee1fd4a6e836.20150420125300.mcz...receiver of "asTimeStamp" is nil === The .mcz load into Pharo image just fine. The last time I did this was Dec 2014 and it worked like a charm. Is it a bug? If not, how can I upload a new .mcz to SmalltalkHub? I can provide .mczs for debugging. Best, Jan

April 20, 2015

Re: [Pharo-dev] TDD and BDD

by Christophe Demarey

Yes, I could but as it is something that is not specific to a project, I would prefer to have it in the system. Le 20 avr. 2015 Ã 12:47, Sven Van Caekenberghe a Ã©crit : > You could override TestCase class>>#testSelectors in your own subclass, no ? > >> On 20 Apr 2015, at 12:02, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: >> >> Hi, >> >> With BDD a current test practice is to start method names with 'should'. >> It is not yet possible in Pharo but easily do-able (update of TestCase and some Nautilus methods). >> I would like that Pharo detects tes methods all methods of a class subclassing (directly or not) TestCase AND starting with either 'test' or 'should'. >> I also would like to add 'deny' to not use 'shouldNot' but here I'm not sure. >> >> WDYT? >> >> Christophe. > >

April 20, 2015

Re: [Pharo-dev] Is there a way to understand why rubric (playground) does not highlight code?

by Peter UhnÃ¡k

This also happened to me several times when executing (do it and go) some Roassal example with error (=it opened debugger). However the occurrence is very inconsistent so I don't know what was the trigger. Peter On Mon, Apr 20, 2015 at 1:29 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > This was just an example. The question is how do I identify what is > blocking the highlighting. > > Uko > > > On 20 Apr 2015, at 12:19, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi > > Maybe highlighting is running in process with lesser priority than default > priority of #fork method. > > Code like "[ [ true ] whileTrue: [ ] ] fork" will block any processes > with lesser priority > > > 2015-04-20 12:51 GMT+03:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > >> Open a new pharo image (Iâve used latest 5, but on 4 it should work as >> well). Open playground and execute: >> >> [ [ true ] whileTrue: [ ] ] fork >> >> now open a new playground and start typing. Characters are invisible. >> Uko >> >> On 20 Apr 2015, at 11:14, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> I did not see this before. Could you reproduce the issue? >> >> Cheers, >> Doru >> >> >> On Mon, Apr 20, 2015 at 11:03 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >> wrote: >> >>> Hi. >>> >>> Sometimes it happens that playground does not do the syntax >>> highlighting. This is especially frustrating when you open a new window and >>> text is either white or transparent i.e. you cannot see what you are typing. >>> >>> I guess this is because some process is blocked by another one. Is there >>> a way to check it? Because I want to understand whether it is because of >>> me, or not. >>> >>> Cheers! >>> Uko >>> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> >> > >

April 20, 2015

Re: [Pharo-dev] PetitMarkdown

by Damien Cassou

Dmitri Zagidulin <dmitri(a)zagidulin.net> writes: > Is this an issue of the version of Pillar that the book's build tools are > using? I thought I implemented that but you are right, it is not implemented. If you are lucky, Cyril will see this thread and fix it (hint, it's in PRLaTeXWriter>>writeEmbeddedPicture:). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 20, 2015

Re: [Pharo-dev] [Pharo-users] [ANN] ArchLinux pharo-vm / pharo-launcher packages

by Damien Cassou

Laurent <laurent.laffont(a)gmail.com> writes: > Yep, I'm not member of github group "pharo-project", it would be nicer > to have a pharo-arch project (like > https://github.com/pharo-project/pharo-ubuntu ) to host these files. > Feel free to create it and give me access I will use this new project > as main repo. what is your github login? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 20, 2015