November 2017 - Pharo-users

Article about PowerPoint and Smalltalk

by askoh

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 Marcus Denker

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

Nov. 21, 2017

Re: [Pharo-users] RBRuleIfNotNilDo usage

by Alistair Grant

Hi Marcus, On 21 November 2017 at 11:18, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> Thanks! >> >> #ifNotNilDo: was deprecated in Pharo 6, and the method was removed >> completely in Pharo 7. >> >> The easiest thing to do is to port #ifNotNilDo: forward to Pharo 7 so >> that the methods are automatically re-written. >> > > Yes, this would be best. > > we never deprecated ifNotNilDo: because it was too intrusive. With the retwriting > deprecation it is possible, but then to not be intrusive, we need to keep the deprecated > methods longer. > > Of course in the end, people only act if they are forced, so the question is if it would > help that much. Actually I meant that I will just port the rewrite rule forward in my image, not that it should be done as part of the official distribution. I agree that we need to be forced, and we don't want to clutter up the image with an ever growing list of deprecated methods, so I'm fine with the current process. Sorry for the poor choice of wording. Cheers, Alistair

Nov. 21, 2017

Re: [Pharo-users] RBRuleIfNotNilDo usage

by Marcus Denker

> > Thanks! > > #ifNotNilDo: was deprecated in Pharo 6, and the method was removed > completely in Pharo 7. > > The easiest thing to do is to port #ifNotNilDo: forward to Pharo 7 so > that the methods are automatically re-written. > Yes, this would be best. we never deprecated ifNotNilDo: because it was too intrusive. With the retwriting deprecation it is possible, but then to not be intrusive, we need to keep the deprecated methods longer. Of course in the end, people only act if they are forced, so the question is if it would help that much. Marcus

Nov. 21, 2017

Roassal2 breaks Pharo 7

by Alistair Grant

Hi Everyone, Loading Roassal 2 in Pharo 7 with: Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; configurationOf: 'Roassal2'; loadStable. makes the image unusable due to changes in NewValueHolder. Roassal adds: NewValueHolder>>announcer ^ announcer which is fine in Pharo 6 because NewValueHodler is a subclass of Object and initialises announcer in #initialize. In Pharo 7 NewValueHolder is a subclass of Model and relies on lazy initialisation of announcer in the corresponding accessor method inherited from Model. But... since Roassal is overriding the accessor method, announcer is never initialised, with the result that errors similar to: UndefinedObject(Object)>>doesNotUnderstand: #announce: are triggered (often enough that the image is largely unusable). I think the solution is to modify the packaging so that NewValueHolder>>announce is moved in to a separate package that is only loaded in Pharo 6 and earlier. Thoughts? Thanks! Alistair

Nov. 21, 2017

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

by Offray Vladimir Luna CÃ¡rdenas

On 20/11/17 20:48, Aliaksei Syrel wrote: > Hi Offray, > > In a first email I sent a wrong installation script of Sparta but then > I sent an email with correct one... looks like it was missed. > Anyway, I updated a baseline of bloc to install Moz2D on 64bit linux. > Seems that Moz2D is installed. > That is why let's try one more time :) > Let's do it :-). > Please, install GToolkit in a fresh 64bit pharo. This way we will make > sure that you use correct versions. > Just in case here is a script. > *Mioz2D will enable itself automatically. You will not need to do > anything.* > > |Metacello new baseline: 'GToolkit'; repository: > 'github://feenkcom/gtoolkit/src'; load.| This was the script I ran the first time. Anyway this time, despite of taking time: - No installation issues are present. The smoother install until now! :-) - The Pillar tab preview is better in fonts rendering as shown below. I would add font increase/decrease on demand, line numbers, syntax highlighting for web urls (http, https), which when clicked are opened via WebBrowser and image preview for some images (maybe some Pillar file could be provided in the install with possibility to test that features). - The Bloc Pillar tab has the same issues reported before. It shows no space between letter. The "Logging an animation" example in the screenshot below produces a UFFI error and after that the tab goes gray and stops working. Cheers, Offray

Nov. 21, 2017

Re: [Pharo-users] Timespan translateToUTC problematic (Alistair Grant)

by Richard A. O'Keefe

