February 2017 - Pharo-users

Re: [Pharo-users] [Pharo-user] Does SSDP package supposed to work on Pharo 6?

by Denis Kudriashov

Forgot to say that I use it with stable VM on Mac Sierra 2017-02-09 16:10 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Hi. > Question probably to Henrik. > > I try SSDP <http://smalltalkhub.com/#!/~henriksp/SSDP> on latest Pharo 6 > and code for server and client signal primitive error on > #primGetAddressInfoHost:service:flags:family:type:protocol:. > > Do you know about such problems? Does it VM or code needs to be adapted > for Pharo6? > > >

Feb. 9, 2017

[Pharo-user] Does SSDP package supposed to work on Pharo 6?

by Denis Kudriashov

Hi. Question probably to Henrik. I try SSDP <http://smalltalkhub.com/#!/~henriksp/SSDP> on latest Pharo 6 and code for server and client signal primitive error on #primGetAddressInfoHost:service:flags:family:type:protocol:. Do you know about such problems? Does it VM or code needs to be adapted for Pharo6?

Feb. 9, 2017

1st CfP: SLE 2017 (10th ACM SIGPLAN International Conference on Software Language Engineering)

by Andrei Chis

======================================================================== **Call for Papers** 10th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2017) 23-24 October 2017, Vancouver, Canada (Co-located with SPLASH 2017) General chair: Benoit Combemale, University of Rennes 1, France Program co-chairs: Marjan Mernik, University of Maribor, Slovenia Bernhard Rumpe, RWTH Aachen University, Germany Artifact evaluation chairs Tanja Mayerhofer, TU Wien, Austria Laurence Tratt, King's College London, UK http://conf.researchr.org/track/sle-2017/sle-2017-papers http://www.sleconf.org/2017 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 2 Jun 2017 - Abstract Submission Fri 9 Jun 2017 - Paper Submission Fri 4 Aug 2017 - Author Notification Thu 10 Aug 2017 - Artifact Submission Fri 1 Sep 2017 - Artifact Notification Fri 8 Sep 2017 - Camera Ready Deadline Sun 22 Oct - SLE workshops Mon 23 Oct - Tue 24 Oct 2017 - SLE 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 and Composition * Coordination 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 including 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 including bibliography in ACM SIGPLAN conference style ( http://www.sigplan.org/Resources/Author/) and a demonstration outline including screenshots of up to 6 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 6-page demonstration outline will be used by the program committee only for evaluating the submission. * **Industrial papers**: These should describe real-world application scenarios of SLE in industry, explained in their context with an analysis of the challenges that were overcome and the lessons which the audience can learn from this experience. Industry paper submissions must not exceed 6 pages including bibliography in ACM SIGPLAN conference style ( http://www.sigplan.org/Resources/Author/) * **New ideas / vision papers**: New ideas papers should describe new, non-conventional SLE research approaches that depart from standard practice. They are intended to describe well-defined research ideas that are at an early stage of investigation. Vision papers are intended to present new unifying theories about existing SLE research that can lead to the development of new technologies or approaches. New ideas / vision papers must not exceed 4 pages including bibliography in ACM SIGPLAN conference style (http://www.sigplan.org/Resources/Author/) ### Artifact evaluation Authors of accepted papers at SLE 2017 are encouraged to submit their experiment results used for underpinning research statements to an artifact evaluation process. 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, industrial papers and new ideas / vision papers will be published in ACM Digital Library. Selected accepted papers will be invited to a special issue of the Computer Languages, Systems and Structures (COMLAN) journal. ### 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. * **Distinguished artifact**: Award for the artifact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artifact evaluation committee. ### Program Committee Marjan Mernik (co-chair), University of Maribor, Slovenia Bernhard Rumpe (co-chair), RWTH Aachen University, Germany Mark van den Brand, TU Eindhoven, The Netherlands Ruth Breu, University of Innsbruck, Austria Jordi Cabot, ICREA, Spain Walter Cazzola, University of Milan, Italy Marsha Chechik, University of Toronto, Canada Tony Clark, Middlesex University, UK Tom Dinkelaker, Ericsson, Germany Bernd Fischer, Stellenbosch University, South Africa Sebastian Gerard, CEA, France Jeff Gray, University of Alabama, USA Esther Guerra, Autonomous University of Madrid, Spain Michael Homer, Victoria University of Wellington, New Zealand Ralf LÃ¤mmel, University of Koblenz-Landau, Germany Tihamer Levendovszky, Microsoft, USA Gunter Mussbacher, McGill University, Canada Terence Parr, University of San Francisco, USA Jaroslav PorubÃ¤n, University of KoÅ¡ice, Slovakia Jan Ringert, Tel Aviv University, Israel Julia Rubin, University of British Columbia, Canada Tony Sloane, Macquarie University, Australia Eugene Syriani, University of Montreal, Canada Emma SÃ¶derberg, Google, Denmark Eric Van Wyk, University of Minnesota, USA Jurgen Vinju, CWI, Netherlands Eric Walkingshaw, Oregon State University, USA Andreas Wortmann, RWTH Aachen University, Germany Tian Zhang, Nanjing University, China ### Contact For any question, please contact the organizers via email: sle2017(a)inria.fr

