April 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [ANN] Genetic Algorithm is available from the Catalog

by stepharo

How does it compare with the algorithms in the Chromosome package of Polymath? Stef Le 26/4/16 Ã 10:49, CÃ©drick BÃ©ler a Ã©crit : > I think this is GeneticAlgorithm ^^ > > Cheers, > Cedrik > > EnvoyÃ© de mon iPhone > >> Le 26 avr. 2016 Ã 10:22, Serge Stinckwich <serge.stinckwich(a)gmail.com> a Ã©crit : >> >> Cool but without name this is maybe difficult to find :-) >> >> On Mon, Apr 25, 2016 at 10:10 PM, Alexandre Bergel >> <alexandre.bergel(a)me.com> wrote: >>> Hi! >>> >>> I did a bit of programmingâ¦ A genetic algorithm is available from the Catalog. >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> -- >> Serge Stinckwich >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ >> >

April 27, 2016

Playgound inspecting

by Hilaire

Hello, >From the playground when ctrl+g an object, instance variables evaluate to nil in the bottom area of the integrated inspector. Am I missing sommething ? Tried with pharo4 Thanks Hilaire -- Dr. Geo http://drgeo.eu

April 27, 2016

Re: [Pharo-users] Playgound inspecting

by Sean P. DeNigris

HilaireFernandes wrote > instance variables evaluate to nil in the bottom area of the integrated > inspector. There is no direct inst var access from the playground. I was initially shocked by this as well and have had to resort to #instVarNamed: on several occasions. On the bright side, you can edit the values in place in the 'Value' column above. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Playgound-inspecting-tp4892388p4892392.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 27, 2016

Re: [Pharo-users] VTermOutPutDriver

by Valentin Ryckewaert

I found the problem, it's just that the dictionnary which make correspond bold to the code needed didn't have the bold (and other stuffs I suppose) I'm trying to fix this. 2016-04-27 12:20 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > Some code I have around: > > > Tools class>>#inform: aString color: aSymbol > | out | > out := VTermOutputDriver stdout. > > out perform: aSymbol. > > DateAndTime now printHMSOn: out. > > out > nextPutAll: ' : '; > nextPutAll: aString. > > out lf. > > Usage: > > Tools inform: 'Blah' color: #red. > > FYI VTermOutputDriver and friends come from another project of Camillo > Bruni (now gone from the list, do not ask) which contained the full support > for termcap. > > I've the source somewhere and it should definitely be revived. > > Phil > > > > On Wed, Apr 27, 2016 at 10:41 AM, Blondeau Vincent < > vincent.blondeau(a)worldline.com> wrote: > > > > Hi, > > > > > > > > Termcap methods seems not implemented and used by the output driver (see > initialize).. Maybe you should implement them before anything ? > > > > > > > > Vincent > > > > > > > > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la > part de Valentin Ryckewaert > > EnvoyÃ© : mercredi 27 avril 2016 10:35 > > Ã : Any question about pharo is welcome > > Objet : [Pharo-users] VTermOutPutDriver > > > > > > > > Hi everyone, > > > > > > > > i'm reading VTermOutPutDriver and I tried to use the example of the > documentation: > > > > > > > > | out | > > > > out := VTermOutputDriver stdout. > > > > out << 'normal text'. > > > > out lf. > > > > 'red text' do: [ :c | out color256: Color red. out << c ]. > > > > out lf. > > > > 'bold text' do: [ :c | out bold. out << c ]. > > > > out clear. > > > > out lf. > > > > > > > > As I understood it > > > > 'bold text' do: [ :c | out bold. out << c ]. > > > > is the problem, the termcap 'md' looks like not existing but it exists : > http://man7.org/linux/man-pages/man5/termcap.5.html > > > > > > > > Should I send an issue for not working method or wrong doc ? > > > > > > > !!!************************************************************************************* > > "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã > l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par > le secret professionnel. Si vous recevez ce message par erreur, merci d'en > avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du > message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de > Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien > que les meilleurs efforts soient faits pour maintenir cette transmission > exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et > sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant > d'un virus transmis. > > > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. As > its integrity cannot be secured on the Internet, the Worldline liability > cannot be triggered for the message content. Although the sender endeavours > to maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted.!!!" >

April 27, 2016

Re: [Pharo-users] VTermOutPutDriver

by phil＠highoctane.be

