- Pharo-users - lists.pharo.org

Willow-Seaside serving static files
by TomaÅ¾ Turk June 17, 2020

June 17, 2020

Hi, I added an image to a subclass of WAFileLibrary to serve it as a static file from within Pharo. Everything seems fine, except that the /files URL is not accessible: Error: you are forbidden to access "/files". and source view displays /files/EMStaticFiles/window.png not found if I click on image's URL. I loaded Seaside as a Willow's dependency. Best wishes, Tomaz

2 3

Git repository add - commit files from Pharo
by Dario Romano Trussardi June 17, 2020

June 17, 2020

Ciao, it happens that i create files directly from Pharo in a git repository configure with Iceberg. Now it would be interesting to automate the registration of these files, for the next commit directly from Pharo. Tips ? Thanks, Dario P.S. known that the commit from pharo, does not consider the files added ( by the shell ) to the local repository with git add â¦.. command.

2 1

TypingVisitor window opens while editing a source
by Richard Van de Moosdijk/G June 17, 2020

June 17, 2020

Hi, Since a few days Pharo opens a Â« TypingVisitor Â» window each time i try to edit a method (every one or two characters). It looks like a debug breakpoint: How can i get rid of this? Thank you for help. Richard

4 3

Fwd: [Pharo-dev] Fwd: Help Needed! Survey on developer knowledge of Breakpoints/Watchpoints
by Steven Costiou June 17, 2020

June 17, 2020

Hello, I did not see this email go through the Pharo users mailing list, so just in case: -------- Courriel original -------- OBJET: [Pharo-dev] Fwd: Help Needed! Survey on developer knowledge of Breakpoints/Watchpoints DATE: 2020-06-10 15:40 DE: Thomas Dupriez <tdupriez(a)ens-paris-saclay.fr> Ã: pharo-dev(a)lists.pharo.org RÃPONDRE Ã: Pharo Development List <pharo-dev(a)lists.pharo.org> Hi all, As part of a research work on watchpoints, we are setting up a survey to gauge the general knowledge developers have on breakpoints/watchpoints. It should take around 10 minutes to complete. Here is the link to participate if you would be so kind: https://forms.gle/eK4HFvU1YNZZkiaHA If you are interested in the results, you can check the box at the end of the survey and we will send you feedback on the results of the survey. Additionally, we are going to set up a controlled experiment to evaluate the effectiveness of a new type of watchpoints we are developing for Pharo. The gist of it is that we will observe participants hunt some bugs, with and without the new tool, and see if their performance improve. So, if you know how to program in Pharo, and would be willing to participate, there is a question in the survey to tell us you are interested. We will get research data, and you will get a new debugging tool in Pharo. So it's a win-win. That's it! Thanks for your time! And extra thanks if you take the survey or consider participating in the experiment! Thomas Dupriez This research work is conducted by: - Eduardo A. Fontana, UniversitÃ© du QuÃ©bec Ã Chicoutimi, Canada. - Thomas Dupriez, Univ. Lille, France. And is supervised by: - Fabio Petrillo, UniversitÃ© du QuÃ©bec Ã Chicoutimi, Chicoutimi, QuÃ©bec, Canada. - Steven Costiou, Inria Lille, France. - YANN-GAÃL GUÃHÃNEUC, Concordia University, Montreal, Quebec, Canada. - STÃPHANE DUCASSE, Inria Lille, France.

1 0

Re: [Pharo-users] Pharo 8.0 bug
by ducasse June 14, 2020

June 14, 2020

Thanks Sebastian We are now since a couple of years managing Pharo via github. I can do a Pull Request with you changes. Now it may be a good occasion for you to practice. Let me know if you want to try by yourself. https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo <https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo> S.

1 0

Re: [Pharo-users] Pharo 8.0 bug
by Ben Coman June 14, 2020

June 14, 2020

