- Pharo-users - lists.pharo.org

A Genetic Algorithms Framework for Pharo

by Alidra Abdelghani

Hi, I just implemented (the kernel of) a Framework for genetic algorithms (https://en.wikipedia.org/wiki/Genetic_algorithm <https://en.wikipedia.org/wiki/Genetic_algorithm>) in Pharo. Some of you could be dealing with optimisation problems. So maybe it could be useful for you. I implemented some basic functionalities : monoobjecitve, multi objective, a crossover and mutation operators, uniform selection... I also implemented some basic exemples ( mono/multi knapsack and travelling salesman) I still need to provide some documentation but there are lot of tests so it is easy to see how it works. I will add more operators from time to time. The code is intended to be as easy to reuse as possible. It is on Smalltalkhub : http://smalltalkhub.com/#!/~Alidra/GeneticAlgorithmsFramework/ <http://smalltalkhub.com/#!/~Alidra/GeneticAlgorithmsFramework/> Please take a look and tell me what you think. I will be pleased to help if you think the Framework can apply to your problem. just let me know :) Abdelghani

Dec. 8, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by Ben Coman

On 8 December 2017 at 03:38, horrido <horrido.hobbies(a)gmail.com> wrote: > I've completed the first draft of my Pharo Quick Start guide > <https://medium.com/@richardeng/pharo-quick-start-5bab70944ce2> . I > decided > to forge ahead anyway. > > Feedback welcome. > > Note that I chose wget instead of curl because many Linux distros do not > have curl installed. > > I've tested the guide for various Linux distros including Mint 18.3 > (Ubuntu-based), Debian 9.2.1, Manjaro 17.0.6 (Arch-based), Solus 3, and > Fedora 27. So it should be good for all the popular distros (Top 10). > Good work. Really nice and succulent. Some random feedback... > due to a known macOS bug, the Pharo application will crash the first time due to a known macOS bug >>> being investigated <<<, the Pharo application >>>>may<<< crash the first time (I presume it is) > To open the System Browser, click on... To open the System Browser, left-click on... *Most* newcomers will assume getting a menu is a right-click (btw like every other menu in Pharo) but Pharo is different here. I do believe we should change it to right-click to lower friction, or even both left-click and right-click to keep newcomers and stalwarts happy. How often does anyone right-click on the World? Could it be moved to a modifier key? > Now we need to create a method or function for our Greeter class. The standard first method is âinitializeâ which is invoked when the Greeter class is instantiated (this is OOP parlance). For simplicity, we shall skip this. For simplicity, just leave it out. ------------------- Now that sparks an idea for a follow-on article "Pharo - the next ten minutes" * show how easy GUI text output is easy (its another equivalent to the printf debugging paradigm every knows) Greeter >> screamIt self inform: 'HELLO WORLD!' * show nice process management and DSLish language Greeter >> counter | count | count := 0. [ count := count + 1. self inform: count printString. 2 seconds wait. ] forkNamed: 'Count de Money' "see..[1]" then World > Tools > Process Browser to Suspend,Resume, Terminate. * show unique feature with continuation of state across sessions... run "Greeter new counter" the get them to close the image and reopen it. cheers -ben P.S. side humor... [1] https://www.youtube.com/watch?v=sztf4hcGrB4

Dec. 8, 2017

Re: [Pharo-users] reloading ffi library

by Esteban Lorenzano

> On 7 Dec 2017, at 17:43, Ben Coman <btc(a)openInWorld.com> wrote: > > >> On 7 Dec 2017, at 16:04, Steven Costiou <steven.costiou(a)kloum.io <mailto:steven.costiou@kloum.io>> wrote: >> >> Hi, >> >> noob question: i installed bloc and tried to run examples. >> >> It worked well on Fedora 27 but not on latest Debian 64 bits because the path of libcairo.so.2 was wrong. >> >> So i fixed it in the code, but when trying the bloc examples again the lib path is still wrong (in the debugger). >> >> >> Is there a way to reload the cairo lib or to reset it, so that the path would be right and it would find the lib ? >> > > I've also been frustrated by this, particularly as a supa-fresh-FFI-noob before I understood what was happening. > I've found it a minor annoyance but sufficient to to close and reopen an image to reset things, > but being able to do it live in-Image is really nice. probably what we need to do is to include cairo library into our distribution as we do with others. this will minimise the problem from one side, but it will enlarge it in other (some distros disallow/discourage the inclusion of 3rd party libraries with your binary) Esteban > > On 7 December 2017 at 23:41, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > you need to reset FFI: > > FFIMethodRegistry resetAll. > > That is really nice to know, but by the time I need it I will probably have forgotten it, > and closing/reopening the Image will be faster than searching forum.world.st <http://forum.world.st/> or asking again the mail list. > Could we possibly have World > Tools > Reset FFI ? > > cheers -ben

Dec. 8, 2017

Re: [Pharo-users] reloading ffi library

by Ben Coman

On 8 December 2017 at 03:40, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Thanks Ben. > I have a question. Would it make sense to have a setting to reset on > each session the registry? > Naively I'd presume it must always do this to cover: * the OS upgrading libraries * moving images between OS platforms and dropping the old platform's FFI in memory * moving images between flavours of Linux where libraries are in different locations * moving images between 64bit & 32bit VMs (or wait! I forget if thats possible?) What are the use cases where you would *not* reset the FFI registry each session? What you should know is that Guille is actively improving > (refactoring, rethinking the API of iceberg) to produce a better UI then. > We are really concerned how we can get the same confort than we got before. > We do not send all the exchanges we have on the topics > Understood. Email is a broad but narrow channel. Although if you use a whiteboard to brainstorm, a quick phone photo & summary notes to the mail list is a good way to ensure all participants are aligned as well as keep the community informed. cheers -ben > On Thu, Dec 7, 2017 at 5:52 PM, Ben Coman <btc(a)openinworld.com> wrote: > > On 8 December 2017 at 00:43, Ben Coman <btc(a)openinworld.com> wrote: > >>> > >>> > >>> On 7 Dec 2017, at 16:04, Steven Costiou <steven.costiou(a)kloum.io> > wrote: > >>> > >>> Hi, > >>> > >>> noob question: i installed bloc and tried to run examples. > >>> > >>> It worked well on Fedora 27 but not on latest Debian 64 bits because > the path of libcairo.so.2 was wrong. > >>> > >>> So i fixed it in the code, but when trying the bloc examples again the > lib path is still wrong (in the debugger). > >>> > >>> > >>> > >>> Is there a way to reload the cairo lib or to reset it, so that the > path would be right and it would find the lib ? > >> > >> I've also been frustrated by this, particularly as a > supa-fresh-FFI-noob before I understood what was happening. > >> I've found it a minor annoyance but sufficient to to close and reopen > an image to reset things, > >> but being able to do it live in-Image is really nice. > >> > >> On 7 December 2017 at 23:41, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >>> > >>> you need to reset FFI: > >>> > >>> FFIMethodRegistry resetAll. > >> > >> > >> That is really nice to know, but by the time I need it I will probably > have forgotten it, > >> and closing/reopening the Image will be faster than searching > forum.world.st or asking again the mail list. > >> Could we possibly have World > Tools > Reset FFI ? > >> > >> cheers -ben > > > > Added https://pharo.fogbugz.com/f/cases/20835/Add-World-Tools-Reset-FFI > > I should have a go at doing it, but I'm not sure which class is > > preferred to hang the menu pragma on, > > and also I'm still lagging for contributing to Pharo 7 (not really any > > technical issue now, but lack of time to practice the workflow) > > > > cheers -ben > > > >

Dec. 8, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by Sean P. DeNigris

hernanmd wrote > To me the Hello World in Smalltalk was always just writing: 'Hello world' +1. While putting it in a class shows a few more of the system's features, it also makes it seem more complex than other languages, when that's not really true. Why not just PrintIt: 'Hello world'? If it seems important to show classes, maybe start with PrintIt: 'Hello world' and step-by-step build through `Transcript show: 'Hello world'` to the class-based solution. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 8, 2017

Re: [Pharo-users] ZnUrls with Non-ASCII characters

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > It would probably be possible to write a more lenient parser as opposed to > a strict one. I have not yet given that idea much thought. K, thanks for the explanation and assistance. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 8, 2017

Re: [Pharo-users] Hello world as initial example

by Richard A. O'Keefe

> From: Offray Vladimir Luna C?rdenas <offray.luna(a)mutabit.com> > That being said, I have always felt that hello world is kind of a > strange introduction to programming: Surely the traditional Smalltalk first step is 1. Open Workspace/Playground. 2. Type 3+4. 3. Cmd-P ? If I can remember that far back, my first exercise was 2+3) 1 <print it> 4+5) 1 class <print it> 6+7) 1 class class <print it> 8+9) 1 class browse <do it> 10) <quit do not save> Having read the three coloured books and Inside Smalltalk -- now freely available and thank you SO MUCH for that -- the language wasn't that strange, but the user interface was utterly unlike anything I'd ever used before, even my beloved Interlisp-D. These days, Pharo-the-IDE is enough different that those books don't help as much as they did when I met Squeak. (For that matter, I am still fairly helpless with VisualAge Smalltalk because of differences in the UI.) Come to think of it, lesson 1 ought to be "how to shut Pharo down". It's the first thing I look for in any programming environment these days.

