January 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Shortcut for programmatically executing a class side method ?

by Gabriel Cotelli

String perform: #method On Sun, Jan 13, 2019, 18:42 Sven Van Caekenberghe <sven(a)stfx.eu wrote: > Hi, > > Does there exist a shortcut for programmatically executing a class side > method ? > > For example, > > String class>>#loremIpsum in: [ :method | > method methodClass instanceSide perform: method selector ]. > > I was looking for a shortcut, like #eval, #execute, #value or something > like that. > > (String class>>#loremIpsum) eval. > > Sven >

Jan. 13, 2019

Re: [Pharo-dev] Shortcut for programmatically executing a class side method ?

by Nicolas Cellier

Normally, primitive 188 and 189 execute a method (the receiver is the method receiver). Maybe search for senders... Le dim. 13 janv. 2019 Ã 22:42, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : > Hi, > > Does there exist a shortcut for programmatically executing a class side > method ? > > For example, > > String class>>#loremIpsum in: [ :method | > method methodClass instanceSide perform: method selector ]. > > I was looking for a shortcut, like #eval, #execute, #value or something > like that. > > (String class>>#loremIpsum) eval. > > Sven >

Jan. 13, 2019

Shortcut for programmatically executing a class side method ?

by Sven Van Caekenberghe

Hi, Does there exist a shortcut for programmatically executing a class side method ? For example, String class>>#loremIpsum in: [ :method | method methodClass instanceSide perform: method selector ]. I was looking for a shortcut, like #eval, #execute, #value or something like that. (String class>>#loremIpsum) eval. Sven

Jan. 13, 2019

Re: [Pharo-dev] Development process: testing the GUI

by Nicolas Cellier

Sure, it will require more uniform API. Elm has an advantage with static typing, but I'm sure we can do without it. Maybe this should be integrated in the requirements/objectives of next frameworks. Le dim. 13 janv. 2019 Ã 10:53, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : > Hi, > > Wellâ¦ we âplanâ to have tests also on UI. > But this is hard. > And not just because of the tooling, but also because having a coherent > metaphor to organise everything is hard. > We are working (very slowly) in that direction. > And eventually, we would like to have also UI tests. > > Esteban > > > On 12 Jan 2019, at 23:34, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > > Hi all, > Pharo team is attaching great care in securing and improving the > development process, notably by promoting usage of tests and continuous > integration. > > I think a very good job is already done in the libraries provided by > Pharo. But sometimes I encounter more hickups with the development tools > themselves. > So I wonder: does this apply to the GUI yet? > This is a difficult area, but nowadays this exists elsewhere. > For example, with Elm and Elmer ( > https://medium.com/@brian.watkins/test-driving-elm-with-elmer-649e2e7e02a8) > TDD can be applied on UI, providing both a formal specification and non > regression tests. > Do we have something similar? > Don't we wish having something similar? > > >

Jan. 13, 2019

[Pharo 7.0] Build #121: 22885-Rename-Calypso-Queries-to-have-Query-suffix

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #121 was: SUCCESS. The Pull Request #2223 was integrated: "22885-Rename-Calypso-Queries-to-have-Query-suffix" Pull request url: https://github.com/pharo-project/pharo/pull/2223 Issue Url: https://pharo.fogbugz.com/f/cases/22885 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 13, 2019

Re: [Pharo-dev] Development process: testing the GUI

by Esteban Lorenzano

