- Pharo-users - lists.pharo.org

Saving selected changes in Monticello

by Andreas Sunardi

I have a half done changes in my image, but I need to distribute the other changes that are done. I thought I was going to do this all at once, but now I realize I should split this into 2 commit versions. Is there a way in Monticello to say save my changes, but not this and that changes? I can't seem to find it nor in books. How do people deal with this situation? -- Andreas Sunardi

June 5, 2017

Re: [Pharo-users] Creating a BaselineOf from a ConfigurationOf>>#baselineXyz:

by HernÃ¡n Morales Durand

Hi Sean, I didn't tried too much but you may first have to match the node in the parse tree. Something like this: | node | node := (RBParseTreeRewriter treeMatching: '`@expr blessing: `#lit' in: (YourClass >> #baseline01:) parseTree). (node parent removeNode: node) newSource. Cheers, HernÃ¡n 2017-06-04 0:48 GMT-03:00 Sean P. DeNigris <sean(a)clipperadams.com>: > I'm trying to write a rewrite rule, but can't quite get it. > > I first want to remove `spec blessing: #baseline.` > > I tried the following with no effect: > > RBParseTreeRewriter new > replace: '`@expr blessing: `#lit' > with: ''; > executeTree: methodTree; > tree. > > NB: If I try to edit the expression instead of remove, by passing something > like '`@expr assert: `#lit' for #with:, it works > > What am I missing here? > > Thanks! > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ > Creating-a-BaselineOf-from-a-ConfigurationOf-baselineXyz-tp4949192.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

June 5, 2017

Re: [Pharo-users] STON Question

by Sven Van Caekenberghe

