November 2017 - Pharo-users

Re: [Pharo-users] Why does the test runner show red when I correct a test?

by Prof. Andrew P. Black

While we are discussing colors, what should we do about a test that does not make any assertions at all? A couple of years ago, a smart student who was working on a testing dialect for me decided that such tests should be in a new category all of their own. Later I simplified things and just made these tests fail. I am pretty convinced now that this is the right behaviour. It certainly suits my purposes (teaching TDD); if the student omits to make any assertions, they have a failing test. The message is: "Failure: test made no assertions". Currently, such a test is green in Pharo. In 2013, I filed a bug report on a bunch of tests of #printOn: on collections that made no assertions. (The test writer didnât understand how streams worked, and made assertions for each element of the empty string.) I was reminded of this just this week, because those tests have yet to be fixed. I suspect that if they had been yellow, rather than green, then they would have been fixed before now. I plan to fix those tests on Friday, but I also wonder about changing the behaviour of the testing framework. What do you think? Andrew

Nov. 21, 2017

Re: [Pharo-users] Bloc installation on Linux [WAS: Re: About implementing a "Mini Pillar" in-image renderer for Pharo ...]

by Tudor Girba

Hi, Thanks for trying the Linux installation. Let me address the non-installation questions below. > On Nov 21, 2017, at 12:56 AM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi Doru & Alex, > > Installation works now. During installation process I get this message: > > === > > This package depends on the following classes: > BrTextEditorPieceElement > You must resolve these dependencies before you will be able to load > these definitions: > BrTextEditorPieceElement>>#drawOnSpartaCanvas: > > === > > That I imagine, is related with the absence of Moz2D. Also, Pillar > syntax works now as shown in the first screenshot, but the bloc preview > looks strange, without preserving proper spacing between characters and > using crossed boxes for character returns (I imagine that is related > with Moz2D, but cairo is working, as you can see in the code previews). > > So, some old questions for my response to the feedback request a year > ago remain and new questions arise. > > The old ones: > > - How can font size of the pillar preview can be increased/decreased on > demand? Having proper text size for reading and writing text is > important in a text editor. The font used is the default text size. To make it customizable, we would need to extend the parser and the UI. I do not plan/have time to make these changes any time soon, but you are welcome to look at the code and propose changes, or simply create your own version. > - How Pillar markup can be extended/changed to support Markdown? You cannot extend it. You would need to hook a Markdown parser into the syntax highlighter for that. > The new ones: > > - Which are the requisites for Moz2D on a Linux environment. It can be > on Ubuntu/Debian. I can try to translate them to Manjaro/Arch. > > - How add line numbers to the "Pillar" tab (similarly to "Contents" tab > and how to make it the default tab view. Letâs take a moment to learn how to learn from the existing system once an example is available. An inspector tab is defined in an extension method in the class of the object you are inspecting. Look at the Meta tab of a FileReference instance, and you get to: gtInspectorContentsIn: composite <gtInspectorPresentationOrder: 5> composite text title: 'Contents'; display: [ self readStreamDo: [ :stream | | result | result := [(stream next: 10000) asString] on: Error do: [ (stream binary next: 10000) asString ]. stream size > 10000 ifTrue: [ result, ' ... truncated ...' ] ifFalse: [ result ] ] ]; withLineNumbers: true; > - How to make the Pillar tab to autosave any changes, in a similar way > to a spec text widget. You would have to hook to the change of the #text port in order to add the autosave. For an example of how to hook to the #text port changes, take a look at GLMBasicExamples>>#onChangeOfPortAction Cheers, Doru > Cheers, > > Offray > > > > On 16/11/17 16:32, Tudor Girba wrote: >> Hi Offray, >> >> Please do not forget to try and let us know if it works now. >> >> Cheers, >> Doru >> >> >> >>> On Nov 15, 2017, at 9:20 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi Offray, >>> >>> Alex took a look at your specific distro and he found and fixed your issue. >>> >>> Please try again installing GT/Bloc from scratch in a fresh Pharo 6.1 image. >>> >>> Please also note that the rendering on Linux is not using Moz2D so it will not be as beautiful as in pictures. The reason for this is that there are external dependencies that are required and we would need help to figure that setup. >>> >>> Cheers, >>> Doru >>> >>> >>>> On Nov 14, 2017, at 10:07 PM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >>>> >>>> Hi, >>>> >>>> The readme is clearer now about Iceberg integration as an option not as >>>> prerequisite. Installation works, but Pillar preview tab is grey and >>>> clicking on it rises: "Instance of FFIExternalResourceManager class did >>>> not understand #removeResource:". Also the syntax highlighting in the >>>> (plain) Pillar tab is not working and neither the image preview. A plain >>>> installation of just Pillar (without GT Documenter) got those two >>>> working once. >>>> >>>> Cheers, >>>> >>>> Offray >>>> >>>> >>>> On 14/11/17 12:37, Tudor Girba wrote: >>>>> Hi, >>>>> >>>>> We changed the baseline to not require Moz2D on Linux. Could you please try again? >>>>> >>>>> I also updated the README. >>>>> >>>>> Cheers, >>>>> Doru >>>>> > > > -- www.tudorgirba.com www.feenk.com "No matter how many recipes we know, we still value a chef."