> From: Alistair Grant <akgrant0710(a)gmail.com> > I think that there's still use for representing a date as a timespan, > i.e. a 24 hour period that we can use to find the intersection of > times, etc (in addition to adding a timezone offset to a DateTime to > figure out the date in a different country). Whether it needs to be a > separate class from Timespan I'm not so sure. From my Smalltalk library: Date methods: asMidnightDateAndTime ^DateAndTime year: self year month: self month day: self dayOfMonth hour: 0 minute: 0 second: 0 pvtSpanFrom: start to: end ^Timespan starting: start asMidnightDateAndTime ending: end asMidnightDateAndTime daySpan ^self pvtSpanFrom: self to: self next monthSpan ^self pvtSpanFrom: self thisMonth to: self nextMonth quarterSpan ^self pvtSpanFrom: self thisQuarter to: self nextQuarter yearSpan ^self pvtSpanFrom: self thisYear to: self nextYear One of the tricky things here is that the result of #daySpan may be 23, 24, or 25 hours, plus or minus a second depending where the leap seconds fall. It is *usually* a 24-hour period, but definitely not always. And of course you can't go *back* from a #daySpan to a Date without reference to a particular time zone (not zone offset, because of course the zone offset can change during a "day").

Nov. 21, 2017

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

by Aliaksei Syrel

Hi Offray, In a first email I sent a wrong installation script of Sparta but then I sent an email with correct one... looks like it was missed. Anyway, I updated a baseline of bloc to install Moz2D on 64bit linux. That is why let's try one more time :) Please, install GToolkit in a fresh 64bit pharo. This way we will make sure that you use correct versions. Just in case here is a script. *Mioz2D will enable itself automatically. You will not need to do anything.* Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load. Cheers, Alex On 21 November 2017 at 02:37, Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com> wrote: > Hi Alex, > > This was the error message I got when I tried to enter the Settings > Browser: > > Cheers, > > Offray > > On 20/11/17 20:18, Aliaksei Syrel wrote: > > Hi Offray, > > That is great news! Now since Moz2D is installed we can continue and > enable Moz2D in Bloc settings: > Here is a screenshot of how to switch rendering backend: > (After changing the backend, please reopen the editor.) > > [image: Inline images 1] > > > > Cheers, > Alex > > On 21 November 2017 at 02:09, Offray Vladimir Luna CÃ¡rdenas < > offray.luna(a)mutabit.com> wrote: > >> Hi Alex, >> >> I have installed Sparta as you told me. Still I have problems with Pillar >> Bloc rendering as show in the screenshots bellow (I forgot to add them to >> my previous mail). >> >> If Sparta is an external library that can work in 64 bits Pharo without >> any external prerequisite, why it can not be installed by the GT Documenter >> install procedure in Linux (64 bits Manjaro/Arch)? >> >> Thanks, >> >> Offray >> >> >> On 20/11/17 19:26, Aliaksei Syrel wrote: >> >> Hi Offray, >> >> === >> >> This package depends on the following classes: >>> BrTextEditorPieceElement >>> You must resolve these dependencies before you will be able to load >>> these definitions: >>> BrTextEditorPieceElement>>#drawOnSpartaCanvas: >> >> >> === >> >> We should also create a stable baseline of Brick... >> I work on text rendering improvements and 3 hours ago committed a faulty >> class (BrTextEditorPieceElement) and then removed it some time ago. You >> installed GToolkit exactly within that not-working windows :) This class is >> not used anywhere, so don't worry. Sorry for the noise. >> >> >> - 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. >> >> >> If you use 64bit Pharo then there are none. It should work out of box. If >> not, let us know. >> >> Metacello new >> baseline: 'Sparta'; >> repository: 'github://syrel/sparta:v1.1/src'; >> load: #development >> >> >> >> I will let Doru answer the other questions. >> >> Cheers, >> Alex >> >> On 21 November 2017 at 00:56, 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. >>> >>> - How Pillar markup can be extended/changed to support Markdown? >>> >>> 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. >>> >>> - How to make the Pillar tab to autosave any changes, in a similar way >>> to a spec text widget. >>> >>> 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 >>> >>>> >>> >>> >>> >>> >> >> > >

Nov. 21, 2017

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

by Offray Vladimir Luna CÃ¡rdenas