Feb. 9, 2017

Re: [Pharo-users] Problems with auto-updating the text of a playground

by Offray Vladimir Luna CÃ¡rdenas

Thanks Doru, That solves it! A quick and clean fix :-). Cheers, Offray On 06/02/17 00:41, Tudor Girba wrote: > Hi, > > I am not quite sure I understand your problem, but I believe what you want is to only react to a change in a text. > > This information is placed in the #text port. Here is a basic example of how to react to it: > http://ws.stfx.eu/ETEC2JH7363M > > Cheers, > Doru > > >> On Feb 6, 2017, at 2:16 AM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >> >> Hi, >> >> For my Grafoscopio notebooks, I have implemented a way to auto-updating the content of a node, so it is automatically saved in the notebook when a node content is changed. The problem is that a node contains an embedded playground that produces text as output when executed (for example the playground reads a file or scraps HTML or calculates a hash), the text of the playground is replaced with the executed output. If the playground produces a visualization or non-textual output, this doesn't happen. >> >> I imagine that the source of the problem is here: >> >> ======= >> >> GrafoscopioNotebook >> autoSaveBodyOf: aNode >> body body class = TextModel >> ifTrue: [ body body whenTextChanged: [ :arg | aNode body: arg ] ]. >> body body class = GlamourPresentationModel >> ifTrue: [ | playground | >> playground := body body glmPres. >> playground >> when: GLMContextChanged >> do: [ :ann | >> ann property = #text >> ifTrue: [ | playgroundText | >> playgroundText := (playground pane ports at: 2) value. >> aNode body: playgroundText ] >> ] >> ] >> >> ======= >> >> as you can see the "when: GLMContextChanged" updates a node body with the playgroundText, as intended, so I can capture any change of the playground code, but I would like to add some condition to **not** update the body content if the text is the result of a playground execution. There is any way to do this? >> >> Thanks, >> >> Offray >> >> > -- > www.tudorgirba.com > www.feenk.com > > "If you can't say why something is relevant, > it probably isn't." > > >

Feb. 9, 2017

Re: [Pharo-users] SLICE-Issue-18901-Highlight-message-send-selector-on-mouse-over-NicolaiHess.4 introduces new bug?

by Alistair Grant