Some code I have around: Tools class>>#inform: aString color: aSymbol | out | out := VTermOutputDriver stdout. out perform: aSymbol. DateAndTime now printHMSOn: out. out nextPutAll: ' : '; nextPutAll: aString. out lf. Usage: Tools inform: 'Blah' color: #red. FYI VTermOutputDriver and friends come from another project of Camillo Bruni (now gone from the list, do not ask) which contained the full support for termcap. I've the source somewhere and it should definitely be revived. Phil On Wed, Apr 27, 2016 at 10:41 AM, Blondeau Vincent < vincent.blondeau(a)worldline.com> wrote: > > Hi, > > > > Termcap methods seems not implemented and used by the output driver (see initialize).. Maybe you should implement them before anything ? > > > > Vincent > > > > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de Valentin Ryckewaert > EnvoyÃ© : mercredi 27 avril 2016 10:35 > Ã : Any question about pharo is welcome > Objet : [Pharo-users] VTermOutPutDriver > > > > Hi everyone, > > > > i'm reading VTermOutPutDriver and I tried to use the example of the documentation: > > > > | out | > > out := VTermOutputDriver stdout. > > out << 'normal text'. > > out lf. > > 'red text' do: [ :c | out color256: Color red. out << c ]. > > out lf. > > 'bold text' do: [ :c | out bold. out << c ]. > > out clear. > > out lf. > > > > As I understood it > > 'bold text' do: [ :c | out bold. out << c ]. > > is the problem, the termcap 'md' looks like not existing but it exists : http://man7.org/linux/man-pages/man5/termcap.5.html > > > > Should I send an issue for not working method or wrong doc ? > > > !!!************************************************************************************* > "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

April 27, 2016

Re: [Pharo-users] VTermOutPutDriver

by Blondeau Vincent

Hi, Termcap methods seems not implemented and used by the output driver (see initialize).. Maybe you should implement them before anything ? Vincent De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de Valentin Ryckewaert EnvoyÃ© : mercredi 27 avril 2016 10:35 Ã : Any question about pharo is welcome Objet : [Pharo-users] VTermOutPutDriver Hi everyone, i'm reading VTermOutPutDriver and I tried to use the example of the documentation: | out | out := VTermOutputDriver stdout. out << 'normal text'. out lf. 'red text' do: [ :c | out color256: Color red. out << c ]. out lf. 'bold text' do: [ :c | out bold. out << c ]. out clear. out lf. As I understood it 'bold text' do: [ :c | out bold. out << c ]. is the problem, the termcap 'md' looks like not existing but it exists : http://man7.org/linux/man-pages/man5/termcap.5.html Should I send an issue for not working method or wrong doc ? !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

April 27, 2016

VTermOutPutDriver

by Valentin Ryckewaert

Hi everyone, i'm reading VTermOutPutDriver and I tried to use the example of the documentation: | out | out := VTermOutputDriver stdout. out << 'normal text'. out lf. 'red text' do: [ :c | out color256: Color red. out << c ]. out lf. 'bold text' do: [ :c | out bold. out << c ]. out clear. out lf. As I understood it 'bold text' do: [ :c | out bold. out << c ]. is the problem, the termcap 'md' looks like not existing but it exists : http://man7.org/linux/man-pages/man5/termcap.5.html Should I send an issue for not working method or wrong doc ?

April 27, 2016

1st CFP: SLE 2016 (9th ACM SIGPLAN International Conference on Software Language Engineering)

by Andrei Chis

