[Pharo-dev] Re: Please check older Issue tracker entries!

[serge . stinckwich]

Thank you Marcus for your effort to engage more people from the community on 
managing the issue tracker entries more efficiently 
Regards,

Sent from my iPhone

> On 18 May 2022, at 14:50, Marcus Denker  wrote:
> 
> Hi,
> 
> One problem with a public issue tracker: it accumulates lots of issues…
> 
> This sadly means that issues will not be looked at one by one… there are
> just too many.
> 
> One thing that is interesting to do is to check the issue that *you* 
> submitted.
> 
>- Is the issue still relevant?
>- is the title good and in sync with the issue?
>- Has it been fixed already ? (it happens!)
> 
> Then, for every issue there is a “next step”. It can be a good thing to spell 
> out
> very explicitly what the next step is “We need to create a Pull Request for 
> the
> suggested fix”.
> 
> Or maybe what is needed is a  summary of the huge discussion in the
> issue tracker entry.
> 
> Another idea: try to find others to help. E.g. 
>
>- send a mail to the mailinglist. 
>- ask on discord.
> 
> Maybe you can find a small group that works on this issue together.
> 
> 
> 
>Marcus
>
> 
> 

[Pharo-dev] Re: [ANN] Pharo 10 released!

[Serge Stinckwich]

You can look at the change, I have done here:

https://github.com/KendrickOrg/kendrick/commit/1fe47c7cb4eebd1a676ffea186c2b6bdef86e3f2

Regards,

On Wed, 6 Apr 2022 at 11:21, o lu  wrote:

> On 4/5/22 21:06, Serge Stinckwich wrote:
>
> Sorry, my fault ... forget to add a baseline for Pharo10.
>
> I'm learning: tell me how you did this.
>
> Again congratulations on all the work done for this new release!
>
> Regards,
>
> On Wed, 6 Apr 2022 at 08:42, Serge Stinckwich 
> wrote:
>
>> Dear all,
>>
>> congratulations on the new release ! Nice to see smaller iterations for
>> the release.
>>
>> I try to load one of my packages with:
>>
>> Metacello new
>> repository: 'github://KendrickOrg/kendrick';
>> baseline: 'Kendrick';
>> onWarningLog ;
>> load
>>
>>
>> Was loading without any issue on Pharo 9 and now in Pharo 10 there is an 
>> error:
>>
>> Error: Name not found: Kendrick
>>
>> Something changed in package loading?
>>
>> Regards,
>>
>> --
> Serge Stinckwic
> ​h​
> https://twitter.com/SergeStinckwich
> ​
>
>
>

-- 
Serge Stinckwic
​h​
https://twitter.com/SergeStinckwich
​

[Pharo-dev] Re: [ANN] Pharo 10 released!

[Serge Stinckwich]

Sorry, my fault ... forget to add a baseline for Pharo10.


Again congratulations on all the work done for this new release!

Regards,

On Wed, 6 Apr 2022 at 08:42, Serge Stinckwich 
wrote:

> Dear all,
>
> congratulations on the new release ! Nice to see smaller iterations for
> the release.
>
> I try to load one of my packages with:
>
> Metacello new
> repository: 'github://KendrickOrg/kendrick';
> baseline: 'Kendrick';
> onWarningLog ;
> load
>
> Was loading without any issue on Pharo 9 and now in Pharo 10 there is an 
> error:
>
> Error: Name not found: Kendrick
>
> Something changed in package loading?
>
> Regards,
>
>
> On Tue, 5 Apr 2022 at 18:40, Esteban Lorenzano  wrote:
>
>> Dear Pharo users and dynamic language lovers:
>>
>> We have released Pharo version 10 <https://pharo.org/> !
>>
>> Pharo is a pure object-oriented programming language and a powerful
>> environment, focused on simplicity and immediate feedback.
>>
>>
>> Pharo 10 was a short iteration where we focused mainly on stability and
>> enhancement of the environment :
>>
>>
>>- Massive system cleanup
>>-
>>   - gained speed
>>   - removed dead code
>>   - removed old/deprecated frameworks (Glamour, GTTools, Spec1)
>>   - All Remaining tools written using the deprecated frameworks have
>>been rewritten: Dependency Analyser, Critique Browser, and many other 
>> small
>>utilities.
>>- Modularisation has made a leap, creating correct baselines (project
>>descriptions) for many internal systems, making possible the work and
>>deployment of minimal images.
>>- Removing support for the old Bytecode sets and embedded blocks
>>simplified the compiler and language core.
>>- As a result, our image size has been reduced by 10% (from 66MB to
>>58MB)
>>- The VM has also improved in several areas: better async I/O
>>support, socket handling, FFI ABI,
>>
>> Even being a short iteration, we have closed a massive amount of issues:
>> around 600 issues and 700 pull requests. A more extended changelog can be
>> found at
>> https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo100ChangeLogs.md
>> .
>>
>> While the technical improvements are significant, still the most
>> impressive fact is that the new code that got in the main Pharo 10 image
>> was contributed by more than 80 people.
>>
>> Pharo is more than code. It is an exciting project involving a great
>> community.
>>
>> We thank all the contributors to this release:
>>
>> Aaron Bieber, Ackerley Tng, Alban Benmouffek, Alejandra Cossio, Aless
>> Hosry, Alexandre Bergel, Aliaksei Syrel, Alistair Grant, Arturo Zambrano,
>> Asbathou Biyalou-Sama, Axel Marlard, Bastien Degardins, Ben Coman, Bernardo
>> Contreras, Bernhard Pieber, Carlo Teixeira, Carlos Lopez, Carolina
>> Hernandez, Christophe Demarey, Clotilde Toullec, Connor Skennerton, Cyril
>> Ferlicot, Dave Mason, David Wickes, Denis Kudriashov, Eric Gade, Erik Stel,
>> Esteban Lorenzano, Evelyn Cusi Lopez, Ezequiel R. Aguerre, Gabriel Omar
>> Cotelli, Geraldine Galindo, Giovanni Corriga, Guille Polito, Himanshu, Jan
>> Bliznicenko, Jaromir Matas, Kasper Østerbye, Kausthub Thekke Madathil,
>> Konrad Hinsen, Kurt Kilpela, Luz Paz, Marco Rimoldi, Marcus Denker, Martín
>> Dias, Massimo Nocentini, Max Leske, Maximilian-ignacio Willembrinck
>> Santander, Miguel Campero, Milton Mamani Torres, Nahuel Palumbo, Norbert
>> Hartl, Norm Green, Nour Djihan, Noury Bouraqadi, Oleksandr Zaitsev, Pablo
>> Sánchez Rodríguez, Pablo Tesone, Pavel Krivanek, Pierre Misse-Chanabier,
>> Quentin Ducasse, Raffaello Giulietti, Rakshit, Renaud de Villemeur, Rob
>> Sayers, Roland Bernard, Ronie Salgado, Santiago Bragagnolo, Sean DeNigris,
>> Sebastian Jordan Montt, Soufyane Labsari, Stephan Eggermont, Steven
>> Costiou, Stéphane Ducasse, Sven Van Caekenberghe, Theo Rogliano, Thomas
>> Dupriez, Théo Lanord, Torsten Bergmann, Vincent Blondeau.
>>
>>
>> (If you contributed to Pharo 10 development in any way and we missed your
>> name, please send us an email and we will add you).
>>
>> Enjoy!
>>
>> The Pharo Team
>>
>> Discover Pharo: https://pharo.org/features
>>
>> Try Pharo: http://pharo.org/download <https://pharo.org/download>
>>
>> Learn Pharo: http://pharo.org/documentation
>> <https://pharo.org/documentation>
>>
>
>
> --
> Serge Stinckwic
> ​h​
> https://twitter.com/SergeStinckwich
> ​
>


-- 
Serge Stinckwic
​h​
https://twitter.com/SergeStinckwich
​

[Pharo-dev] Re: [ANN] Pharo 10 released!

[Serge Stinckwich]

Dear all,

congratulations on the new release ! Nice to see smaller iterations for the
release.

I try to load one of my packages with:

Metacello new
repository: 'github://KendrickOrg/kendrick';
baseline: 'Kendrick';
onWarningLog ;
load

Was loading without any issue on Pharo 9 and now in Pharo 10 there is an error:

Error: Name not found: Kendrick

Something changed in package loading?

Regards,


On Tue, 5 Apr 2022 at 18:40, Esteban Lorenzano  wrote:

> Dear Pharo users and dynamic language lovers:
>
> We have released Pharo version 10  !
>
> Pharo is a pure object-oriented programming language and a powerful
> environment, focused on simplicity and immediate feedback.
>
>
> Pharo 10 was a short iteration where we focused mainly on stability and
> enhancement of the environment :
>
>
>- Massive system cleanup
>-
>   - gained speed
>   - removed dead code
>   - removed old/deprecated frameworks (Glamour, GTTools, Spec1)
>   - All Remaining tools written using the deprecated frameworks have
>been rewritten: Dependency Analyser, Critique Browser, and many other small
>utilities.
>- Modularisation has made a leap, creating correct baselines (project
>descriptions) for many internal systems, making possible the work and
>deployment of minimal images.
>- Removing support for the old Bytecode sets and embedded blocks
>simplified the compiler and language core.
>- As a result, our image size has been reduced by 10% (from 66MB to
>58MB)
>- The VM has also improved in several areas: better async I/O support,
>socket handling, FFI ABI,
>
> Even being a short iteration, we have closed a massive amount of issues:
> around 600 issues and 700 pull requests. A more extended changelog can be
> found at
> https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo100ChangeLogs.md
> .
>
> While the technical improvements are significant, still the most
> impressive fact is that the new code that got in the main Pharo 10 image
> was contributed by more than 80 people.
>
> Pharo is more than code. It is an exciting project involving a great
> community.
>
> We thank all the contributors to this release:
>
> Aaron Bieber, Ackerley Tng, Alban Benmouffek, Alejandra Cossio, Aless
> Hosry, Alexandre Bergel, Aliaksei Syrel, Alistair Grant, Arturo Zambrano,
> Asbathou Biyalou-Sama, Axel Marlard, Bastien Degardins, Ben Coman, Bernardo
> Contreras, Bernhard Pieber, Carlo Teixeira, Carlos Lopez, Carolina
> Hernandez, Christophe Demarey, Clotilde Toullec, Connor Skennerton, Cyril
> Ferlicot, Dave Mason, David Wickes, Denis Kudriashov, Eric Gade, Erik Stel,
> Esteban Lorenzano, Evelyn Cusi Lopez, Ezequiel R. Aguerre, Gabriel Omar
> Cotelli, Geraldine Galindo, Giovanni Corriga, Guille Polito, Himanshu, Jan
> Bliznicenko, Jaromir Matas, Kasper Østerbye, Kausthub Thekke Madathil,
> Konrad Hinsen, Kurt Kilpela, Luz Paz, Marco Rimoldi, Marcus Denker, Martín
> Dias, Massimo Nocentini, Max Leske, Maximilian-ignacio Willembrinck
> Santander, Miguel Campero, Milton Mamani Torres, Nahuel Palumbo, Norbert
> Hartl, Norm Green, Nour Djihan, Noury Bouraqadi, Oleksandr Zaitsev, Pablo
> Sánchez Rodríguez, Pablo Tesone, Pavel Krivanek, Pierre Misse-Chanabier,
> Quentin Ducasse, Raffaello Giulietti, Rakshit, Renaud de Villemeur, Rob
> Sayers, Roland Bernard, Ronie Salgado, Santiago Bragagnolo, Sean DeNigris,
> Sebastian Jordan Montt, Soufyane Labsari, Stephan Eggermont, Steven
> Costiou, Stéphane Ducasse, Sven Van Caekenberghe, Theo Rogliano, Thomas
> Dupriez, Théo Lanord, Torsten Bergmann, Vincent Blondeau.
>
>
> (If you contributed to Pharo 10 development in any way and we missed your
> name, please send us an email and we will add you).
>
> Enjoy!
>
> The Pharo Team
>
> Discover Pharo: https://pharo.org/features
>
> Try Pharo: http://pharo.org/download 
>
> Learn Pharo: http://pharo.org/documentation
> 
>


-- 
Serge Stinckwic
​h​
https://twitter.com/SergeStinckwich
​

[Pharo-dev] Re: [Pharo-users] Pharo - GSOC 2021

[Serge Stinckwich]

Yes accepted as an organization.
The Pharo GSOC admins will provide more details soon.

On Thu, 11 Mar 2021 at 21:13, Norbert Hartl  wrote:

> Great! This is to be accepted as organization? Projects still have to be
> accepted IIRC. Right?
>
> Norbert
>
> Am 11.03.2021 um 07:33 schrieb Serge Stinckwich <
> serge.stinckw...@gmail.com>:
>
> Dear all,
>
> great news I want to share with you: Pharo has been selected to be part of
> GSOC 2021
>
>
> https://summerofcode.withgoogle.com/organizations/?sp-search=pharo#4667274369171456
>
> Thank you to the great team of admins for making this happen: Oleksandr
> Zaitsev, Gordana Rakic and Juan Pablo Sandoval Alcocer !
>
> We will send updates soon on the student selection process soon.
> Regards,
> --
> Serge Stinckwic
> h
> https://twitter.com/SergeStinckwich
>
>
>

-- 
Serge Stinckwic
​h​
https://twitter.com/SergeStinckwich
​

[Pharo-dev] Pharo - GSOC 2021

[Serge Stinckwich]

Dear all,

great news I want to share with you: Pharo has been selected to be part of
GSOC 2021

https://summerofcode.withgoogle.com/organizations/?sp-search=pharo#4667274369171456

Thank you to the great team of admins for making this happen: Oleksandr
Zaitsev, Gordana Rakic and Juan Pablo Sandoval Alcocer !

We will send updates soon on the student selection process soon.
Regards,
-- 
Serge Stinckwic
h
https://twitter.com/SergeStinckwich

Re: [Pharo-dev] Project of Interest => Jekyll + Dynamic processing integration + Git(hubs)Pages => pharo in the middle

[serge . stinckwich]

There is already a static website generator in Pharo: 
https://github.com/guillep/ecstatic
Maybe you should start from that?
It would be great.
Regards

Sent from my iPhone

> On 27 May 2020, at 19:49, Esteban Maringolo  wrote:
> 
> On Wed, May 27, 2020 at 3:59 AM Cédrick Béler  wrote:
> 
>>> Hi - a bit late to reply on this one, but I did try Jekyl years ago, it was 
>>> ok but over time frustrating to use and difficult to make the pipeline 
>>> understandable ...
>>> I looked at Hugo and a few others but ended up going with Metalsmith (a JS 
>>> static generator). I liked the plugable pipeline model of it, but cursed 
>>> the state of Js tools (a few years ago) .
>> It seems indeed that Jekyll can become frustrating. I’m using Hugo right 
>> now. I didn’t know metalsmith...
> 
> I tried Jekyll and Gatsby.js, and albeit the latest is a mix of SSR
> and SPA, I found some of their ideas in how to organize content to be
> valuable, but I can't stand the tooling or the feeling of facing an
> unneeded accidental complexity.
> 
>>> I’ve been meaning for ages to reimplement it in Smalltalk with a nice oo 
>>> composite pipeline model and an easy way to debug and visualise what is 
>>> going when getting your template right.
>> I’ve tried to restrain myself not to redo it in smalltalk but that would be 
>> great option. I don’t know the required effort though but I’ll be glad to be 
>> part of such project.
> 
> I spent the last weekend giving a try to that Gatbsy thing (nuxt.js
> and vuepress are in the backlog too), and at 10PM on sunday I decided
> to start coding something in Smalltalk, because it just feels better
> to me.
> 
> I don't know how harder would it be, but that's a tool we currently
> lack, the static-site generator. And we have support for different
> templating, rendering canvas, and whatnot.
> 
>>> Combine this with the new headless image and it should easily plug into 
>>> netlify .
>> Plus to netlify but also class export to servers. I thing Git(hubs) Pages 
>> are a nice option. In any cas, one nice pattern is to use git to store pages 
>> versions, and then you can replay on Pages / or on your own server / or on 
>> netlify.
> 
> When I think about netlify I don't think about an app (as in, an
> executable) but as a simple static site, but if it possible to deploy
> an app that is distributed and served by their CDN, then better!
> 
>> I also wonder what would be possible with mini-image like Erik did.
> 
> I need to see more!
> I don't know how independent a client image can be, how much you can
> "pre-deploy" without needed to rehydrate the browser with server
> changes, etc.
> It's promising.
> 
> Regards!
> 

Re: [Pharo-dev] Squeak and Pharo speed differences

[Serge Stinckwich]

Arithmetic changes proposed in Squeak have no relationships to VM.


On Fri, May 15, 2020 at 2:09 PM Shaping  wrote:

> There is an issue about incorporating Squeak arithmetic changes in Pharo:
>
> https://github.com/pharo-project/pharo/issues/3322
>
>
>
> I start to understand what could be done and could not find time to do the
> changes.
>
> You are welcome if you want to help.
>
>
>
>
>
> Arithmetic speed is important if most of one’s work is math and modeling.
>
>
>
> I want to help, but need to port first from VW, and I’m trying to choose
> Squeak or Pharo.  Both have speed problems.  Squeak has fewer, but Pharo
> could be much faster with broad use of Spec2.
>
>
>
> *Would reintegrating Squeak and Pharo development make more sense?*
>
>
>
> This change would effectively create more devs willing to work on any
> problem.  This change would also prevent fracturing of feature-sets across
> the two Smalltalks from happening in the first place.
>
>
>
> Why can’t the OSVM be a single, unforked, maxed-out VM with all the best
> and fastest features working in Squeak and Pharo?   *Why did the split
> happen?*  It looks like a bad use of energy in a community that is small
> and needs to use its human resources efficiently.
>
>
>
> Squeak and Pharo GUI styles are different.  So be it.  Can’t the GUI
> frameworks and conventions be separated in the same image, and configured
> as desired in GUI sections of Settings?
>
>
>
>
>
> Shaping
>
>
>
>
>
> On Fri, May 15, 2020 at 12:48 PM Shaping  wrote:
>
> Hi all.
>
>
>
>
>
> Squeak 5.3:
>
>   Time millisecondsToRun: [ 10 factorial  ] 6250
>
>
>
> Pharo 8:
>
>   Time millisecondsToRun: [ 10 factorial  ] 7736
>
>
>
> Why the difference?
>
>
>
> Squeak 5.3 release notes describe arithmetic improvements.  Nice.  I
> crunch very big numbers, and these improvements therefore have value.  Why
> would they not be included in OSVM (forked or not) and the basic class-set
> for both Squeak and Pharo?
>
>
>
> Playing with Squeak 5.3, I’ve noticed that the GUI is snappier.  Browser
> ergonomics are better too (for me at least), but that can be fixed/tuned in
> either environ to suit the developer.  (Still that’s some work I prefer not
> to do.)  Pharo GUIs are now generally slower, except for the Launcher,
> which is delightfully quick because it is written in Spec2.  I presume that
> all Pharo GUIs will eventually (ETA?) be written in Spec2 and that Pharo
> will then be quick in all its GUIs.  The obvious question is:  Will Squeak
> be improving GUI look/behavior and speed with Spec2?  If not, can I load
> Spec2 into Squeak so that I can do new GUI work there?
>
>
>
> Both Squeak and Pharo have slow text selection.  Pick any word in any
> pane, and double click it to select it.  When I do this, I sense a 75 to
> 100 ms latency between the end of the double click and the selection
> highlight appearing on the word.   I thought I’d entered a wormhole.  So I
> did the same experiment in VW 8.3.2, VS Code, and Notepad, and all three
> showed undetectable latencies.   This matters to me.  I’m trying to port
> from VW to Pharo or Squeak (for a really long time now), and can’t push
> myself past the text-selection delay problem.  Can text-selection speed be
> improved to the level of VW’s?   Can someone sketch the algo used and/or
> point me to the right class/methods.
>
>
>
> The Squeak debugging experience step-to-step is much quicker.  The
> latencies in Pharo after button- release are very long.  I estimate 100 to
> 150 ms.   That’s too long for me to work productively.  I lose my mental
> thread with many of those delays, and have to restart the thought.  It’s a
> serious problem, caused mostly by acclimation to no detectable latency for
> many years (Dolphin and VW have quick GUIs).  Is speeding up the Pharo
> debugger with Spec2 a priority?  I can’t think of a better GUI-related
> priority for Pharo.
>
>
>
>
>
> Not speed-related:
>
>
>
> -  How can I load additional fonts into Squeak?  Pharo does this with the
> font dialog’s Update button.
>
>
>
> - Where in the Squeak and Pharo images can I change mouse-selection
> behavior to be leading-edge?  Some of the Squeak panes have this; others
> don’t.  I want leading-edge action in all panes, and wish the feature were
> in Preferences/Settings.
>
>
>
>
>
>
>
> Shaping
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> Serge Stinckwic
>
> ​h​
>
> https://twitter.com/SergeStinckwich
>
> ​
>


