February 2017 - Pharo-users

1st CfP: SLE 2017 (10th ACM SIGPLAN International Conference on Software Language Engineering)
by Andrei Chis Feb. 9, 2017

Feb. 9, 2017

======================================================================== **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

1 0

Problems with auto-updating the text of a playground
by Offray Vladimir Luna CÃ¡rdenas Feb. 9, 2017

Feb. 9, 2017

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

2 2

SLICE-Issue-18901-Highlight-message-send-selector-on-mouse-over-NicolaiHess.4 introduces new bug?
by Alistair Grant Feb. 8, 2017

Feb. 8, 2017

Hi All, I'm attempting to port some code that works in Pharo 5 to Pharo 6 and have hit a problem when attempting to inspect text. Inspecting the following: | text | text := Text fromString: 'Hello World'. text addAttribute: (TextAction new actOnClickBlock: [ self halt ]) from: 1 to: 5. text. And then moving the mouse over the text causes the traceback included below in Pharo 6, but is fine in Pharo 5. I think the problem was introduced as part of SLICE-Issue-18901-Highlight-message-send-selector-on-mouse-over-NicolaiHess.4 in RubAbstractTextArea>>mouseMove: where the line: self paragraph move: evt for: model controller: self editor. was added to the start of the method. I'm not familiar with this code, so it would be great if someone (Nicolai? :-)) who has a better understanding of the original intention can offer a suggested fix. Removing the addition appears to resolve the problem, although I expect it introduces other unwanted side effects, and the remainder of the method was also refactored. Thanks! Alistair RubCurrentLineBarDecorator(Object)>>doesNotUnderstand: #move:for:controller: [ super doesNotUnderstand: aMessage ] in RubCurrentLineBarDecorator(RubParagraphDecorator)>>doesNotUnderstand: #move:for:controller: BlockClosure>>cull: Context>>evaluateSignal: Context>>handleSignal: MessageNotUnderstood(Exception)>>signal RubExtraSelectionDecorator(Object)>>doesNotUnderstand: #move:for:controller: [ super doesNotUnderstand: aMessage ] in RubExtraSelectionDecorator(RubParagraphDecorator)>>doesNotUnderstand: #move:for:controller: BlockClosure>>cull: Context>>evaluateSignal: Context>>handleSignal: MessageNotUnderstood(Exception)>>signal RubOpeningClosingDelimiterDecorator(Object)>>doesNotUnderstand: #move:for:controller: [ super doesNotUnderstand: aMessage ] in RubOpeningClosingDelimiterDecorator(RubParagraphDecorator)>>doesNotUnderstand: #move:for:controller: BlockClosure>>cull: Context>>evaluateSignal: Context>>handleSignal: MessageNotUnderstood(Exception)>>signal TextAction(Object)>>doesNotUnderstand: #actOnMove:for:in:editor: [ :attribute | | target | "evaluate the attribute action" target := model ifNil: [ textArea ]. (attribute actOnMove: anEvent for: target in: self editor: editor) == true ifTrue: [ ^ true ] ] in RubParagraph>>move:for:controller: BlockClosure>>cull: BlockClosure>>cull:cull: [ :attribute | | range boxes | "find the boxes for the current attribute range" range := self text rangeOf: attribute startingAt: startBlock stringIndex. boxes := self selectionRectsFrom: (self characterBlockForIndex: range first) to: (self characterBlockForIndex: range last + 1). (boxes detect: [ :each | each containsPoint: aClickPoint ] ifNone: [ nil ]) ifNotNil: [ aBlock cull: attribute cull: boxes ] ] in RubParagraph>>actionAttributesUnder:event:do: Array(SequenceableCollection)>>select:thenDo: RubParagraph>>actionAttributesUnder:event:do: RubParagraph>>move:for:controller: Message>>sendTo: [ aMessage sendTo: next ] in RubOpeningClosingDelimiterDecorator(RubParagraphDecorator)>>doesNotUnderstand: #move:for:controller: BlockClosure>>on:do: RubOpeningClosingDelimiterDecorator(RubParagraphDecorator)>>doesNotUnderstand: #move:for:controller: Message>>sendTo: [ aMessage sendTo: next ] in RubExtraSelectionDecorator(RubParagraphDecorator)>>doesNotUnderstand: #move:for:controller: BlockClosure>>on:do: RubExtraSelectionDecorator(RubParagraphDecorator)>>doesNotUnderstand: #move:for:controller: Message>>sendTo: [ aMessage sendTo: next ] in RubCurrentLineBarDecorator(RubParagraphDecorator)>>doesNotUnderstand: #move:for:controller: BlockClosure>>on:do: RubCurrentLineBarDecorator(RubParagraphDecorator)>>doesNotUnderstand: #move:for:controller: RubEditingArea(RubAbstractTextArea)>>mouseMove: RubEditingArea>>mouseMove: RubEditingArea(RubAbstractTextArea)>>handleMouseMove: MouseMoveEvent>>sentTo: RubEditingArea(Morph)>>handleEvent: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: RubEditingArea(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: TransformWithLayoutMorph(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: RubTextScrollPane(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: RubScrolledTextMorph(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: PanelMorph(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: LazyTabGroupMorph(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: PanelMorph(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: PanelMorph(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: LazyTabGroupMorph(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: PanelMorph(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: GLMMorphBrick(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: GLMScrollPaneBandBrick(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: GLMPagerScrollBrick(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: GLMPagerBrick(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: GLMFoundationBrick(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: GLMSystemWindow(Morph)>>processEvent:using: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseMove: MouseMoveEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with: WorldMorph(Morph)>>processEvent:using: WorldMorph(Morph)>>processEvent: HandMorph>>sendEvent:focus:clear: HandMorph>>sendMouseEvent: HandMorph>>handleEvent: HandMorph>>processEventsFromQueue: HandMorph>>processEvents [ :h | self activeHand: h. h processEvents. self activeHand: nil ] in WorldState>>doOneCycleNowFor: Array(SequenceableCollection)>>do: WorldState>>handsDo: WorldState>>doOneCycleNowFor: WorldState>>doOneCycleFor: WorldMorph>>doOneCycle WorldMorph class>>doOneCycle [ [ WorldMorph doOneCycle. Processor yield. false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess [ self value. Processor terminateActive ] in BlockClosure>>newProcess

