November 2017 - Pharo-users

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

by Aliaksei Syrel

> > 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.) > > [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 Aliaksei Syrel

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, 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: About implementing a "Mini Pillar" in-image renderer for Pharo ...]

by Aliaksei Syrel

Oops, the wrong script. Here is the right one: Metacello new baseline: 'Sparta'; repository: 'github://syrel/sparta/src'; load: #development Cheers, Alex On 21 November 2017 at 01:26, Aliaksei Syrel <alex.syrel(a)gmail.com> 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 Aliaksei Syrel

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 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. 20, 2017

Re: [Pharo-users] New Pharo article at The Cohort

by Offray Vladimir Luna CÃ¡rdenas

That would be nice. So the issue is how we can find the proper size of the community learning/doing together. On 20/11/17 12:10, horrido wrote: > Well, I don't think we have to worry about Pharo becoming too big. > > I never expected Smalltalk to ever become big (again). I just want to see it > lifted out of obscurity. If people talk about Pharo in the same breath as > Clojure, Elixir, Haskell, and Rust, that would be great. > > > > Offray Vladimir Luna CÃ¡rdenas-2 wrote >> Agreed. This obsession with popularity in North America is kind of sad >> when is looked from elsewhere and is really pervasive: from teenagers >> comedies to technologies and business. Any community needs "proper size" >> to keep momentum and agility. Too big, it become bureaucratic or >> stagnant. Too little, it become fragile and non supportive. >> >> Cheers, >> >> Offray >> >> >> On 20/11/17 11:20, Andrew Glynn wrote: >>> The amount of FUD spread by M$ and IBM, just two very noticeable >>> examples out of numerous others, is possible because very few of those >>> laws are applicable unless the statement is part of a paid campaign by >>> the originating company.Â If I exaggerate how well my MB 400E was made >>> on a blog post, neither I nor MB are likely to run into any legal >>> issues.Â If MB does so in an advertisement, it becomes a different >>> matter. >>> >>> Â >>> >>> That said, I donât think merit is really in question.Â There are two >>> bigger ones:Â >>> >>> Â >>> >>> 1. To whose advantage is inefficient development and the tooling that >>> promotes it? >>> >>> Â >>> >>> 2. How would people who find it too /difficult/ to maintain state in >>> a single threaded language acclimatize themselves to Pharo >>> Smalltalk (or to any actual programming language, for that matter) ? >>> >>> Â >>> >>> The first question doesnât have one answer, since itâs to the >>> advantage of a number of interested parties, from large organizations >>> that can afford inefficiency more than smaller competitors (and >>> simultaneously can afford the not inconsequential investment in >>> writing a proprietary Smalltalk or something similar for things that >>> âmust workâ), to click-bait online âforumsâ such as âSlack Overloadâ.Â >>> >>> Â >>> >>> The second, well, I suppose how you would answer it depends on your >>> experience working with said people. Â My own hasnât been particularly >>> positive. >>> >>> Â >>> >>> Not that Iâm particularly enamoured with the idea of Pharo becoming >>> mainstream.Â It would then be subject to the same disruption as >>> current mainstream environments.Â The degradation of Java environments >>> over the past 20 years is a good example.Â It was never great, but the >>> combination of syntactic parmesan to hide the bad spaghetti and the >>> need to support every passing fad has made it nearly unusable. Iâve >>> seen a number of companies specifying Java 7 or even Java 6 in their >>> tech stacks âbecause Java 8 is too unreliableâ. >>> >>> Â >>> >>> Until mainstream âsoftware engineersâ start /acting/ like engineers, >>> i.e. people who make things /work/, rather than popularity contestants >>> or fashion victims, that wonât change. >>> >>> Â >>> >>> Andrew Glynn >>> >>> Â >>> >>> *From: *Richard A. O'Keefe <mailto: >> ok@.ac >> > >>> *Sent: *Sunday, November 19, 2017 6:19 PM >>> *To: * >> Pharo-users@.pharo >> <mailto: >> Pharo-users@.pharo >> > >>> *Subject: *Re: [Pharo-users] New Pharo article at The Cohort >>> >>> Â >>> >>> I'm obviously missing a lot of the context here, but inÂ my >>> >>> country (New Zealand) there is something called the >>> >>> Fair Trading Act. >>> >>> Â >>> >>> My understanding from reading the Commerce Commission web >>> >>> site is that >>> >>> Â - false or misleading representations about goods or >>> >>> Â Â Â services or the availability of goods are against the >>> >>> Â Â Â law >>> >>> Â - "The penalties for breaching the Act can be severe" >>> >>> Â Â Â (Grant Harris). >>> >>> Â - obviously wild exaggerations made to be funny are sort >>> >>> Â Â Â of OK, but if anyone falls for them you could find this >>> >>> Â Â Â tested in court >>> >>> Â - "Any claims made to bolster the image of a business or >>> >>> Â Â Â its products or services must be accurate." >>> >>> Â - "The Act applies even when there was no intention to >>> >>> Â Â Â breach the Act".Â (Grant Harris again.) >>> >>> Â >>> >>> http://www.comcom.govt.nz/fair-trading/fair-trading-act-fact-sheets/claimin… >>> >>> Â >>> >>> The Fair Trading Act was passed as part of a program of market >>> >>> liberalisation and in order to foster competition and market >>> >>> efficiency, and the majority of the cases have been trader-to- >>> >>> trader.Â Why mention this?Â Because it's not just places where >>> >>> consumer protection is high-ranked that have such laws; it's >>> >>> also places that are gung-ho about free markets and competition >>> >>> and want to protect businesses. >>> >>> Â >>> >>> Law in the USA varies from state to state.Â For California, see >>> >>> https://www.truthinadvertising.org/california/ >>> >>> (which has a navbar on the right for other states). >>> >>> Â >>> >>> Me, I think Pharo is good enough to "sell" on its merits >>> >>> without any exaggerations.Â (If you could combine the great >>> >>> looks of Dolphin Smalltalk with the great features of Pharo, >>> >>> drool...) >>> >>> Â >>> >>> Â >>> > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Nov. 20, 2017