Dec. 8, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by HernÃ¡n Morales Durand

To me the Hello World in Smalltalk was always just writing: 'Hello world' 2017-12-07 19:35 GMT-03:00 horrido <horrido.hobbies(a)gmail.com>: > Done. Class #Hello is now #Greeter in package "HelloDemo". > > I presume we're good to go, then? > > > > Offray Vladimir Luna CÃ¡rdenas-2 wrote >> May be the class name could be changed a little bit to allow more >> flexibility using the Pharo Quick Start as a base. Something like >> "Greeter" and "Greeter new say: 'Hello world!'" or "Greeter new sayIt" >> could be implemented from there. Nice to see more and more documentation >> around Pharo, including this one. >> >> That being said, I have always felt that hello world is kind of a >> strange introduction to programming: >> >> http://mutabit.com/offray/blog/en/entry/dumb-hello-world >> >> Cheers, >> >> Offray >> >> >> On 07/12/17 15:31, horrido wrote: >>> I've revised the draft slightly for the comments given here: >>> https://medium.com/@richardeng/pharo-quick-start-5bab70944ce2 >>> >>> Yes, it's a definite improvement. Thanks. >>> >>> >>> >>> Richard Sargent wrote >>>> Excellent work, Richard! >>>> >>>> May I offer the small criticism against using #initialize for the method >>>> name? I think a name like #sayIt (for example) and invocation like >>>> "Hello >>>> new sayIt" would make it explicit. >>>> >>>> This will be a great help for people who drop by out of curiosity. >>>> >>>> >>>> On Thu, Dec 7, 2017 at 11:38 AM, horrido < >>>> horrido.hobbies@ >>>> > wrote: >>>> >>>>> I've completed the first draft of my Pharo Quick Start guide >>>>> <https://medium.com/@richardeng/pharo-quick-start-5bab70944ce2> >>>>> . >>>>> I >>>>> decided >>>>> to forge ahead anyway. >>>>> >>>>> Feedback welcome. >>>>> >>>>> Note that I chose wget instead of curl because many Linux distros do >>>>> not >>>>> have curl installed. >>>>> >>>>> I've tested the guide for various Linux distros including Mint 18.3 >>>>> (Ubuntu-based), Debian 9.2.1, Manjaro 17.0.6 (Arch-based), Solus 3, and >>>>> Fedora 27. So it should be good for all the popular distros (Top 10). >>>>> >>>>> >>>>> >>>>> -- >>>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>>>> >>>>> >>> >>> >>> >>> >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >>> > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Dec. 8, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by horrido