-- 
Serge Stinckwic
​h​
https://twitter.com/SergeStinckwich
​

Re: [Pharo-dev] Squeak and Pharo speed differences

[Serge Stinckwich]

There is an issue about incorporating Squeak arithmetic changes in Pharo:
https://github.com/pharo-project/pharo/issues/3322

I start to understand what could be done and could not find time to do the
changes.
You are welcome if you want to help.


On Fri, May 15, 2020 at 12:48 PM Shaping  wrote:

> Hi all.
>
>
>
>
>
> Squeak 5.3:
>
>   Time millisecondsToRun: [ 10 factorial  ] 6250
>
>
>
> Pharo 8:
>
>   Time millisecondsToRun: [ 10 factorial  ] 7736
>
>
>
> Why the difference?
>
>
>
> Squeak 5.3 release notes describe arithmetic improvements.  Nice.  I
> crunch very big numbers, and these improvements therefore have value.  Why
> would they not be included in OSVM (forked or not) and the basic class-set
> for both Squeak and Pharo?
>
>
>
> Playing with Squeak 5.3, I’ve noticed that the GUI is snappier.  Browser
> ergonomics are better too (for me at least), but that can be fixed/tuned in
> either environ to suit the developer.  (Still that’s some work I prefer not
> to do.)  Pharo GUIs are now generally slower, except for the Launcher,
> which is delightfully quick because it is written in Spec2.  I presume that
> all Pharo GUIs will eventually (ETA?) be written in Spec2 and that Pharo
> will then be quick in all its GUIs.  The obvious question is:  Will Squeak
> be improving GUI look/behavior and speed with Spec2?  If not, can I load
> Spec2 into Squeak so that I can do new GUI work there?
>
>
>
> Both Squeak and Pharo have slow text selection.  Pick any word in any
> pane, and double click it to select it.  When I do this, I sense a 75 to
> 100 ms latency between the end of the double click and the selection
> highlight appearing on the word.   I thought I’d entered a wormhole.  So I
> did the same experiment in VW 8.3.2, VS Code, and Notepad, and all three
> showed undetectable latencies.   This matters to me.  I’m trying to port
> from VW to Pharo or Squeak (for a really long time now), and can’t push
> myself past the text-selection delay problem.  Can text-selection speed be
> improved to the level of VW’s?   Can someone sketch the algo used and/or
> point me to the right class/methods.
>
>
>
> The Squeak debugging experience step-to-step is much quicker.  The
> latencies in Pharo after button- release are very long.  I estimate 100 to
> 150 ms.   That’s too long for me to work productively.  I lose my mental
> thread with many of those delays, and have to restart the thought.  It’s a
> serious problem, caused mostly by acclimation to no detectable latency for
> many years (Dolphin and VW have quick GUIs).  Is speeding up the Pharo
> debugger with Spec2 a priority?  I can’t think of a better GUI-related
> priority for Pharo.
>
>
>
>
>
> Not speed-related:
>
>
>
> -  How can I load additional fonts into Squeak?  Pharo does this with the
> font dialog’s Update button.
>
>
>
> - Where in the Squeak and Pharo images can I change mouse-selection
> behavior to be leading-edge?  Some of the Squeak panes have this; others
> don’t.  I want leading-edge action in all panes, and wish the feature were
> in Preferences/Settings.
>
>
>
>
>
>
>
> Shaping
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>


-- 
Serge Stinckwic
​h​
https://twitter.com/SergeStinckwich
​

Re: [Pharo-dev] [Mm10s] 2020-02-3

[Serge Stinckwich]

On Mon, Feb 3, 2020 at 9:52 AM Esteban Lorenzano 
wrote:

> ### Last week
>
> * add FFILibraryFinder helper to find libraries in the standard
> directories for each
> platform. They are still incomplete (since linux in particular has a
> lot), but is a begining.
>

This is great work !

Apparently the search is not done recursively in directories.

For example, I'm looking for libsqlite3.13.0.dylib on MacOS
who is located in : /usr/local/lib/sqlite3.13.0
and the FFILibraryFinder could not find it.

-- 
Serge Stinckwic
h

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)
U
niversity of Yaoundé I, Cameroon
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich

Re: [Pharo-dev] Unnecessary double checks of infinity

[Serge Stinckwich]

https://github.com/pharo-project/pharo/issues/5542

On Sun, Dec 22, 2019 at 5:12 PM Serge Stinckwich 
wrote:

> Hi all,
> I'm having a look how floats are printed.
> Why we check two times if a Float is infinite ?
> A first time in:
>
> Float>>printOn: stream base: base
> ...
> self isInfinite
> ifTrue: [
> stream nextPutAll: 'Float infinity'.
> ^ self sign = -1 ifTrue: [ stream nextPutAll: ' negated' ] ].
> ...
>
> and a second time in:
>
> Float>>absPrintExactlyOn: aStream base: base
> ...
> self isInfinite ifTrue: [
> aStream nextPutAll: 'Float infinity'.
> ^ self].
> ...
>
> the same in Float>>absPrintInexactlyOn: aStream base: base
> ...
> self isInfinite ifTrue: [aStream nextPutAll: 'Float infinity'. ^ self].
> ...
>
> Apparently the last two methods are never called when number is infinite.
>
> I remove the second checks and apparently nothing breaks (all number tests
> are still green).
>
> Regards,
> --
> Serge Stinckwic
> h
>
> Int. Research Unit
>  on Modelling/Simulation of Complex Systems (UMMISCO)
> Sorbonne University
>  (SU)
> French National Research Institute for Sustainable Development (IRD)
> U
> niversity of Yaoundé I, Cameroon
> "Programs must be written for people to read, and only incidentally for
> machines to execute."
> https://twitter.com/SergeStinckwich
>


-- 
Serge Stinckwic
​h​

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
​Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)​
U
​niversity of Yaoundé I​, Cameroon
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich
​

Re: [Pharo-dev] Pharo key features (document)

[serge . stinckwich]

Impressive list !!!

Would be nice to have an html version at the end with high-resolution screen 
shots and put it on the pharo.org website with nice transition animations like 
the one you found on Apple website for example.

Sent from my iPhone

> On 5 Jan 2020, at 11:02, Pavel Krivanek  wrote:
> 
> 
> Hi, I have created a list of the key Pharo features with some images and 
> animations that should help to explain to public what is cool on Pharo. It is 
> based on a list formerly created for a Wikipedia article.
> 
> https://github.com/pavel-krivanek/pharoMaterials/blob/master/features/PharoKeyFeatures.md
> 
> Please look at it to check if something is worth to add or change before we 
> will try to use it somewhere for real.
> 
> Cheers,
> -- Pavel

[Pharo-dev] Unnecessary double checks of infinity

[Serge Stinckwich]

Hi all,
I'm having a look how floats are printed.
Why we check two times if a Float is infinite ?
A first time in:

Float>>printOn: stream base: base
...
self isInfinite
ifTrue: [
stream nextPutAll: 'Float infinity'.
^ self sign = -1 ifTrue: [ stream nextPutAll: ' negated' ] ].
...

and a second time in:

Float>>absPrintExactlyOn: aStream base: base
...
self isInfinite ifTrue: [
aStream nextPutAll: 'Float infinity'.
^ self].
...

the same in Float>>absPrintInexactlyOn: aStream base: base
...
self isInfinite ifTrue: [aStream nextPutAll: 'Float infinity'. ^ self].
...

Apparently the last two methods are never called when number is infinite.

I remove the second checks and apparently nothing breaks (all number tests
are still green).

Regards,
-- 
Serge Stinckwic
h

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)
U
niversity of Yaoundé I, Cameroon
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich

Re: [Pharo-dev] code loading performance

[Serge Stinckwich]

On Fri, Dec 6, 2019 at 5:08 PM George Ganea  wrote:

> Hi all,
>
> Currently loading GToolkit takes quite some time (arount 18 minutes at the
> best of times) we were wondering if there’s been any attempts at improving
> code loading times in Metacello/Monticello. Or mabye there are some ideas
> on how one might start doing something like this?
>
>
Could be even worse when you dl from low-bandwith countries like in Africa.
While waiting a better solution, it possible to have build images available
from PharoLauncher ?
Regards,

-- 
Serge Stinckwic
h

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)
U
niversity of Yaoundé I, Cameroon
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich

Re: [Pharo-dev] make github issues clearer?

[Serge Stinckwich]

Maybe this is possible with people with enough privilege to edit the issues
in order to provide more details ?

I try for the PolyMath project to have more elaborate labels:
https://github.com/PolyMathOrg/PolyMath/labels
with different status, priorities and types like describe here:
https://medium.com/@dave_lunny/sane-github-labels-c5d2e6004b63
but you need people to tag correctly issues and labelling is more complex.
And I guess for Pharo, you will have to use a label to know what is the
area of the system impact (like Compiler or UI).

More people are needed to the triage of issues and polish them for sure.
Regards,


On Mon, Oct 28, 2019 at 11:23 PM Nicolas Cellier <
nicolas.cellier.aka.n...@gmail.com> wrote:

> +1 for improving the issues.
> I call that the "checkbox attitude":
> Opening an issue is mandatory for a change to be merged?
> No problem, i open an issue (just a title), check the box, et voilà...
>
> That's applying the letter of the law rather than the spirit of the law.
> Either the law is bad (too cumbersome for trivial changes?), or we are at
> degree zero of quality...
> I also call that quality-dry:
> It has the color of quality, the smell of quality, but it's not quality ;)
>
>
> Le lun. 28 oct. 2019 à 23:12, Myroslava Romaniuk via Pharo-dev <
> pharo-dev@lists.pharo.org> a écrit :
>
>> Hi everyone
>>
>> Maybe it makes sense to generate some github issue templates and
>> encourage people to fill in the related information from a prompt? I think
>> with bug reports the situation is better, but for feature requests the
>> state of things could be very much improved by adding a template that goes:
>> "describe problem", "describe solution you'd like", "other alternatives",
>> "additional context".
>>
>> Because right now github issues are a mess. I get it that some projects
>> have particular maintainers and they know what the issues are and the
>> phrasing doesn't matter, ok, but a lot of the issues that don't have a tie
>> to any particular project and are labeled "easy" or "beginner" take a while
>> to understand because you have no idea what the person who created the
>> issue actually means.
>>
>> Just a suggestion, but i think there's really a lot of room to improve
>> with labels and templates for issues, and make them more accessible to
>> outsiders.
>>
>> Best,
>> Myroslava
>>
>

-- 
Serge Stinckwic
​h​

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
​Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)​
U
​niversity of Yaoundé I​, Cameroon
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich
​

Re: [Pharo-dev] [ANN] New Windows VM - Fixes 1903 error

[Serge Stinckwich]

On Fri, Sep 20, 2019 at 11:07 AM teso...@gmail.com 
wrote:

> Hello,
> a new stable VM has been deployed. This VM uses a new version of
> libSSH allowing us to work in the latest Windows version.
>
> It can be directly updated using Pharo Launcher or downloaded using
> ZeroConf scripts.
>
> To update from Pharo Launcher you have to access to the VM Manager window.
> Just click on the marked button and then in "Update"
> [image: updateVM.png]
>
>
This great Pablo, I didn't know that there is a VM manager.
I want to save my bandwidth.
How do we know, we have the last VM ?


-- 
Serge Stinckwic
h

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)
U
niversity of Yaoundé I, Cameroon
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich

Re: [Pharo-dev] I have a dream... or why I think that compatibility is an illusion and bring us to the past

[Serge Stinckwich]

On Wed, Sep 11, 2019 at 2:14 AM Gabriel Cotelli  wrote:

> Looks like Christmas season opened early this year :)
>
> Jokes aside, I'm in favor of changing some of the characters we use for
> binary selectors to allow it to be used in keyword/unary messages.
>
> I'll include % in that list. For me its more useful as a way to create
> percentages ( 5 % ) than to be used as a binary message for keeping an ugly
> name from C-like languages.
>
>- · is middle dot and it's used in some math operations AFAIR
>- × is used in math also (it's used as the multiplication sign for
>scalars, cross product for vectors and cartesian product for sets)
>
> One thing that would be really cool is that we can use the full power of
> Unicode in methods/class names. Projects like polymath and DSLs can clearly
> take advantage of that. Some examples I've just invented, but can be
> supported:
>
>
>-
>
>∑ from: 1 to: 5 do: [:i | i + i squared ]
>-
>
>1 ≥ 3
>-
>
>∃ anyIn: #( 1 2 4) such: [:x | x isPrime ]
>-
>
>∅ includes: 1
>
>
>
Yes I would like to have something like that for PolyMath :-)
Is it possible to use Unicode characters for identifiers already ?

I working on the port of : https://github.com/len/Domains
to Pharo. The author modify the Cuis parser, so he can do things like that
:

"⊕ is used for direct sums, ⊗ for tensor products, × for cartesian product,
direct product of groups, ring products, and in general for categorical
products."

and also define ^ as a binary method:

"The ^ (hat) operator is used for exponentiation as well as conjugation by
group elements, and for creating free modules of tuples and matrices."

I'm not sure this is a good idea, because ^ is used also to return values.

A+
-- 
Serge Stinckwic
h

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)
U
niversity of Yaoundé I, Cameroon
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich

Re: [Pharo-dev] A small game: do one trivial improvement every day

[Serge Stinckwich]

Can we define a tag for such issues ?


On Fri, Jun 28, 2019 at 9:37 PM Marcus Denker 
wrote:

>
> >
> > Trivial improvement of the day:
> >
> > simplify #allSelectorsInProtocol:
> >   https://github.com/pharo-project/pharo/pull/3647
> >
>
> has been merged.
> >
> >
> > Trivial thing to do for someone else:
> >
> > #zapAllMethods can be removed
> >   https://github.com/pharo-project/pharo/issues/3656
> >
>
> was done (not by me!) and merged!
>
> Trivial thing done today:
>
> simplify allUnreferencedClassVariables
> https://github.com/pharo-project/pharo/issues/3661
>
> this is a nice example how other trivial unimportant changes make things
> trivial that where not trivial before.
> After
> - adding  #isReferenced for class variables (
> https://github.com/pharo-project/pharo/pull/3653)
> - adding #allClassVariables for classes (
> https://github.com/pharo-project/pharo/pull/3658)
>
> this was trivial. So I guess doing trivial things (that you might think
> are not important because they are oh so trivial) actually
> have the effect to make something trivial that was not trivial before?
> That is odd…
>
> Trivial thing for someone else to do:
>
> fix typo in Welcome bot message: “runn”
> https://github.com/pharo-project/pharo/issues/3696
>
> One of the welcome bot messages has a typo: “runn" should be “run"
>
> This needs to be fixed here:
>
>
> https://github.com/pharo-project/pharo/blob/Pharo8.0/.github/config.yml
>
> the file can be edited right from the GitHub interface
>
>
> Marcus
>
>
>

-- 
Serge Stinckwic
​h​

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
​Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)​
U
​niversity of Yaoundé I​, Cameroon
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich
​

Re: [Pharo-dev] FloatArray

[Serge Stinckwich]

There is another solution with my TensorFlow Pharo binding:
https://github.com/PolyMathOrg/libtensorflow-pharo-bindings

You can do a matrix multiplication like that :

| graph t1 t2 c1 c2 mult session result |
graph := TF_Graph create.
t1 := TF_Tensor fromFloats: (1 to:100) asArray shape:#(1000 1000).
t2 := TF_Tensor fromFloats: (1 to:100) asArray shape:#(1000 1000).
c1 := graph const: 'c1' value: t1.
c2 := graph const: 'c2' value: t2.
mult := c1 * c2.
session := TF_Session on: graph.
result := session runOutput: (mult output: 0).
result asNumbers

Here I'm doing a multiplication between 2 matrices of 1000X1000 size in 537
ms on my computer.

All operations can be done in a graph of operations that is run outside
Pharo, so could be very fast.
Operations can be done on CPU or GPU. 32 bits or 64 bits float operations
are possible.

This is a work in progress but can already be used.
Regards,



On Tue, May 21, 2019 at 6:54 AM Jimmie Houchin  wrote:

> I wasn't worried about how to do sliding windows. My problem is that using
> LapackDGEMatrix in my example was 18x slower than FloatArray, which is
> slower than Numpy. It isn't what I was expecting.
>
> What I didn't know is if I was doing something wrong to cause such a
> tremendous slow down.
>
> Python and Numpy is not my favorite. But it isn't uncomfortable.
>
> So I gave up and went back to Numpy.
>
> Thanks.
>
>
>
> On 5/20/19 5:17 PM, Nicolas Cellier wrote:
>
> Hi Jimmie,
> effectively I did not subsribe...
> Having efficient methods for sliding window average is possible, here is
> how I would do it:
>
> "Create a vector with 100,000 rows filles with random values (uniform
> distrubution in [0,1]"
> v := LapackDGEMatrix randUniform: #(10 1).
>
> "extract values from rank 10001 to 2"
> w1 := v atIntervalFrom: 10001 to: 2 by: 1.
>
> "create a left multiplier matrix for performing average of w1"
> a := LapackDGEMatrix nrow: 1 ncol: w1 nrow withAll: 1.0 / w1 size.
>
> "get the average (this is a 1x1 matrix from which we take first element)"
> avg1 := (a * w1) at: 1.
>
> [ "select another slice of same size"
> w2 := v atIntervalFrom: 15001 to: 25000 by: 1.
>
> "get the average (we can recycle a)"
> avg2 := (a * w2) at: 1 ] bench.
>
> This gives:
>  '16,500 per second. 60.7 microseconds per run.'
> versus:
> [w2 sum / w2 size] bench.
>  '1,100 per second. 908 microseconds per run.'
>
> For max and min, it's harder. Lapack/Blas only provide max of absolute
> value as primitive:
> [w2 absMax] bench.
>  '19,400 per second. 51.5 microseconds per run.'
>
> Everything else will be slower, unless we write new primitives in C and
> connect them...
> [w2 maxOf: [:each | each]] bench.
>  '984 per second. 1.02 milliseconds per run.'
>
> Le dim. 19 mai 2019 à 14:58, Jimmie  a écrit :
>
>> On 5/16/19 1:26 PM, Nicolas Cellier wrote:> Any feedback on this?
>>  > Did someone tried to use Smallapack in Pharo?
>>  > Jimmie?
>>  >
>>
>> I am going to guess that you are not on pharo-users. My bad.
>> I posted this in pharo-users as I it wasn't Pharo development question.
>>
>> I probably should have posted here or emailed you directly.
>>
>> All I really need is good performance with a simple array of floats. No
>> matrix math. Nothing complicated. Moving Averages over a slice of the
>> array. A variety of different averages, weighted, etc. Max/min of the
>> array. But just a single simple array.
>>
>> Any help greatly appreciated.
>>
>> Thanks.
>>
>>
>> On 4/28/19 8:32 PM, Jimmie Houchin wrote:
>> Hello,
>>
>> I have installed Smallapack into Pharo 7.0.3. Thanks Nicholas.
>>
>> I am very unsure on my use of Smallapack. I am not a mathematician or
>> scientist. However the only part of Smallapack I am trying to use at the
>> moment is something that would  be 64bit and compare to FloatArray so
>> that I can do some simple accessing, slicing, sum, and average on the
>> array.
>>
>> Here is some sample code I wrote just to play in a playground.
>>
>> I have an ExternalDoubleArray, LapackDGEMatrix, and a FloatArray
>> samples. The ones not in use are commented out for any run.
>>
>> fp is a download from
>> http://ratedata.gaincapital.com/2018/12%20December/EUR_USD_Week1.zip
>> and unzipped to a directory.
>>
>> fp := '/home/jimmie/data/EUR_USD_Week1.csv'
>> index := 0.
>> pricesSum := 0.
>> asum := 0.
>> ttr := [
>>  lines := fp asFileReference contents lines allButFirst.
>>  a := ExternalDoubleArray new: lines size.
>>  "la := LapackDGEMatrix allocateNrow: lines size ncol: 1.
>>  a := la columnAt: 1."
>>  "a := FloatArray new: lines size."
>>  lines do: [ :line || parts price |
>>  parts := ',' split: line.
>>  index := index + 1.
>>  price := Float readFrom: (parts last).
>>  a at: index put: price.
>>  pricesSum := pricesSum + price.
>>  (index rem: 100) = 0 ifTrue: [
>>  asum := a sum.
>>   ]]] timeToRun.
>> { index. pricesSum. asum. ttr }.
>>   "ExternalDoubleArray 

Re: [Pharo-dev] ESUG 2019 - Call for presentations

[serge . stinckwich]

IWST is a research track and you have to submit a paper. For the regular 
conference, a title and a summary should be enough.


Sent from my iPhone

> On 16 May 2019, at 22:51, askoh  wrote:
> 
> Thanks for reply.
> Do I submit to both to see which one will accept my presentation? 
> Or am I restricted to submit to one only?
> 
> All the best,
> Aik-Siong Koh
> 
> 
> 
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
> 

Re: [Pharo-dev] FloatArray

[Serge Stinckwich]

On Wed, Apr 24, 2019 at 6:20 AM Nicolas Cellier <
nicolas.cellier.aka.n...@gmail.com> wrote:

> Hi,
> I recommand inquiring about Smallapack, the Smalltalk interface to LAPACK, on
> squeaksource.com or github. You'll get the speed of numpy. There is a
> Metacello configuration. I have not checked the port on current
> Pharo, but I can reactivate if there is some interest.
>
>
Yes, we be nice to have a Pharo port.
I would really like to integrate this with PolyMath in one way or another.

Do you have a benchmark to test the performance ?
We have already one implementation of SVD in PolyMath.
We can compare the results with LAPACK.

Not sure we can do sum of vectors or matrices with LAPACK ?

Regards,
-- 
Serge Stinckwic
h

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)
U
niversity of Yaoundé I, Cameroun
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich

Re: [Pharo-dev] Recent Pharo 6.1 OSX shows lots of "Error: unsupported compressor 8 on command line"

[Serge Stinckwich]

done : https://github.com/pillar-markup/pillar/issues/368

On Thu, Apr 18, 2019 at 4:15 PM ducasse  wrote:

> Hi serge
>
> I cannot check now but Pillar should be running in P7 64 bits without
> problem.
> I see many warnings too.
> Can you open a bug entry?
> Stef
>
>
> On 18 Apr 2019, at 15:48, Serge Stinckwich 
> wrote:
>
> Any news on this ? This is only a 32 bits VM problem ?
> Why when I install Pillar on MacOS, the 32bits VM is used and not 64bits
> VM ?
>
>
> On Fri, May 11, 2018 at 11:37 AM  wrote:
>
>> Yes this is just a little bit annoying when you use Pillar because you
>> have a lot of noise ;-)
>>
>> Envoyé de mon iPhone
>>
>> > Le 11 mai 2018 à 17:17, Esteban Lorenzano  a
>> écrit :
>> >
>> > This is a problem since more than one year.
>> > Apple changed something on their apis and nobody knows how to fix it.
>> >
>> > but it is just a warning and you can work normally anyway :)
>> >
>> > cheers,
>> > Esteban
>> >
>> >> On 11 May 2018, at 00:14, Sven Van Caekenberghe  wrote:
>> >>
>> >> Yeah, I saw that for a while too, but my 64bit P7 VMs from the last
>> couple of days don't do this anymore.
>> >> I don't know why.
>> >>
>> >>> On 10 May 2018, at 23:53, Tim Mackinnon  wrote:
>> >>>
>> >>> I noticed that recent Pharo 6.1 zero conf downloads show lots of
>> these errors when you run the image in the terminal. Previous versions
>> didn’t do this - is this something to do with the latest vm upgrade?
>> >>>
>> >>> ./pharo-ui PagerDuty.image
>> >>>
>> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50:
>> Error: unsupported compressor 8
>> >>>
>> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353:
>> Error: Unknown compression scheme encountered for file
>> '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist'
>> >>>
>> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50:
>> Error: unsupported compressor 8
>> >>>
>> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353:
>> Error: Unknown compression scheme encountered for file
>> '/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist'
>> >>>
>> >>>
>> >>> Tim
>> >>
>> >>
>> >
>> >
>>
>
>
> --
> Serge Stinckwic
> h
>
> Int. Research Unit
>  on Modelling/Simulation of Complex Systems (UMMISCO)
> Sorbonne University
>  (SU)
> French National Research Institute for Sustainable Development (IRD)
> U
> niversity of Yaoundé I, Cameroun
> "Programs must be written for people to read, and only incidentally for
> machines to execute."
> https://twitter.com/SergeStinckwich
>
>
>

-- 
Serge Stinckwic
​h​

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
​Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)​
U
​niversity of Yaoundé I​, Cameroun
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich
​

Re: [Pharo-dev] Recent Pharo 6.1 OSX shows lots of "Error: unsupported compressor 8 on command line"

[Serge Stinckwich]

Any news on this ? This is only a 32 bits VM problem ?
Why when I install Pillar on MacOS, the 32bits VM is used and not 64bits VM
?


On Fri, May 11, 2018 at 11:37 AM  wrote:

> Yes this is just a little bit annoying when you use Pillar because you
> have a lot of noise ;-)
>
> Envoyé de mon iPhone
>
> > Le 11 mai 2018 à 17:17, Esteban Lorenzano  a écrit
> :
> >
> > This is a problem since more than one year.
> > Apple changed something on their apis and nobody knows how to fix it.
> >
> > but it is just a warning and you can work normally anyway :)
> >
> > cheers,
> > Esteban
> >
> >> On 11 May 2018, at 00:14, Sven Van Caekenberghe  wrote:
> >>
> >> Yeah, I saw that for a while too, but my 64bit P7 VMs from the last
> couple of days don't do this anymore.
> >> I don't know why.
> >>
> >>> On 10 May 2018, at 23:53, Tim Mackinnon  wrote:
> >>>
> >>> I noticed that recent Pharo 6.1 zero conf downloads show lots of these
> errors when you run the image in the terminal. Previous versions didn’t do
> this - is this something to do with the latest vm upgrade?
> >>>
> >>> ./pharo-ui PagerDuty.image
> >>>
> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50:
> Error: unsupported compressor 8
> >>>
> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353:
> Error: Unknown compression scheme encountered for file
> '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist'
> >>>
> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50:
> Error: unsupported compressor 8
> >>>
> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353:
> Error: Unknown compression scheme encountered for file
> '/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist'
> >>>
> >>>
> >>> Tim
> >>
> >>
> >
> >
>


-- 
Serge Stinckwic
h

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)
U
niversity of Yaoundé I, Cameroun
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich

Re: [Pharo-dev] How to manage your code with Iceberg

[Serge Stinckwich]

On Mon, Mar 25, 2019 at 10:11 AM ducasse  wrote:

> For recent projects but for old projects we will not be able to update
> them anymore.
> I’m looking for an alternative to bintray.
>
>
Why not using github releases like Etienne is doing here:
https://github.com/cormas/Booklet-CORMAS

-- 
Serge Stinckwic
h

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)
U
niversity of Yaoundé I, Cameroun
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich

Re: [Pharo-dev] Issue Tracker: enabled Projects (Boards)

[Serge Stinckwich]

but you need to be on the Pharo organization to be able to add/modify card
on the board ?
A+

On Tue, Mar 19, 2019 at 11:07 AM Marcus Denker 
wrote:

> Hi,
>
> it seems that the account / access model of GitHub forces us to move the
> boards to the organisation level
> (where we can have a user group with write access for the boards).
>
> This means I will move them slowly to
>
> https://github.com/orgs/pharo-project/projects
>
> So lets treat all this as a test… as soon as it is really working I will
> send another mail.
>
> On 18 Mar 2019, at 08:27, Marcus Denker  wrote:
>
> Hi,
>
> We enabled the GitHub “Projects” feature for the pharo repo:
>
> https://github.com/pharo-project/pharo/projects
>
>
> The idea is that one can add as many “Kanban” style boards as one wants.
> issues and pull requests can be added, as well as simple cards that are
> not yet issues.
>
> This is quite nice as an issue tracker gets very confusing and
> overwhelming as soon as there
> are >500 issues.
>
> With these boards, we can create “views” on this sea of issues.
>
> I created for now:
>
> -> some board related to specific parts of the system (e.g. Traits or
> Reflectivity)
> example: https://github.com/pharo-project/pharo/projects/11
> -> "Pharo7 Backporting”
> https://github.com/pharo-project/pharo/projects/12
> -> "Simple Issues for Beginners”
> https://github.com/pharo-project/pharo/projects/14
> Here the feature to be able to put things that are not yet
> issue tracker entries seems very useful
>
>
> I think this can be quite nice… we should add more Projects as soon as we
> find that they make sense
> and should move issues there.
>
> Marcus
>
>
>

-- 
Serge Stinckwic
​h​

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
​Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)​
U
​niversity of Yaoundé I​, Cameroun
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich
​

Re: [Pharo-dev] Roassal Animations

[Serge Stinckwich]

Most of the animations are available in the Roassal3 code:

https://github.com/ObjectProfile/Roassal3

On Sun, Mar 17, 2019 at 7:23 PM Sven Van Caekenberghe  wrote:

> Hi,
>
> Who has seen these Roassal Animations on Twitter recently ?
>
> These are crazy cool and super slick.
>
> Is there a place where they are all collected, maybe with their code ?
>
> Sven
>
>
>

-- 
Serge Stinckwic
​h​

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
​Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)​
U
​niversity of Yaoundé I​, Cameroun
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich
​

Re: [Pharo-dev] [ANN] Pharo Consortium New Academic Member: CIRAD

[Serge Stinckwich]

On Mon, Mar 11, 2019 at 10:03 AM Esteban Lorenzano 
wrote:

> Hi,
>
> > On 11 Mar 2019, at 04:24, askoh  wrote:
> >
> > It would be very interesting if there is a list showing what each
> consortium
> > member uses Pharo or Smalltalk for.
>
> Sadly, that’s not really possible :(
> While many members have no problem on freely talk about what they do,
> others do not have same approach :)
>
>
Yes I guess this is difficult for some members to be explicit about what
they are doing with Pharo.
For CIRAD, I can say that they use Smalltalk for their multi-agent modeling
platform : http://cormas.cirad.fr/indexeng.htm
There is an ongoing work to port CORMAS from VW to Pharo:
https://github.com/cormas/cormas

Regards,

-- 
Serge Stinckwic
h

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)
U
niversity of Yaoundé I, Cameroun
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich

Re: [Pharo-dev] Roadmap for Pharo 8.0

[Serge Stinckwich]

On Fri, Feb 8, 2019 at 4:41 PM Alexandre Bergel via Pharo-dev <
pharo-dev@lists.pharo.org> wrote:

> Dear All,
>
> At the consortium meeting we discussed the possibility to have a
> mini-Roassal included in Pharo8. Many opportunities exist: displaying graph
> of commits in iceberg, displaying UML within the code browser, visualizing
> dependencies between packages.
>
> We are motivated about it, and we should produce a runnable proposal ready
> to be evaluated by the community within a couple of months.
> Does it make sense? Any thought about it? Do you have a wishlist?
>
>
I will not be be strongly against it because I see benefits, but IHMO we
need to reduce the size of Pharo image.
Might be interesting to have charts included in the base.
A+

-- 
Serge Stinckwic
h

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)
U
niversity of Yaoundé I, Cameroun
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich

Re: [Pharo-dev] WELL512 PRNG

[Serge Stinckwich]

On Fri, Nov 9, 2018 at 5:54 PM Norbert Hartl  wrote:

> I was about to say let‘s add this to the Cryptography package 
>
>
How much RNGs are implemented in the crypto packages ?
Maybe we need to sync one day :-)

-- 
Serge Stinckwic
h

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)
U
niversity of Yaoundé I, Cameroun
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich

Re: [Pharo-dev] WELL512 PRNG

[Serge Stinckwich]

Can you contribute your code to PolyMath:
https://github.com/PolyMathOrg/PolyMath
We have other RNGs available.

Thank you.

On Fri, Nov 9, 2018 at 3:23 PM Sven Van Caekenberghe  wrote:

> Hi,
>
> By accident I came across a pseudo random number generator that I never
> heard off before. It is supposed to be pretty good and had a very simple
> implementation. So I ported it to Pharo.
>
> 
>
> I am RandomWELL512, a random number generator.
>
> I use the PRNG (Pseudo Randon Number Generator) WELL (Well equidistributed
> long-period linear) with a 512 bit state.
>
>   https://en.wikipedia.org/wiki/Well_equidistributed_long-period_linear
>   http://www.iro.umontreal.ca/~lecuyer/myftp/papers/wellrng.pdf
>
> Implementation algorithm (See #nextUInt32)
>
>   http://www.lomont.org/Math/Papers/2008/Lomont_PRNG_2008.pdf (Chris
> Lomont, www.lomont.org)
>
> Usage
>
>   RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextUInt32 ]
> ].
>
>   RandomWELL512 new useUnixRandomGeneratorSeed; in: [ :r | (1 to: 10)
> collect: [ :i | r next ] ].
>
>   RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextInt: 1000
> ] ].
>
>   RandomWELL512 new in: [ :random | | count all |
> random useUnixRandomGeneratorSeed.
> count := 1024 * 1024.
> all := Array new: count streamContents: [ :out |
>   count timesRepeat: [ out nextPut: random next ] ].
> { all min. all max. all average. all stdev } ].
>
>   [ RandomWELL512 new in: [ :random | 1 to: 1e6 do: [ :i | random next ] ]
> ] timeToRun.
>
> Note that you should create one instance, seed it properly, and keep using
> it.
>
> 
>
> It is acceptably fast, generating 1M [0,1) Floats in about 0.1s. I
> compared the output with a fixed initial state to the C code that I started
> from and I got the same numbers. Maybe some people find this interesting.
>
> I attached a file out.
>
> Sven
>
>
>
>

-- 
Serge Stinckwic
h

Int. Research Unit
 on Modelling/Simulation of Complex Systems (UMMISCO)
Sorbonne University
 (SU)
French National Research Institute for Sustainable Development (IRD)
U
niversity of Yaoundé I, Cameroun
"Programs must be written for people to read, and only incidentally for
machines to execute."
https://twitter.com/SergeStinckwich

Re: [Pharo-dev] [cormas-dev] Pharo eye-candy: Domain-Specific Modeling and Simulation

[serge . stinckwich]

Great ! A presentation of CORMAS simulation platform will be done at next ESUG. 
See you there.

Envoyé de mon iPhone

> Le 6 sept. 2018 à 19:17, Nick Papoylias  a écrit :
> 
> A nice example of how Pharo can be used for
> domain-specific modeling and simulation. Short 
> session from one of our projects at Rochelle:
> 
> https://www.youtube.com/watch?v=Z7wJNhAIaVQ
> 
> Some additional info here: https://goo.gl/jS4NjB
> 
> Currently investigating how to incorporate the new Bloc based 
> widgets of @feenkcom into the workflow.
> 
> Cheers,
> 
> Nick
> -- 
> You received this message because you are subscribed to the Google Groups 
> "cormas-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to cormas-dev+unsubscr...@googlegroups.com.
> To post to this group, send email to cormas-...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/cormas-dev/CACEStOjqbQt96qeae_4Nsf%3DEBqrQzxZ%3DsNNuwGpk5DWS3W4a3w%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

[Pharo-dev] Pharo TechTalk at 5pm (UTC+2)

[Serge Stinckwich]

I will start my techtalk at 5pm (UTC+2) about Pharo:
https://association.pharo.org/event-2973748

on Youtube live:
https://www.youtube.com/channel/UCtelfhEzvzvsNjXrGesm2fA

Questions on Discord, channel #techtalk: http://discord.gg/Sj2rhxn

Thank you.
-- 
Serge Stinckwich
UMI UMMISCO 209 (SU/IRD/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] Need help to get a list of Pharo projects with tests

[Serge Stinckwich]

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
> when the test is run.
> To have more details on the subject, you can check the research report
> related to our first definition of these tests freely available on HAL [1].
>
> In this context, we built a test analyser which, given a Pharo package
> containing tests, finds rotten tests [2]. This analyser is still under
> development.
>
> We would like to extend the experiment of our research report [1] and to
> analyse more projects in order to get a better understanding of rotten
> tests.
>
> To do that, we need your help. You can help us in two ways:
> 1. Answer this email with links to one or many open-source Pharo projects
> containing tests.
>

​We have 774 tests in PolyMath:
https://github.com/PolyMathOrg/PolyMath

-- 
Serge Stinckwich
UMI UMMISCO 209 (SU/IRD/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] Call for TechTalks

[Serge Stinckwich]

On Fri, Jun 15, 2018 at 11:36 AM Marcus Denker 
wrote:

> Hi,
>
> As you might now, we organised “tech talks” in the past:
>
> https://pharo.org/TechTalk
>
> We would like to continue the next half of 2018 with this series.
>
> The form itself is quite open: it can be a lecture, a demo, or just some
> “guided” discussion on Discord.
>
> If you have ideas —> send me a mail.
>
>
​I can do something about Machine Learning with TensorFlow and Pharo.
I already do a short presentation at the Pharo Club and another one will be
done during ESUG 2018.