Hi All, I've created the issue and associated slice: https://pharo.fogbugz.com/f/cases/19680/DNU-bug-in-SLICE-18901 Thanks, Alistair On 8 February 2017 at 17:25, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > Am 08.02.2017 2:12 vorm. schrieb "Alistair Grant" <akgrant0710(a)gmail.com>: > > Hi Nicolai, > > On 7 February 2017 at 18:56, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >> Hi Alistair, >> the error messages from Rubric-Components, if there occured an error is >> often misleading. >> >> I added this act-on-move-functionality for highlighting message sends and >> I >> forgot to respect to full TextAction hierarchy >> (I only implemented the >> actOnMove: anEvent for: target in: aParagraph editor: anEditor >> method for TextLink and TextMethodLink and not for TextAction) >> >> You can solve this by moving the implementation >> actOnMove: anEvent for: target in: aParagraph editor: anEditor >> "override in subclasses" >> ^ false >> >> from TextLink, up to TextAction. > > Thanks - that fixes the issue! Thanks also for your quick reply. > > Would you like me to submit a bug report and slice to fogbugz? > > > Yes, please. > > > > > > > Thanks again, > Alistair > >

Feb. 8, 2017

Re: [Pharo-users] [Metacello] Adding existing metacello project to my new project

by phil＠highoctane.be

https://github.com/Pharophile/PechaKucha/tree/master/packages/BaselineOfPec… ConfigurationOf is for the Catalog Phil On Wed, Feb 8, 2017 at 8:29 PM, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > I think iâm doing it wrong.. > > this is all i could find in there.. > > https://github.com/Pharophile/PechaKucha/blob/master/packages/ > ConfigurationOfPechaKucha.package/ConfigurationOfPechaKucha. > class/instance/version10..st > > > > On February 8, 2017 at 10:22:17 AM, Gabriel Cotelli (g.cotelli(a)gmail.com) > wrote: > > Check how seaside dependency is done in here: https://github.com/ > Pharophile/PechaKucha > > Phil > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.Village-Buzz.com > http://www.ThoseOptimizeGuys.com > http://www.coffee-black.com > http://www.painlessfrugality.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 >

Feb. 8, 2017

Re: [Pharo-users] [Metacello] Adding existing metacello project to my new project

by sergio ruiz

found it..Â load: #( 'mongo' 'tests')Â should be: loads: #( 'mongo' 'tests')Â thanks! On February 8, 2017 at 10:22:17 AM, Gabriel Cotelli (g.cotelli(a)gmail.com) wrote: spec Â Â Â Â Â Â baseline: 'Voyage' with: [ spec repository: 'github://pharo-nosql/voyage/mc'; load: #( 'mongo' 'tests') ]; import: 'Voyage'. ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 8, 2017

Re: [Pharo-users] [Metacello] Adding existing metacello project to my new project

by sergio ruiz

Hmmm.. gonna have to toy with this.. this is giving me other errors.. namely that baseline is no longer defined.. On February 8, 2017 at 10:22:17 AM, Gabriel Cotelli (g.cotelli(a)gmail.com) wrote: spec Â Â Â Â Â Â baseline: 'Voyage' with: [ spec repository: 'github://pharo-nosql/voyage/mc'; load: #( 'mongo' 'tests') ]; import: 'Voyage'. ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 8, 2017

Re: [Pharo-users] [Metacello] Adding existing metacello project to my new project

by sergio ruiz

I think iâm doing it wrong.. this is all i could find in there.. https://github.com/Pharophile/PechaKucha/blob/master/packages/Configuration… On February 8, 2017 at 10:22:17 AM, Gabriel Cotelli (g.cotelli(a)gmail.com) wrote: Check how seaside dependency is done in here:Â https://github.com/Pharophile/PechaKucha Phil ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 8, 2017

Re: [Pharo-users] [Pharo-dev] Book farm working again

by Guillermo Polito

Thanks! On Wed, Feb 8, 2017 at 6:05 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi > > ï»¿https://ci.inria.fr/pharo-contribution/view/Books/ > I realised that jenkins dropped the connection to the github repositories > of the books and that they were not updated. > You can find my current evening occupation: Learning OOP with Pharo :) > I fixed some problems in UnifiedFFI and clean a bit before restarting to > work on Pillar. > > And we get more green books job. > > Stef >

Feb. 8, 2017