hi Sebastian, Thanks for taking the time to report your issue. Note that Fogbugz is no longer used for issue tracking. Issues are now tracked at... https://github.com/pharo-project/pharo/issues Could you try creating your issue there? cheers -ben On Sun, 14 Jun 2020 at 13:35, Sebastian Heidbrink via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Hello, > > I am unfortunately not able to register at https://pharo.fogbugz.com/ > because "/issues-register-service not found". > > This is why I post the following bug here: > > I attached a test case and how that somebody can recreate it. > > I just downloaded a Pharo 8.0 64Bit image with the pharolauncher to a > Windows 10 machine. > > Depending on my actions within the dev environment the test case passes > or fails in the last two asserts. > > What one has to do is just run the test and see if it fails the first time. > > If it does not fail then: > > 1. Remove the comment in the test method. > > 2. Within the System Browser navigate to the ValueHolderTestClass and > back to ValueHolderTestCase again. > > 3. Rerun the test > > With a little back and forth you will eventually see the last asserts > fails with > > "TestFailure: Got '13' instead for 'Test3' " > > > It would be highly appreciated if somebody with access to > pharo.fogbugz.com would find the time to try this and upload the > information provided. > > > Here the full info about the image: > Pharo 8.0.0 > Build information: > Pharo-8.0.0+build.1124.sha.0932da82f08175e906b0e2a8052120c823374e9f (64 > Bit) > > > Thank you! > > Cheers! > > Sebastian > > >

2 1

Pharo 8.0 bug
by Sebastian Heidbrink June 14, 2020

June 14, 2020

Hello, I am unfortunately not able to register at https://pharo.fogbugz.com/ because "/issues-register-service not found". This is why I post the following bug here: I attached a test case and how that somebody can recreate it. I just downloaded a Pharo 8.0 64Bit image with the pharolauncher to a Windows 10 machine. Depending on my actions within the dev environment the test case passes or fails in the last two asserts. What one has to do is just run the test and see if it fails the first time. If it does not fail then: 1. Remove the comment in the test method. 2. Within the System Browser navigate to the ValueHolderTestClass and back to ValueHolderTestCase again. 3. Rerun the test With a little back and forth you will eventually see the last asserts fails with "TestFailure: Got '13' instead for 'Test3' " It would be highly appreciated if somebody with access to pharo.fogbugz.com would find the time to try this and upload the information provided. Here the full info about the image: Pharo 8.0.0 Build information: Pharo-8.0.0+build.1124.sha.0932da82f08175e906b0e2a8052120c823374e9f (64 Bit) Thank you! Cheers! Sebastian

2 1

[ANN] Willow-Auth0 v1.0.0 [v1.0.0] released!
by Buenos Aires Smalltalk June 12, 2020

June 12, 2020

1 0

HOPL-4 papers
by Rafael Luque June 12, 2020

June 12, 2020

Hi all, Not strictly related with Pharo, but I think it could be interesting to any Smalltalker. ACM has just published the History of Programming Languages 4. The papers cover the following languages: APL, C++, Closure, Fortran parallelism, D, Emacs Lisp, F#, Groovy, Hygienic Macros (Scheme), JavaScript, LabVIEW, Logo. MATLAB, Objective-C, Oz, R, ML, Verilog and Smalltalk. The paper dedicated to Smalltalk is "The evolution of Smalltalk: from Smalltalk-72 through Squeak" by Dan Ingalls. All the papers are available to download here: https://dl.acm.org/toc/pacmpl/2020/4/HOPL Rafael Luque

1 0

Monticello Bug introduced in Pharo 8
by Peter Newton June 11, 2020

June 11, 2020

Hi. I'm a Smalltalk newcomer, slowly exploring Pharo to understand its potential and in the process I've found and fixed what seems to be a bug in Metacello (although it could be more widespread). So what now, how to best report the bug and my fix? To reproduce the bug, in Pharo 8 or 9, simply chose 'Save' from the Monticello browser when a repository is selected and edit either the version name or the log message, you should see the error "/MCSaveVersionDialog doesn't understand #selectedClassOrMetaClass/". As far as I can tell, Pharo 8 introduced the idea of a CompletionEngine for Smalltalk text areas that sends /#selectedClassOrMetaClass/ to the text area. This method is implemented in descendants of MCCodeTool but doesn't exist in the parent MCTool - which is what MCSaveVersionDialog derives from. My fix reworks /MCTool>>textMorph:/ to allow the version dialog text areas to be constructed with the message #beForSmalltalkComment rather than #beForSmalltalkScripting. This works, but I have no idea if this is the best way, how to share my fix, or how to raise this as a bug with the Pharo maintainers to make Pharo a more stable platform. All advice is most welcome. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

3 3