​A+
-- 
Serge Stinckwich
UMI UMMISCO 209 (SU/IRD/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] Pharo 10th Anniversary

[Serge Stinckwich]

Congrats !!!

On Wed, May 30, 2018 at 9:10 AM Sven Van Caekenberghe  wrote:

> Hi,
>
> This short post by Stéphane Ducasse is worth sharing:
>
>   https://pharoweekly.wordpress.com/2018/05/29/pharo-got-10-years/
>
> Congratulation !
>
> Sven
>
> --
> Sven Van Caekenberghe
> Proudly supporting Pharo
> http://pharo.org
> http://association.pharo.org
> http://consortium.pharo.org
>
>
>
>
>
>

-- 
Serge Stinckwich
UMI UMMISCO 209 (SU/IRD/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] Recent Pharo 6.1 OSX shows lots of "Error: unsupported compressor 8 on command line"

[serge . stinckwich]

Yes this is just a little bit annoying when you use Pillar because you have a 
lot of noise ;-)

Envoyé de mon iPhone

> Le 11 mai 2018 à 17:17, Esteban Lorenzano  a écrit :
> 
> This is a problem since more than one year. 
> Apple changed something on their apis and nobody knows how to fix it. 
> 
> but it is just a warning and you can work normally anyway :)
> 
> cheers, 
> Esteban
> 
>> On 11 May 2018, at 00:14, Sven Van Caekenberghe  wrote:
>> 
>> Yeah, I saw that for a while too, but my 64bit P7 VMs from the last couple 
>> of days don't do this anymore. 
>> I don't know why. 
>> 
>>> On 10 May 2018, at 23:53, Tim Mackinnon  wrote:
>>> 
>>> I noticed that recent Pharo 6.1 zero conf downloads show lots of these 
>>> errors when you run the image in the terminal. Previous versions didn’t do 
>>> this - is this something to do with the latest vm upgrade?
>>> 
>>> ./pharo-ui PagerDuty.image 
>>> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50:
>>>  Error: unsupported compressor 8
>>> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353:
>>>  Error: Unknown compression scheme encountered for file 
>>> '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist'
>>> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50:
>>>  Error: unsupported compressor 8
>>> /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353:
>>>  Error: Unknown compression scheme encountered for file 
>>> '/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist'
>>> 
>>> 
>>> Tim
>> 
>> 
> 
> 

Re: [Pharo-dev] Iceberg2.0 crash test passed :)

[Serge Stinckwich]

On Fri, Apr 13, 2018 at 8:54 PM, Esteban Lorenzano <esteba...@gmail.com>
wrote:

>
>
> On 13 Apr 2018, at 21:43, Serge Stinckwich <serge.stinckw...@gmail.com>
> wrote:
>
> Yes I was able to commit also.
> Very slick interface :-)
>
>
> But now, every time I want to commit, my image crash and I have:
>
> Assertion failed: (git_atomic_get(__n_inits) > 0), function
> git__global_state, file /Users/travis/build/OpenSmalltalk/opensmalltalk-
> vm/build.macos64x64/pharo.cog.spur/build/third-party/libgit2-0.25.1/src/global.c,
> line 322.
>
>
> there is a current bug on initialisation (no idea why, still
> investigating).
>
> this is fixed by executing:
>
> LGitLibrary initialize.
>
>
​Thank you Esteban, you save my time :-)
​

​Apparently this crash happens after I relaunch my image with Iceberg
running.​

-- 
Serge Stinckwich
UMI UMMISCO 209 (SU/IRD/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] Iceberg2.0 crash test passed :)

[Serge Stinckwich]

Yes Pharo 7.0, latest VM 64 bits

On Fri, Apr 13, 2018 at 8:46 PM, Guillermo Polito <guillermopol...@gmail.com
> wrote:

> Is that Pharo 7?
>
> On Fri, Apr 13, 2018 at 9:43 PM, Serge Stinckwich <
> serge.stinckw...@gmail.com> wrote:
>
>> Yes I was able to commit also.
>> Very slick interface :-)
>>
>>
>> But now, every time I want to commit, my image crash and I have:
>>
>> Assertion failed: (git_atomic_get(__n_inits) > 0), function
>> git__global_state, file /Users/travis/build/OpenSmallt
>> alk/opensmalltalk-vm/build.macos64x64/pharo.cog.spur/
>> build/third-party/libgit2-0.25.1/src/global.c, line 322.
>>
>>
>> On Fri, Apr 13, 2018 at 8:02 PM, Stephane Ducasse <
>> stepharo.s...@gmail.com> wrote:
>>
>>> I could commit my first commit with iceberg 2.0
>>> Well done
>>>
>>> It feels nicer :).
>>>
>>> Stef
>>>
>>>
>>
>>
>> --
>> Serge Stinckwich
>> UMI UMMISCO 209 (SU/IRD/UY1)
>> "Programs must be written for people to read, and only incidentally for
>> machines to execute."http://www.doesnotunderstand.org/
>>
>
>
>
> --
>
>
>
> Guille Polito
>
> Research Engineer
>
> Centre de Recherche en Informatique, Signal et Automatique de Lille
>
> CRIStAL - UMR 9189
>
> French National Center for Scientific Research - *http://www.cnrs.fr
> <http://www.cnrs.fr>*
>
>
> *Web:* *http://guillep.github.io* <http://guillep.github.io>
>
> *Phone: *+33 06 52 70 66 13
>



-- 
Serge Stinckwich
UMI UMMISCO 209 (SU/IRD/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] Iceberg2.0 crash test passed :)

[Serge Stinckwich]

Yes I was able to commit also.
Very slick interface :-)


But now, every time I want to commit, my image crash and I have:

Assertion failed: (git_atomic_get(__n_inits) > 0), function
git__global_state, file
/Users/travis/build/OpenSmalltalk/opensmalltalk-vm/build.macos64x64/pharo.cog.spur/build/third-party/libgit2-0.25.1/src/global.c,
line 322.


On Fri, Apr 13, 2018 at 8:02 PM, Stephane Ducasse <stepharo.s...@gmail.com>
wrote:

> I could commit my first commit with iceberg 2.0
> Well done
>
> It feels nicer :).
>
> Stef
>
>


-- 
Serge Stinckwich
UMI UMMISCO 209 (SU/IRD/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] [ANN] New VM stables promoted

[Serge Stinckwich]

Thank you Esteban. Including 7.0 64 bits ?

On Fri, Apr 13, 2018 at 8:55 AM, Esteban Lorenzano <esteba...@gmail.com>
wrote:

> Hi,
>
> I just promoted new VMs as stable.
>
> This are the builds corresponding to:
>
> 20180416 (07c6dc3)
>
> this passed the build tests so *it should* be ok.
>
> can you people test?
>
> thanks!
>
> Esteban
>
>


-- 
Serge Stinckwich
UMI UMMISCO 209 (SU/IRD/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] Did magritte change? Magritte-Morph-SeasnDeNigris.95 is not found

[Serge Stinckwich]

On Mon, Apr 9, 2018 at 2:07 PM, Sean P. DeNigris <s...@clipperadams.com>
wrote:

> Stephane Ducasse-3 wrote
> > I will create one
>
> There is https://github.com/magritte-metamodel/magritte which I forked
> from.
> I wonder if we can make that canonical. It would be easy for me to sync my
> changes back and from the README, it appears that most other Smalltalk load
> Magritte from elsewhere. Regarding Sqeak, there are the mcz repos, and
> IFAICT Squeak has not shown much interest in git, so we're probably safe
> there. Either way, please coordinate with me because the StHub repo is
> wy behind my fork…
>
>

​Yes I guess, this is better to reuse existing org on github.
Sean or me can invite people.

​Regards,​

-- 
Serge Stinckwich
UMI UMMISCO 209 (SU/IRD/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] call for help: answer on HN :)

[Serge Stinckwich]

On Sat, Apr 7, 2018 at 4:48 PM, Aliaksei Syrel <alex.sy...@gmail.com> wrote:

> Hi
>
> Here is a link to a report about their experience with Pharo:
> https://gitlab.fit.cvut.cz/taibrmar/sokoban-using-bloc
>
> There definitely exist things that should be improved. It is a pity when
> tiny “minor” issues leave such an unpleasant aftertaste.
>
>
​Yes minor details kill most of the time the experience of new learners.
For more experienced people like us, we know how to avoid them :-)

Maybe specific sprints should be done to take care of some of them ?
​

​Regards,​
-- 
Serge Stinckwich
UMI UMMISCO 209 (SU/IRD/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] call for help: answer on HN :)

[Serge Stinckwich]

I guess the more Pharo will be known, the more we will have FUD.
I think we should ignore them most of the time.

What is problematic here is personal attack with anonymous alias ...

Regards

On Sat, Apr 7, 2018 at 4:26 PM, Stephane Ducasse <stepharo.s...@gmail.com>
wrote:

> I tend to not care about people pissing on me via a pseudo. This is
> too easy and too microscopic to have any value.
> Thanks Philippe, Luke and Ben because you use your real names.
>
> On Thu, Apr 5, 2018 at 2:07 PM, Esteban Lorenzano <esteba...@gmail.com>
> wrote:
> > Hi,
> >
> > yesterday someone posted an article on HN about the Pharo MOOC and there
> has
> > been some negative posts there.
> > I would like to call people who can have the time to answer there and
> help
> > to explain better and also contribute to contest that FUD someones (we
> know
> > who they are… sames as always) are spreading.
> >
> > here the link : https://news.ycombinator.com/item?id=16754872
> >
> > (this is not loosing time, people searching for Pharo will likely see
> this
> > kind of messages… at least we need to offer our point of view)
> >
> > cheers!
> > Esteban
>
>


-- 
Serge Stinckwich
UMI UMMISCO 209 (SU/IRD/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] Looking for names for the booklet collection

[serge . stinckwich]

Envoyé de mon iPhone

> Le 4 mars 2018 à 13:21, Stephane Ducasse  a écrit :
> 
> Hi
> 
> I would like to make a distinction between booklet on Pharo
> technologies (Smacc, Voyage, Scraping ...) and the booklets more
> oriented towards teaching something with pharo (building an
> interpreter, a reflective language...)
> 
> Right now we have The Pharo Booklet Collection.
> And I'm looking for two names

Booklet means small books or brochure.
I guess booklet is more for small books less then 50 pages, books instead.

> the Pharo academic booklet collection ?
> and
> the Pharo technology booklet collection ?
> 

Maybe : “Pharo Textbook series”  for teaching books.

> Stef
> 

Re: [Pharo-dev] [ANN] Updating Consultants Listing

[Serge Stinckwich]

Consultants listed on this board are not gold association member like said
here ?
https://association.pharo.org/Benefits

On Wed, Jan 17, 2018 at 5:27 PM, Marcus Denker <marcus.den...@inria.fr>
wrote:

> Hi,
>
> We have http://consultants.pharo.org
>
> I want to change it to
> - not be a forward to files.pharo.org
> - be auto-generated from the https://association.pharo.org
>
>
> But we should update it already before that is finished. So:
>
> If you want to be listed, please send your infos in the form:
>
> PharoConsultant {
> #name : Your name',
> #email : y...@email.com <y...@email.com>',
> #website : 'http://your-website.com',
> #id : 'yourname (currently not used for anything)',
> #location : 'City, Country of your business',
> #languages : 'what languages do you speak',
> #industryExperienceSince : 1994,
> #pharoExperienceSince : 2008,
> #areasOfExpertise : 'what are your areas of expertise. E.g. business
> apllications, user interface, legacy, ...',
> #smalltalkExperienceSince : 2002
> }
>
> (or open a pull request at: https://github.com/pharo-
> project/pharo-project-consultants/)
>
> Marcus
>



-- 
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] [Pharo-users] Google Summer of Code 2018 with Pharo Consortium

[Serge Stinckwich]

Just a reminder that we need your subject idea !

The deadline to apply is January 23, 2018.

Thank you !

On Wed, Jan 10, 2018 at 6:10 AM, Jigyasa Grover <grover.jigya...@gmail.com>
wrote:

> Hello Pharo-ers !
>
> On behalf of the community, I would like to thank each one of you for their
> significant contribution in the previously concluded *Google Summer of Code
> 2017* with *Pharo Consortium*. We aspire to take-off on a long flight after
> this successful stint by applying to participate in the upcoming *Google
> Summer of Code 2018*.
>
> As many of you might know, Google Summer of Code is a global program
> focused
> on bringing more student developers into open source software development.
> Students work with an open source organization on a 3 month programming
> project during their break from school. Read more about the program here:
> https://summerofcode.withgoogle.com/
>
> The deadline for organisations to apply is January 23, 2018 which is fast
> approaching. As an open source evangelist and a Pharo developer, I would
> like to invite all the experienced members to be a part of the "GSoC 2018
> with Pharo Consortium" Team and mentor students. Propose fresh ideas for
> projects which shall help improve Pharo or volunteer to mentor any of the
> existing one (Listed here: http://gsoc.pharo.org/). To add your own
> project
> idea to the list, visit http://gsoc.pharo.org/#adding-a-proposal
>
> Looking forward to an appreciable representation from the Pharo community.
>
> Best regards
> Jigyasa Grover
> Pharo Consortium Org Admin, Google Summer of Code 2017 [hidden email]
>
>
>
>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>
>


-- 
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] [Pharo-users] [ANN] PharoLauncher v1.1 released!

[Serge Stinckwich]

Thank you Christophe for this wonderful work !

On Tue, Jan 16, 2018 at 9:46 PM, Christophe Demarey <
christophe.dema...@inria.fr> wrote:

> Hi all,
>
> I just released *PharoLauncher 1.1*. There are now 64-bits versions for
> Mac and Linux. Jenkins build is now managed through a Jenkins file.
>
> Here is the changelog (details on https://github.com/pharo-
> project/pharo-launcher/issues):
> New features:
> #66 new command: import an image into the launcher default image folder
> #65 new command: remove a template from "Downloaded templates"
> #64 new command: create a local template from an image and remove the image
> #57 new option: run an image from a login shell to inherit from shell
> startup scripts to set up environment variables.
> #54 It is now possible to run an image anywhere on your file system if you
> click "launch" and no image is selected
> #23 Pharo Launcher now has an "about" box giving its description, version
> and a link to the bug tracker.
> Improvements:
> #62 Pharo Launcher should not load default Pharo settings
> #51 Pharo Launcher now sets the current directory to the directory
> containing the image (was the VM directory). Avoid confusions in Pharo 7
> images.
> Bux fixes:
> #60 hardReset option causes troubles to PharoLauncher
> #56 #, was sent to nil
> #55 Display name of Pharo 7 images unusable
> #52 Cannot open a Pharo 2 image
> #47 Cannot run pharo 50 pre-Spur images
>
> You can get platform bundles from files.pharo.org:
> http://files.pharo.org/pharo-launcher/1.1/
>
> Regards,
> Christophe.
>



-- 
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] [Pharo-users] Pharo Lecture at Tunis next week

[Serge Stinckwich]

Thank you Stéphane for your continued effort to do Pharo lectures all
around the world.
I try do to the same in Cameroon.


On Sat, Jan 13, 2018 at 1:36 PM, Stephane Ducasse <stepharo.s...@gmail.com>
wrote:

> Hi guys
>
> just to tell you that next week I will give a lecture at ENIS at tunis.
> 3 full days of Pharo and advanced design.
>
> Stef
>
>


-- 
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] New Year Wishlist (2018) ?

[serge . stinckwich]

Yes we talk about something like that with Clément some months ago.

Envoyé de mon iPhone

> Le 25 déc. 2017 à 20:29, Dimitris Chloupis  a écrit :
> 
> 
>> On Mon, Dec 25, 2017 at 3:18 PM Torsten Bergmann  wrote:
>> A GUI builder is always a nice thing ... and there already was an attempt
>> for Pharo:
>> 
>>   http://www.squeaksource.com/UIBuilder/
>> 
>> Now marked as "Failed attempt of develop a UI builder for Pharo-Smalltalk. 
>> That version
>> only works in Pharo 1.1. Is opened for any developer.".
>> 
>> Dont know why it failed ... maybe because the UI (especially with Morphic 
>> legacy)
>> is still too shaky are in Pharo.
>> 
>> But I guess the order will be/needs to be:
>> 
>>  - good and stable graphics framework (maybe solved with Bloc)
>>  - good and stable standardized widget set (maybe solved with Brick)
>>  - then place a UI builder on top of it
>> 
>> Bye
> 
> Yeap that's the ideology about GUI designers , which is why so few IDE's have 
> them. It's like the man waiting for the perfect woman to marry, ending up all 
> alone and miserable. 
> 
> As a designer myself I cannot follow easily this ideology. Actually I cannot 
> follow it at all. 
> 
> I see it the exact opposite way, if you don't have a good GUI designer , your 
> ability to provide a stable and powerful GUI API will be limited because less 
> people will use it. 
> 
> The most stable and powerful GUI api I ever used was VCL , the standard 
> library of Delphi and surprise, surprise it has a GUI designer. The most 
> powerful I used so far.
> 
> Open source wise QT dominates , surprise , surprise it has a very powerful 
> GUI designer. 
> 
> On Windows you have VS studio GUI designer on MacOS and iOS the XCode GUI 
> Designer and so forth. 
> 
> There a ton of GUI APIs out there that almost none uses, is it because they 
> are not stable ?
> 
> Well ... *cough* Windows *cough* ... sure. 
> 
> Making GUIs via code, is not as much fun, its slower and ends up being also 
> less flexible as you can easily lose track of what you intend to do trying to 
> understand the internals of a GUI API. Not fun at all. Especially if you 
> experienced the horrors of MFC. 
> 
> But I am realistic , don't expect a GUI designer any time soon in Pharo. They 
> are very hard to make and coders being allergic to GUIs does not help 
> motivate to make one. 
> 
> I am ok with just a modular image format. 
> 
> Also I drink my own poison. I have made my own GUI API in Python with OpenGL 
> (used from inside Blender for an application I am developing) very loosely 
> inspired by some things I liked about Morphic. The more complex it becomes 
> the more I feel the need to create a designer that will handle the boring 
> stuff for me. 
> 
> For now I use the excellent excuse you provide of stability and inability to 
> promise the structure of the GUI API in the future. But its an excuse with an 
> expiration date. Making the GUI I have in my head using plain code , without 
> a GUI designer, is a nightmare that is highly unlikely I will let myself 
> experience. 
>  
> On the other hand when one makes his own GUI API the good news is that he can 
> make it fits well in the workflow of a GUI designer. This way instead of 
> trying to make the Designer according to the API , I make the API according 
> to the designer. 
> 
>  But the good news is that it has helped me realize the amount work needed to 
> put in GUI API to become really useful. Fortunately making API to find only 
> my needs has made things far easier and far smaller. I cannot imagine making 
> something like Bloc and keeping my sanity. This way the next time I complain 
> about a GUI API, I will have a whole different level of respect for the 
> developers behind it. 

Re: [Pharo-dev] Advent of code

[Serge Stinckwich]

On Wed, Nov 22, 2017 at 4:55 PM, Stephane Ducasse <stepharo.s...@gmail.com>
wrote:

> Julien
>
> could you open a github project so that we can do the same as norviq?
> And get a log of the problems and solution?
>
>
​Yes would be nice.

-- 
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] Advent of code

[Serge Stinckwich]

BTW, the Japanese Smalltalk community is doing an advent Calendar every
year:

https://qiita.com/advent-calendar/2016/smalltalk

The 2017 edition is in preparation here:
https://qiita.com/advent-calendar/2017/smalltalk



On Wed, Nov 22, 2017 at 1:29 PM, Stephane Ducasse <stepharo.s...@gmail.com>
wrote:

> Hi pharoers
>
> I would like to know if you would like to participate to
> http://adventofcode.com/2016
>
> For example we could do the same as
> https://github.com/norvig/pytudes/blob/master/ipynb/
> Advent%20of%20Code.ipynb
>
> Stef
>
>


-- 
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC/UY1)
"Programs must be written for people to read, and only incidentally for
machines to execute."http://www.doesnotunderstand.org/

Re: [Pharo-dev] State of files.pharo.org

[serge . stinckwich]

Maybe this is a transient problem, because we had some problems this morning to 
dl files from files.pharo.org from Cameroun.

Envoyé de mon iPhone

> Le 5 oct. 2017 à 12:35, Norbert Hartl  a écrit :
> 
> I'm trying to download images from files.pharo.org. Either it takes a lot of 
> time or get something like
> 
> Downloading the latest 70 Image:
> http://files.pharo.org/get-files/70/pharo.zip
>   error:  invalid compressed data to inflate 
> image.7vLfZK/Pharo7.0-32bit-6bff78c.image
> image.7vLfZK/Pharo7.0-32bit-6bff78c.sources  bad CRC 724d27ab  (should be 
> f4d1baa8)
> 
> That is really sad. What use is this wonderful environment if nobody can 
> download it? We need to sort that out.
> 
> So is this hosted in Inria data center?
> 
> Norbert
> 

Re: [Pharo-dev] Can Realm (DB) and Pharo play together (or can we have a Pharo Realm Object Server to ROS) ?

[Serge Stinckwich]

Hi Cedrick,
If you want to develop mobile app, you should discuss with Noury and have a
look to Pharo/JS:
https://pharojs.github.io/

​Can you move such discussions on pharo-users mailing-list and not
pharo-dev ?
Thank you.​


On Sun, Sep 10, 2017 at 12:14 PM, Cédrick Béler <cdric...@gmail.com> wrote:

> Hello all,
>
> I’ve spent some time in the summer in what I call my quest to the ultimate
> and easy and fun architecture to prototype some personal administration
> apps and have fun :-)
> I’ll share some experience and wonder if there are alternative in Pharo.
>
> I want app that are mobile firsts, then manageable with a computer (for
> more complex administrative tasks).
> I want them reactive (I especially like reactive data driven application
> like meteor.js), ubiquitous around my devices and not always connected
> (offline-first - this is very important if not the first objective).
>
> Ok, so I was lurking around looking for server and mobile distributed
> databases and I finally found Realm (https://realm.io/products/
> realm-mobile-platform/) which is a cool architecture plenty of promises,
> well documented, lots of tutorials... The architecture is composed of 2
> products:
> - Realm DB [1] that runs on mobile device - multiplatform - fully
> open-source - performant - an object DB with some limitation though
> - Realm Object Server (ROS) [2] - provide two-way data sync simple and
> easy - BUT proprietary even if free for developers … the entry point for
> serious developments (in particular access programmatically to the server)
> is very expensive ! 1500$mo !
>
> The developer edition with is free is already quite outstanding to me.
> Looks at this demo page on GitHub [3] !
>
> But… without any control to the ROS, I find ROS quite limited finally. I
> may then use the DB part, ROS free for what really need sync reactivity
> between devices or between group of people (like a black board), but store
> all less transient information to WhateverNoSQLDB probably in REST.
>
> Anyway I want to share that with you because it rings a smalltalk bell in
> my head… it’s about object data, live feeling, and I want to use Pharo on
> the server :)
>
> Maybe some people here have thought of an alternative ROS in Pharo or
> Gemstone ? Any ideas or remarks ?
> I was aware of sebastian Flow living full-stack framework attempt but
> don’t know more.
>
> TIA
> Cédrick
>
> NB: Pharo looks more and more great ! Congratulations guys for you job ! I
> hope ESUG was nice.
> I’ve just tried Telepharo on Pharo 6 (64 bit). Really great work too... It
> works like a charm, out of the box on low cost dedicated ubuntu servers [4]
> => 10€mo
> Pharo 64 tinyBenchmarks is 2,75 times slower than on my Mac mini Core i5
> 2,5GHz from 2012 with SSD (I guess it’s not that bad and usable for
> personal applications servers). I think it’ about 3 times faster than on a
> raspberry Pi.
> Mac mini (32 bit version):  '1329870129 bytecodes/sec; 108576799 sends/sec’
> Dedibox Low Cost server (64 bit version)’  '595695171 bytecodes/sec;
> 39441333 sends/sec'
>
> NB2: to download/install Pharo from command line, on the web site
> instructions, it seems it lacks the trailing slash. I had to add it.
>
> curl get.pharo.org/64*/* | bash
>
>
> [1] https://realm.io/products/realm-mobile-database/
> [2] https://realm.io/products/realm-mobile-platform/
> [3] https://github.com/realm-demos
> [4] https://www.online.net/fr/serveur-dedie/dedibox-sc
>
>
>



-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] The mooc is looking for forum moderators

[Serge Stinckwich]

I should be able to help like last year.

On Fri, Sep 1, 2017 at 11:37 AM, Stephane Ducasse <stepharo.s...@gmail.com>
wrote:

> Hi guys
>
> we are looking for some brave souls to help us helping newbies during
> the next run of the mooc
> planned for October 16th 2017...
>
> https://www.fun-mooc.fr/courses/course-v1:inria+41010+session02/about
>
> Please let me know if you are interested helping.
>
> Stef
>
>


-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] [Ann][Pillar] Travis -> Bintray for PDFs

[Serge Stinckwich]

This is great Stef !
I'm waiting for the documentation to update all my projects with the new
process.


On Fri, Aug 25, 2017 at 4:42 PM, Stephane Ducasse <stepharo.s...@gmail.com>
wrote:

>  Hi
>
> with Damien Pollet, we went over all the booklets and some of the
> Pharo books currently written in Pillar and made sure that each time
> you commit
>
> - a travis job is run
> - latex is produced as well as pdf
> - the pdf is stored on bintray
> - the release versions are stored on the github repo (I should verify)
>
> So now you can just do a PR and you get a super nice PDF.
>
> Have a look at Glorp or Voyage for example
>
> - https://github.com/SquareBracketAssociates/Booklet-Glorp
> - https://github.com/SquareBracketAssociates/Booklet-Voyage
>
> You can access the bintray files from the squarebracketassociates
> lovely binTray account :)
>
> https://bintray.com/squarebracketassociates/wip/download_file?file_path=
> voyage-wip.pdf
>
>
> I'm writing a doc of the process so that other people can do it for
> their private projects.
>
>
> Stef
>
>


-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] [Ann] PharoThings a live programming IoT platform based on Pharo

[Serge Stinckwich]

Really impressive work ! Definitively interested to have a look for
projects I have in my research lab in Cameroon.



On Fri, Aug 25, 2017 at 4:25 PM, Denis Kudriashov <dionisi...@gmail.com>
wrote:

> Hi.
>
> I am glad to announce the project PharoThings
> <https://github.com/pharo-iot/PharoThings> which brings the live
> programming environment into IoT domain.
>
> It includes:
>
>- development tools to lively program, explore and debug remote boards
>(based on TelePharo <https://github.com/dionisiydk/TelePharo>)
>- board modeling library which simplifies board configuration
>   - Raspberry driven by WiringPi library
>   - Arduino driven by Firmata, soon
>   - Beaglebone, soon
>
> Follow github page <https://github.com/pharo-iot/PharoThings> and videos
> to get a feeling of this project:
> - https://youtu.be/ezfjditHjq4
> - https://youtu.be/5i0tsgFtlOg
> - https://youtu.be/0H9of7PQet0
>
> Now PharoThings is in beta stage together with documentation and videos. I
> would like any feedback on how to improve them.
>
> If you are going to Esug conference you can see PharoThings in live at
> awards competition.
>
> Best regards,
> Denis
>



-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] [Pharo-users] TechTalk Dates for the rest of 2017

[Serge Stinckwich]

On Tue, Aug 22, 2017 at 8:31 AM, Marcus Denker <marcus.den...@inria.fr>
wrote:

>
> > On 21 Aug 2017, at 19:08, serge.stinckw...@gmail.com wrote:
> >
> > I'm not sure Pharo tech talk is the good place but would love to see
> such a presentation.
> >
> Why not? I am sure Alex will have some code in there.. " programming, from
> scratch, a small artificial intelligence”
> if done with Pharo would be a very nice thing todo for the tech talk.
>
>

​I thought that Pharo tech talk was only for core Pharo technologies.
​But Alex proposal is really great.

-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] TechTalk Dates for the rest of 2017

[serge . stinckwich]

I'm not sure Pharo tech talk is the good place but would love to see such a 
presentation. 

Maybe you can do a Google or Twitch live video about that ?

Envoyé de mon iPhone

> Le 21 août 2017 à 18:38, Alexandre Bergel  a écrit :
> 
> Hi!
> 
> I am currently giving a lecture on Neural Networks and Genetic 
> Algorithm/Programming.
> Maybe I could turn this into an express 2 hours mini-lecture. Would this 
> work? 
> 
> Anyone is interesting in programming, from scratch, a small artificial 
> intelligence? 
> 
> Cheers,
> Alexandre
> 
> 
>> On Aug 21, 2017, at 10:32 AM, Marcus Denker  wrote:
>> 
>> Hi,
>> 
>> We have added dates for tech talk discussions / Demos for the rest of 2017:
>>https://association.pharo.org/events
>> 
>> We need to find some topics. In the past we had often formal “talks” or 
>> demos about
>> a topic with discussion afterwards, but a more relaxed form of just an open 
>> discussion
>> about a topic is possible, too,
>> 
>> If you like to lead one of the dates (all but the November dates are 
>> available still), this
>> would be great.
>> 
>> If a date does find a topic, we keep it as an open discussion round. 
>> 
>>Marcus
> 
> -- 
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> 
> 
> 
> 

Re: [Pharo-dev] Using Orca for a modern 'sexy' Smalltalk User Interface

[serge . stinckwich]

You should have a look to PharoJS that allows you to deploy Pharo app in the 
browser: https://pharojs.github.io/

PharoJS is fully supported.

Envoyé de mon iPhone

> Le 13 août 2017 à 13:42, Frank-B  a écrit :
> 
> @Stephan
> 
> Granted and agreed!
> 
> But that does not explain why it seems that nobody has really used this
> obviously brilliant Orca approach!
> 
> In my view, this Orca approach seems by far 'better' in many respects than
> some pseudo-solutions that expect us to program in the browser (= just
> absurd) and which neglect the gigantic advantages of our Smalltalk IDEs over
> the JavaScript world.
> 
> Any Smalltalker who has ever tried to develop a bigger piece of JavsScript
> code (like I did) must have been disgusted by the stone-age status of the
> available tools and should welcome the availability to develop client-server
> solution entirely in Smalltalk.
> 
> And today, with the availability of WebSockets, there should even be far
> better ways of having an Orca-based client communicate with a Smalltalk
> driven server on a message-passing level. It seems that WebSockets have not
> been used in Orca in 2011 and before, but it should not be problem to add
> them.
> 
> Further, I see TIRADE by Göran Krampe
> http://goran.krampe.se/category/tirade/  as another useful addition.
> 
> But most importantly, Orca should be the basis for a much better alternative
> to this (in my view) insane, ugly and very slow Seaside.
> 
> Orca is the perfect tool to create a modern and entirely browser-based user
> interface with ONE single source code for browser AND desktop based
> Smalltalk driven applications.
> 
> This would overcome our (Smalltalk in general) greatest deficiency and that
> has always been the user-interface, which is the by far most decisive
> success factor for every application software today.
> 
> Look at the *Smalltalk UI status*, which for me is still nothing but a
> *tragedy*:
> 
> Desk-top only UI definitions exist in *VA and Dolphin* where Dolphin is at
> least close to what most users consider and expect as the standard and that
> is, if we like it or not, Windows.
> 
> The same is true for VW where the *VisualWorks UI* is internally totally
> insane, undocumented, old-fashioned in many aspects, not multi-lingual at
> all (despite their claims), 'polling', it’s simply “kaputt” from the very
> beginning.
> 
> *Squeak’s UI* is out of any discussion and *Pharo‘s UI* is somewhat more
> modern but miles away from what end-users expect and tolerate, not to
> mention what they would love as an application UI.
> 
> Having separate UI code for the desk-top and the browser is a sick idea
> anyway and therefore NO Smalltalk today is really suitable for developing
> modern, end-user friendly, simply “sexy” user interfaces.
> 
> I have always been convinced that the total absence of a 'good UI' in
> Smalltalk for desk-top and browser has been *the major reason for
> Smalltalk's failure* to attract a large and prefessional (developers of
> wide-spread standard software) user-base, apart from the greed [Goldberg]
> and arrogance towards the UI and the absurd licensing conditions and
> price-wishes of the early managers not only at ParcPlace but also at their
> successors (some of their licencing is rather slavery). 
> 
> Shouldn't we finally change this sad situation? 
> 
> 
> 
> --
> View this message in context: 
> http://forum.world.st/Anybody-using-Orca-Smalltalk-to-JavaScript-tp4960519p4960668.html
> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
> 

Re: [Pharo-dev] Pull requests ready to be reviewed

[Serge Stinckwich]

This is great to see the workflow start to emerge.
I guess all PRs tagged with human-review-needed are the one to take care ?

https://github.com/pharo-project/pharo/pulls?q=is%3Apr+is%3Aopen+label%3Ahuman-review-needed

On Wed, Aug 9, 2017 at 10:09 AM, Pavel Krivanek <pavel.kriva...@gmail.com>
wrote:

> We have several pull requests validated successfully by the
> infrastructure. They need to be reviewed by humans:
>
> https://github.com/pharo-project/pharo/pull/75
>
> https://github.com/pharo-project/pharo/pull/66
>
> https://github.com/pharo-project/pharo/pull/175
>
> https://github.com/pharo-project/pharo/pull/172
>
> https://github.com/pharo-project/pharo/pull/169
>
> https://github.com/pharo-project/pharo/pull/168
>
> https://github.com/pharo-project/pharo/pull/134
>
> Cheers,
> -- Pavel
>
>
>


-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

[serge . stinckwich]

One of my students was confused also.


Envoyé de mon iPhone

> Le 29 juil. 2017 à 09:50, Volkert  a écrit :
> 
> 
> 
>> On 29.07.2017 10:39, Esteban Lorenzano wrote:
>> 
>>> On 29 Jul 2017, at 10:07, Volkert  wrote:
>>> 
>>> Cool. How do i figure out, if i have installed 6.1? The Welcome Page shows 
>>> 6.0?
>>> 
>>> i used ...
>>> wget -O- get.pharo.org/stable+vm | bash 
>>> Ubuntu 16.10
>>> LG,
>>> 
>>> Volkert
>>> 
>> yes, you have 6.1
>> believe it or not, the cost of doing a “proper release” (changing all 
>> numbers. etc.) is too big to do it frequently. That’s why we do not do this 
>> more often (also this is one of the many reasons why we are changing our 
>> process: with PR system + bootstrap, produce correct version numbers will be 
>> a lot easier).
>> 
>> Esteban
>> 
> better I believe you. ;-) but it is really confusing to talk about Pharo 6.1 
> and finding no information / notes with the release.
> 
> Volkert

Re: [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

[Serge Stinckwich]

On Thu, Jul 27, 2017 at 10:04 AM, Hilaire <hila...@drgeo.eu> wrote:

> If you read carefully what I wrote, I was wondering what were these small
> bugs fixes... and if P6.1 would be helpful for the drgeo problems: a list
> of bugs with links to the bug tracker will have been enough.
>
>
​I guess this will easier for Pharo 7. We can group PR with milestones on
github in order to built nice list when release new version. I guess
something similar could be done on fogbugz.

​


> Hilaire
>
>
> Le 26/07/2017 à 16:25, Stephane Ducasse a écrit :
>
>> People are nice and trying to help now everybody has its own agenda
>> and we set these "rules"
>>
>
> --
> Dr. Geo
> http://drgeo.eu
>
>
>
>


-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Simply Happy

[Serge Stinckwich]

Thank you !
I'm trying to push Pharo in Cameroon now.

On Thu, Jul 6, 2017 at 9:57 AM, Stephane Ducasse <stepharo.s...@gmail.com>
wrote:

> Hi pharoing people
>
> Just a little word to tell you that I'm super happy about the future of
> Pharo.
> The consortium is growing and will probably be able to pay esteban and
> clement.
> The roadmap for Pharo 70 is really exciting.
> The bootstrap, git and the new project in the pipe will boost us.
> So I wanted to thanks you all for all this super great energy.
>
> We (you and us) are building a super cool future.
>
> Stef
>
>


-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Pharo Launcher

[Serge Stinckwich]

On Thu, Jun 29, 2017 at 2:32 PM, Stephane Ducasse <stepharo.s...@gmail.com>
wrote:

> Hi
>
> where can I find the pharo launcher for the latest version of Pharo?
>
>

​I'm still fighting to use Pharo Launcher in Cameroon with very low
bandwidth ...
Most of the time I have an error: can't find EOCD position.
What is the meaning of this error ? a latency problem ?
 ​

Stef
>
>


-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Reflecting on data (literal) object syntax

[Serge Stinckwich]

ritten in code it is important that it reads well even if there are
> noisy characters.
>
>
> would give a PointCollection of two point objects. My future wish would be
> that there is an object literal parser that takes all of the information
> from the format. And then a object literal parser that is aware of slot
> information. Meaning that the type information can be gathered from the
> object class instead having it to write in the format. In the
> PointCollection the slot for points would have the type information #Point
> attached. The format goes then to
>
> { #points -> {
>   { #x -> 10 . #y -> 20 }.
>   { #x -> 5 . #y -> 8 } }
>
> which would then the equivalent to something like JSON
>
> { "points" : [
> { "x" : 10, "y" : 20 },
> { "x" : 5, "y" : 8 } ] }
>
> What I don't know is how to solve the difference between a dictionary and
> an collection of associations.
>
>
> That's incidental to the format, internal to the parser.  If the parser
> chooses to build a dictionary as it parses so be it.  The point is that the
> output is as you specify; a tree of objects.
>
> The thing to think about is how to introduce labels so that sub objects
> can be shared in the graph, the naïve deepCopy vs deepCopyUsing: issue.
>
>
>
> I'm not sure this is necessary. It should be a format to easily
> instantiate a small tree of objects. Making it build a graph instead of a
> tree makes everything much more complicated. Either we decide that STON can
> do the full set and in that case it is probably less valuable to have a
> simple syntax to write in code. Or we need to break pairs rule. In that
> case an object definition can have an optional third argument which would
> be the label for the object. The draback is that the label needs to be
> before the array of slots
>
>
>
> { :v1 #ValueHolder { 'contents' . { ValueHolder . { 'contents' . @v1 
>
>
>
> Or something like this. It would be in theory closer to STON using the @
> reference. The difference is that STON has indexed object access and that
> variant would make it based on labels.Or something like this.
>
>
>
> Norbert
>
>
>
>
>
>
> Norbert
>
>
>
>
> As a dictionary is both, an array of associations and a key-value store,
> it works perfectly there. But for other objects I have doubts. Especially
> is in a lot of contexts you need to have a mapping of internal state to
> external representation. It can be applied afterwards but I'm not sure that
> can work all the time.
>
>
> Yes after we should focus on the frequent cases. And may be having a
> literal syntax for dictionary would be good enough.
>
> I will do another version of igor's proposal with associations to see
> how it feels.
>
>
>
> my 2 cents,
>
> Norbert
>
>
>
> Stef
>
>
>
>
> -- Forwarded message --
> From: Igor Stasenko <siguc...@gmail.com>
> Date: Fri, Oct 19, 2012 at 1:09 PM
> Subject: [Pharo-project] Yet another Notation format: Object literals
> To: Pharo Development <pharo-proj...@lists.gforge.inria.fr>
>
>
> Hi,
> as i promised before, here the simple smalltalk-based literal format.
> It based on smalltalk syntax, and so, unlike JSON, it doesn't needs to
> have separate parser (a normal smalltalk parser used for that).
>
> The idea is quite simple:
> you can tell any object to represent itself as an 'object literal' ,
> for example:
>
> (1@3) asObjectLiteral
> -->  #(#Point 1 3)
>
> { 1@2.  3@4. true. false . nil  } asObjectLiteral
>
> -> #(#Array #(#Point 1 2) #(#Point 3 4) true false nil)
>
> (Dictionary newFromPairs: { 1->#(1 2 3) . 'foo' -> 'bar' }) asObjectLiteral
> ->
> #(#Dictionary 1 #(#Array 1 2 3) 'foo' 'bar')
>
> Next thing, you can 'pretty-print' it (kinda):
>
> #(#Dictionary 1 #(#Array 1 2 3) 'foo' 'bar') printObjectLiteral
>
> '#(#Dictionary
> 1
> (#Array 1 2 3)
> ''foo'' ''bar'')'
>
>
> and sure thing, you can do reverse conversion:
>
> '#(#Dictionary
> 1
> (#Array 1 2 3)
> ''foo'' ''bar'')'  parseAsObjectLiteral
>
> a Dictionary('foo'->'bar' 1->#(1 2 3) )
>
> Initially, i thought that it could be generic (by implementing default
> Object>>#asObjectLiteral),
> but then after discussing it with others, we decided to leave
>
> Object>>#asObjectLiteral to be a subclass responsibility.
> So, potentially the format allows to represent any object(s) as
> literals, except from circular referencing objects, of course.
>
> The implementation is fairly simple, as you may guess and contains no
> new classes, but just extension methods here and there.
>
> Take it with grain and salt, since it is just a small proof of
> concept. (And if doing it for real it may need some changes etc).
> Since i am far from areas right now, where it can be used, i don't
> want to pursue it further or advocate if this is the right way to do
> things.
> Neither i having a public repository for this project..
>
> So, if there anyone who willing to pick it up and pursue the idea
> further, please feel free to do so and make a public repository for
> project.
>
>
>



-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Reflecting on data (literal) object syntax

[Serge Stinckwich]

On Fri, Jun 30, 2017 at 11:03 AM, Stephane Ducasse <stepharo.s...@gmail.com>
wrote:

> Hi
>
> recently I started to read a book on machine learning and they
> manipulate dictionary of dictionary. (So I started my own
> implementation and I will switch to DataFrame).
>
> Now it occurred to me that when we program complex objects we do not
> need a compact literal syntax for our objects. But when we manipulate
> data objects it is super handy.
>
> I ended up doing a lot of
>
>  self new
>   addRow: 'Claudia Puig'
>   withTaggedValues:
> {('Snakes on a Plane' -> 3.5). ('Just My Luck' -> 3.0).
> ('The Night Listener' -> 4.5). ('Superman Returns' -> 4.0). ('You, Me
> and Dupree' -> 2.5)}.
>
> And I was not in the mood to write a class for the taggedValues and
> writing a class would not have really help me.
>
>
> Now we also have STON but STON is not yet part of the language
> grammar. So we have to have an explicit conversion call.
>
> STON fromString: 'Point[10,20]'
>
> We were brainstorming with marcus and we could have a first nice extension:
>
> { 'x' -> 10 .'y' -> 20 } asObjectOf: #Point.
> >>> 10@20
>
> Now in addition I think that there is a value in having an object
> literal syntax.
>
> I pasted the old mail of igor on object literals because I like the
> idea since it does not add any change in the parser.
> Do you remember what were the problem raised by this solution (beside
> the fact that it had too many # and the order was like in ston not
> explicit).
>
> I would love to have another pass on the idea of Igor.
>
>

​Thank you Stéphane for having this kind of discussion.
This is quite important to have a compact literal notations for tables or
dataframes in Pharo,
if we want to be able to manipulate data like they are doing in Python or R.

I'm not sure we should have a literal notations for all kind of objects.

-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Pharo 7 provisional HOWTO

[Serge Stinckwich]

On Tue, Jun 27, 2017 at 3:10 PM, Pavel Krivanek
<pavel.kriva...@gmail.com> wrote:
>
>
> 2017-06-27 15:57 GMT+02:00 Serge Stinckwich <serge.stinckw...@gmail.com>:
>>
>> On Mon, Jun 26, 2017 at 12:14 PM, Pavel Krivanek
>> <pavel.kriva...@gmail.com> wrote:
>> > Hi,
>> >
>> > this mail describes how to start to send pull requests to Pharo 7 Github
>> > repository from Pharo 7.
>>
>> Thank you for the great explanation Pavel.
>>
>> > Preparations
>> > =
>> >
>> > - you need to have a Github account and set SSH keys. See
>> > https://help.github.com/articles/connecting-to-github-with-ssh/
>> > - create own pharo-project/pharo repository fork. Go to
>> > https://github.com/pharo-project/pharo, click on "Fork" button and
>> > follow
>> > the instructions
>>
>> [ ... ]
>>
>> > Issue processing
>> > =
>> >
>> > - create new case on FogBugz to get the issue number
>> > - open Iceberg and from the context menu on the 'pharo' repository do:
>> > Pharo
>> > - Create new branch from FogBugz issue, enter the issue ID and it will
>> > fill
>> > the full branch name for you
>> > - create your changes (you can do it before the creation of the branch
>> > too)
>> > - commit and push your changes in Iceberg, this way you will commit your
>> > branch to your fork repository. Remember that the Iceberg commit window
>> > has
>> > two buttons, one for local commit, the second for commit with immediate
>> > push. They can be very long because they contain the full branch (issue)
>> > name
>> > - in Iceberg in the 'pharo' repository context menu do: Pharo - Create
>> > pull
>> > request, fill your
>> > - fill your Github credentials
>> > - leave the PR title, comment is not required, check the pull request
>> > head
>> > and base. The base MUST be pharo-project/pharo development. Create the
>> > pull
>> > requests
>> > - go to https://github.com/pharo-project/pharo/pulls, check your pull
>> > requests and put URL of it into the issue record on FogBugz (as a
>> > comment).
>> > Resolve the issue as Fix review needed
>>
>> It means, there is no PR without a corresponding FogBugz issue ?
>
>
> Yes, at least for code changes we would like to keep this relation. If it is
> a really trivial change in readme or something like that, we can accept no
> related issue record.
> Please prefer to comment the issues instead of PRs directly to have all
> information at one place.

Thank you Pavel for the explanation.

Maybe in the future, it will make sense to put everything in the PR
and use github issues.
You will use CI travis builds for all PR ?

Regards,
-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Pharo 7 provisional HOWTO

[Serge Stinckwich]

On Mon, Jun 26, 2017 at 12:14 PM, Pavel Krivanek
<pavel.kriva...@gmail.com> wrote:
> Hi,
>
> this mail describes how to start to send pull requests to Pharo 7 Github
> repository from Pharo 7.

Thank you for the great explanation Pavel.

> Preparations
> =
>
> - you need to have a Github account and set SSH keys. See
> https://help.github.com/articles/connecting-to-github-with-ssh/
> - create own pharo-project/pharo repository fork. Go to
> https://github.com/pharo-project/pharo, click on "Fork" button and follow
> the instructions

[ ... ]

> Issue processing
> =
>
> - create new case on FogBugz to get the issue number
> - open Iceberg and from the context menu on the 'pharo' repository do: Pharo
> - Create new branch from FogBugz issue, enter the issue ID and it will fill
> the full branch name for you
> - create your changes (you can do it before the creation of the branch too)
> - commit and push your changes in Iceberg, this way you will commit your
> branch to your fork repository. Remember that the Iceberg commit window has
> two buttons, one for local commit, the second for commit with immediate
> push. They can be very long because they contain the full branch (issue)
> name
> - in Iceberg in the 'pharo' repository context menu do: Pharo - Create pull
> request, fill your
> - fill your Github credentials
> - leave the PR title, comment is not required, check the pull request head
> and base. The base MUST be pharo-project/pharo development. Create the pull
> requests
> - go to https://github.com/pharo-project/pharo/pulls, check your pull
> requests and put URL of it into the issue record on FogBugz (as a comment).
> Resolve the issue as Fix review needed

It means, there is no PR without a corresponding FogBugz issue ?

Regards,
-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Esteban's ChangeLog week of 12 June 2017

[Serge Stinckwich]

On Mon, Jun 19, 2017 at 12:40 PM, Esteban Lorenzano <esteba...@gmail.com> wrote:
>
>> On 19 Jun 2017, at 13:22, Serge Stinckwich <serge.stinckw...@gmail.com> 
>> wrote:
>>
>> On Mon, Jun 19, 2017 at 7:00 AM,  <esteba...@gmail.com> wrote:
>>> Hello!
>>>
>>> This is my weekly ChangeLog, from 12 June 2017 to 18 June 2017.
>>> You can see it in a better format by going here: 
>>> http://log.smallworks.eu/web/search?from=12/6/2017=18/6/2017
>>>
>>> ChangeLog
>>> =
>>>
>>> 15 June 2017:
>>> -
>>>
>>> *I finished an iteration for allowing cherry-pick into 
>>> [iceberg](http://github.com/pharo-vcs/iceberg).
>>>
>>>Now, I just need to make it work on 64bits and we will be ready-to-go 
>>> for releasing it :)
>>
>> Great work Esteban !
>>
>> Cherry-picking is integrated with Kommiter or the UI is completely different 
>> ?
>
> is a different implementation. Is integrated into iceberg (you will see the 
> checkboxes when commiting).
> Kommiter in fact does not works since ages.

Yes it was working more or less and I like it !

If we have a similar interface in Iceberg, this will be great :-)

-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Esteban's ChangeLog week of 12 June 2017

[Serge Stinckwich]

On Mon, Jun 19, 2017 at 7:00 AM,  <esteba...@gmail.com> wrote:
> Hello!
>
> This is my weekly ChangeLog, from 12 June 2017 to 18 June 2017.
> You can see it in a better format by going here: 
> http://log.smallworks.eu/web/search?from=12/6/2017=18/6/2017
>
> ChangeLog
> =
>
> 15 June 2017:
> -
>
> *I finished an iteration for allowing cherry-pick into 
> [iceberg](http://github.com/pharo-vcs/iceberg).
>
> Now, I just need to make it work on 64bits and we will be ready-to-go for 
> releasing it :)

Great work Esteban !

Cherry-picking is integrated with Kommiter or the UI is completely different ?

Regards,
-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] I want to get in contact with raphael luque from madrid :)

[Serge Stinckwich]

Maybe you can try to contact him on Twitter: https://twitter.com/rafael_luque


On Wed, Jun 14, 2017 at 1:11 PM, Stephane Ducasse
<stepharo.s...@gmail.com> wrote:
> Hi guys.
>
> I tried to get in contact with raphael but my emails do not seem to go
> to destination.
> Do you have the email of raph/fael luque from madrid?
>
> Stef
>



-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Chrome DevTools Protocol and Pharo

[serge . stinckwich]

Thank you guys for your contributions, but I think that this kind of 
discussions should be done on pharo-users mailing-list, not here.

pharo-dev should be use only if you contribute to core-pharo.

Thank you

Envoyé de mon iPhone

> Le 28 mai 2017 à 10:22, askoh  a écrit :
> 
> Wonderful contribution. Having full control of an internet browser will give 
> Smalltalk more freedom to innovate. 
> 
> Now, can we make Pharo be a web server on demand? Then we can give anyone a 
> URL and they can see the app or info we want to present. Pharo can 
> communicate with anyone using a browser either automatically or under 
> developer control. 
> 
> All the best,
> Aik-Siong Koh
> 
>> On May 27, 2017, at 3:23 PM, Alistair Grant [via Smalltalk] <[hidden email]> 
>> wrote:
>> 
>> Hi Torsten and All, 
>> 
>> Quick Introduction for those not familiar with Pharo-Chrome: 
>> 
>> Pharo-Chrome enables Pharo to control and query Chrome / Chromium, in 
>> particular to retrieve the DOM of a page.  This is useful as many modern 
>> pages are just a template which then loads some javascript to 
>> asynchronously build the DOM, meaning that the ZnEasy / Soap combination 
>> doesn't get the bulk of the information on a page. 
>> 
>> 
>> 
>> Pharo-Chrome is now mostly working, i.e. it is possible to open 
>> a connection to Chrome, navigate to a requested URL, wait for it to 
>> load, retrieve the DOM and then navigate the DOM using a subset of the 
>> Soap API, e.g. #findAllStrings:, #findAllTags:, attributeAt:, etc.. 
>> 
>> GoogleChrome class>>exampleNavigation has been updated to retrieve the 
>> DOM from http://pharo.org. 
>> 
>> GoogleChrome class>>get: is analogous to ZnEasy class>>get:, although it 
>> returns a ChromeNode, not an html string. 
>> 
>> I wasn't able to get rid of the delay while waiting for the page to 
>> finish loading.   This actually makes sense, since, as mentioned above, 
>> many modern pages build the DOM asynchronously, so there's no clear 
>> indication of when it is complete.  The default delay is currently 2000 
>> milliseconds, which is about twice the maximum I saw needed (983ms), but 
>> this can be changed (ChromeTabPage>>pageLoadDelay:). 
>> 
>> I had three use cases for this library: one which works with 
>> ZnEasy+Soap, one that used to work with ZnEasy+Soap, but doesn't due to 
>> a page redesign, and one which I hadn't got working before.  All three 
>> are working now. 
>> 
>> Unlike Soap, I've currently modelled the nodes as a single class, and 
>> have only implemented a subset of Soap's methods, but is enough for what 
>> I need. 
>> 
>> I've introduced a dependency on the Beacon logging framework.  I find it 
>> useful, but can remove it if you don't want the additional dependency. 
>> (I'm planning to add some GoogleChrome specific logging classes and use 
>> those to better understand what pageLoadDelay should be). 
>> 
>> I was focussed on trying to understand the events that Chrome generates, 
>> so documentation is still lacking (read "missing" :-)). 
>> 
>> I'll generate a pull request after some more testing, tweaking and 
>> documenting, but if you would like to take a look, the code is available 
>> at: 
>> 
>> https://github.com/akgrant43/Pharo-Chrome/tree/development
>> 
>> I haven't yet updated BaselineOfChrome with the Beacon dependency.  I 
>> did merge in your two commits from May 23. 
>> 
>> If you, or anyone else, finds this useful, I welcome any feedback. 
>> 
>> P.S.  I've just realised that I need to tidy up #sendMessage:, 
>> #sendMessageDictionary and #sendMessageDictionary:wait:.  I'll do that 
>> as part of the genral tidy up. 
>> 
>> Cheers, 
>> Alistair 
>> 
>> 
>> # vim: tw=72 
>> On Sun, May 21, 2017 at 09:37:56PM +, Alistair Grant wrote:
>> 
>> > Hi Torsten, 
>> > 
>> > On Fri, May 19, 2017 at 09:20:48PM +, Alistair Grant wrote: 
>> > > 
>> > > On Fri, May 19, 2017 at 10:50:41PM +0200, Torsten Bergmann wrote: 
>> > > > Hi Alistair, 
>> > > > 
>> > > > cant look right now but two things: 
>> > > > 
>> > > >   - there are also events in the protocol - if we could hook Pharo 
>> > > > into them 
>> > > > this would solve the problem without abusing delay (because then 
>> > > > you will 
>> > > > get informed when the page loading is finished) 
>> > > 
>> > > That would be great.  It will be a while before I get a chance to look 
>> > > at this (I want to finish some proposed changes to the FileSystem 
>> > > packages first), but I'll try and include it then. 
>> > 
>> > I've got basic event listening working.  It requires that all messages 
>> > are read asynchronously, so I'll need to change the interface to handle 
>> > that. 
>> > 
>> > Knowing when a page has finished loading isn't quite as simple as 
>> > looking for an event - a page can consist of multiple frames, and 
>> > notifications are delivered for each frame.  The page I'm interested in 
>> > has around 25 frames. 
>> > 
>> > If anyone has a good design 

Re: [Pharo-dev] Official cover for the Pharo booklet collection

[serge . stinckwich]

Nice !!!

Envoyé de mon iPhone

> Le 12 mai 2017 à 20:43, Stephane Ducasse  a écrit :
> 
> Tx damien
> 
> Stef
> 
> 

[Pharo-dev] GSOC Mentors - We need you.

[Serge Stinckwich]

Dear mentors,

we are currently reviewing all the students proposals. Please join the
#gsoc-planning on Discord for giving your insights about the students.
The deadline for the final selection will be Monday 24th 6pm CEST.

As a reminder, we have 5 slots given by Google this year.
Regards,
-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Tired of losing messages after 10k. Can we re-discuss moving Slack community to Discord?

[Serge Stinckwich]

On Fri, Apr 7, 2017 at 4:39 PM, philippe.b...@highoctane.be
<philippe.b...@gmail.com> wrote:
> We just invited gsoc students and we have the mentors channel running and
> then we shit things down.

We can keep this until the GSOC is finish.

-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

[Pharo-dev] Today is GSOC deadline

[Serge Stinckwich]

Dear all,

just a reminder for all mentors: the deadline for submitting
your GSOC proposal is today at 6pm CEST. You have to submit the final
pdf paper before that time.

Thank you.
Regards,
-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Pharo Papers

[Serge Stinckwich]

With Nick, we try to add the PHARO tag on some on our publications but
apparently he does appear in the list. Is it updated from time to time
?

Regards,

On Thu, Feb 23, 2017 at 10:57 AM, denker <marcus.den...@inria.fr> wrote:
> Hello,
>
> I have setup a collection at HAL. For now it is empty, we should fill it and 
> then add it to the website
> (and announce it then, not now…).
>
> The collection automatically has every paper on HAL that has “PHARO” as a 
> keyword in the field
> "Project/Collaboration”.
>
> https://hal.inria.fr/PHARO/
> https://hal.archives-ouvertes.fr/PHARO
>
> HAL is not Inria specific, here is some more infos (from 
> https://hal.archives-ouvertes.fr ):
>
> HAL is an open archive where authors can deposit scholarly documents 
> from all academic fields.
>
> For the attention of the authors
>
> • The deposit must be made in agreement with the co-authors 
> and in the respect for the policy of the publishers.
> • The deposit is subject of a control, HAL reserves the right 
> to refuse items that do not meet the criteria of the archive.
> • Any deposit is definitive, no withdrawals will be made 
> after the on-line posting of the publication.
> • Text files in pdf format or image files are sent to CINES 
> (https://www.cines.fr/en/) for long-term archiving.
>
> For the attention of the readers
>
> • In a context of electronic distribution, every author keep all its 
> intellectual property rights.
>
>
>
>
>> On 16 Feb 2017, at 15:13, denker <marcus.den...@inria.fr> wrote:
>>
>> One idea on my TODO that I got from colleagues here working on another 
>> OpenSource/Research
>> system (Sofa3D): to add all publication to the website automatically using 
>> HAL (the national french
>> paper database).
>>
>> It looks like this on the website:
>>   https://www.sofa-framework.org/applications/publications/
>>
>> and here “how to add a paper”:
>>
>>   
>> https://www.sofa-framework.org/applications/publications/add-a-publication-with-hal/
>>
>> I will definitely set this up for Pharo later this year (read: as soon as 
>> possible)
>>
>>   Marcus
>>
>>
>>> On 16 Feb 2017, at 14:30, Ben Coman <b...@openinworld.com> wrote:
>>>
>>> And now for your regularly scheduled random trivia show...
>>> I was mildly curious about how many papers touched on Pharo.
>>>
>>> 1,110 on google scholar for...
>>> "pharo" "programming"
>>> http://tiny.cc/pharo-scholar
>>>
>>> 1,630 on normal google for...
>>> "pharo" "programming" "abstract" "introduction" "conclusion"
>>> "references" filetype:pdf
>>> http://tiny.cc/pharo-papers
>>>
>>> Probably a lot of overlap between them.
>>> cheers -ben
>>>
>>
>
>



-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

[Pharo-dev] Fwd: GSoC 2017: Tips on Reviewing Student Proposals

[Serge Stinckwich]

Dear all,

this is a short update for the Google Summer of Code 2017.
The students have to submit your proposals on the Google website before
April 3rd.
See details below.

I dunno exactly who are the students/mentors who are submitting a proposal
for Pharo.
Can the mentors (or students) send me in private an email about the name of
the students/mentors + a title of your project ?

Thank you very much.

Regards,


-- Forwarded message --
From: Google Summer of Code <summerofcode-nore...@google.com>
Date: Mon, Mar 20, 2017 at 7:26 PM
Subject: GSoC 2017: Tips on Reviewing Student Proposals
To: sergestinckw...@gmail.com


[image: Google Summer of Code]

Hi Serge Stinckwich,

Thank you for registering to be a GSoC 2017 mentor or organization
administrator!

We have many new mentors and organizations this year so we wanted to go
through some important details to help you understand the process for the
next couple of months.

Please take the time to reach out to your organization administrator about
what is expected of you this year as a mentor. We also encourage you to
read the entire Google Summer of Code mentor manual
<http://write.flossmanuals.net/gsoc-mentoring/about-this-manual/> and the
Roles and Responsibilities doc if you haven't done so already. Both the
manual and Roles and Responsibilities doc were written by GSoC veteran Org
Admins, Mentors, former students and Google Program Admins. They have
helpful information about the program and how to participate successfully
at each step in GSoC.

*New GSoC Orgs*: the section about participating in your first GSoC has
some great tips.

To see all emails sent to mentors and org admins visit this page
<https://developers.google.com/open-source/gsoc/2017/mentor-oa-announcements>
that will continue to be updated throughout the program.
Student Proposals

As of today, students are able to submit their proposals via the website.
Each student may submit up to 5 proposals to the program. They can submit
multiple proposals to the same organization for different projects if they
wish.

Historically, the students with the best proposals reach out to the orgs
early to receive feedback before submitting their final proposal. To
encourage more students to seek feedback on their proposals we made draft
proposals part of the official proposal workflow. Be sure to refresh your
dashboard periodically so that you can see when new drafts are ready to
review. You will not receive an email. We are encouraging the use of Google
Docs for proposals as this will allow you to comment directly on the
proposal (if the student sets their sharing settings correctly).

Over the next couple of weeks you will be interacting with dozens and in
some cases hundreds of students interested in working with your project. We
know many of you may become overwhelmed and some students can be impatient,
so you may want to have an auto-responder or some sort of canned response
to let students know you are looking at their proposals but it could take X
days to receive a response.

Students *must* submit their final proposal as a PDF through the website.
It will be visible to you after the deadline for student applications
(April 3 16:00 UTC). You should make your decisions on which students to
accept based on the contents of the final PDF proposal and your
interactions with the student.

Students can delete their proposals and you will not receive an email of
the deletion. If a proposal disappears from your list, it is likely because
they deleted it.
Working with Students

All student projects must have at least 1 mentor assigned to the project.
We strongly encourage assigning a second mentor as a backup mentor or
co-mentor. A mentor should not be the primary mentor for more than one or
two students. Mentoring can be a lot of work and we don’t want anyone to
burn out and become frustrated with the program.
Important GSoC 2017 Dates and Deadlines

*March 20 - April 3 16:00 UTC*: Mentors and Org Admins review student draft
proposals and give students feedback on their proposals.
*April 3 - 16:* Review all submitted student proposals with your org and
consider how many you want to select and how many you can handle. Decide on
the minimum/maximum number of student slots to request.
*April 17, 16:00 UTC*: Deadline to submit slot requests (OAs enter requests)
*April 19, 16:00 UTC*: Slot allocations are announced by Google
*April 19 - 24 16:00 UTC* : Select the proposals to become student
projects. At least 1 mentor must be assigned to each project before it can
be selected. (OAs enter selections)
*April 24 - May 4:* Google Program Admins will do another review of student
eligibility
*May 4*: Accepted GSoC students/projects are announced
*May 4 - 29*: Community Bonding Period
*May 30*: Coding begins
*June 26-30*: First evaluation period - mentors evaluate students, students
evaluate mentors
*July 24 - 28*: Second evaluation period - mentors evaluate students,
students evaluate 

Re: [Pharo-dev] Helvetia in Pharo?

[Serge Stinckwich]

On Thu, Mar 2, 2017 at 8:51 PM, Tudor Girba <tu...@tudorgirba.com> wrote:
> Hi,
>
> Helvetia requires a couple of things:

BTW, with Nick Papoylias we have a working version of Helvetia for
Pharo 5.0/Moose 6.0 here:
https://github.com/UMMISCO/Helvetia

We have the permissions of Lukas Renggli and Oscar Nierstrasz to port
Helvetia to recent versions of Pharo.

We are using Helvetia for our own research about Domain-Specific Languages
for complex system especially in the context of the Kendrick DSL for
epidemiology: https://ummisco.github.io/kendrick/

> - Flexible parsing. Lukas built PetitParser for this and now PetitParser2 is 
> even faster and more powerful (for example, with bounded seas parsing) while 
> preserving the same flexibility.
> - Flexible compilation toolchain. At the time, Lukas employed a significant 
> amount of overrides. Now we have Opal which makes this step easier.

This has been the most difficult part of the port because the API
change a lot since the PhD of Lukas :-)
At the moment, the modifications that we have done are still a little
bit hackish and more integration with Opal has to be done in the
future.

> - Moldable development tools. GT was designed with moldability in mind so at 
> least the debugging part should be easier to handle. We still need work in 
> the area of syntax highlighting, completion and editing.


We will move soon the code on github so people could send pull requests.

Regards,
-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Google Summer of Code 2017: Call for mentors for Pharo Consortium

[Serge Stinckwich]

Dear all,

we have 10 mentors + 4 admin at the moment. We are looking for me !
Please join the #gsoc-planning Slack channel.
Thank you.

On Wed, Mar 1, 2017 at 1:45 PM, Serge Stinckwich
<serge.stinckw...@gmail.com> wrote:
> Heartiest Congratulations !
>
> Pharo Consortium has been selected as a mentor organisation for Google
> Summer of Code 2017.
>
> Google Summer of Code is a global program focused on introducing
> students to open source software development.
>
> Students work on a 3 month programming project with an open source
> organisation during their break from university. Read more at
> https://summerofcode.withgoogle.com/
>
> How the program works ?
>
> Organizations:
> Open source projects apply to be mentor organizations. Once accepted,
> organizations discuss possible ideas with students and then decide on
> the proposals they wish to mentor for the summer. They provide mentors
> to help guide each student through the program.
>
> Mentors:
> Existing contributors with the organizations can choose to mentor a
> student project. Mentors and students work together to determine
> appropriate milestones and requirements for the summer. Mentor
> interaction is a vital part of the program. A mentor may propose or
> endorse a project  and each project has to be about Pharo or its
> ecosystem (e.g., a library). Projects will be mentored by one or more
> mentors and executed by one student.
>
> Students:
> Students contact the mentor organizations they want to work with and
> write up a project proposal for the summer. If accepted, students
> spend a month integrating with their organizations prior to the start
> of coding. Students then have three months to code, meeting the
> deadlines agreed upon with their mentors. Student coding period: May
> 30 - Aug 29 (Entire timeline can be viewed at:
> https://summerofcode.withgoogle.com/how-it-works/#timeline). Student
> stipend: https://developers.google.com/open-source/gsoc/help/student-stipends
>
> We are currently at the phase of identifying mentors and projects. The
> next phases will be about students selecting projects, and the
> community selecting the projects with their associated mentors and
> students which will be sponsored by the GSOC program.
>
> How to register ?
> Simply by replying to this email and joining the Slack channel... to
> have more discussion about what project the mentor will take up, what
> she/he wants at the end of the coding period and then we can invite
> them to the GSoC org dashboard).
>
> Hence, we invite regular & enthusiastic Pharo contributors to be a
> mentor with Pharo Consortium for GSoC 2017:
>
> 1. Kindly respond on this thread if you'd like to be a mentor, or wish
> to propose a project.
>
> An existing list of projects is already available here:
> http://gsoc.pharo.org/ and we already have a handful of projects and
> mentors chosen. Feel free to collaborate with existing mentors as
> well.
>
> 2. Join dedicated channels, #gsoc-students for general interactions
> with students & #gsoc-planning channel only for GSOC admins and
> mentors on Pharo slack. In order to get an invitation for
> pharoproject.slack.com visit the URL here:
> http://slackinvites.pharo.org/
>
> 3. Please open relevant issues and make a roadmap of the projects
> being mentored by you so that students can start contributing to them
> already. If you want to mentor a project and there is no open-source
> repository at the moment, please built one ASAP.
>
> 4. If you know any students that might be interested to work on Pharo
> during the summer and be a part of GSoC as well, please ask him/her to
> start contributing to the Pharo projects, discuss their proposal,
> follow instructions that shall be posted soon in this mailing thread
> and submit their application by April 3, 2017.
> We don't know the number of slots attributed by Google to Pharo org,
> but the more students proposal we will receive, the more slots will be
> attributed to us.
>
> We remind you about the mentor responsibilities:
>
> ... to your Org Admins
>
> - Communicate availability and interaction expectations
> - Inform when mentoring capacity will be reduced, as early as possible
> (e.g., family, health, vacation)
> - Inform when there is an issue with a student
>- Lacking communication, activity, visibility (MIA), or progress
>- Participant Agreement violations (e.g., plagiarism, harassment, fraud)
>- Bad fit or stepping down
> - Formally evaluate student participation.
>- Communicate with admin and student before failing
>
> ... to your Students
>
> - Help and/or teach the student
>- how to be a part of your community
>- communicate

Re: [Pharo-dev] Google Summer of Code 2017: Call for mentors for Pharo Consortium

[Serge Stinckwich]

Please join the #gsoc-planning channel on Slack !

On Wed, Mar 1, 2017 at 8:16 PM, Max Leske <maxle...@gmail.com> wrote:
> Good stuff!
>
> I’m up for mentoring.
>
>> On 1 Mar 2017, at 13:45, Serge Stinckwich <serge.stinckw...@gmail.com> wrote:
>>
>> Heartiest Congratulations !
>>
>> Pharo Consortium has been selected as a mentor organisation for Google
>> Summer of Code 2017.
>>
>> Google Summer of Code is a global program focused on introducing
>> students to open source software development.
>>
>> Students work on a 3 month programming project with an open source
>> organisation during their break from university. Read more at
>> https://summerofcode.withgoogle.com/
>>
>> How the program works ?
>>
>> Organizations:
>> Open source projects apply to be mentor organizations. Once accepted,
>> organizations discuss possible ideas with students and then decide on
>> the proposals they wish to mentor for the summer. They provide mentors
>> to help guide each student through the program.
>>
>> Mentors:
>> Existing contributors with the organizations can choose to mentor a
>> student project. Mentors and students work together to determine
>> appropriate milestones and requirements for the summer. Mentor
>> interaction is a vital part of the program. A mentor may propose or
>> endorse a project  and each project has to be about Pharo or its
>> ecosystem (e.g., a library). Projects will be mentored by one or more
>> mentors and executed by one student.
>>
>> Students:
>> Students contact the mentor organizations they want to work with and
>> write up a project proposal for the summer. If accepted, students
>> spend a month integrating with their organizations prior to the start
>> of coding. Students then have three months to code, meeting the
>> deadlines agreed upon with their mentors. Student coding period: May
>> 30 - Aug 29 (Entire timeline can be viewed at:
>> https://summerofcode.withgoogle.com/how-it-works/#timeline). Student
>> stipend: https://developers.google.com/open-source/gsoc/help/student-stipends
>>
>> We are currently at the phase of identifying mentors and projects. The
>> next phases will be about students selecting projects, and the
>> community selecting the projects with their associated mentors and
>> students which will be sponsored by the GSOC program.
>>
>> How to register ?
>> Simply by replying to this email and joining the Slack channel... to
>> have more discussion about what project the mentor will take up, what
>> she/he wants at the end of the coding period and then we can invite
>> them to the GSoC org dashboard).
>>
>> Hence, we invite regular & enthusiastic Pharo contributors to be a
>> mentor with Pharo Consortium for GSoC 2017:
>>
>> 1. Kindly respond on this thread if you'd like to be a mentor, or wish
>> to propose a project.
>>
>> An existing list of projects is already available here:
>> http://gsoc.pharo.org/ and we already have a handful of projects and
>> mentors chosen. Feel free to collaborate with existing mentors as
>> well.
>>
>> 2. Join dedicated channels, #gsoc-students for general interactions
>> with students & #gsoc-planning channel only for GSOC admins and
>> mentors on Pharo slack. In order to get an invitation for
>> pharoproject.slack.com visit the URL here:
>> http://slackinvites.pharo.org/
>>
>> 3. Please open relevant issues and make a roadmap of the projects
>> being mentored by you so that students can start contributing to them
>> already. If you want to mentor a project and there is no open-source
>> repository at the moment, please built one ASAP.
>>
>> 4. If you know any students that might be interested to work on Pharo
>> during the summer and be a part of GSoC as well, please ask him/her to
>> start contributing to the Pharo projects, discuss their proposal,
>> follow instructions that shall be posted soon in this mailing thread
>> and submit their application by April 3, 2017.
>> We don't know the number of slots attributed by Google to Pharo org,
>> but the more students proposal we will receive, the more slots will be
>> attributed to us.
>>
>> We remind you about the mentor responsibilities:
>>
>> ... to your Org Admins
>>
>> - Communicate availability and interaction expectations
>> - Inform when mentoring capacity will be reduced, as early as possible
>> (e.g., family, health, vacation)
>> - Inform when there is an issue with a student
>>   - Lacking communi

[Pharo-dev] Google Summer of Code 2017: Call for mentors for Pharo Consortium

[Serge Stinckwich]

ons
- Re-evaluate scope with student when significantly ahead of or behind
expectations
- Work with devs and community to facilitate acceptance of student work

Read more about responsibilities here:
https://developers.google.com/open-source/gsoc/help/responsibilities

Looking forward to a great guided summer by the talented mentors of
our organisation.

Warm Regards
Pharo Organisation Admins
(Alexandre Bergel, Jigyasa Grover, Serge Stinckwich & Yuriy Tymchuk)

Re: [Pharo-dev] [Pharo-users] Fwd: GSoC 2017: Pharo Consortium has been accepted as a mentor organization!

[Serge Stinckwich]

On Mon, Feb 27, 2017 at 8:19 PM, Peter Uhnak <i.uh...@gmail.com> wrote:
>
> Congratulations!
>
> p.s. I think my name was there from last year (I didn't have time for this 
> this year), so if you encounter it anywhere, feel free to remove it.

BTW, I add you name, because you help a lot last year :-)

-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

[Pharo-dev] Fwd: GSoC 2017: Pharo Consortium has been accepted as a mentor organization!

[Serge Stinckwich]

Great news !

Thank you Jigyasa, Uko, Peter and Alex for your great work this year !


-- Forwarded message --
From: Google Summer of Code <summerofcode-nore...@google.com>
Date: Mon, Feb 27, 2017 at 6:00 PM
Subject: GSoC 2017: Pharo Consortium has been accepted as a mentor
organization!
To: sergestinckw...@gmail.com


[image: Google Summer of Code]

Congratulations! Pharo Consortium has been selected as a Google Summer of
Code 2017 mentor organization.

You can now invite mentors and update your organization profile.

Please click here to visit your dashboard: https://summerofcode.
withgoogle.com/dashboard/

This email was sent to serge.stinckw...@gmail.com.

You are receiving this email because of your participation in Google Summer
of Code 2017.
https://summerofcode.withgoogle.com

To leave the program and stop receiving all emails, you can go to your
profile <https://summerofcode.withgoogle.com/dashboard/profile/> and
request deletion of your program profile.

For any questions, please contact gsoc-supp...@google.com. Replies to this
message go to an unmonitored mailbox.

© 2017 Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA



-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] FileTree

[serge . stinckwich]

I don't understand because you can load your project in a Pharo image and save 
it as with FileTree.

Envoyé de mon iPhone

> Le 18 févr. 2017 à 13:09, Guillermo Polito <guillermopol...@gmail.com> a 
> écrit :
> 
> Hi Serge,
> 
> Jonathan is trying to convert some old code I have in here:
> 
> https://github.com/guillep/PharoCandle
> 
> to Filtree.
> 
> The thing is that at that moment I started that, FileTree was not there, So I 
> made my own format and my own parser based and PetitParser and the Smalltalk 
> petit parser that produced my own little meta-model :P.
> 
> But now we want to move to the standard tools of today.
> 
> What we would like to know is what should we use to write FileTree from 
> something that is not Monticello, what is the class to look at, and the API 
> to use.
> 
> ANY information is welcome :)
> 
> Thanks,
> Guille
> 
>> On Fri, Feb 17, 2017 at 5:22 PM, Jonathan Khalil <jonat...@esp.sn> wrote:
>> Oh really ? My school is Ecole Supérieur Polytechnique (ESP).
>> 
>> I want to rewrite the pharoCandle in the FileTree format but i don't know 
>> where to start. 
>> 
>> Jonathan
>> 
>> 2017-02-17 16:37 GMT+01:00 Serge Stinckwich <serge.stinckw...@gmail.com>:
>>> On Fri, Feb 17, 2017 at 3:06 PM, Jonathan Khalil <jonat...@esp.sn> wrote:
>>> > Hi everyone,
>>> >
>>> > I'm Jonathan, student in master, from Dakar, Sénégal and i will be working
>>> > with stephane ducasse's team for my internship.
>>> 
>>> Great Jonathan. Where are you located ? My research team is working in
>>> Senegal in Dakar and St-Louis.
>>> 
>>> > I need some lectures on FileTree.
>>> > Someone know how can i get it ?
>>> 
>>> What kind of information you are looking for FileTree ?
>>> I'm not sure that there is that much information about it except the code 
>>> :-)
>>> 
>>> https://github.com/dalehenrich/filetree
>>> 
>>> Regards,
>>> --
>>> Serge Stinckwich
>>> UCBN & UMI UMMISCO 209 (IRD/UPMC)
>>> Every DSL ends up being Smalltalk
>>> http://www.doesnotunderstand.org/
>>> 
>> 
> 

Re: [Pharo-dev] FileTree

[Serge Stinckwich]

On Fri, Feb 17, 2017 at 3:06 PM, Jonathan Khalil <jonat...@esp.sn> wrote:
> Hi everyone,
>
> I'm Jonathan, student in master, from Dakar, Sénégal and i will be working
> with stephane ducasse's team for my internship.

Great Jonathan. Where are you located ? My research team is working in
Senegal in Dakar and St-Louis.

> I need some lectures on FileTree.
> Someone know how can i get it ?

What kind of information you are looking for FileTree ?
I'm not sure that there is that much information about it except the code :-)

https://github.com/dalehenrich/filetree

Regards,
-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Pharo Papers

[Serge Stinckwich]

Yes definitively will be nice to have a list of research about Pharo
or based on Pharo.
Thank you Marcus.

On Thu, Feb 16, 2017 at 3:13 PM, denker <marcus.den...@inria.fr> wrote:
> One idea on my TODO that I got from colleagues here working on another
> OpenSource/Research
> system (Sofa3D): to add all publication to the website automatically using
> HAL (the national french
> paper database).
>
> It looks like this on the website:
> https://www.sofa-framework.org/applications/publications/
>
> and here “how to add a paper”:
>
> https://www.sofa-framework.org/applications/publications/add-a-publication-with-hal/
>
> I will definitely set this up for Pharo later this year (read: as soon as
> possible)
>
> Marcus
>
>
> On 16 Feb 2017, at 14:30, Ben Coman <b...@openinworld.com> wrote:
>
> And now for your regularly scheduled random trivia show...
> I was mildly curious about how many papers touched on Pharo.
>
> 1,110 on google scholar for...
> "pharo" "programming"
> http://tiny.cc/pharo-scholar
>
> 1,630 on normal google for...
> "pharo" "programming" "abstract" "introduction" "conclusion"
> "references" filetype:pdf
> http://tiny.cc/pharo-papers
>
> Probably a lot of overlap between them.
> cheers -ben
>
>



-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

[Pharo-dev] GSOC Pharo application done

[Serge Stinckwich]

Dear all,

thanks to the efforts of Jigyasa Grover,  Yuriy Tymchuk and Alexandre
Bergel, , we were able to have a GSOC 2017 application for the Pharo
Consortium. This is only the first phase. If we are selected by
Google, they will give some slots for students.

We have a list of projects for GSOC here : http://gsoc.pharo.org/

If you have more ideas, please send them to me or send a PR on :
https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics.st

Try to describe your project idea with 10-15 lines maximum.
The ideas is not too much projects proposals but to find important
projects for the Pharo community (i.e that will have some impact for
the community) with the support of the appropriate mentors.

I would like to have maximum 2-3 projects for each mentors.

Thank you.
Cheers,
-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] [Pharo-users] Final rush for submitting GSOC proposal - Need your help

[Serge Stinckwich]

On Thu, Feb 9, 2017 at 5:28 PM, Stephan Eggermont <step...@stack.nl> wrote:
> On 09/02/17 17:05, Serge Stinckwich wrote:
>>
>> but all the projects are coming from RMOD team, but having all the
>> projects proposal coming from the same place might be perceived
>> negatively from Google. Can we add more projects from previous gsoc
>> from other people also ?
>
>
> My two earlier proposals are fine, and already on the site.

Can you reduce the size of the "Distributed Issue Tracker" subject
because there is too much details compared to other subjects.

Thank you.
-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Slack, fragmentation and design information

[Serge Stinckwich]

On Fri, Feb 10, 2017 at 10:58 AM, Esteban Lorenzano <esteba...@gmail.com> wrote:
> Hi Stephan,
>
>> On 10 Feb 2017, at 10:27, Stephan Eggermont <step...@stack.nl> wrote:
>>
>> The past year we have started using Slack to communicate in real-time about 
>> Pharo. It has nice (mobile) clients and makes it easy to share pictures and 
>> snippets. As a result a large part of the communication about design and how 
>> to do things has moved from the mailing lists to Slack. As we're using the 
>> free version, and cannot afford to use the commercial version, we have no 
>> long-time storage of the design discussions. This contrasts with our mailing 
>> lists, that have a long-term archive. There was some discussion about this, 
>> and I'm not aware of that resulting in an accessible, easy to access 
>> archive. Also, we have not succeeded in summarizing design discussions from 
>> slack to the mailing lists. The resulting gap in design information forms an 
>> enormous long-term risk for our community. Without the design discussions it 
>> is much more difficult to later understand why decisions were taken. We 
>> cannot afford to let this short-term ease-of-use destroy Pharo's community 
>> history, and thereby Pharo. Let us fix this.

Yes I agree with your concerns.

> I share many of what you say… but in the other point of view, Slack as really 
> worked and there is a lot more happening now in Slack + mailing list than 
> what was before just in mailing list.
> But most of that is lost because of Slack policies (also Slack pricing model 
> is impossible for a community as ours), and we need to find a solution for 
> that.

Yes this is too expensive for the Pharo consortium ?

> Last days we were experimenting with @kilon again on use discord as a 
> substitute and I find that for now it works really well and with a bit of 
> work we can have all what you want: discord incorporated a search function 
> (and they do not have the 10k limit) and we could do a bot that logs 
> everything that happens there and stores that into gists (or whatever, but 
> gists seems like a good idea).
>
> With this we would have enhanced the availability of those discussions (it 
> remains the fact that immediate communication is worst organised than mails, 
> but well… we need to try)

and move all the community on discord ? Or use an open-source slack
like : https://about.mattermost.com/
and host our own chat server.

-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Final rush for submitting GSOC proposal - Need your help

[serge . stinckwich]

Ok can you send me again your projects.
I will integrate them. Try to put maximum 10-15 lines for description.


Envoyé de mon iPhone

> Le 9 févr. 2017 à 18:06, "p...@highoctane.be" <p...@highoctane.be> a écrit :
> 
> I think that I send a couple topics before.
> 
>> On Thu, Feb 9, 2017 at 5:05 PM, Serge Stinckwich 
>> <serge.stinckw...@gmail.com> wrote:
>> Hi all,
>> 
>> we are currently working with Alexandre to submit the gsoc proposal to 
>> Google.
>> I was a little bit busy with my lectures and I didn't check the
>> current proposals available here:
>> 
>> http://gsoc.pharo.org/
>> 
>> but all the projects are coming from RMOD team, but having all the
>> projects proposal coming from the same place might be perceived
>> negatively from Google. Can we add more projects from previous gsoc
>> form other people also ?
>> 
>> We have only one hour to polish the list.
>> Thank you for your help.
>> 
>> --
>> Serge Stinckwich
>> UCBN & UMI UMMISCO 209 (IRD/UPMC)
>> Every DSL ends up being Smalltalk
>> http://www.doesnotunderstand.org/
>> 
> 

Re: [Pharo-dev] [Pharo-users] Final rush for submitting GSOC proposal - Need your help

[Serge Stinckwich]

Yes, thank you Stephan. I just add them ;-)

I think we can change the list of projects until tomorrow.

Regards,

On Thu, Feb 9, 2017 at 5:28 PM, Stephan Eggermont <step...@stack.nl> wrote:
> On 09/02/17 17:05, Serge Stinckwich wrote:
>>
>> but all the projects are coming from RMOD team, but having all the
>> projects proposal coming from the same place might be perceived
>> negatively from Google. Can we add more projects from previous gsoc
>> from other people also ?
>
>
> My two earlier proposals are fine, and already on the site.
>
> Stephan
>
>
>



-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

[Pharo-dev] Final rush for submitting GSOC proposal - Need your help

[Serge Stinckwich]

Hi all,

we are currently working with Alexandre to submit the gsoc proposal to Google.
I was a little bit busy with my lectures and I didn't check the
current proposals available here:

http://gsoc.pharo.org/

but all the projects are coming from RMOD team, but having all the
projects proposal coming from the same place might be perceived
negatively from Google. Can we add more projects from previous gsoc
form other people also ?

We have only one hour to polish the list.
Thank you for your help.

-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] [QA] quality assurance

[serge . stinckwich]

Great ! Thank you Hilaire. I will help when I'm free.

Envoyé de mon iPhone

> Le 6 févr. 2017 à 00:38, Ben Coman  a écrit :
> 
>> On Mon, Feb 6, 2017 at 4:51 AM, Hilaire  wrote:
>> Hi,
>> 
>> I discussed briefly with Steph about QA team and dedicated mailing list.
>> He proposed to just use the @devel list with an appropriate [QA] tag, so
>> every one can participate or just discard the topic without too much noise.
> 
> That seems appropriate.
> A separate list makes it hard to draw new people in to help.
> And part of the discussion can occur on the Fogbugz.
> 
> cheers -ben
> 

Re: [Pharo-dev] Pharo 6 update catalog entries

[Serge Stinckwich]

I update PolyMath for Pharo 6.0.
All tests are green: https://github.com/PolyMathOrg/PolyMath

On Tue, Jan 31, 2017 at 10:44 AM, Torsten Bergmann <asta...@gmx.de> wrote:
> Hi,
>
> in preparation of upcoming Pharo 6 release we already should do a pass on
> all our external loadable projects:
>
>  - load them into Pharo 6 to see if they could be loaded cleanly
>(due to automatic transformation of deprecated messages your packages
> get dirty when converted)
>  - check if they are already/still working in Pharo 6 by using them
>  - check that the tests are running in Pharo 6
>  - check that we have a proper config with catalog methods and
>that the latest config is in the MetaRepoForPharo60 repository
>http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo60
>
> I did a pass over most projects I implemented or contributed to
> and we now have much more Pharo 6 based projects in catalog:
>
>  - Units, Artefact
>  - EventRecorder, Bugzilla, PunQlite, HubCap, VistaCursors, INIFile
>  - Pomodoro, DesktopManager, QuickAccess, WebBrowser, MessageFlowBrowser
>  - ScriptManager (now with icons)
>  - Tealight, Teapot, Nginx, NPMJS, GitHubAPI, FogBugz
>  - OSWindows, OSOSX, OSUnix, OSLinuxCentOS, OSLinuxUbuntu, OSRaspbian
>  - ...
>
> You should do the same with your projects!
>
> Also if you have a project on SqueakSource, STHub or GitHub that
> is not yet in the catalog it would be good to provide a ConfigurationOf...
> with a catalog description. Using Versionner it is easy to create one
> or generate the required catalog methods.
>
> This would give more visibility to your projects!
>
> Thanks
> T.
>



-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Google summer of code

[Serge Stinckwich]

On Wed, Jan 25, 2017 at 7:38 AM, Stephan Eggermont <step...@stack.nl> wrote:
> On 24/01/17 10:11, Guillermo Polito wrote:
>>
>> Besides, I'm interested in knowing the official reasons for why we were
>> rejected last years :P.
>
>
> That's the always the same: we get many more applications than we can
> sponsor, and we have to make a choice.

+1
yes we receive this answer last year.

One option to enhance the situation this year is maybe to have less
projects proposed by Pharo community (10-12 ?) but with more detailed
explanations. Apparently this is something important to be accepted as
an organisation by Google.

There is a small team with Jigyasa, Yuriy, Alexandre who is working on that.
If you have ideas and want to help, you can join #gsoc-planning on Slack.

Thank you.
Regards,

-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Pharo by Example 50 released!

[Serge Stinckwich]

Congrats for the hard work !

On Sun, Jan 22, 2017 at 4:53 PM, stepharong <stephar...@free.fr> wrote:
> https://pharoweekly.wordpress.com/2017/01/22/pharo-by-example-50-released/
>
> Super special thanks to Nicolai Hess that pushed me to do the last steps to
> release.
> Thanks Nicolai your steady commits pushed me!
>
> Stef
>



-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Google summer of code

[Serge Stinckwich]

Thank you Uko to join the team :-)

On Mon, Jan 23, 2017 at 5:15 PM, Yuriy Tymchuk <yuriy.tymc...@me.com> wrote:
> I can also update my projects and help with the application if needed (I was
> a part of the application team for the last two years I think)
>
> Uko
>
> On 22 Jan 2017, at 16:33, Jigyasa Grover <grover.jigya...@gmail.com> wrote:
>
> Also, a good application is equally important as the list of clearly defined
> projects.
>
> - J
>
> On Sun, Jan 22, 2017 at 4:30 PM, Serge Stinckwich
> <serge.stinckw...@gmail.com> wrote:
>>
>> The list of previous projects is here:
>> https://github.com/pharo-project/pharo-project-proposals
>>
>> On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover
>> <grover.jigya...@gmail.com> wrote:
>> > Dear Prof Serge
>> >
>> > Thanks for the introduction.
>> >
>> > Dear Alexandre
>> > I have been a past Google Summer of Code student and also mentor budding
>> > developers in Google Code-In.
>> > This time, I was hoping to plug-in the loopholes which might have been
>> > present in last year's organisation application.
>> > Kindly let me know how can we collaborate further on this.
>> > Looking forward to your response.
>> > Thanks and Regards
>> > Jigyasa
>> >
>> >
>> > On Sat, Jan 21, 2017 at 9:06 AM, <serge.stinckw...@gmail.com> wrote:
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> Envoyé de mon iPhone
>> >> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk <yuriy.tymc...@me.com> a écrit
>> >> :
>> >>
>> >> What do we do?
>> >>
>> >>
>> >>
>> >> We have to apply ! ;-)
>> >>
>> >> We talk with Jigyasa Grover who is doing an internship in my lab at the
>> >> moment and she is willing to help. Jigyasa was a student in a former
>> >> Google
>> >> Summer of code and is involved in several open-source initiative like
>> >> Women
>> >> who Code and FOSSASIA. She is a mentor of GoogleCodeIn.
>> >>
>> >> You can find a small presentation during last FOSSASIA : "
>> >>
>> >> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA
>> >> 2016"
>> >>
>> >> https://m.youtube.com/watch?v=uLIzylxvIz4
>> >>
>> >> She has done a streaming video this morning also: http://goo.gl/UyclKP
>> >> http://youtube.com/watch?v=2iRG_jpOL54
>> >>
>> >> Anyone to help her setup a small team for Pharo proposal to Google
>> >> Summer
>> >> of Code this year ?
>> >>
>> >>
>> >> On 20 Jan 2017, at 20:38, Alexandre Bergel <alexandre.ber...@me.com>
>> >> wrote:
>> >>
>> >> Hi everyone-
>> >>
>> >> Google Summer of Code 2017 has officially begun! Organization
>> >> applications
>> >> open today, Thursday January 19 and are open through Thursday, February
>> >> 9th.
>> >> Please see our program site, official timeline and FAQ for more
>> >> details.
>> >>
>> >> What makes a good organization application? Take a look at our manuals
>> >> for
>> >> tips and best practices.
>> >>
>> >> We look forward to seeing each of your applications and kicking off
>> >> another great year of GSoC. If you have any questions, don’t hesitate
>> >> to
>> >> reach out to gsoc-supp...@google.com. We’re here to help!
>> >>
>> >> Google Open Source Programs Office
>> >> --
>> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> >> Alexandre Bergel  http://www.bergel.eu
>> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> >>
>> >>
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Serge Stinckwich
>> UCBN & UMI UMMISCO 209 (IRD/UPMC)
>> Every DSL ends up being Smalltalk
>> http://www.doesnotunderstand.org/
>>
>
>



-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Google summer of code

[Serge Stinckwich]

The list of previous projects is here:
https://github.com/pharo-project/pharo-project-proposals

On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover
<grover.jigya...@gmail.com> wrote:
> Dear Prof Serge
>
> Thanks for the introduction.
>
> Dear Alexandre
> I have been a past Google Summer of Code student and also mentor budding
> developers in Google Code-In.
> This time, I was hoping to plug-in the loopholes which might have been
> present in last year's organisation application.
> Kindly let me know how can we collaborate further on this.
> Looking forward to your response.
> Thanks and Regards
> Jigyasa
>
>
> On Sat, Jan 21, 2017 at 9:06 AM, <serge.stinckw...@gmail.com> wrote:
>>
>>
>>
>>
>>
>> Envoyé de mon iPhone
>> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk <yuriy.tymc...@me.com> a écrit :
>>
>> What do we do?
>>
>>
>>
>> We have to apply ! ;-)
>>
>> We talk with Jigyasa Grover who is doing an internship in my lab at the
>> moment and she is willing to help. Jigyasa was a student in a former Google
>> Summer of code and is involved in several open-source initiative like Women
>> who Code and FOSSASIA. She is a mentor of GoogleCodeIn.
>>
>> You can find a small presentation during last FOSSASIA : "
>>
>> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA
>> 2016"
>>
>> https://m.youtube.com/watch?v=uLIzylxvIz4
>>
>> She has done a streaming video this morning also: http://goo.gl/UyclKP
>> http://youtube.com/watch?v=2iRG_jpOL54
>>
>> Anyone to help her setup a small team for Pharo proposal to Google Summer
>> of Code this year ?
>>
>>
>> On 20 Jan 2017, at 20:38, Alexandre Bergel <alexandre.ber...@me.com>
>> wrote:
>>
>> Hi everyone-
>>
>> Google Summer of Code 2017 has officially begun! Organization applications
>> open today, Thursday January 19 and are open through Thursday, February 9th.
>> Please see our program site, official timeline and FAQ for more details.
>>
>> What makes a good organization application? Take a look at our manuals for
>> tips and best practices.
>>
>> We look forward to seeing each of your applications and kicking off
>> another great year of GSoC. If you have any questions, don’t hesitate to
>> reach out to gsoc-supp...@google.com. We’re here to help!
>>
>> Google Open Source Programs Office
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>



-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Google summer of code

[serge . stinckwich]

Envoyé de mon iPhone
> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk  a écrit :
> 
> What do we do?


We have to apply ! ;-)

We talk with Jigyasa Grover who is doing an internship in my lab at the moment 
and she is willing to help. Jigyasa was a student in a former Google Summer of 
code and is involved in several open-source initiative like Women who Code and 
FOSSASIA. She is a mentor of GoogleCodeIn.

You can find a small presentation during last FOSSASIA : "
My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA 2016"
https://m.youtube.com/watch?v=uLIzylxvIz4

She has done a streaming video this morning also: http://goo.gl/UyclKP
http://youtube.com/watch?v=2iRG_jpOL54

Anyone to help her setup a small team for Pharo proposal to Google Summer of 
Code this year ?

> 
>> On 20 Jan 2017, at 20:38, Alexandre Bergel  wrote:
>> 
>> Hi everyone- 
>> 
>> Google Summer of Code 2017 has officially begun! Organization applications 
>> open today, Thursday January 19 and are open through Thursday, February 9th. 
>> Please see our program site, official timeline and FAQ for more details.
>> 
>> What makes a good organization application? Take a look at our manuals for 
>> tips and best practices. 
>> 
>> We look forward to seeing each of your applications and kicking off another 
>> great year of GSoC. If you have any questions, don’t hesitate to reach out 
>> to gsoc-supp...@google.com. We’re here to help!
>> 
>> Google Open Source Programs Office
>> -- 
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> 
>> 
>> 
>