Nov. 21, 2017

Re: [Pharo-users] [ANN] Pharo TechTalk 21 Nov: Discord Demo

by Juraj Kubelka

Hi, the TechTalk record is available at the same link: https://www.youtube.com/watch?v=33kXsOiP6wA <https://www.youtube.com/watch?v=33kXsOiP6wA> and includes outline to simplify navigation. Cheers, Juraj TechTalk Outline: - 01:58 The beginning of the talk - 04:30 Webhook - 04:33 How to Create Webhook - 05:39 Webhook Examples - 10:33 Webhook Use Case: Script of the Day from Nautilus Code Browser - 18:39 Webhook Use Case: Server Problem Notification - 22:45 Bot App (chatbot) - 24:47 How to Create a Bot App - 28:28 Bot App Examples - 33:17 Bot Use Case: Source Code Expertise - 41:40 Standard User Client - 42:57 User Client Example - 45:06 User Client Use Case: Asking Directly from Pharo Playground - 47:06 User Client Use Case: Receiving Questions and Answering in Pharo - 50:50 Final Thoughts About Discord Integration in Inspector and Debugger - 52:44 Discussion > On Nov 21, 2017, at 12:54, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > Hi! > > The TechTalk starts in about 10 minutes. Join us on Discord, the techtalk channel. > > Cheers, > Juraj > > >> On Nov 21, 2017, at 10:11, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> The link to the live stream is this: >> >> https://www.youtube.com/watch?v=33kXsOiP6wA <https://www.youtube.com/watch?v=33kXsOiP6wA> >> >> It start in a bit less than 3 hours. >> >> Marcus >> >>> On 18 Nov 2017, at 09:13, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >>> >>> Pharo TechTalk: Discord Demo >>> When? 21 Nov 2017 5:00 PM - 7:00 PM (UTC+01:00) >>> >>> Topic: "Discord communication Demoâ, how to script discord from Pharo. >>> >>> https://association.pharo.org/event-2642665 <https://association.pharo.org/event-2642665> >> >

Nov. 21, 2017

Re: [Pharo-users] Why does the test runner show red when I correct a test?

by Tim Mackinnon

I would agree that grey is better than red - but I personally think weâre being too pedantic on this - particularly when doing TDD and coding in the debugger. If Iâm writing straight forward tests and like to see a red failure (either by deliberately returning false, or a subclass responsibility, or -1) and then correct that failure in the debugger to return the correct result - then its tedious to have to run the test again (in fact it feels odd). For the rare time that I got it wrong - it will show up when I run all tests on the next phase. I accept that others may see this the other way around - but Iâm a more optimistic guy. This said - maybe we make it an option (or an easy code switch) - Iâd default it to the optimistic TDD mode personally. My CI server will give me the full lowdown. Tim > On 15 Nov 2017, at 21:50, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Richard Sargent wrote >> I would go a little further. Any method modified by the developer during >> the course of running a test voids the ability to claim the test >> succeeded. >> Likewise, for any object editted in an inspector. > > That makes sense to me. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Nov. 21, 2017

Re: [Pharo-users] Timespan translateToUTC problematic

by Sven Van Caekenberghe