Stef, STON is like FUEL, it can write any object to a stream and read it back. Although you can customise how this is done, only one way of doing so is supported (i.e. you cannot change the format for each application). People have used STON for various applications now, including for configuration stuff (because it is a textual format that is easy to read). I would suggest you just try to see what your config looks like once you have the objects in Pharo. STON toStringPretty: myConfig. Then we can see how to tune the representation. Sven > On 4 Jun 2017, at 22:58, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi sven > > I'm working on a new configuration frameworks similar to the one use pillar.conf. > > So basically I have > > ston := '{ > "newLine":#unix, > "separateOutputFiles":true > }'. > and I want to recreate it. > > So I did > > Object >> toConfigurationString > > ^ STON toString: self > > SimpleConfiguration >> exportStream > > ^ String streamContents: [ :str | > str << '{' . > self propertiesKeysAndValuesDo: [ :key :value| > str << key toConfigurationString. > str << ':'. > str << value toConfigurationString. > str << ','. > str lf. > ]. > str << '}'. > str contents > ] > > The idea is that for special configuration values people should be able to define > how to go from the object to configuration. > For example for some FileReference I want to have just the path up to the baseDirectory. > > Now I wonder if I could not better reuse ston. > I saw the stonOn: > but I did not look further because I was wondering how the writer where passed. > > Any feedback is welcome. > > Stef (now bed time). >

June 4, 2017

Wiring objects, IoC and Service Locator

by Vitor Medina Cruz

Hello, I would like to know how people in Pharo ecosystem do to deal with object wiring, as described by Marting Fowler in https://martinfowler.com/articles/injection.html#FormsOfDependencyInjection: "A common issue to deal with is how to wire together different elements: how do you fit together this web controller architecture with that database interface backing when they were built by different teams with little knowledge of each other." He gives an example, I will leave it in java as it is simple enough to understand: "class MovieLister... public Movie[] moviesDirectedBy(String arg) { List allMovies = finder.findAll(); for (Iterator it = allMovies.iterator(); it.hasNext();) { Movie movie = (Movie) it.next(); if (!movie.getDirector().equals(arg)) it.remove(); } return (Movie[]) allMovies.toArray(new Movie[allMovies.size()]); }" The question is how to provide the finder object in a decoupled matter, a naive approach would be: " private MovieFinder finder; public MovieLister() { finder = new ColonDelimitedMovieFinder("movies1.txt"); }" Which couples the MovieLister to the specific ColonDelimitedMovieFinder class. Fowler explains how to decouple using an IoC framework or a Service Locator. In Java and .Net IoC is used most of the time. I Googled how this problem is approached in Smalltalk/Pharo, and I generally I found answers "that is easy to do in Smalltalk, so there is no need of a framework", what I miss is a description on *how* to do that: https://stackoverflow.com/questions/243905/smalltalk-and-ioc https://stackoverflow.com/questions/2684326/is-there-a-dependency-injection… https://stackoverflow.com/questions/243905/smalltalk-and-ioc/347477#347477 I know that in Smalltalk I can make MovieLister to receive, upon construction, a class representing MovieFinder and call it construction message. As long an object that responds to this message is provided, I can create as many derivations I want and the MovieLister will be decoupled from the MovieFinder. That way, however, I still have to wire things by hand, and I am not sure if this is what I am supposed to do in order to solve the decouple problem. Can you explain me how this is done in Pharo? It's is usually wiring by hand? Is there a simple construction that deals with the wiring problem that I cannot foresee? Thanks in advance, Vitor

June 4, 2017

STON Question

by Stephane Ducasse

Hi sven I'm working on a new configuration frameworks similar to the one use pillar.conf. So basically I have ston := '{ "newLine":#unix, "separateOutputFiles":true }'. and I want to recreate it. So I did Object >> toConfigurationString ^ STON toString: self SimpleConfiguration >> exportStream ^ String streamContents: [ :str | str << '{' . self propertiesKeysAndValuesDo: [ :key :value| str << key toConfigurationString. str << ':'. str << value toConfigurationString. str << ','. str lf. ]. str << '}'. str contents ] The idea is that for special configuration values people should be able to define how to go from the object to configuration. For example for some FileReference I want to have just the path up to the baseDirectory. Now I wonder if I could not better reuse ston. I saw the stonOn: but I did not look further because I was wondering how the writer where passed. Any feedback is welcome. Stef (now bed time).

June 4, 2017

Deadline Extension - SLE 2017 (10th ACM SIGPLAN International Conference on Software Language Engineering)

by Andrei Chis

======================================================================== **Call for Papers** - **Deadline Extension** **Abstract Submission**: Friday 9, June 2017 **Paper Submission**: Friday 16, June 2017 ======================================================================== 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 Keynote Speaker: Peter D. Mosses, Swansea University, UK (http://cs.swan.ac.uk/~cspdm/) 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 9 Jun 2017 - Abstract Submission Fri 16 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 acmart 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 acmart 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 acmart 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 acmart conference style (http://www.sigplan.org/Resources/Author/) ### Artifact evaluation SLE will for the second year use an evaluation process for assessing the quality of artifacts on which papers are based. The aim of this evaluation process is to foster a culture of experimental reproducibility as well as a higher quality in the research area as a whole. Authors of papers accepted for SLE 2017 will be invited to submit artifacts. Any kind of artifact that is presented in the paper, supplements the paper with further details, or underlies the paper can be submitted. This includes, for instance, tools, grammars, metamodels, models, programs, algorithms, scripts, proofs, datasets, statistical tests, checklists, surveys, interview scripts, visualizations, annotated bibliographies, and tutorials. The submitted artifacts will be reviewed by a dedicated Artifact Evaluation Committee (AEC). Artifacts that live up to the expectations created by the paper will receive a badge of approval from the AEC. The approved artifacts will be invited for inclusion in the electronic conference proceedings published in the ACM Digital Library. This will ensure the permanent and durable storage of the artifacts alongside the published papers fostering the repeatability of experiments, enabling precise comparison with alternative approaches, and helping the dissemination of the authorâs ideas in detail. Participating in the artifact evaluation and publishing approved artifacts in the ACM Digital Library is voluntary. However, we strongly encourage authors to consider this possibility as the availability of artifacts will greatly benefit readers of papers and increase the impact of the work. Note that the artifact evaluation cannot affect the acceptance of the paper, because it only happens after the decision about acceptance has been made. ### 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 Christian Berger, Chalmers, Sweden 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

June 4, 2017

snap morphs/windows to each other when dragging

by Peter Uhnak

Hi, is it possible to tell windows to "snap" to other windows when dragging? So e.g. when I am dragging Playground window, it will try to snap side by side with a close-by another window, so they don't overlap (unless I e.g. press shift or something). Thanks, Peter

June 4, 2017

Creating a BaselineOf from a ConfigurationOf>>#baselineXyz:

by Sean P. DeNigris

I'm trying to write a rewrite rule, but can't quite get it. I first want to remove `spec blessing: #baseline.` I tried the following with no effect: RBParseTreeRewriter new replace: '`@expr blessing: `#lit' with: ''; executeTree: methodTree; tree. NB: If I try to edit the expression instead of remove, by passing something like '`@expr assert: `#lit' for #with:, it works What am I missing here? Thanks! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Creating-a-BaselineOf-from-a-ConfigurationOf-baseline… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 4, 2017

Re: [Pharo-users] Porting Transducers to Pharo

by Steffen MÃ¤rcker

Dear all, attached are updated file-outs. I fixed a couple of annoyances that slipped through yesterday evening. Most notable: 1) Random generator now works. 2) Early termination via Reduced exception does MNU anymore. 3) Printing a transducer holding a block does not MNU anymore. Please, give it a spin and tell me your impressions. (At least) The coin-flipping the example from the package comment works now: scale := [:x | (x * 2 + 1) floor] map. sides := #(heads tails) replace. count := 1000 take. collect := [:bag :c | bag add: c; yourself]. experiment := (scale * sides * count) transform: collect. "experiment cannot be re-used" samples := Random new reduce: experiment init: Bag new. "transform and reduce in one step" samples := Random new transduce: scale * sides * count reduce: collect init: Bag new. "assemble coin (eduction) and flip (reduction) objects" coin := sides <~ scale <~ Random new. flip := Bag <~ count. "flip coin =)" samples := flip <~ coin. Cheers! Steffen Am .06.2017, 23:08 Uhr, schrieb Steffen MÃ¤rcker <merkste(a)web.de>: > Thanks, this appears to work. Attached you'll find the file-out from > VisualWorks and the file-out from Pharo (includes package comment). > > Cheers! > Steffen > > > Am .06.2017, 20:06 Uhr, schrieb Yanni Chiu <yanni.code(a)gmail.com>: > >> To get the extension methods into the Transducers package, the following >> worked for me - edit the category to have the prefix '*Transducers-' >> >> 2710c2710 >> >> < !Number methodsFor: 'transforming' stamp: ' 2/6/17 15:38'! >> >> --- >> >>> !Number methodsFor: '*Transducers-transforming' stamp: ' 2/6/17 15:38'! >> >> >> On Fri, Jun 2, 2017 at 11:05 AM, Steffen MÃ¤rcker <merkste(a)web.de> wrote: >> >>> Dear all, >>> >>> thanks for the many suggestions. I didn't had time to test all >>> import/export ways yet. But for now, I can report on two: >>> >>> 1) NGFileOuter >>> Unfortunately It raised several MNUs in my image. I'll investigate them >>> later. >>> >>> 2) FileOut30 (VW Contributed) >>> I was able to file out the code except for the package definition. >>> Replacing {category: ''} in the class definitions with {package: >>> 'Transducers'} fixed that. However, methods that extend existing >>> classes >>> did not end up in the Transducers package. Is there a similar easy >>> change >>> to the file-out making that happen? Also I'd like to add the package >>> comment if that's possible. >>> >>> Most things appear to work as far as I can see. Two exceptions: >>> 1) Random is a subclass of Stream in VW and in Pharo it is not. Hence, >>> I'll have to copy some methods from Stream to Random. >>> 2) I used #beImmutable in VW but I couldn't yet figure out how to make >>> objects immutable in Pharo. >>> >>> However, until the tests are ported, I cannot guarantee. Porting the >>> test >>> suite will be another beast, since I rely on the excellent >>> mocking/stubbing >>> library DoubleAgents by Randy Coulman. I am not sure how I will handle >>> that. In general, I think it would be really worth the effort to be >>> ported >>> to Pharo, too. DoubleAgents is pretty powerful and produces easy to >>> read >>> and understand mocking/stubbing code. Personally, I prefer it clearly, >>> e.g., over Mocketry (no offence intended!). >>> >>> Attached you'll find the file-out that I loaded into Pharo. The issues >>> above are not addressed yet. However, the following example works: >>> >>> | scale sides count collect experiment random samples coin flip | >>> scale := [:x | (x * 2 + 1) floor] map. >>> sides := #(heads tails) replace. >>> count := 1000 take. >>> collect := [:bag :c | bag add: c; yourself]. >>> experiment := (scale * sides * count) transform: collect. >>> random := #(0.1 0.3 0.4 0.5 0.6 0.7 0.8 0.9). >>> >>> samples := random >>> reduce: experiment >>> init: Bag new. >>> >>> samples := random >>> transduce: scale * sides * count >>> reduce: collect >>> init: Bag new. >>> >>> coin := sides <~ scale <~ random. >>> flip := Bag <~ count. >>> >>> samples := flip <~ coin. >>> >>> >>> Best, Steffen >>> >>> >>> >>> Am .06.2017, 08:16 Uhr, schrieb Stephane Ducasse >>> <stepharo.self(a)gmail.com >>> >: >>> >>> There is a package for that NGFileOuter or something like that on >>> cincom >>>> store. >>>> We used it for mobydic code. >>>> >>>> On Wed, May 31, 2017 at 6:35 PM, Alexandre Bergel < >>>> alexandre.bergel(a)me.com> >>>> wrote: >>>> >>>> If I remember correctly, there is a parcel in VisualWorks to export a >>>> file >>>>> out (Squeak format). >>>>> >>>>> @Milton, can you give a hand to Steffen? >>>>> >>>>> Alexandre >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> On May 31, 2017, at 10:32 AM, Steffen MÃ¤rcker <merkste(a)web.de> wrote: >>>>> >>>>> Thanks for the encouraging response! First question: Which is the >>>>> recommended (friction free) way to exchange code between VW and >>>>> Pharo? >>>>> >>>>> Cheers! >>>>> Steffen >>>>> >>>>> Am .05.2017, 16:22 Uhr, schrieb Alexandre Bergel < >>>>> alexandre.bergel(a)me.com >>>>> >: >>>>> >>>>> I second Sven. This is very exciting! >>>>> >>>>> Let us know when you have something ready to be tested. >>>>> >>>>> Alexandre >>>>> >>>>>

June 3, 2017

Re: Morphic or forking bug?

by Milan Vavra

Sven's Clock example. Just unzip & file in. MyClock.zip <http://forum.world.st/file/n4949170/MyClock.zip> Best Regards, Milan Vavra -- View this message in context: http://forum.world.st/Morphic-or-forking-bug-tp4948727p4949170.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 3, 2017