Hi Alex, This was the error message I got when I tried to enter the Settings Browser: Cheers, Offray On 20/11/17 20:18, Aliaksei Syrel wrote: > Hi Offray, > > That is great news! Now since Moz2D is installed we can continue and > enable Moz2D in Bloc settings: > Here is a screenshot of how to switch rendering backend: > (After changing the backend, please reopen the editor.) > > Inline images 1 > > > > Cheers, > Alex > > On 21 November 2017 at 02:09, Offray Vladimir Luna CÃ¡rdenas > <offray.luna(a)mutabit.com <mailto:offray.luna@mutabit.com>> wrote: > > Hi Alex, > > I have installed Sparta as you told me. Still I have problems with > Pillar Bloc rendering as show in the screenshots bellow (I forgot > to add them to my previous mail). > > If Sparta is an external library that can work in 64 bits Pharo > without any external prerequisite, why it can not be installed by > the GT Documenter install procedure in Linux (64 bits Manjaro/Arch)? > > Thanks, > > Offray > > > On 20/11/17 19:26, Aliaksei Syrel wrote: >> Hi Offray, >> >> === >> >> This package depends on the following classes: >> Â BrTextEditorPieceElement >> You must resolve these dependencies before you will be able >> to load >> these definitions: >> Â BrTextEditorPieceElement>>#drawOnSpartaCanvas: >> >> >> === >> >> We should also create a stable baseline of Brick... >> I work on text rendering improvements and 3 hours ago committed a >> faulty class (BrTextEditorPieceElement) and then removed it some >> time ago. You installed GToolkit exactly within that not-working >> windows :) This class is not used anywhere, so don't worry. Sorry >> for the noise. >> >> >> - 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. >> >> >> If you use 64bit Pharo then there are none. It should work out of >> box. If not, let us know. >> >> Metacello new >> baseline: 'Sparta'; >> repository: 'github://syrel/sparta:v1.1/src'; >> load: #development >> >> >> I will let Doru answer the other questions. >> >> Cheers, >> Alex >> >> On 21 November 2017 at 00:56, Offray Vladimir Luna CÃ¡rdenas >> <offray.luna(a)mutabit.com <mailto:offray.luna@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. >> >> - How Pillar markup can be extended/changed to support Markdown? >> >> 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. >> >> - How to make the Pillar tab to autosave any changes, in a >> similar way >> to a spec text widget. >> >> 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 <mailto:tudor@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 >> <mailto:offray.luna@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 >> >>>> >> >> >> >> > >

Nov. 21, 2017

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

by Andrew Glynn

Here is a page with a set of scripts to install Moz2d for various *nixes (different Linux distros, OS X) https://github.com/syrel/Moz2D Sent from Mail for Windows 10 From: Aliaksei Syrel Sent: Monday, November 20, 2017 8:32 PM To: Any question about pharo is welcome Subject: Re: [Pharo-users] Bloc installation on Linux [WAS: Re: Aboutimplementing a "Mini Pillar" in-image renderer for Pharo ...] If Sparta is an external library that can work in 64 bits Pharo without any external prerequisite, why it can not be installed by the GT Documenter install procedure in Linux (64 bits Manjaro/Arch)? It will be :) The problem is that I got a first confirmation that it works just a week ago. I am in the process of collecting more feedback from people using various linux distros. Also, I work on a smarter Sparta installer that first tries to actually install Moz2D, checks whether it works and if not falls back to Cairo. Hopefully we will ship installer soon. Cheers, Alex On 21 November 2017 at 02:18, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: Hi Offray, That is great news! Now since Moz2D is installed we can continue and enable Moz2D in Bloc settings: Here is a screenshot of how to switch rendering backend: (After changing the backend, please reopen the editor.) Cheers, Alex On 21 November 2017 at 02:09, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: Hi Alex, I have installed Sparta as you told me. Still I have problems with Pillar Bloc rendering as show in the screenshots bellow (I forgot to add them to my previous mail). If Sparta is an external library that can work in 64 bits Pharo without any external prerequisite, why it can not be installed by the GT Documenter install procedure in Linux (64 bits Manjaro/Arch)? Thanks, Offray On 20/11/17 19:26, Aliaksei Syrel wrote: Hi Offray, === This package depends on the following classes: Â BrTextEditorPieceElement You must resolve these dependencies before you will be able to load these definitions: Â BrTextEditorPieceElement>>#drawOnSpartaCanvas: === We should also create a stable baseline of Brick... I work on text rendering improvements and 3 hours ago committed a faulty class (BrTextEditorPieceElement) and then removed it some time ago. You installed GToolkit exactly within that not-working windows :) This class is not used anywhere, so don't worry. Sorry for the noise. - 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. If you use 64bit Pharo then there are none. It should work out of box. If not, let us know. Metacello new baseline: 'Sparta'; repository: 'github://syrel/sparta:v1.1/src'; load: #development I will let Doru answer the other questions. Cheers, Alex On 21 November 2017 at 00:56, 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. - How Pillar markup can be extended/changed to support Markdown? 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. - How to make the Pillar tab to autosave any changes, in a similar way to a spec text widget. 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 >>>>

Nov. 21, 2017