Hi, Wellâ¦ we âplanâ to have tests also on UI. But this is hard. And not just because of the tooling, but also because having a coherent metaphor to organise everything is hard. We are working (very slowly) in that direction. And eventually, we would like to have also UI tests. Esteban > On 12 Jan 2019, at 23:34, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > Hi all, > Pharo team is attaching great care in securing and improving the development process, notably by promoting usage of tests and continuous integration. > > I think a very good job is already done in the libraries provided by Pharo. But sometimes I encounter more hickups with the development tools themselves. > So I wonder: does this apply to the GUI yet? > This is a difficult area, but nowadays this exists elsewhere. > For example, with Elm and Elmer (https://medium.com/@brian.watkins/test-driving-elm-with-elmer-649e2e7e02a8 <https://medium.com/@brian.watkins/test-driving-elm-with-elmer-649e2e7e02a8>), TDD can be applied on UI, providing both a formal specification and non regression tests. > Do we have something similar? > Don't we wish having something similar?

Jan. 13, 2019

Development process: testing the GUI

by Nicolas Cellier

Hi all, Pharo team is attaching great care in securing and improving the development process, notably by promoting usage of tests and continuous integration. I think a very good job is already done in the libraries provided by Pharo. But sometimes I encounter more hickups with the development tools themselves. So I wonder: does this apply to the GUI yet? This is a difficult area, but nowadays this exists elsewhere. For example, with Elm and Elmer ( https://medium.com/@brian.watkins/test-driving-elm-with-elmer-649e2e7e02a8) TDD can be applied on UI, providing both a formal specification and non regression tests. Do we have something similar? Don't we wish having something similar?

Jan. 12, 2019

Re: [Pharo-dev] IceGitHubError API rate limit exceeded

by Paul DeBruicker

github allows 60 unauthenticated requests per hour per IP. IF you authenticate your requests you can make 5,000 per hour. If you don't want to wait an hour after hitting this error you should create a personal, no scope token following the instructions here: https://blog.github.com/2013-05-16-personal-api-tokens/ The no-scope token can only be used to read public repository information and cannot make any changes to any of your repos. You can use the token to authenticate your requests by setting your github username as the username and the token as the password in a HTTP basic authentication request to their servers. I know ZnClient has #username:password: and so guess that Iceberg has or can have a similar method. Dont share the token. bpi wrote > Hi, > > I followed these instructions for contributing to Pharo: > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo > > During Step 1 Repairing local repository missing I get the following > error: > IceGitHubError: API rate limit exceeded > > I retried with a new Pharo 7.0 - 64bit (development version) in Pharo > Launcher and got the same error. > > I searched the mailing list but did not find anything. Am I really the > only one who ever encountered this? Any tips? > > Cheers, > Bernhard -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Jan. 12, 2019

Re: [Pharo-dev] IceGitHubError API rate limit exceeded

by Sabine Manaa

Hi Bernhard, I did not go deep in it but this could be related or similar: -> https://github.com/pharo-vcs/iceberg#for-pharo-61 -> If you get a API rate limit exceeded error from github, like "Error accessing tags for github project: 'pharo-vcs/iceberg' -> 'API rate limit exceeded for...." then you can replace the metacello statement above with: Metacello new githubUser: 'pharo-vcs' project: 'Iceberg' commitish: 'v1.?' path: ''; baseline: 'Iceberg'; load. -> https://developer.github.com/v3/#rate-limiting regards Sabine Am Sa., 12. Jan. 2019 um 19:52 Uhr schrieb Bernhard Pieber < bernhard(a)pieber.com>: > > Hi, > > I followed these instructions for contributing to Pharo: > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo > > During Step 1 Repairing local repository missing I get the following error: > IceGitHubError: API rate limit exceeded > > I retried with a new Pharo 7.0 - 64bit (development version) in Pharo Launcher and got the same error. > > I searched the mailing list but did not find anything. Am I really the only one who ever encountered this? Any tips? > > Cheers, > Bernhard

Jan. 12, 2019

IceGitHubError API rate limit exceeded

by Bernhard Pieber

Hi, I followed these instructions for contributing to Pharo: https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo During Step 1 Repairing local repository missing I get the following error: IceGitHubError: API rate limit exceeded I retried with a new Pharo 7.0 - 64bit (development version) in Pharo Launcher and got the same error. I searched the mailing list but did not find anything. Am I really the only one who ever encountered this? Any tips? Cheers, Bernhard

Jan. 12, 2019