**Call for Papers** ======================================================================== 9th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2016) Oct 31-Nov 1, 2016, Amsterdam, Netherlands (Co-located with SPLASH 2016) General chair: Tijs van der Storm, CWI, Netherlands Program co-chairs: DÃ¡niel Varro, Budapest University of Technology and Economics, Hungary Emilie Balland, Sensational AG, Switzerland http://conf.researchr.org/track/sle-2016/sle-2016-papers http://www.sleconf.org/2016/ Follow us on twitter: https://twitter.com/sleconf ======================================================================== Software Language Engineering (SLE) is the application of systematic, disciplined, and measurable approaches to the development, use, deployment, and maintenance of software languages. The term "software language" is used broadly, and includes: general-purpose programming languages; domain-specific languages (e.g. BPMN, Simulink, Modelica); modeling and metamodeling languages (e.g. SysML and UML); data models and ontologies (e.g. XML-based and OWL-based languages and vocabularies). ### Important Dates Fri 17 Jun 2016 - Abstract Submission Fri 24 Jun 2016 - Paper Submission Fri 26 Aug 2016 - Notification Fri 2 Sep 2016 - Artifact submission Fri 16 Sep 2016 - Artifact notification Fri 16 Sep 2016 - Camera ready deadline Mon 31 Oct 09:00 - Tue 1 Nov 18:00 2016 Conference ### Topics of Interest SLE aims to be broad-minded and inclusive about relevance and scope. We solicit high-quality contributions in areas ranging from theoretical and conceptual contributions to tools, techniques, and frameworks in the domain of language engineering. Topics relevant to SLE cover generic aspects of software languages development rather than aspects of engineering a specific language. In particular, SLE is interested in principled engineering approaches and techniques in the following areas: * Language Design and Implementation * Approaches and methodologies for language design * Static semantics (e.g., design rules, well-formedness constraints) * Techniques for behavioral / executable semantics * Generative approaches (incl. code synthesis, compilation) * Meta-languages, meta-tools, language workbenches * Language Validation * Verification and formal methods for languages * Testing techniques for languages * Simulation techniques for languages * Language Integration * Coordination between of heterogeneous languages and tools * Mappings between languages (incl. transformation languages) * Traceability between languages * Deployment of languages to different platforms * Language Maintenance * Software language reuse * Language evolution * Language families and variability * Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) * Empirical evaluation and experience reports of language engineering tools * User studies evaluating usability * Performance benchmarks * Industrial applications ### Types of Submissions * **Research papers**: These should report a substantial research contribution to SLE or successful application of SLE techniques or both. Full paper submissions must not exceed 12 pages excluding bibliography (in ACM SIGPLAN conference style (http://www.sigplan.org/Resources/Author/)) * **Tool papers**: Because of SLEâs interest in tools, we seek papers that present software tools related to the field of SLE. Selection criteria include originality of the tool, its innovative aspects, and relevance to SLE. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must provide a tool description of 4 pages in SIGPLAN proceedings style (see above), with 1 optional additional page for bibliographic references, and a demonstration outline including screenshots of up to 4 pages. Tool demonstrations must have the keywords "Tool Demo" or âTool Demonstrationâ in the title. The 4-page tool description will, if the demonstration is accepted, be published in the proceedings. The 4-page demonstration outline will be used by the program committee only for evaluating the submission. ### Artifact evaluation Authors of accepted papers at SLE 2016 are encouraged to submit their experiment results used for underpinning research statements to an artifact evaluation process carried out in early September 2016. This submission is voluntary and will not influence the final decision regarding the papers. Papers that go through the Artifact Evaluation process successfully receive a seal of approval printed on the first page of the paper in the proceedings. Authors of papers with accepted artifacts are encouraged to make these materials publicly available upon publication of the proceedings, by including them as "source materials" in the ACM Digital Library. ### Publications All submitted papers will be reviewed by at least three members of the program committee. All accepted papers, including tool papers will be published in ACM Digital Library. Authors of distinguished papers from the conference will be invited to revise and submit extended versions of their papers for a Journal special issue. ### Awards * Distinguished paper. Award for most notable paper, as determined by the PC chairs based on the recommendations of the program committee. * Distinguished reviewer. Award for distinguished reviewer, as determined by the PC chairs using feedback from the authors. ### Program Committee Emilie Balland (co-chair), Sensational AG (SUI) Daniel Varro (co-chair), BME (HUN) Anya Helene Bagge, Univ. Bergen (NOR) Ruth Breu, Univ. Innsbruck (AUT) Jordi Cabot, Univ. Oberta de Catalunya (ESP) Marsha Chechik, Univ. Toronto (CAN) Marcus Denker, INRIA (FRA) Davide Di Ruscio, Univ. LâAquila (ITA) Martin Erwig, Oregon State Univ. (USA) Bernd Fischer, Stellenbosch University (RSA) Sebastian Gerard, CEA (FRA) Jeremy Gibbons, Oxford Univ. (UK) Holger Giese, Hasso Plattner Inst. (GER) Martin Gogolla, Univ. Bremen (GER) Jeff Gray, Univ. Alabama (USA) Esther Guerra, Autonomous Univ. of Madrid (ESP) Gorel Hedin, Lund Univ. (SWE) Michael Homer, Victoria Univ. Wellington (NZL) Dimitris Kolovos, Univ. York (UK) Ralf LÃ¤mmel, Univ. Koblenz (GER) Julia Lawall, LIP6 (FRA) Tihamer Levendovszky, Microsoft (USA) Heather Miller, EPFL (SUI) Pierre-Etienne Moreau, Loria (FRA) GÃ¼nter Mussbacher, McGill Univ. (CAN) Bruno Oliveira, Univ. of Hong Kong (HKG) Terence Parr, Univ. San Francisco (USA) IstvÃ¡n RÃ¡th, IncQuery Labs (HUN) Julia Rubin, MIT (USA) Bernhard Schatz, Fortiss (GER) Sibylle Schupp, Univ. Hamburg (GER) Anthony Sloane, Macquarie Univ. (AUS) Emma SÃ¶derberg, Google (USA) Eugene Syriani, Univ. MontrÃ©al (CAN) Gabi Taentzer, Univ. Marburg (GER) Eric Van Wyk, Univ. Minnesota (USA) Hans Vangheluwe, Univ. Antwerp (BEL) Jurgen Vinju, CWI (NED) Guido Wachsmuth, TU Delft (NED) Eric Walkingshaw, Oregon State Univ. (USA) Andrzej WÄsowski, ITU (DEN) Manuel Wimmer, TU Wien (AUT) Tian Zhang, Nanjing Univ. (CHN)