> On 21 Nov 2017, at 18:07, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > On 20 November 2017 at 09:16, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> We can discuss about this ad infinitum. I think we all agree that >> there are 2 views (abstract calendar date and concrete time >> interval/span, which requires a TZ), as well as 2 possible ways to >> deal with the second case (TZ inside date or as context outside of the >> date). > > > Right, I think changing things now will be quite a bit of work. > > However there are a couple of things we can do to make life a bit easier: > > 1. Add a method that facilitates TZ independent comparisons. > 2. Add a bit more information in the class comments. > > > I've named the method #dmyEquals: below, although I don't particularly > like it. If anyone has a better idea, please reply. #equals: #calendarEquals: #equalIgnoreTimezone: > I've also added some proposed text for the class comments. More comments are always good. > If I don't hear back in a couple of days I'll submit a PR (with > automated tests). > > > Cheers, > Alistair > > ---- > > dmyEquals: aDate > "Perform a time zone independent comparison of the dates, i.e. > only compare day, month and year" > > ^self year = aDate year and: [ > self monthIndex = aDate monthIndex and: > [ self dayOfMonth = aDate dayOfMonth ] ] > > ---- > Class comment: > > Instances of Date are Timespans with duration of 1 day. > Their default creation assumes a start of midnight in the local time zone. > > !Comparing Dates > > We tend to use dates in one of two modes: > > - Time zone dependent > - Time zone independent > > In the first instance, dates are only the same if they are in the same > time zone (otherwise they are two different 24 hour periods). This is > the default behaviour of Date. > > In the second, comparison is only interested in whether the day, month > and year are the same. > > As an example, take someone's birthday. If I want to know whether we > were born on the same day, I will want to compare dates without time > zones. If I want to know if it is currently their birthday where they > are, I'll want to use time zones. > > > [[[language=smalltalk > | birthday1 birthday2 | > > birthday1 := (DateAndTime fromString: '2018/01/01T00:00:00+10') asDate. > birthday2 := (DateAndTime fromString: '2018/01/01T00:00:00+01') asDate. > > "Is it person 1's birthday now? (where they live: UTC+10)" > birthday1 includes: DateAndTime now. > > "Do person 1 and person 2 have the same birthday?" > birthday1 dmyEquals: birthday2. > ]]] >

Nov. 21, 2017

Re: [Pharo-users] Timespan translateToUTC problematic

by Alistair Grant

On 20 November 2017 at 09:16, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > We can discuss about this ad infinitum. I think we all agree that > there are 2 views (abstract calendar date and concrete time > interval/span, which requires a TZ), as well as 2 possible ways to > deal with the second case (TZ inside date or as context outside of the > date). Right, I think changing things now will be quite a bit of work. However there are a couple of things we can do to make life a bit easier: 1. Add a method that facilitates TZ independent comparisons. 2. Add a bit more information in the class comments. I've named the method #dmyEquals: below, although I don't particularly like it. If anyone has a better idea, please reply. I've also added some proposed text for the class comments. If I don't hear back in a couple of days I'll submit a PR (with automated tests). Cheers, Alistair ---- dmyEquals: aDate "Perform a time zone independent comparison of the dates, i.e. only compare day, month and year" ^self year = aDate year and: [ self monthIndex = aDate monthIndex and: [ self dayOfMonth = aDate dayOfMonth ] ] ---- Class comment: Instances of Date are Timespans with duration of 1 day. Their default creation assumes a start of midnight in the local time zone. !Comparing Dates We tend to use dates in one of two modes: - Time zone dependent - Time zone independent In the first instance, dates are only the same if they are in the same time zone (otherwise they are two different 24 hour periods). This is the default behaviour of Date. In the second, comparison is only interested in whether the day, month and year are the same. As an example, take someone's birthday. If I want to know whether we were born on the same day, I will want to compare dates without time zones. If I want to know if it is currently their birthday where they are, I'll want to use time zones. [[[language=smalltalk | birthday1 birthday2 | birthday1 := (DateAndTime fromString: '2018/01/01T00:00:00+10') asDate. birthday2 := (DateAndTime fromString: '2018/01/01T00:00:00+01') asDate. "Is it person 1's birthday now? (where they live: UTC+10)" birthday1 includes: DateAndTime now. "Do person 1 and person 2 have the same birthday?" birthday1 dmyEquals: birthday2. ]]]

Nov. 21, 2017

Re: [Pharo-users] Article about PowerPoint and Smalltalk

by Andrew Glynn