Re: [Pharo-users] New Pharo article at The Cohort

by horrido

Well, I don't think we have to worry about Pharo becoming too big. I never expected Smalltalk to ever become big (again). I just want to see it lifted out of obscurity. If people talk about Pharo in the same breath as Clojure, Elixir, Haskell, and Rust, that would be great. Offray Vladimir Luna CÃ¡rdenas-2 wrote > Agreed. This obsession with popularity in North America is kind of sad > when is looked from elsewhere and is really pervasive: from teenagers > comedies to technologies and business. Any community needs "proper size" > to keep momentum and agility. Too big, it become bureaucratic or > stagnant. Too little, it become fragile and non supportive. > > Cheers, > > Offray > > > On 20/11/17 11:20, Andrew Glynn wrote: >> >> The amount of FUD spread by M$ and IBM, just two very noticeable >> examples out of numerous others, is possible because very few of those >> laws are applicable unless the statement is part of a paid campaign by >> the originating company.Â If I exaggerate how well my MB 400E was made >> on a blog post, neither I nor MB are likely to run into any legal >> issues.Â If MB does so in an advertisement, it becomes a different >> matter. >> >> Â >> >> That said, I donât think merit is really in question.Â There are two >> bigger ones:Â >> >> Â >> >> 1. To whose advantage is inefficient development and the tooling that >> promotes it? >> >> Â >> >> 2. How would people who find it too /difficult/ to maintain state in >> a single threaded language acclimatize themselves to Pharo >> Smalltalk (or to any actual programming language, for that matter) ? >> >> Â >> >> The first question doesnât have one answer, since itâs to the >> advantage of a number of interested parties, from large organizations >> that can afford inefficiency more than smaller competitors (and >> simultaneously can afford the not inconsequential investment in >> writing a proprietary Smalltalk or something similar for things that >> âmust workâ), to click-bait online âforumsâ such as âSlack Overloadâ.Â >> >> Â >> >> The second, well, I suppose how you would answer it depends on your >> experience working with said people. Â My own hasnât been particularly >> positive. >> >> Â >> >> Not that Iâm particularly enamoured with the idea of Pharo becoming >> mainstream.Â It would then be subject to the same disruption as >> current mainstream environments.Â The degradation of Java environments >> over the past 20 years is a good example.Â It was never great, but the >> combination of syntactic parmesan to hide the bad spaghetti and the >> need to support every passing fad has made it nearly unusable. Iâve >> seen a number of companies specifying Java 7 or even Java 6 in their >> tech stacks âbecause Java 8 is too unreliableâ. >> >> Â >> >> Until mainstream âsoftware engineersâ start /acting/ like engineers, >> i.e. people who make things /work/, rather than popularity contestants >> or fashion victims, that wonât change. >> >> Â >> >> Andrew Glynn >> >> Â >> >> *From: *Richard A. O'Keefe <mailto: > ok@.ac > > >> *Sent: *Sunday, November 19, 2017 6:19 PM >> *To: * > Pharo-users@.pharo > <mailto: > Pharo-users@.pharo > > >> *Subject: *Re: [Pharo-users] New Pharo article at The Cohort >> >> Â >> >> I'm obviously missing a lot of the context here, but inÂ my >> >> country (New Zealand) there is something called the >> >> Fair Trading Act. >> >> Â >> >> My understanding from reading the Commerce Commission web >> >> site is that >> >> Â - false or misleading representations about goods or >> >> Â Â Â services or the availability of goods are against the >> >> Â Â Â law >> >> Â - "The penalties for breaching the Act can be severe" >> >> Â Â Â (Grant Harris). >> >> Â - obviously wild exaggerations made to be funny are sort >> >> Â Â Â of OK, but if anyone falls for them you could find this >> >> Â Â Â tested in court >> >> Â - "Any claims made to bolster the image of a business or >> >> Â Â Â its products or services must be accurate." >> >> Â - "The Act applies even when there was no intention to >> >> Â Â Â breach the Act".Â (Grant Harris again.) >> >> Â >> >> http://www.comcom.govt.nz/fair-trading/fair-trading-act-fact-sheets/claimin… >> >> Â >> >> The Fair Trading Act was passed as part of a program of market >> >> liberalisation and in order to foster competition and market >> >> efficiency, and the majority of the cases have been trader-to- >> >> trader.Â Why mention this?Â Because it's not just places where >> >> consumer protection is high-ranked that have such laws; it's >> >> also places that are gung-ho about free markets and competition >> >> and want to protect businesses. >> >> Â >> >> Law in the USA varies from state to state.Â For California, see >> >> https://www.truthinadvertising.org/california/ >> >> (which has a navbar on the right for other states). >> >> Â >> >> Me, I think Pharo is good enough to "sell" on its merits >> >> without any exaggerations.Â (If you could combine the great >> >> looks of Dolphin Smalltalk with the great features of Pharo, >> >> drool...) >> >> Â >> >> Â >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 20, 2017