April 26, 2016

Re: [Pharo-users] Messages interceptions without using "halt"

by Denis Kudriashov

But if you want new message send logic only for your registered objects then you can use Ghost for this. It provides some infrastructure to implement such strange objects 2016-04-26 15:30 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Hi > > 2016-04-26 14:39 GMT+02:00 Steven Costiou <steven.costiou(a)kloum.io>: > >> Hello, >> >> i am not new to Pharo nor to the list but this is the first time i speak >> here, so : hi =) >> >> >> >> I started a phd a few month ago (with Alain Plantec) on context oriented >> programming and dynamic programs adaptation. I am using Pharo for my >> experiments and i would like to intercept messages sent to an object just >> before they get to their receiver. To be more specific, when #msg is sent >> to an object o, i want to be able to intercept it just before it is >> actually executed with the following objects at my disposal : the receiver >> (o), the message or selector, the sender. My objective by doing that is to >> (try to) change the lookup for a given method, and to be able to choose in >> which class the lookup will start. >> >> >> >> I have been looking a bit and it does not seem to be a "simple" way to do >> that in Pharo. Is that even possible and if so, any advice on where i >> should look ? >> > I think it is not possible from image side. As I understand correctly you > are going to change general message send mechanizm. You could hack VM for > this. >

April 26, 2016

Re: [Pharo-users] Messages interceptions without using "halt"

by Thierry Goubier

2016-04-26 15:07 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > it is not what MetaLinks are for? > I think is easier than Ghost nowadaysâ¦ but not sure :) > > look at > > ReflectivityControlTest>>testBeforeSend > > seems to be installing an interception âbefore sendâ, who is what you are > asking for. > It depends if it is an interception before send or an interception before receive ;) If one is to change the method lookup, then this is done at the receiver end of the message send, and, then, I think a ghost is more appropriate. Or metalinks upon entry to the receiver method (i.e. method wrappers type of thing). Thierry > > Esteban > > ps: but I might be wrongâ¦ Marcus can explain better :) > > > On 26 Apr 2016, at 14:50, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > Hi Steven, > > 2016-04-26 14:39 GMT+02:00 Steven Costiou <steven.costiou(a)kloum.io>: > >> Hello, >> >> i am not new to Pharo nor to the list but this is the first time i speak >> here, so : hi =) >> >> >> I started a phd a few month ago (with Alain Plantec) on context oriented >> programming and dynamic programs adaptation. I am using Pharo for my >> experiments and i would like to intercept messages sent to an object just >> before they get to their receiver. To be more specific, when #msg is sent >> to an object o, i want to be able to intercept it just before it is >> actually executed with the following objects at my disposal : the receiver >> (o), the message or selector, the sender. My objective by doing that is to >> (try to) change the lookup for a given method, and to be able to choose in >> which class the lookup will start. >> >> >> I have been looking a bit and it does not seem to be a "simple" way to do >> that in Pharo. Is that even possible and if so, any advice on where i >> should look ? >> > The easiest would be to use proxy or ghost objects, which catches all > message sends to a proxy of the real object and let you decide what to do > with them. A recent announcement on Ghosts for Pharo 5 was done, maybe > starting with that could be an idea. > > http://forum.world.st/Ann-New-version-of-Ghost-td4886357.html > > For old timers: wasn't Actalk done that way ? > > Thierry > > >> >> >> Thanks, >> >> Steven. >> > > >

April 26, 2016