2 4

[Metacello] Adding existing metacello project to my new project
by sergio ruiz Feb. 8, 2017

Feb. 8, 2017

okay, i have finally decided to spend some time figuring out metacello.. for those doing the same, i would say, do this first: http://sleepycoders.blogspot.com/2013/10/dead-simple-intro-to-metacello.html then, use the âdeep into pharoâ chapter as needed.. anyway.. i am having a little bit of trouble doing one thing. I need to include VoyageMongo in my project. Itâs available in the project catalog, so i tried doing something like: baseline01: spec <version: '0.1-baseline'> spec for: #common do: [ spec blessing: #baseline. spec repository: 'http://smalltalkhub.com/mc/sergio101/InternetRadioRest/main'. spec package: 'InternetRadioJam'. spec package: 'VoyageMongoâ ] but that doesnât work. i tried several other configurations with no luck.. The website for VoyageMongo shows: Metacello new repository: 'github://pharo-nosql/voyage/mc'; baseline: 'Voyage'; load: 'mongo testsâ but i canât quite figure out the proper syntax to make this happen.. ideas? thanks! ---- 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

3 6

Book farm working again
by Stephane Ducasse Feb. 8, 2017

Feb. 8, 2017

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

2 1

[ANN] Lighthouse (for Pharo Discord server)
by Dimitris Chloupis Feb. 8, 2017

Feb. 8, 2017

Hey guys we have some new features for our online Discord chat server , called Pharo, you may find interesting. I added 2 new bots. The first one goes with the name "Pharo" its basically Mee6 bot https://mee6.xyz/ Pharo bot is responsible for many features 1) it offers moderator commands for me and Esteban 2) it offers user commands , these can be used by anyone, which are convenient ways to bring up links to pharo documentation, pharo website and my youtube pharo video tutorial playlist 3) it integrates with reddit so we can keep an eye on the smalltalk subreddit where pharoers post from time to time 4) it integrates with Esteban's rss for getting the latest news for his work on Pharo 5) it integrates with Pharo rss where news and announcement appear 6) it integrates with twitter for tracking down any new tweet from Pharo twitter account (probably more accounts will be added in the future) 7) A welcome message for beginners to get you started 8) it also has a level up system , like an rpg , that awards experience points when people participate. The lighthouse bot on the other hand is made for more advanced pharo related features. First of all the github repo is here for anyone familiar with python and Discord that is willing to give a helping hand. https://github.com/kilon/lighthouse The intention is to add a documentation system that a new user can ask question and get quick links to specific documentation. I am inspired by the fsbot in #emacs irc channel at freenode that is heavily used by new and experienced emacs users. The bot has features to search documentation and create new documentation directly from the online chat. I like also to take this opportunity to ask for suggestions , advice , desires or curses. If there is anything you would like added to the bot and you cannot be bothered to learn python or discord api just drop it on the table and if I find it interesting and easy enough I will implement it. I am also investigating a python library I found for AI chatbot which learns the more it chats with you and it could be turned to an online assistant for newcomers and experienced pharo users. Maybe its a bit far fetched but I willing to give it a try. So no promises.

1 0

visualizing ConfigurationOf dependencies with GTInspector?
by Peter Uhnak Feb. 7, 2017

Feb. 7, 2017

Hi, maybe I was dreaming but I thought I saw somewhere that GTInspector could show the dependencies and groups in ConfigurationOf classes. Does something like that exist? (Obviously when I inspect any such class it doesn't show it). Thanks, Peter

2 2

Persisting data in the Image
by sergio ruiz Feb. 7, 2017

Feb. 7, 2017

Is it enough to create a collection on a class to persist data and keep it away from the GC? something like: class Person>>people ^ <an ordered collection of people> where add: and remove: would remove them from the collection.. ---- 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

3 3

Pharo Spur 64 VM
by Benoit St-Jean Feb. 6, 2017

Feb. 6, 2017

Is this normal, I could not find the Spur 64bit VM for Windows on the Pharo file server? It is available for Mac & Linux but there's no file in the "win" directory.Â tia

1 0

Slack Invites doesn't work correctly
by mldavis＠chaparralwest.com Feb. 6, 2017

Feb. 6, 2017

In the milestone release of Pharo By Example 5: "Pharo is also active on Slack - a platform for chat based on IRC (http: //pharoproject.slack.com), just ask for an invitation at http://slackinvites.pharo.org. Everybody is welcomed." However, http://slackinvites.pharo.org goes to what appears to be an invalid page. How can a user get access to Pharo on slack? --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 4