Pharo success in in the website, twitter and youtube channel.
Popularity wise the clear indication is community, I joined Pharo back in
2011 when it was already 3 years old and we had only one active mailing
list , pharo-dev, pharo-users were practically unused. Then we got so many
new people we
--- Begin Message ---
Congrat Cedric for your position!
Alexandre
> On Jul 4, 2018, at 1:33 PM, Cédrick Béler wrote:
>
> First of all, thanks for the introduction Marcus.
>
> Just that people know, and to introduce myself, I’m Cédrik Béler, associate
> professor at ENIT (Nation Engineering S
Thanks, Kilon for such an insightful answer. Lots of stuff to think about.
I guess what I was waiting for is some success stories (which we already
have on the website), but coming from you guys as consultants saying
something like: "oh, this year I have more projects than last year" or "now
my net
You can check the github repos, github allows you to browse project repos per
language. You could probably automate that from Pharo, use the Github API
like Iceberg does fetch the names of all projects using smalltalk language
and check to see which ones have commits the last year and then make a n
Another solution is to clone the wiki, it offers its github link and then
make a new repo for the wiki alone and upload the files which are regular md
files (github markdown). The good news is that you wont be losing any of the
conveniences because github offers a markdown editor with live previews
1. https://github.com/ba-st/Buoy 185 tests
2. https://github.com/ba-st/RenoirSt 306 tests
3. https://github.com/ba-st/Willow 501 tests
4. https://travis-ci.org/ba-st/HighchartsSt 46833 tests
5. https://github.com/ba-st/Willow-Bootstrap 441 tests
6. https://github.com/ba-st/Aconcag
On Thu, Jul 5, 2018 at 3:24 PM Julien wrote:
> Hello Pharo community,
>
> I am currently working on detecting rotten tests in Pharo projects.
>
> Rotten tests are defined as test methods containing one or many assertions
> in their source code but one or many of these assertions are not executed
Hello Pharo community,
I am currently working on detecting rotten tests in Pharo projects.
Rotten tests are defined as test methods containing one or many assertions in
their source code but one or many of these assertions are not executed when the
test is run.
To have more details on the subje
Hi Hernán,
On Wed, Jul 4, 2018 at 7:57 PM Hernán Morales Durand <
hernan.mora...@gmail.com> wrote:
> I wonder if anyone could help here. I am installing a BaselineOf in
> Pharo 6.1 (Windows)
Unfortunately this version of Iceberg is too old... I'd go with what
Esteban describes and try to see if
Hi Hernan,
Pharo 6.1 has a very old version of iceberg that is obsoleted by current
development. Nevertheless this error seems to indicate the download failed and
sources are not present (this could be an “accumulative error”: the error could
have happen before and now, since Iceberg looks for
> On 5 Jul 2018, at 09:40, Guillermo Polito wrote:
>
> Hi Dario,
>
> Have you defined those methods in the class side?
>
> a) propertyAt: aKey ifAbsent: aBlock
>^ self properties at: aKey ifAbsent: aBlock
> b) propertyAt: aKey ifAbsentPut: aBlock
>^
Hi Dario,
Have you defined those methods in the class side?
a) propertyAt: aKey ifAbsent: aBlock
>^ self properties at: aKey ifAbsent: aBlock
> b) propertyAt: aKey ifAbsentPut: aBlock
>^ self properties at: aKey ifAbsentPut: aBlock
> c) propertyAt
12 matches
Mail list logo