Re: [Pharo-users] New Pharo article at The Cohort

by Offray Vladimir Luna CÃ¡rdenas

Agreed. This obsession with popularity in North America is kind of sad when is looked from elsewhere and is really pervasive: from teenagers comedies to technologies and business. Any community needs "proper size" to keep momentum and agility. Too big, it become bureaucratic or stagnant. Too little, it become fragile and non supportive. Cheers, Offray On 20/11/17 11:20, Andrew Glynn wrote: > > The amount of FUD spread by M$ and IBM, just two very noticeable > examples out of numerous others, is possible because very few of those > laws are applicable unless the statement is part of a paid campaign by > the originating company.Â If I exaggerate how well my MB 400E was made > on a blog post, neither I nor MB are likely to run into any legal > issues.Â If MB does so in an advertisement, it becomes a different matter. > > Â > > That said, I donât think merit is really in question.Â There are two > bigger ones:Â > > Â > > 1. To whose advantage is inefficient development and the tooling that > promotes it? > > Â > > 2. How would people who find it too /difficult/ to maintain state in > a single threaded language acclimatize themselves to Pharo > Smalltalk (or to any actual programming language, for that matter) ? > > Â > > The first question doesnât have one answer, since itâs to the > advantage of a number of interested parties, from large organizations > that can afford inefficiency more than smaller competitors (and > simultaneously can afford the not inconsequential investment in > writing a proprietary Smalltalk or something similar for things that > âmust workâ), to click-bait online âforumsâ such as âSlack Overloadâ.Â > > Â > > The second, well, I suppose how you would answer it depends on your > experience working with said people. Â My own hasnât been particularly > positive. > > Â > > Not that Iâm particularly enamoured with the idea of Pharo becoming > mainstream.Â It would then be subject to the same disruption as > current mainstream environments.Â The degradation of Java environments > over the past 20 years is a good example.Â It was never great, but the > combination of syntactic parmesan to hide the bad spaghetti and the > need to support every passing fad has made it nearly unusable. Iâve > seen a number of companies specifying Java 7 or even Java 6 in their > tech stacks âbecause Java 8 is too unreliableâ. > > Â > > Until mainstream âsoftware engineersâ start /acting/ like engineers, > i.e. people who make things /work/, rather than popularity contestants > or fashion victims, that wonât change. > > Â > > Andrew Glynn > > Â > > *From: *Richard A. O'Keefe <mailto:ok@cs.otago.ac.nz> > *Sent: *Sunday, November 19, 2017 6:19 PM > *To: *Pharo-users(a)lists.pharo.org <mailto:Pharo-users@lists.pharo.org> > *Subject: *Re: [Pharo-users] New Pharo article at The Cohort > > Â > > I'm obviously missing a lot of the context here, but inÂ my > > country (New Zealand) there is something called the > > Fair Trading Act. > > Â > > My understanding from reading the Commerce Commission web > > site is that > > Â - false or misleading representations about goods or > > Â Â Â services or the availability of goods are against the > > Â Â Â law > > Â - "The penalties for breaching the Act can be severe" > > Â Â Â (Grant Harris). > > Â - obviously wild exaggerations made to be funny are sort > > Â Â Â of OK, but if anyone falls for them you could find this > > Â Â Â tested in court > > Â - "Any claims made to bolster the image of a business or > > Â Â Â its products or services must be accurate." > > Â - "The Act applies even when there was no intention to > > Â Â Â breach the Act".Â (Grant Harris again.) > > Â > > http://www.comcom.govt.nz/fair-trading/fair-trading-act-fact-sheets/claimin… > > Â > > The Fair Trading Act was passed as part of a program of market > > liberalisation and in order to foster competition and market > > efficiency, and the majority of the cases have been trader-to- > > trader.Â Why mention this?Â Because it's not just places where > > consumer protection is high-ranked that have such laws; it's > > also places that are gung-ho about free markets and competition > > and want to protect businesses. > > Â > > Law in the USA varies from state to state.Â For California, see > > https://www.truthinadvertising.org/california/ > > (which has a navbar on the right for other states). > > Â > > Me, I think Pharo is good enough to "sell" on its merits > > without any exaggerations.Â (If you could combine the great > > looks of Dolphin Smalltalk with the great features of Pharo, > > drool...) > > Â > > Â >

Nov. 20, 2017

Re: [Pharo-users] New Pharo article at The Cohort

by Offray Vladimir Luna CÃ¡rdenas

Richard, I don't mean to be harsh, but I'm amused that you think that everyone misunderstand you, and you have nothing to learn from the community that is using and developing the technologies you're promoting. As said in my previous email about this thread, what is the point of having a community that writes, reads and talks if we're unable to learn and change? Cheers, Offray On 20/11/17 11:17, horrido wrote: > Fortunately, I'm not selling a product, good or service. I'm selling an idea. > The idea that you should use Pharo for software development. This isn't > about commerce or trade, and thus there can be no basis for litigation. > > I'm rather amused that everyone has missed the fundamental point, which I > made long ago at the start of my campaign: > > *I'm adopting marketing techniques or practices to promote Smalltalk.* > > That's not to say that I'm marketing a good or service, so whatever laws > there are, they don't apply. I'm just borrowing a method to *raise public > awareness*. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Nov. 20, 2017