February 2017 - Pharo-users

Book farm working again

by Stephane Ducasse

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

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

by Gabriel Cotelli

Something like this: ... spec baseline: 'Voyage' with: [ spec repository: 'github://pharo-nosql/voyage/mc'; load: #( 'mongo' 'tests') ]; import: 'Voyage'. spec package: 'InternetRadioJam' with: [ spec requires: 'Voyage' ] ... On Wed, Feb 8, 2017 at 12:06 PM, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > > 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 >

Feb. 8, 2017

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

by phil＠highoctane.be

Check how seaside dependency is done in here: https://github.com/Pharophile/PechaKucha Phil On Wed, Feb 8, 2017 at 4:06 PM, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > > 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 >

Feb. 8, 2017

[Metacello] Adding existing metacello project to my new project

by sergio ruiz

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

Feb. 8, 2017

[ANN] Lighthouse (for Pharo Discord server)

by Dimitris Chloupis

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.

Feb. 8, 2017

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

by Nicolai Hess

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] SLICE-Issue-18901-Highlight-message-send-selector-on-mouse-over-NicolaiHess.4 introduces new bug?

by Alistair Grant

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? Thanks again, Alistair

Feb. 8, 2017

Re: [Pharo-users] visualizing ConfigurationOf dependencies with GTInspector?

by Peter Uhnak

Yes, this. Thanks! Peter On Sun, Feb 05, 2017 at 05:50:51PM +0100, Tudor Girba wrote: > Hi, > > The dependencies extensions are available in the ConfigurationOfGTInspector (or in the Moose image). > > You have to inspect a version object: > > > > > Cheers, > Doru > > > > > On Feb 5, 2017, at 4:51 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > > 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 > > > > -- > www.tudorgirba.com > www.feenk.com > > "Every thing has its own flow." > > > > >

Feb. 7, 2017

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

by Nicolai Hess

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. nicolai 2017-02-07 6:37 GMT+01:00 Alistair Grant <akgrant0710(a)gmail.com>: > 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 > >

Feb. 7, 2017

Re: [Pharo-users] Pharo Spur 64 VM

by Esteban Lorenzano

> On 6 Feb 2017, at 21:41, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Le 06/02/2017 Ã 21:31, Benoit St-Jean via Pharo-users a Ã©crit : > > > Hi! > > IIRC, the windows VM will need some more time to be ready. Only Linux > and OSX ones are usable at the moment. ^ this. as Cyril says, win 64bits vm is still not ready (and it will take some more time to be). Esteban > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

Feb. 7, 2017