Done. Class #Hello is now #Greeter in package "HelloDemo". I presume we're good to go, then? Offray Vladimir Luna CÃ¡rdenas-2 wrote > May be the class name could be changed a little bit to allow more > flexibility using the Pharo Quick Start as a base. Something like > "Greeter" and "Greeter new say: 'Hello world!'" or "Greeter new sayIt" > could be implemented from there. Nice to see more and more documentation > around Pharo, including this one. > > That being said, I have always felt that hello world is kind of a > strange introduction to programming: > > http://mutabit.com/offray/blog/en/entry/dumb-hello-world > > Cheers, > > Offray > > > On 07/12/17 15:31, horrido wrote: >> I've revised the draft slightly for the comments given here: >> https://medium.com/@richardeng/pharo-quick-start-5bab70944ce2 >> >> Yes, it's a definite improvement. Thanks. >> >> >> >> Richard Sargent wrote >>> Excellent work, Richard! >>> >>> May I offer the small criticism against using #initialize for the method >>> name? I think a name like #sayIt (for example) and invocation like >>> "Hello >>> new sayIt" would make it explicit. >>> >>> This will be a great help for people who drop by out of curiosity. >>> >>> >>> On Thu, Dec 7, 2017 at 11:38 AM, horrido < >>> horrido.hobbies@ >>> > wrote: >>> >>>> I've completed the first draft of my Pharo Quick Start guide >>>> <https://medium.com/@richardeng/pharo-quick-start-5bab70944ce2> >>>> . >>>> I >>>> decided >>>> to forge ahead anyway. >>>> >>>> Feedback welcome. >>>> >>>> Note that I chose wget instead of curl because many Linux distros do >>>> not >>>> have curl installed. >>>> >>>> I've tested the guide for various Linux distros including Mint 18.3 >>>> (Ubuntu-based), Debian 9.2.1, Manjaro 17.0.6 (Arch-based), Solus 3, and >>>> Fedora 27. So it should be good for all the popular distros (Top 10). >>>> >>>> >>>> >>>> -- >>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>>> >>>> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 7, 2017

Re: [Pharo-users] ZnUrls with Non-ASCII characters

by Sven Van Caekenberghe

> On 7 Dec 2017, at 18:00, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Why not: > 'https://en.wiktionary.org/wiki/prÃªt#French' asUrl => > https://en.wiktionary.org/wiki/pr%C3%AAt#French > ? #asUrl invokes the URL parser that takes the EXTERNAL string representation of a URL as input. It stays strict to the specification and as such does not allow non-encoded non-ascii characters. If you construct a URL from INTERNAL parts, that's different. It would probably be possible to write a more lenient parser as opposed to a strict one. I have not yet given that idea much thought. > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Dec. 7, 2017