https://youtu.be/_JU48-FVqvQ Doug is a fellow I worked with early in my career, writing Lingo in Director for presentations. Andrew Glynn From: askoh Sent: Tuesday, November 21, 2017 10:51 AM To: pharo-users(a)lists.pharo.org Subject: [Pharo-users] Article about PowerPoint and Smalltalk https://spectrum.ieee.org/tech-history/cyberspace/the-improbable-origins-of… I like the end "Meanwhile, the dominant mode of personal computing globally has firmly shifted from the desktop and laptop to the smartphone. As yet, no new vision of personal computing like the one that came from Xerox PARC in the 1970s has emerged. And so for the moment, it appears that PowerPoint, as we know it, is here to stay." Aik-Siong Koh -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 21, 2017

Re: [Pharo-users] Article about PowerPoint and Smalltalk

by Andrew Glynn

Sounds a lot like OpenDoc. http://apple.wikia.com/wiki/OpenDoc Btw it was the Xerox Star, which was largely an early version of Smalltalk with the colors inverted to look more like paper (for desktop publishing). Some of the other technologies that came out of the Star were postscript (itâs inventor left and founded Adobe), Ethernet (its inventor founded 3COM), and WYSIWYG editing. The Star came out in 1976. Andrew Glynn From: H. Hirzel Sent: Tuesday, November 21, 2017 11:16 AM To: Any question about pharo is welcome Subject: Re: [Pharo-users] Article about PowerPoint and Smalltalk Interesting... "The pair left Apple late in 1982, and by early 1983," .... "Pohlman and Campbellâs idea was to bring a graphical-software environment like the Xerox Altoâs to the hugely popular but graphically challenged PC." "Pohlman and Campbell envisioned an object-oriented software platform called Foundation, which was centered around documents. Each Foundation document would act like an object in Smalltalk, which a business user would stitch together with other documents to create, say, a report containing a graph of recent sales, a statistical analysis of customer traits, drawings of proposed changes to a product, and a block of explanatory text. Each element would be live, malleable, and programmable. " Thank you for the link --Hannes On 11/21/17, askoh <askoh(a)askoh.com> wrote: > https://spectrum.ieee.org/tech-history/cyberspace/the-improbable-origins-of… > > > I like the end > "Meanwhile, the dominant mode of personal computing globally has firmly > shifted from the desktop and laptop to the smartphone. As yet, no new > vision > of personal computing like the one that came from Xerox PARC in the 1970s > has emerged. And so for the moment, it appears that PowerPoint, as we know > it, is here to stay." > > Aik-Siong Koh > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Nov. 21, 2017

Re: [Pharo-users] Article about PowerPoint and Smalltalk

by H. Hirzel

Interesting... "The pair left Apple late in 1982, and by early 1983," .... "Pohlman and Campbellâs idea was to bring a graphical-software environment like the Xerox Altoâs to the hugely popular but graphically challenged PC." "Pohlman and Campbell envisioned an object-oriented software platform called Foundation, which was centered around documents. Each Foundation document would act like an object in Smalltalk, which a business user would stitch together with other documents to create, say, a report containing a graph of recent sales, a statistical analysis of customer traits, drawings of proposed changes to a product, and a block of explanatory text. Each element would be live, malleable, and programmable. " Thank you for the link --Hannes On 11/21/17, askoh <askoh(a)askoh.com> wrote: > https://spectrum.ieee.org/tech-history/cyberspace/the-improbable-origins-of… > > > I like the end > "Meanwhile, the dominant mode of personal computing globally has firmly > shifted from the desktop and laptop to the smartphone. As yet, no new > vision > of personal computing like the one that came from Xerox PARC in the 1970s > has emerged. And so for the moment, it appears that PowerPoint, as we know > it, is here to stay." > > Aik-Siong Koh > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Nov. 21, 2017

Re: [Pharo-users] [ANN] Pharo TechTalk 21 Nov: Discord Demo

by Juraj Kubelka

Hi! The TechTalk starts in about 10 minutes. Join us on Discord, the techtalk channel. Cheers, Juraj > On Nov 21, 2017, at 10:11, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > The link to the live stream is this: > > https://www.youtube.com/watch?v=33kXsOiP6wA <https://www.youtube.com/watch?v=33kXsOiP6wA> > > It start in a bit less than 3 hours. > > Marcus > >> On 18 Nov 2017, at 09:13, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> Pharo TechTalk: Discord Demo >> When? 21 Nov 2017 5:00 PM - 7:00 PM (UTC+01:00) >> >> Topic: "Discord communication Demoâ, how to script discord from Pharo. >> >> https://association.pharo.org/event-2642665 <https://association.pharo.org/event-2642665> >

Nov. 21, 2017