July 2021 - Pharo-users - lists.pharo.org

Re: Error in Pharo 9's Spec UI Framework Demo

by Esteban Lorenzano

Hi Tau, The filter that was bundled with the list components is deprecated and should not be used. Instead, we provide another component with that functionality: SpFilteringListPresenter. Take a loot there and its examples. Esteban On Jul 25 2021, at 5:52 am, tau <tau(a)cedalion.info> wrote: > > In the Spec2 examples included with Pharo9, in the example for SpListPresenter, when I try to input text in the list filter, I get an error: the debug window says: "Instance of OrderedCollection did not understand #hasElementAt:". The example works correctly in Pharo8. > > Is there a workaround to make the example work?

July 25, 2021

Error in Pharo 9's Spec UI Framework Demo

by tau

In the Spec2 examples included with Pharo9, in the example for SpListPresenter, when I try to input text in the list filter, I get an error: the debug window says: "Instance of OrderedCollection did not understand #hasElementAt:". The example works correctly in Pharo8. Is there a workaround to make the example work?

July 25, 2021

The Greatest Contributors to Smalltalk since 1980

by horrido.hobbies＠gmail.com

Iâm looking for a list of individuals who have contributed greatly to the advancement of Smalltalk, post Xerox PARC period (1972-1980). By advancement, I donât only mean on a technical basis but on an educational or public awareness basis (this could include books, podcasts, talk circuit, video instruction, etc.). Any basis that has made Smalltalk a success in the marketplace (including commercialization). I posted this question on LinkedIn and got one useful response: the late James Robertson. My personal nomination is Kent Beck. Iâm not that familiar with the deep history of Smalltalk, so Iâm looking for more nominations. Thanks.

July 24, 2021

Re: How do I remove old classes?

by Clacton Server

Good thinking. I will check that out. Thank you. David > On 23 Jul 2021, at 16:34, Richard Sargent <richard.sargent(a)gemtalksystems.com> wrote: > > > > On Fri, Jul 23, 2021, 06:57 Clacton Server <david(a)totallyobjects.com <mailto:david@totallyobjects.com>> wrote: > I have been having an enduring problem with Pharo "disappearing" on any machine I try it on. In an effort to resolve that it isn't my code, I want to remove the Package that contains all my Seaside code so that I can install a minimal home page under Seaside. This will, at least exonerate my code. However, I have removed the offending package, executed Smalltalk cleanUp: true but I can still get into the old code. A debugger comes up when I try the old code and it shows "AnObsoleteCNWMeetingsGalleries(AnObsoleteCNWBasic)" so the code is still there and all the bots that have the address will still be calling it. How do I finally remove the code? > > I would venture that you previously registered the class as a Seaside handler/application/whatever and the registry holds the class despite it being removed from the Smalltalk global dictionary. > > If so, you would need to remove it from the registry. > > > David Pennington

July 23, 2021

Re: How do I remove old classes?

by Richard Sargent

On Fri, Jul 23, 2021, 06:57 Clacton Server <david(a)totallyobjects.com> wrote: > I have been having an enduring problem with Pharo "disappearing" on any > machine I try it on. In an effort to resolve that it isn't my code, I want > to remove the Package that contains all my Seaside code so that I can > install a minimal home page under Seaside. This will, at least exonerate my > code. However, I have removed the offending package, executed Smalltalk > cleanUp: true but I can still get into the old code. A debugger comes up > when I try the old code and it shows > "AnObsoleteCNWMeetingsGalleries(AnObsoleteCNWBasic)" so the code is still > there and all the bots that have the address will still be calling it. How > do I finally remove the code? > I would venture that you previously registered the class as a Seaside handler/application/whatever and the registry holds the class despite it being removed from the Smalltalk global dictionary. If so, you would need to remove it from the registry. > David Pennington

July 23, 2021

Re: How do I remove old classes?

by Kasper Osterbye

Not knowing your specific usage, this tends to happen if you have an instance of class X, and then remove the class. To save the instance from going stale, Smalltalk has always made an Obsolete class. You can find the offending X instance by inspecting this: ReferenceFinder findAllPathsTo: X allInstances first This examines the first instance, you might want to print X allInstances size to see how big your issue is. Also, perhaps you need to force a garbage collect first: Smalltalk image garbageCollect Tracing the back-references can be a bit overwhelming the first times. For me the culprit has often been some global variable I thought I had under control. Best, Kasper > On 23 Jul 2021, at 15.56, Clacton Server <david(a)totallyobjects.com> wrote: > > I have been having an enduring problem with Pharo "disappearing" on any machine I try it on. In an effort to resolve that it isn't my code, I want to remove the Package that contains all my Seaside code so that I can install a minimal home page under Seaside. This will, at least exonerate my code. However, I have removed the offending package, executed Smalltalk cleanUp: true but I can still get into the old code. A debugger comes up when I try the old code and it shows "AnObsoleteCNWMeetingsGalleries(AnObsoleteCNWBasic)" so the code is still there and all the bots that have the address will still be calling it. How do I finally remove the code? > > David Pennington

July 23, 2021

How do I remove old classes?

by Clacton Server

I have been having an enduring problem with Pharo "disappearing" on any machine I try it on. In an effort to resolve that it isn't my code, I want to remove the Package that contains all my Seaside code so that I can install a minimal home page under Seaside. This will, at least exonerate my code. However, I have removed the offending package, executed Smalltalk cleanUp: true but I can still get into the old code. A debugger comes up when I try the old code and it shows "AnObsoleteCNWMeetingsGalleries(AnObsoleteCNWBasic)" so the code is still there and all the bots that have the address will still be calling it. How do I finally remove the code? David Pennington

July 23, 2021

[ANN] Buoy v6.1.0 [v6.1.0] released!

by Buenos Aires Smalltalk

July 23, 2021

Re: Pharo concurrency: select on socket or file IO

by vinref＠gmail.com

TaskIt is fantastic! I never realised this existed at all. This is exactly what I need. Thanks Pablo

July 22, 2021

Re: ZnServer on a cheap server: your experiences

by Esteban Maringolo

Yeap, not much more to add than what Sven said. What's important to mention is that they are really stable. I've been running Pharo servers in DO droplets of all sizes, without issues (some running for months), I only had to upscale one droplet to more memory, and it was because of a leak I introduced with PGSQL connections, otherwise, they're pretty lightweight for today's standards and a normal workload. I have deployments with nginx and Pharo images as upstreams, and I have one with Docker swarm and Traefik doing the load balancing among different Pharo workers and acting as the HTTPS endpoint. I'm removing this option though and moving back to nginx only. What I never tried was to host a docker container running Pharo, in some Docker hosting. It might be the best option as a quick start, but after doing the math, it's always more expensive than a Droplet. Best regards, Esteban A. Maringolo On Thu, Jul 22, 2021 at 3:21 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Vince, > > That is certainly possible and works well. I would recommend an instance with 1GB RAM, that leaves you some headroom. > > Deploying web applications is of course a broad subject, much of the required knowledge is not Pharo specific, but needed anyway. > > The last chapter in the Pharo Enterprise book (https://books.pharo.org/enterprise-pharo/) is a good starting point (Deployment). But there are other and different approaches. > > A plain HTTP demo instance running on a DO instance can be found here: http://zn.stfx.eu/welcome > > For production use you should front with NGINX or something similar to add HTTPS. > > May people on this mailing list deploy Pharo server applications, we have tens of them in day to day production doing real work. > > Good luck on your journey, you know where to ask questions. > > Regards, > > Sven > > > On 22 Jul 2021, at 07:56, vinref(a)gmail.com wrote: > > > > Anyone here run a web app using plain ZnServer (or subclasses) on a cheap VPS (i.e., $10/month DO droplet or equivalent). What are your experiences?, suggestions. > > > > I am planning a web app with just plain ZnServer, SQLite3, ATS or equivalent. > > > > Thanks, Vince > >

July 22, 2021

Re: Share package

by Renaud de Villemeur

Hi, You need to define a baseline, that will contain a definition of your dependencies, and everything needed to load and run your package with Metacello in Pharo. For a full documentation, look here:Â https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… All package inside pharo are using a baseline, but some can be more intimidating than others to study. If you are looking for a simple, basic working example, you can have a look toÂ https://github.com/rvillemeur/SmallGameOfLife Renaud Jul 21, 2021, 11:10 by mspgate(a)gmail.com: > > Hello everybody, > > > sorry for the newbie question. I would like to know what is the fastest, lightweight way to share a package with other Pharo users. the package can be downloaded from my GitHub. > > > thanks. > > > d > >

July 22, 2021

Re: Pharo concurrency: select on socket or file IO

by tesonep＠gmail.com

Hi, Socket implementation in the VM already handles Async IO operations. The execution model in Pharo is intended to have many concurrent green threads (they are not OS threads, they are handled by Pharo VM). These green threads are called processes in Pharo. Pharo Green threads are quite cheap to create and use, and the context switch of them is quite cheap also. The programming model of Pharo is intended to have many concurrent green threads, without caring if they block in tIO operations. These block green threads are handled by the VM and the VM continue executing useful code. For orchestrating and communication between the green threads you can use low-level synchronization as semaphores and mutex, but also there is a rich library (Taskit) for using Asynchronous tasks, Callables and Futures. Cheers, Pablo On Thu, Jul 22, 2021 at 8:57 AM <vinref(a)gmail.com> wrote: > Can the Pharo VM or a library do a âselectâ on a collection of processes > waiting on a socket or file IO? Something like > https://man7.org/linux/man-pages/man2/select.2.html, or > https://docs.microsoft.com/en-us/windows/win32/api/winsock2/nf-winsock2-sel… > . > > Say I have a bunch of forked processes and some will get blocked waiting > for IO. I would put the blocked connections/processes in a collection and > non-blocked processes can continue to do useful work. At some appropriate I > would do a select on the blocked processes and resume those that are done. > > Vince > -- Pablo Tesone. tesonep(a)gmail.com

July 22, 2021

Re: Pharo concurrency: select on socket or file IO

by giorgio ferraris

Hi, Vince, I don't know exactly Pharo, but when you fork a process, it becomes an independent thread of work. So in that process you can send your async call and wait for a response and then do the work. All inside the forked process. It's the smallalk's scheduler that will take care of passing control to other available (green) threads So it's not clear from me what you need. If you have many forked processes, each one will do is work up to the end. No need to resume it from outside. hth ciao giorgio On Thu, Jul 22, 2021 at 8:57 AM <vinref(a)gmail.com> wrote: > Can the Pharo VM or a library do a âselectâ on a collection of processes > waiting on a socket or file IO? Something like > https://man7.org/linux/man-pages/man2/select.2.html, or > https://docs.microsoft.com/en-us/windows/win32/api/winsock2/nf-winsock2-sel… > . > > Say I have a bunch of forked processes and some will get blocked waiting > for IO. I would put the blocked connections/processes in a collection and > non-blocked processes can continue to do useful work. At some appropriate I > would do a select on the blocked processes and resume those that are done. > > Vince >

July 22, 2021

Pharo concurrency: select on socket or file IO

by vinref＠gmail.com

Can the Pharo VM or a library do a âselectâ on a collection of processes waiting on a socket or file IO? Something like https://man7.org/linux/man-pages/man2/select.2.html, or https://docs.microsoft.com/en-us/windows/win32/api/winsock2/nf-winsock2-sel…. Say I have a bunch of forked processes and some will get blocked waiting for IO. I would put the blocked connections/processes in a collection and non-blocked processes can continue to do useful work. At some appropriate I would do a select on the blocked processes and resume those that are done. Vince

July 22, 2021

Re: ZnServer on a cheap server: your experiences

by Sven Van Caekenberghe

Hi Vince, That is certainly possible and works well. I would recommend an instance with 1GB RAM, that leaves you some headroom. Deploying web applications is of course a broad subject, much of the required knowledge is not Pharo specific, but needed anyway. The last chapter in the Pharo Enterprise book (https://books.pharo.org/enterprise-pharo/) is a good starting point (Deployment). But there are other and different approaches. A plain HTTP demo instance running on a DO instance can be found here: http://zn.stfx.eu/welcome For production use you should front with NGINX or something similar to add HTTPS. May people on this mailing list deploy Pharo server applications, we have tens of them in day to day production doing real work. Good luck on your journey, you know where to ask questions. Regards, Sven > On 22 Jul 2021, at 07:56, vinref(a)gmail.com wrote: > > Anyone here run a web app using plain ZnServer (or subclasses) on a cheap VPS (i.e., $10/month DO droplet or equivalent). What are your experiences?, suggestions. > > I am planning a web app with just plain ZnServer, SQLite3, ATS or equivalent. > > Thanks, Vince >

July 22, 2021

ZnServer on a cheap server: your experiences

by vinref＠gmail.com

Anyone here run a web app using plain ZnServer (or subclasses) on a cheap VPS (i.e., $10/month DO droplet or equivalent). What are your experiences?, suggestions. I am planning a web app with just plain ZnServer, SQLite3, ATS or equivalent. Thanks, Vince

July 22, 2021

[ANN] smalltalkCI now supports Pharo 10

by Esteban Lorenzano

... this is more for Pharo developpers than Pharo users, but informing also users just in case :) https://github.com/hpi-swa/smalltalkCI/pull/538 Esteban

July 21, 2021

Share package

by mspgate＠gmail.com

Hello everybody, sorry for the newbie question. I would like to know what is the fastest, lightweight way to share a package with other Pharo users. the package can be downloaded from my GitHub. thanks. d

July 21, 2021

Re: How to handle (recover) from a ZnInvalidUTF8: Illegal continuation byte for utf-8 encoding error?

by Sven Van Caekenberghe

There is ZnCharacterEncoder knownEncodingIdentifiers. You either provide an identifier from this list (as string or symbol) or an instance (the argument gets sent #asZnCharacterEncoder if you want to know). Most text editors will tell you the encoding they are using to read your file and you can use that to inspect the contents. If you want, you can sent me such a file privately. Yes, you can access the encoder from the character read stream to configure it further. Or you do it upfront as an instance instead of an identifier. > On 20 Jul 2021, at 15:47, Tim Mackinnon <tim(a)testit.works> wrote: > > Hey thanks guys - so looking at readStreamEncoded: - how do I know what the valid encodings are? Skimming those docâs Sven referenced, I can start to pick out some - but is there a list? I see that method parameter says âanEncodingâ but the type hint on that is misleading as it seems like its a String or is it a Symbol? If I search for Encoder classes - I do find ZnCharacterEncoder - and it has class methods for latin1, utf8, ascii - so is this the definitive list? And should the encoding strings used in those methods be constants or something I can reference in my code? > > Gosh - this raises a whole host of things I just naively assumed happened for me. > > So it looks like the file giving me issues - seems to have characters like Â£ or Â¬ in it. So Iâm wondering how I know what the proper encoding format would be (I think these files were written out with some PHP app) - is it just a trial and error thing? > > I tried changing my code to: > > details parseStream: (firmEfs readStreamEncoded: 'iso-8859-1â). - and other variants like âASCIIâ and âlatin1â - and this then gives me another error: > "ZnCharacterEncodingError: Character Unicode code point outside encoder rangeâ > > So it does sound like I have a file that isnât conforming to known standards - and I guess I have to use #beLenient option. > > Sven - In the examples for using #beLenient - you seem to show something that assumes you will iterate with Do - as my existing code takes a stream, that it wants to do a #nextLine on - would it be bad to do something like this: > > efsStream := (firmEfs readStreamEncoded: 'latin1'). > efsStream encoder beLenient. > > details parsStream: efsStream. > > That is - get the endcoder from my Stream and make it lenient? > > Appreciate the pointers on this guys - Iâm definitely learning something new here. > > Tim > >> On 20 Jul 2021, at 12:11, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >> >> >>> El 20 jul 2021, a las 11:45, Sven Van Caekenberghe <sven(a)stfx.eu> escribiÃ³: >>> >>> >>> >>>> On 20 Jul 2021, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> Hi Tim, >>>> >>>> An introduction to this part of the system is in https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… [Character Encoding and Resource Meta Description] from the "Enterprise Pharo" book. >>>> >>>> The error means that a file that you try to read as UTF-8 does contain things that are invalid with respect to the UTF-8 standard. >>>> >>>> Are you sure the file is in UTF-8, maybe it is in ASCII, Latin-1 or something else ? >>>> >>>> It is possible to customise the encoding to something different than the default UTF-8. For non-UTF encoders, there is a strict/lenient option to disallow/allow illegal stuff (but then you will get these in your strings). >>>> >>>> I can show you how to do that if you want. >>> >>> '/var/log/system.log' asFileReference readStreamDo: [ :in | in upToEnd ]. >>> >>> '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | >>> (ZnCharacterReadStream on: in encoding: #ascii) upToEnd ]. >>> >>> '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | >>> (ZnCharacterReadStream on: in encoding: ZnCharacterEncoder ascii beLenient) upToEnd ]. >> >> There is also readStreamEncoded:[do:], which is a bit more concise but does the same :) >> >>> >>> HTH >>> >>>> Sven >>>> >>>>> On 20 Jul 2021, at 10:31, Tim Mackinnon <tim(a)testit.works> wrote: >>>>> >>>>> Hi - Iâm doing a bit of log file processing with Pharo - and Iâve hit an unexpected error and am wondering what the best way to approach it is. >>>>> >>>>> It seems that I have a log file that has unexpected characters, and so my readStream loop that reads lines gets an error: "ZnInvalidUTF8: Illegal continuation byte for utf-8 encodingâ. >>>>> >>>>> For some reason this file (unlike my others) seems to contain characters that it shouldnât - but what is the best way for me to continue processing? Should I be opening my files in a different way - or can I resume the error somehow- Iâm not familiar with this area of Pharo and am after a bit of advice. >>>>> >>>>> My code is like this (and I get the error when doing nextLine) >>>>> >>>>> >>>>> parseStream: aFileStream with: aBlock >>>>> | line items | >>>>> [ (line := aFileStream nextLine) isNil ] >>>>> whileFalse: [ >>>>> items := $/ split: line. >>>>> items size = 3 ifTrue: [aBlock value: items]] >>>>> >>>>> My stream is created like this: >>>>> >>>>> firmEfs := (pathName , '/' , firmName , '_files') asFileReference. >>>>> details parseStream: firmEfs readStream. >>>>> >>>>> >>>>> Should I be opening the stream a bit differently - or can I catch that encoding error and resume it with some safe character? >>>>> >>>>> Thanks for any help. >>>>> >>>>> Tim >

July 20, 2021

Re: How to handle (recover) from a ZnInvalidUTF8: Illegal continuation byte for utf-8 encoding error?

by Tim Mackinnon

Hey thanks guys - so looking at readStreamEncoded: - how do I know what the valid encodings are? Skimming those docâs Sven referenced, I can start to pick out some - but is there a list? I see that method parameter says âanEncodingâ but the type hint on that is misleading as it seems like its a String or is it a Symbol? If I search for Encoder classes - I do find ZnCharacterEncoder - and it has class methods for latin1, utf8, ascii - so is this the definitive list? And should the encoding strings used in those methods be constants or something I can reference in my code? Gosh - this raises a whole host of things I just naively assumed happened for me. So it looks like the file giving me issues - seems to have characters like Â£ or Â¬ in it. So Iâm wondering how I know what the proper encoding format would be (I think these files were written out with some PHP app) - is it just a trial and error thing? I tried changing my code to: details parseStream: (firmEfs readStreamEncoded: 'iso-8859-1â). - and other variants like âASCIIâ and âlatin1â - and this then gives me another error: "ZnCharacterEncodingError: Character Unicode code point outside encoder rangeâ So it does sound like I have a file that isnât conforming to known standards - and I guess I have to use #beLenient option. Sven - In the examples for using #beLenient - you seem to show something that assumes you will iterate with Do - as my existing code takes a stream, that it wants to do a #nextLine on - would it be bad to do something like this: efsStream := (firmEfs readStreamEncoded: 'latin1'). efsStream encoder beLenient. details parsStream: efsStream. That is - get the endcoder from my Stream and make it lenient? Appreciate the pointers on this guys - Iâm definitely learning something new here. Tim > On 20 Jul 2021, at 12:11, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: > > > >> El 20 jul 2021, a las 11:45, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> escribiÃ³: >> >> >> >>> On 20 Jul 2021, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: >>> >>> Hi Tim, >>> >>> An introduction to this part of the system is in https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… <https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf…> [Character Encoding and Resource Meta Description] from the "Enterprise Pharo" book. >>> >>> The error means that a file that you try to read as UTF-8 does contain things that are invalid with respect to the UTF-8 standard. >>> >>> Are you sure the file is in UTF-8, maybe it is in ASCII, Latin-1 or something else ? >>> >>> It is possible to customise the encoding to something different than the default UTF-8. For non-UTF encoders, there is a strict/lenient option to disallow/allow illegal stuff (but then you will get these in your strings). >>> >>> I can show you how to do that if you want. >> >> '/var/log/system.log' asFileReference readStreamDo: [ :in | in upToEnd ]. >> >> '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | >> (ZnCharacterReadStream on: in encoding: #ascii) upToEnd ]. >> >> '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | >> (ZnCharacterReadStream on: in encoding: ZnCharacterEncoder ascii beLenient) upToEnd ]. > > There is also readStreamEncoded:[do:], which is a bit more concise but does the same :) > >> >> HTH >> >>> Sven >>> >>>> On 20 Jul 2021, at 10:31, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >>>> >>>> Hi - Iâm doing a bit of log file processing with Pharo - and Iâve hit an unexpected error and am wondering what the best way to approach it is. >>>> >>>> It seems that I have a log file that has unexpected characters, and so my readStream loop that reads lines gets an error: "ZnInvalidUTF8: Illegal continuation byte for utf-8 encodingâ. >>>> >>>> For some reason this file (unlike my others) seems to contain characters that it shouldnât - but what is the best way for me to continue processing? Should I be opening my files in a different way - or can I resume the error somehow- Iâm not familiar with this area of Pharo and am after a bit of advice. >>>> >>>> My code is like this (and I get the error when doing nextLine) >>>> >>>> >>>> parseStream: aFileStream with: aBlock >>>> | line items | >>>> [ (line := aFileStream nextLine) isNil ] >>>> whileFalse: [ >>>> items := $/ split: line. >>>> items size = 3 ifTrue: [aBlock value: items]] >>>> >>>> My stream is created like this: >>>> >>>> firmEfs := (pathName , '/' , firmName , '_files') asFileReference. >>>> details parseStream: firmEfs readStream. >>>> >>>> >>>> Should I be opening the stream a bit differently - or can I catch that encoding error and resume it with some safe character? >>>> >>>> Thanks for any help. >>>> >>>> Tim

July 20, 2021

Re: How to handle (recover) from a ZnInvalidUTF8: Illegal continuation byte for utf-8 encoding error?

by Sven Van Caekenberghe

> On 20 Jul 2021, at 12:11, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > >> El 20 jul 2021, a las 11:45, Sven Van Caekenberghe <sven(a)stfx.eu> escribiÃ³: >> >> >> >>> On 20 Jul 2021, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> Hi Tim, >>> >>> An introduction to this part of the system is in https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… [Character Encoding and Resource Meta Description] from the "Enterprise Pharo" book. >>> >>> The error means that a file that you try to read as UTF-8 does contain things that are invalid with respect to the UTF-8 standard. >>> >>> Are you sure the file is in UTF-8, maybe it is in ASCII, Latin-1 or something else ? >>> >>> It is possible to customise the encoding to something different than the default UTF-8. For non-UTF encoders, there is a strict/lenient option to disallow/allow illegal stuff (but then you will get these in your strings). >>> >>> I can show you how to do that if you want. >> >> '/var/log/system.log' asFileReference readStreamDo: [ :in | in upToEnd ]. >> >> '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | >> (ZnCharacterReadStream on: in encoding: #ascii) upToEnd ]. >> >> '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | >> (ZnCharacterReadStream on: in encoding: ZnCharacterEncoder ascii beLenient) upToEnd ]. > > There is also readStreamEncoded:[do:], which is a bit more concise but does the same :) Yes indeed ! >> HTH >> >>> Sven >>> >>>> On 20 Jul 2021, at 10:31, Tim Mackinnon <tim(a)testit.works> wrote: >>>> >>>> Hi - Iâm doing a bit of log file processing with Pharo - and Iâve hit an unexpected error and am wondering what the best way to approach it is. >>>> >>>> It seems that I have a log file that has unexpected characters, and so my readStream loop that reads lines gets an error: "ZnInvalidUTF8: Illegal continuation byte for utf-8 encodingâ. >>>> >>>> For some reason this file (unlike my others) seems to contain characters that it shouldnât - but what is the best way for me to continue processing? Should I be opening my files in a different way - or can I resume the error somehow- Iâm not familiar with this area of Pharo and am after a bit of advice. >>>> >>>> My code is like this (and I get the error when doing nextLine) >>>> >>>> >>>> parseStream: aFileStream with: aBlock >>>> | line items | >>>> [ (line := aFileStream nextLine) isNil ] >>>> whileFalse: [ >>>> items := $/ split: line. >>>> items size = 3 ifTrue: [aBlock value: items]] >>>> >>>> My stream is created like this: >>>> >>>> firmEfs := (pathName , '/' , firmName , '_files') asFileReference. >>>> details parseStream: firmEfs readStream. >>>> >>>> >>>> Should I be opening the stream a bit differently - or can I catch that encoding error and resume it with some safe character? >>>> >>>> Thanks for any help. >>>> >>>> Tim

July 20, 2021

Re: How to handle (recover) from a ZnInvalidUTF8: Illegal continuation byte for utf-8 encoding error?

by Guillermo Polito

> El 20 jul 2021, a las 11:45, Sven Van Caekenberghe <sven(a)stfx.eu> escribiÃ³: > > > >> On 20 Jul 2021, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi Tim, >> >> An introduction to this part of the system is in https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… [Character Encoding and Resource Meta Description] from the "Enterprise Pharo" book. >> >> The error means that a file that you try to read as UTF-8 does contain things that are invalid with respect to the UTF-8 standard. >> >> Are you sure the file is in UTF-8, maybe it is in ASCII, Latin-1 or something else ? >> >> It is possible to customise the encoding to something different than the default UTF-8. For non-UTF encoders, there is a strict/lenient option to disallow/allow illegal stuff (but then you will get these in your strings). >> >> I can show you how to do that if you want. > > '/var/log/system.log' asFileReference readStreamDo: [ :in | in upToEnd ]. > > '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | > (ZnCharacterReadStream on: in encoding: #ascii) upToEnd ]. > > '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | > (ZnCharacterReadStream on: in encoding: ZnCharacterEncoder ascii beLenient) upToEnd ]. There is also readStreamEncoded:[do:], which is a bit more concise but does the same :) > > HTH > >> Sven >> >>> On 20 Jul 2021, at 10:31, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>> Hi - Iâm doing a bit of log file processing with Pharo - and Iâve hit an unexpected error and am wondering what the best way to approach it is. >>> >>> It seems that I have a log file that has unexpected characters, and so my readStream loop that reads lines gets an error: "ZnInvalidUTF8: Illegal continuation byte for utf-8 encodingâ. >>> >>> For some reason this file (unlike my others) seems to contain characters that it shouldnât - but what is the best way for me to continue processing? Should I be opening my files in a different way - or can I resume the error somehow- Iâm not familiar with this area of Pharo and am after a bit of advice. >>> >>> My code is like this (and I get the error when doing nextLine) >>> >>> >>> parseStream: aFileStream with: aBlock >>> | line items | >>> [ (line := aFileStream nextLine) isNil ] >>> whileFalse: [ >>> items := $/ split: line. >>> items size = 3 ifTrue: [aBlock value: items]] >>> >>> My stream is created like this: >>> >>> firmEfs := (pathName , '/' , firmName , '_files') asFileReference. >>> details parseStream: firmEfs readStream. >>> >>> >>> Should I be opening the stream a bit differently - or can I catch that encoding error and resume it with some safe character? >>> >>> Thanks for any help. >>> >>> Tim

July 20, 2021

Re: How to handle (recover) from a ZnInvalidUTF8: Illegal continuation byte for utf-8 encoding error?

by Sven Van Caekenberghe

> On 20 Jul 2021, at 11:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Tim, > > An introduction to this part of the system is in https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… [Character Encoding and Resource Meta Description] from the "Enterprise Pharo" book. > > The error means that a file that you try to read as UTF-8 does contain things that are invalid with respect to the UTF-8 standard. > > Are you sure the file is in UTF-8, maybe it is in ASCII, Latin-1 or something else ? > > It is possible to customise the encoding to something different than the default UTF-8. For non-UTF encoders, there is a strict/lenient option to disallow/allow illegal stuff (but then you will get these in your strings). > > I can show you how to do that if you want. '/var/log/system.log' asFileReference readStreamDo: [ :in | in upToEnd ]. '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | (ZnCharacterReadStream on: in encoding: #ascii) upToEnd ]. '/var/log/system.log' asFileReference binaryReadStreamDo: [ :in | (ZnCharacterReadStream on: in encoding: ZnCharacterEncoder ascii beLenient) upToEnd ]. HTH > Sven > >> On 20 Jul 2021, at 10:31, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi - Iâm doing a bit of log file processing with Pharo - and Iâve hit an unexpected error and am wondering what the best way to approach it is. >> >> It seems that I have a log file that has unexpected characters, and so my readStream loop that reads lines gets an error: "ZnInvalidUTF8: Illegal continuation byte for utf-8 encodingâ. >> >> For some reason this file (unlike my others) seems to contain characters that it shouldnât - but what is the best way for me to continue processing? Should I be opening my files in a different way - or can I resume the error somehow- Iâm not familiar with this area of Pharo and am after a bit of advice. >> >> My code is like this (and I get the error when doing nextLine) >> >> >> parseStream: aFileStream with: aBlock >> | line items | >> [ (line := aFileStream nextLine) isNil ] >> whileFalse: [ >> items := $/ split: line. >> items size = 3 ifTrue: [aBlock value: items]] >> >> My stream is created like this: >> >> firmEfs := (pathName , '/' , firmName , '_files') asFileReference. >> details parseStream: firmEfs readStream. >> >> >> Should I be opening the stream a bit differently - or can I catch that encoding error and resume it with some safe character? >> >> Thanks for any help. >> >> Tim >

July 20, 2021

Re: How to handle (recover) from a ZnInvalidUTF8: Illegal continuation byte for utf-8 encoding error?

by Sven Van Caekenberghe

Hi Tim, An introduction to this part of the system is in https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… [Character Encoding and Resource Meta Description] from the "Enterprise Pharo" book. The error means that a file that you try to read as UTF-8 does contain things that are invalid with respect to the UTF-8 standard. Are you sure the file is in UTF-8, maybe it is in ASCII, Latin-1 or something else ? It is possible to customise the encoding to something different than the default UTF-8. For non-UTF encoders, there is a strict/lenient option to disallow/allow illegal stuff (but then you will get these in your strings). I can show you how to do that if you want. Sven > On 20 Jul 2021, at 10:31, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - Iâm doing a bit of log file processing with Pharo - and Iâve hit an unexpected error and am wondering what the best way to approach it is. > > It seems that I have a log file that has unexpected characters, and so my readStream loop that reads lines gets an error: "ZnInvalidUTF8: Illegal continuation byte for utf-8 encodingâ. > > For some reason this file (unlike my others) seems to contain characters that it shouldnât - but what is the best way for me to continue processing? Should I be opening my files in a different way - or can I resume the error somehow- Iâm not familiar with this area of Pharo and am after a bit of advice. > > My code is like this (and I get the error when doing nextLine) > > > parseStream: aFileStream with: aBlock > | line items | > [ (line := aFileStream nextLine) isNil ] > whileFalse: [ > items := $/ split: line. > items size = 3 ifTrue: [aBlock value: items]] > > My stream is created like this: > > firmEfs := (pathName , '/' , firmName , '_files') asFileReference. > details parseStream: firmEfs readStream. > > > Should I be opening the stream a bit differently - or can I catch that encoding error and resume it with some safe character? > > Thanks for any help. > > Tim

July 20, 2021

How to handle (recover) from a ZnInvalidUTF8: Illegal continuation byte for utf-8 encoding error?

by Tim Mackinnon

Hi - Iâm doing a bit of log file processing with Pharo - and Iâve hit an unexpected error and am wondering what the best way to approach it is. It seems that I have a log file that has unexpected characters, and so my readStream loop that reads lines gets an error: "ZnInvalidUTF8: Illegal continuation byte for utf-8 encodingâ. For some reason this file (unlike my others) seems to contain characters that it shouldnât - but what is the best way for me to continue processing? Should I be opening my files in a different way - or can I resume the error somehow- Iâm not familiar with this area of Pharo and am after a bit of advice. My code is like this (and I get the error when doing nextLine) parseStream: aFileStream with: aBlock | line items | [ (line := aFileStream nextLine) isNil ] whileFalse: [ items := $/ split: line. items size = 3 ifTrue: [aBlock value: items]] My stream is created like this: firmEfs := (pathName , '/' , firmName , '_files') asFileReference. details parseStream: firmEfs readStream. Should I be opening the stream a bit differently - or can I catch that encoding error and resume it with some safe character? Thanks for any help. Tim

July 20, 2021

Re: Pharo 9.0 vm same-as Pharo 8.0 ?

by tesonep＠gmail.com

Thanks for the report, I will update the page. On Mon, Jul 19, 2021 at 6:34 PM Isaac Gouy via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > On Monday, July 19, 2021, 12:55:08 AM PDT, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > > > > that link is now obsolete in favour of pharo-vm-Linux-[ARCH]-stable.zip. > > > > > That "obsolete" link is still given in the section > > "Pharo standalone" > > on the page > > "https://pharo.org/download" > -- Pablo Tesone. tesonep(a)gmail.com

July 20, 2021

Re: Pharo 9.0 vm same-as Pharo 8.0 ?

by Isaac Gouy

On Monday, July 19, 2021, 12:55:08 AM PDT, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > that link is now obsolete in favour of pharo-vm-Linux-[ARCH]-stable.zip. That "obsolete" link is still given in the section Â Â Â "Pharo standalone" on the page Â Â Â "https://pharo.org/download"

July 19, 2021

Re: How to use Spec 2.0 with GTK in Pharo 9.

by Esteban Lorenzano

Hi Tau, the gtk backend does not comes loaded by default, you need to load it: Metacello new repository: 'github://pharo-spec/Spec-Gtk'; baseline: 'SpecGtk'; onConflict: [ :e | e useIncoming ]; onUpgrade: [ :e | e useIncoming ]; load. and of course, remember you need gtk3 in your system :) check here: https://github.com/pharo-spec/Spec-Gtk cheers! Esteban On Jul 19 2021, at 12:15 am, jbn126859530.7 <tau(a)cedalion.info> wrote: > > Hi. > > I'm learning Spec 2.0 with the help of the book "Building user interface with Spec 2.0". In section 2.17 of the book, the authors make a subclass of SpGtkConfiguration. However, no such class exists, only a SpMorphicConfiguration. Moreover, if I do something like: "app useBackend: #Gtk", I get a NotFound error. Again, "app useBackend: #Morphic" work as intended. As Pharo 9 annonced the availability of a GTK backend, I would like to know how to access it. > > Thanks. > > tau.

July 19, 2021

Re: Pharo 9 released - a brief experience report

by Guillermo Polito

Hi Yanni, Now vms are organised by architecture. The link to get the lastest vm for Darwin x86_64 is now https://files.pharo.org/get-files/90/pharo-vm-Darwin-x86_64-latest.zip Otherwise, we recommend using zeroconf or the pharo launcher, as they detect your machineâs architecture and download the right thing for you regardless of the link. Cheers, G > El 16 jul 2021, a las 18:17, Yanni Chiu <yannix7db(a)gmail.com> escribiÃ³: > > Thanks for updating the release. > > Iâve downloaded again using âcurl -L https://get.pharo.org/64/ | > bashâ, and Pharo 9.0.0 came up without problem. > > BTW, I noticed that the vm it downloaded today, was: > http://files.pharo.org/get-files/90/pharo-vm-Darwin-x86_64-stable.zip > > Yesterday, when I poked around some more, I decided to download: > https://files.pharo.org/get-files/90/pharo64-mac-headless-latest.zip > which looked to be newest available. > It mostly worked, but I got some debuggers when trying the Spec and > Spec2 examples (and even saw the dreaded pane with the X, which Iâve > not seen in years). With todayâs clean update, I only got one debugger > for the Spec âButtonsâ example. (Stack trace below). > ==== > KeyboardKey(Object)>>doesNotUnderstand: #asLowercase > ButtonPresenter>>addShortcutTipFor:on: > ButtonPresenter>>addShortcutTipFor: > ButtonPresenter>>label > MorphicButtonAdapter>>label > PluggableButtonMorph>>update: > PluggableButtonMorph>>on:getState:action:label:icon:menu: > PluggableButtonMorph class>>on:getState:action:label:menu: > MorphicButtonAdapter>>buildWidget > MorphicButtonAdapter(AbstractAdapter)>>adapt: > SpecInterpreter>>actionToPerformWithSelector:arguments: > SpecInterpreter>>performNextSelectorAndIncrementIndex > SpecInterpreter>>interpretASpec:selector: > SpecInterpreter>>interpretASpec:model:selector: > SpecInterpreter class>>private_interpretASpec:model:selector: > SpecInterpreter class>>private_buildWidgetFor:withSpec: > ButtonPresenter(ComposablePresenter)>>privateAdapterFromModel:withSpec: > ButtonPresenter(ComposablePresenter)>>private_buildWithSpec: > ButtonPresenter(ComposablePresenter)>>private_buildWithSpec > SpecInterpreter>>returnInterpretationOf: > SpecInterpreter>>interpretASpec:selector: > SpecInterpreter>>interpretASpec:model:selector: > SpecInterpreter class>>private_interpretASpec:model:selector: > SpecInterpreter>>computeSpecFrom:selector: > SpecInterpreter>>retrieveSpecFrom:selector: > SpecInterpreter>>interpretASpec:selector: > SpecInterpreter>>interpretASpec:model:selector: > SpecInterpreter class>>private_interpretASpec:model:selector: > [ :each | self class private_interpretASpec: each model: model > selector: spec selector ] in > SpecInterpreter>>performNextSelectorAndIncrementIndex in Block: [ > :each | self class private_interpretASpec: each ...etc... > Array(SequenceableCollection)>>collect:

July 19, 2021

Re: Pharo 9.0 vm same-as Pharo 8.0 ?

by Guillermo Polito

Hi Igouy, Kind of, yes. In Pharo9 we now support many different architectures, meaning that vms are not only compiled for 32/64 bits, but for aarch64 or x86-64. This means that link is now obsolete in favour of pharo-vm-Linux-[ARCH]-stable.zip. For example - pharo-vm-Linux-x86_64-stable.zip - pharo-vm-Linux-aarch64-stable.zip Regardless of that, one important point is that all files inside get-files are intended to be private to zeroconf and subject to change. The public download links are (as always) inside: https://files.pharo.org/vm/pharo-spur64/ Where for Pharo9 they are now organised by architecture too. Old versions (pre pharo9) are still there in the old places. G > El 16 jul 2021, a las 20:17, igouy2--- via Pharo-users <pharo-users(a)lists.pharo.org> escribiÃ³: > > Seems like the files from â > > https://files.pharo.org/get-files/90/pharo64-linux-stable.zip > > â are the same as Pharo 8.0 â > > 5.0-202002121043 Wed Feb 12 11:06:45 UTC 2020 gcc 5.4.0 [Production Spur 64-bit VM] > > > > Is that as-intended? >

July 19, 2021

How to use Spec 2.0 with GTK in Pharo 9.

by jbn126859530.7

Hi. I'm learning Spec 2.0 with the help of the book "Building user interface with Spec 2.0". In section 2.17 of the book, the authors make a subclass of SpGtkConfiguration. However, no such class exists, only a SpMorphicConfiguration. Moreover, if I do something like: "app useBackend: #Gtk", I get a NotFound error. Again, "app useBackend: #Morphic" work as intended. As Pharo 9 annonced the availability of a GTK backend, I would like to know how to access it. Thanks. tau.

July 18, 2021

leave

by cedalion

July 18, 2021

Pharo 9.0 vm same-as Pharo 8.0 ?

by igouy2＠yahoo.com

Seems like the files from â https://files.pharo.org/get-files/90/pharo64-linux-stable.zip â are the same as Pharo 8.0 â 5\.0-202002121043 Wed Feb 12 11:06:45 UTC 2020 gcc 5.4.0 \[Production Spur 64-bit VM\] Is that as-intended?

July 16, 2021

Re: Pharo 9 released - a brief experience report

by Yanni Chiu

Thanks for updating the release. Iâve downloaded again using âcurl -L https://get.pharo.org/64/ | bashâ, and Pharo 9.0.0 came up without problem. BTW, I noticed that the vm it downloaded today, was: http://files.pharo.org/get-files/90/pharo-vm-Darwin-x86_64-stable.zip Yesterday, when I poked around some more, I decided to download: https://files.pharo.org/get-files/90/pharo64-mac-headless-latest.zip which looked to be newest available. It mostly worked, but I got some debuggers when trying the Spec and Spec2 examples (and even saw the dreaded pane with the X, which Iâve not seen in years). With todayâs clean update, I only got one debugger for the Spec âButtonsâ example. (Stack trace below). ==== KeyboardKey(Object)>>doesNotUnderstand: #asLowercase ButtonPresenter>>addShortcutTipFor:on: ButtonPresenter>>addShortcutTipFor: ButtonPresenter>>label MorphicButtonAdapter>>label PluggableButtonMorph>>update: PluggableButtonMorph>>on:getState:action:label:icon:menu: PluggableButtonMorph class>>on:getState:action:label:menu: MorphicButtonAdapter>>buildWidget MorphicButtonAdapter(AbstractAdapter)>>adapt: SpecInterpreter>>actionToPerformWithSelector:arguments: SpecInterpreter>>performNextSelectorAndIncrementIndex SpecInterpreter>>interpretASpec:selector: SpecInterpreter>>interpretASpec:model:selector: SpecInterpreter class>>private_interpretASpec:model:selector: SpecInterpreter class>>private_buildWidgetFor:withSpec: ButtonPresenter(ComposablePresenter)>>privateAdapterFromModel:withSpec: ButtonPresenter(ComposablePresenter)>>private_buildWithSpec: ButtonPresenter(ComposablePresenter)>>private_buildWithSpec SpecInterpreter>>returnInterpretationOf: SpecInterpreter>>interpretASpec:selector: SpecInterpreter>>interpretASpec:model:selector: SpecInterpreter class>>private_interpretASpec:model:selector: SpecInterpreter>>computeSpecFrom:selector: SpecInterpreter>>retrieveSpecFrom:selector: SpecInterpreter>>interpretASpec:selector: SpecInterpreter>>interpretASpec:model:selector: SpecInterpreter class>>private_interpretASpec:model:selector: [ :each | self class private_interpretASpec: each model: model selector: spec selector ] in SpecInterpreter>>performNextSelectorAndIncrementIndex in Block: [ :each | self class private_interpretASpec: each ...etc... Array(SequenceableCollection)>>collect:

July 16, 2021

Re: [Pharo-dev] [ANN] Pharo 9 released!

by Esteban Maringolo

Thanks team. Impressive release. Keep up the good work! Esteban A. Maringolo On Thu, Jul 15, 2021 at 6:14 AM Esteban Lorenzano <estebanlm(a)netc.eu> wrote: > Dear World and dynamic language lovers: > > The time has come for Pharo 9 <https://pharo.org/> ! > > Pharo is a pure object-oriented programming language and a powerful > environment, focused on simplicity and immediate feedback. > > > Here are the key features of Pharo 9: > > > - Full redesign of the Spec UI framework (new logic, application, > style, GTK3 back-end) > - New tools: > - > - new playground, > - new object centric inspector, > - new object centric debugger. > - better and new Refactorings > - class comments are now written in Microdown format (Markdown > compatible) > - classes now can be defined using a "fluid" api (Preview) > - New completion framework that adapts better to edition contexts > and is customizable > - Fast universal non-blocking FFI which now uses libFFI as backend. > - Pharo now supports Windows, OSX, Linux (Ubuntu, Debian, Fedora, > openSUSE, Arch, Raspbian) and multiple architectures (Intel/ARM 32/64bits). > - Virtual Machine > - > - Idle VM > - Support for ARM 64bits > - Support for Apple M1 > - More than 3000 tests > - Built for Ubuntu 18.04, 19.04, 20.04, 21.04, 21.10; Debian 9, 10, > Testing; Fedora 32, 32, 34; openSUSE 15.1, 15.2, Tumbleweed; Manjaro; Arch > - Uses SDL 2.0 as back-end by default. It supports extended event > handling, including trackpad support. > - General speed up due to compiler optimisations and UI simplification. > - And many, many more tests. > > > These are just the more prominent highlights, but the details are just as > important. We have closed a massive amount of issues: around 1400 issues > and 2150 pull requests. > > A more extended changelog can be found at > https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo90Change… > . > > While the technical improvements are significant, still the most > impressive fact is that the new code that got in the main Pharo 9 image was > contributed by more than 90 people. > > Pharo is more than code. It is an exciting project involving a great > community. > > We thank all the contributors to this release: > > Aaron Bieber, Ackerley Tng, Alban Benmouffek, Ale Cossio, Alexandre > Bergel, Alistair Grant, Allex Oliveira, Angela Chia-Ling, Arturo Zambrano, > Asbathou Biyalou-Sama, Ben Coman, Benoit Verhaegue, Carlo Teixeira, Carlos > Lopez, Carolina Hernandez, Charles A. Monteiro, Christoph Thiede, > Christophe Demarey, Clotilde Toullec, Cyril Ferlicot, Damien Pollet, Daniel > Aparicio, David Bajger, David SÃ¡nchez i Gregori, Denis Kudriashov, Ellis > Harris, Eric Brandwein, Eric Gade, Erik Stel, ErikOnBike, Esteban > Lorenzano, Esteban Villalobos, Evelyn Cusi Lopez, Evelyn Cusi Lopez, Ewan > Dawson, Francis Pineda, Francis Pineda, Gabriel Omar Cotelli, Geraldine > Galindo, Giovanni Corriga, Guille Polito, Himanshu jld, Johan Brichau, > Jonathan van Alteren, Jordan Montt, Julien Delplanque, Kamil Kukura, Kasper > Ãsterbye, Kurt Kilpela, Laurine Dargaud, Marco Rimoldi, Marcus Denker, > Martin Dias, Martin McClure, Massimo Nocentini, Max Leske, Maximilian > Ignacio Willembrinck Santander, Milton Mamani Torres, Moussa Saker, > Myroslava Romaniuk, Nicolas Anquetil, Norbert Hartl, Nour Djihan, Oleksandr > Zaitsev, Pablo SÃ¡nchez RodrÃguez, Pablo Tesone, Pavel Krivanek, Philippe > Lesueur, Pierre Misse, Rakshit P., Rob Sayers, Roland Bernard, Ronie > Salgado, Sean DeNigris, Sebastian Jordan MontaÃ±o, Serge Stinckwich, Stephan > Eggermont, Steven Costiou, StÃ©phane Ducasse, Sven Van Caekenberghe, Thomas > Dupriez, ThÃ©o Lanord, ThÃ©o Rogliano, Todd Blanchard, Torsten Bergmann, > Vincent Blondeau, WÃ©slleymberg Lisboa. > > > (If you contributed with Pharo 9 development in any way and we missed your > name, please send us an email and we will add you). > > Enjoy! > > The Pharo Team > > Try Pharo: http://pharo.org/download <https://pharo.org/download> > > Learn Pharo: http://pharo.org/documentation > <https://pharo.org/documentation> >

July 16, 2021

Re: [ANN] Pharo 9 released!

by Richard O'Keefe

Congratulations. This must have been a huge amount of work. On Thu, 15 Jul 2021 at 21:15, Esteban Lorenzano <estebanlm(a)netc.eu> wrote: > Dear World and dynamic language lovers: > > The time has come for Pharo 9 <https://pharo.org/> ! > > Pharo is a pure object-oriented programming language and a powerful > environment, focused on simplicity and immediate feedback. > > > Here are the key features of Pharo 9: > > > - Full redesign of the Spec UI framework (new logic, application, > style, GTK3 back-end) > - New tools: > - > - new playground, > - new object centric inspector, > - new object centric debugger. > - better and new Refactorings > - class comments are now written in Microdown format (Markdown > compatible) > - classes now can be defined using a "fluid" api (Preview) > - New completion framework that adapts better to edition contexts > and is customizable > - Fast universal non-blocking FFI which now uses libFFI as backend. > - Pharo now supports Windows, OSX, Linux (Ubuntu, Debian, Fedora, > openSUSE, Arch, Raspbian) and multiple architectures (Intel/ARM 32/64bits). > - Virtual Machine > - > - Idle VM > - Support for ARM 64bits > - Support for Apple M1 > - More than 3000 tests > - Built for Ubuntu 18.04, 19.04, 20.04, 21.04, 21.10; Debian 9, 10, > Testing; Fedora 32, 32, 34; openSUSE 15.1, 15.2, Tumbleweed; Manjaro; Arch > - Uses SDL 2.0 as back-end by default. It supports extended event > handling, including trackpad support. > - General speed up due to compiler optimisations and UI simplification. > - And many, many more tests. > > > These are just the more prominent highlights, but the details are just as > important. We have closed a massive amount of issues: around 1400 issues > and 2150 pull requests. > > A more extended changelog can be found at > https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo90Change… > . > > While the technical improvements are significant, still the most > impressive fact is that the new code that got in the main Pharo 9 image was > contributed by more than 90 people. > > Pharo is more than code. It is an exciting project involving a great > community. > > We thank all the contributors to this release: > > Aaron Bieber, Ackerley Tng, Alban Benmouffek, Ale Cossio, Alexandre > Bergel, Alistair Grant, Allex Oliveira, Angela Chia-Ling, Arturo Zambrano, > Asbathou Biyalou-Sama, Ben Coman, Benoit Verhaegue, Carlo Teixeira, Carlos > Lopez, Carolina Hernandez, Charles A. Monteiro, Christoph Thiede, > Christophe Demarey, Clotilde Toullec, Cyril Ferlicot, Damien Pollet, Daniel > Aparicio, David Bajger, David SÃ¡nchez i Gregori, Denis Kudriashov, Ellis > Harris, Eric Brandwein, Eric Gade, Erik Stel, ErikOnBike, Esteban > Lorenzano, Esteban Villalobos, Evelyn Cusi Lopez, Evelyn Cusi Lopez, Ewan > Dawson, Francis Pineda, Francis Pineda, Gabriel Omar Cotelli, Geraldine > Galindo, Giovanni Corriga, Guille Polito, Himanshu jld, Johan Brichau, > Jonathan van Alteren, Jordan Montt, Julien Delplanque, Kamil Kukura, Kasper > Ãsterbye, Kurt Kilpela, Laurine Dargaud, Marco Rimoldi, Marcus Denker, > Martin Dias, Martin McClure, Massimo Nocentini, Max Leske, Maximilian > Ignacio Willembrinck Santander, Milton Mamani Torres, Moussa Saker, > Myroslava Romaniuk, Nicolas Anquetil, Norbert Hartl, Nour Djihan, Oleksandr > Zaitsev, Pablo SÃ¡nchez RodrÃguez, Pablo Tesone, Pavel Krivanek, Philippe > Lesueur, Pierre Misse, Rakshit P., Rob Sayers, Roland Bernard, Ronie > Salgado, Sean DeNigris, Sebastian Jordan MontaÃ±o, Serge Stinckwich, Stephan > Eggermont, Steven Costiou, StÃ©phane Ducasse, Sven Van Caekenberghe, Thomas > Dupriez, ThÃ©o Lanord, ThÃ©o Rogliano, Todd Blanchard, Torsten Bergmann, > Vincent Blondeau, WÃ©slleymberg Lisboa. > > > (If you contributed with Pharo 9 development in any way and we missed your > name, please send us an email and we will add you). > > Enjoy! > > The Pharo Team > > Try Pharo: http://pharo.org/download <https://pharo.org/download> > > Learn Pharo: http://pharo.org/documentation > <https://pharo.org/documentation> >

July 16, 2021

Re: Pharo 9 released - a brief experience report

by Guillermo Polito

Hi Yanni Chiu, Thanks for the reports, > El 15 jul 2021, a las 20:49, Yanni Chiu <yannix7db(a)gmail.com> escribiÃ³: > > First, great work and thanks to all contributors. > > Using macOS Big Sur version 11.4 on MacBook Air 2019... > > 1. In a new sub-directory "pharo9" (I was using a pharo8 directory, so > pharo9 is to keep things separate). In pharo9, I used "curl -L > https://get.pharo.org/64/ | bash" to get the latest release. Then I > ran ./pharo-ui to start Pharo. Very strangely, it was able to present > my pharo8 images to choose for opening. I quit without choosing any > image, then went looking to find out how it was able to find the > settings. In the course of that, I realized the default download had > got me the 8.0 release. Yes, this was due to my updates to zeroconf. There was a missing update at https://get.pharo.org/64/ and https://get.pharo.org/32. Iâve fixed these and wrote an issue to automate this in the future https://github.com/pharo-project/pharo-zeroconf/issues/34 > > 2. Then I used "curl https://get.pharo.org/90+wm | bash". The image > came up with a strange looking dialog across the top that indicated > freetype font lib's could not be loaded. I just proceeded and was able > to navigate somewhat. The Settings for fonts were completely absent. I > kept browsing, but more freetype font problems kept appearing. > > 3. I then compared the dylib's in the pharo-vm (what I had in pharo8) > vs. what I just got in pharo9 - very different lists. I copied the > libfreetype.6.dylib, libfreetype.dylib, and libFT2Plugin.dylib files > to the new vm, and then the Pharo9 image came up nicely. > > 4. I thought I was home free, and continued browsing. I happened to > look at the Pillar-Core code, and I got "Cannot locate > libcairo.2.dylib". Browsing a few other places did not show this > problem. That's it for now. I will try a bit more later, but I'm going > back to Pharo8 for today. Pablo has updated the VMs just some minutes ago, so these issues should be resolved. Thanks again! :) Guille > > Yanni Chiu

July 16, 2021

UK Smalltalk User Group Meeting - Wednesday 28th July 2021

by Giovanni Corriga

The next meeting of the UK Smalltalk User Group will be on Wednesday, July 30th. Russell Allen will talk to us about Self ( https://selflanguage.org/ ). Dating back to the late 1980s, Self is a prototype based programming language and environment in the broader Smalltalk family. Although Self has always been a niche research system, its influence can still be seen in areas as diverse as the fast VMs of Java and Javascript, in the prototype semantics of Javascript, and in the Morphic user interface used by Squeak, Pharo and Cuis. Russell Allen ( https://twitter.com/russell_allen_ ) has a background in law and computers and first came across Self in the late 1990s. Around 2008 he helped get Self running on Linux x86, set up the Self website and GitHub account, and for the last decade or so he has been helping keep Self as a project alive. In this talk, Russell will demonstrate Self as a running system, including the object semantics, language, and the multi-user Morphic development environment. heâll talk about the current status of the project and the challenges it faces for the future. Given the current COVID-19 restrictions, this will be an online meeting from home. Please note that the meeting will start later than usual, to accomodate the speaker who will connect from Australia. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/UKSTUG/events/cbklbrycckblc/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

July 16, 2021

Re: [Pharo-dev] [ANN] Pharo 9 released!

by Tudor Girba

Congratulations! Tudor > On Jul 15, 2021, at 11:14 AM, Esteban Lorenzano <estebanlm(a)netc.eu> wrote: > > Dear World and dynamic language lovers: > > The time has come for Pharo 9 ! > > Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. > > > > Here are the key features of Pharo 9: > > â¢ Full redesign of the Spec UI framework (new logic, application, style, GTK3 back-end) > â¢ New tools: > â¢ > â¢ new playground, > â¢ new object centric inspector, > â¢ new object centric debugger. > â¢ better and new Refactorings > â¢ class comments are now written in Microdown format (Markdown compatible) > â¢ classes now can be defined using a "fluid" api (Preview) > â¢ New completion framework that adapts better to edition contexts and is customizable > â¢ Fast universal non-blocking FFI which now uses libFFI as backend. > â¢ Pharo now supports Windows, OSX, Linux (Ubuntu, Debian, Fedora, openSUSE, Arch, Raspbian) and multiple architectures (Intel/ARM 32/64bits). > â¢ Virtual Machine > â¢ > â¢ Idle VM > â¢ Support for ARM 64bits > â¢ Support for Apple M1 > â¢ More than 3000 tests > â¢ Built for Ubuntu 18.04, 19.04, 20.04, 21.04, 21.10; Debian 9, 10, Testing; Fedora 32, 32, 34; openSUSE 15.1, 15.2, Tumbleweed; Manjaro; Arch > â¢ Uses SDL 2.0 as back-end by default. It supports extended event handling, including trackpad support. > â¢ General speed up due to compiler optimisations and UI simplification. > â¢ And many, many more tests. > > These are just the more prominent highlights, but the details are just as important. We have closed a massive amount of issues: around 1400 issues and 2150 pull requests. > > A more extended changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo90Change…. > > While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 9 image was contributed by more than 90 people. > > Pharo is more than code. It is an exciting project involving a great community. > > We thank all the contributors to this release: > > Aaron Bieber, Ackerley Tng, Alban Benmouffek, Ale Cossio, Alexandre Bergel, Alistair Grant, Allex Oliveira, Angela Chia-Ling, Arturo Zambrano, Asbathou Biyalou-Sama, Ben Coman, Benoit Verhaegue, Carlo Teixeira, Carlos Lopez, Carolina Hernandez, Charles A. Monteiro, Christoph Thiede, Christophe Demarey, Clotilde Toullec, Cyril Ferlicot, Damien Pollet, Daniel Aparicio, David Bajger, David SÃ¡nchez i Gregori, Denis Kudriashov, Ellis Harris, Eric Brandwein, Eric Gade, Erik Stel, ErikOnBike, Esteban Lorenzano, Esteban Villalobos, Evelyn Cusi Lopez, Evelyn Cusi Lopez, Ewan Dawson, Francis Pineda, Francis Pineda, Gabriel Omar Cotelli, Geraldine Galindo, Giovanni Corriga, Guille Polito, Himanshu jld, Johan Brichau, Jonathan van Alteren, Jordan Montt, Julien Delplanque, Kamil Kukura, Kasper Ãsterbye, Kurt Kilpela, Laurine Dargaud, Marco Rimoldi, Marcus Denker, Martin Dias, Martin McClure, Massimo Nocentini, Max Leske, Maximilian Ignacio Willembrinck Santander, Milton Mamani Torres, Moussa Saker, Myroslava Romaniuk, Nicolas Anquetil, Norbert Hartl, Nour Djihan, Oleksandr Zaitsev, Pablo SÃ¡nchez RodrÃguez, Pablo Tesone, Pavel Krivanek, Philippe Lesueur, Pierre Misse, Rakshit P., Rob Sayers, Roland Bernard, Ronie Salgado, Sean DeNigris, Sebastian Jordan MontaÃ±o, Serge Stinckwich, Stephan Eggermont, Steven Costiou, StÃ©phane Ducasse, Sven Van Caekenberghe, Thomas Dupriez, ThÃ©o Lanord, ThÃ©o Rogliano, Todd Blanchard, Torsten Bergmann, Vincent Blondeau, WÃ©slleymberg Lisboa. > > > (If you contributed with Pharo 9 development in any way and we missed your name, please send us an email and we will add you). > > Enjoy! > > The Pharo Team > > Try Pharo: http://pharo.org/download > > Learn Pharo: http://pharo.org/documentation -- feenk.com "No matter how many recipes we know, we still value a chef."

July 16, 2021

Re: [ANN] Pharo 9 released!

by Norbert Hartl

Great news! Finally it arrived. Big changes happened and this release might feel a bit rough. But that is expected. And we should not underestimate the value of moving all tools to spec. That makes all of it (yet again) less dependent in morphic. Having an idle vm is also highly appreciated for peole like me that do a lot of server installations. Well done and thanks for the hard work! Norbert > Am 15.07.2021 um 11:15 schrieb Esteban Lorenzano <estebanlm(a)netc.eu>: > > ï»¿ > Dear World and dynamic language lovers: > > The time has come for Pharo 9 ! > > Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. > > > > Here are the key features of Pharo 9: > > Full redesign of the Spec UI framework (new logic, application, style, GTK3 back-end) > New tools: > new playground, > new object centric inspector, > new object centric debugger. > better and new Refactorings > class comments are now written in Microdown format (Markdown compatible) > classes now can be defined using a "fluid" api (Preview) > New completion framework that adapts better to edition contexts and is customizable > Fast universal non-blocking FFI which now uses libFFI as backend. > Pharo now supports Windows, OSX, Linux (Ubuntu, Debian, Fedora, openSUSE, Arch, Raspbian) and multiple architectures (Intel/ARM 32/64bits). > Virtual Machine > Idle VM > Support for ARM 64bits > Support for Apple M1 > More than 3000 tests > Built for Ubuntu 18.04, 19.04, 20.04, 21.04, 21.10; Debian 9, 10, Testing; Fedora 32, 32, 34; openSUSE 15.1, 15.2, Tumbleweed; Manjaro; Arch > Uses SDL 2.0 as back-end by default. It supports extended event handling, including trackpad support. > General speed up due to compiler optimisations and UI simplification. > And many, many more tests. > > These are just the more prominent highlights, but the details are just as important. We have closed a massive amount of issues: around 1400 issues and 2150 pull requests. > > A more extended changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo90Change…. > > While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 9 image was contributed by more than 90 people. > > Pharo is more than code. It is an exciting project involving a great community. > > We thank all the contributors to this release: > > Aaron Bieber, Ackerley Tng, Alban Benmouffek, Ale Cossio, Alexandre Bergel, Alistair Grant, Allex Oliveira, Angela Chia-Ling, Arturo Zambrano, Asbathou Biyalou-Sama, Ben Coman, Benoit Verhaegue, Carlo Teixeira, Carlos Lopez, Carolina Hernandez, Charles A. Monteiro, Christoph Thiede, Christophe Demarey, Clotilde Toullec, Cyril Ferlicot, Damien Pollet, Daniel Aparicio, David Bajger, David SÃ¡nchez i Gregori, Denis Kudriashov, Ellis Harris, Eric Brandwein, Eric Gade, Erik Stel, ErikOnBike, Esteban Lorenzano, Esteban Villalobos, Evelyn Cusi Lopez, Evelyn Cusi Lopez, Ewan Dawson, Francis Pineda, Francis Pineda, Gabriel Omar Cotelli, Geraldine Galindo, Giovanni Corriga, Guille Polito, Himanshu jld, Johan Brichau, Jonathan van Alteren, Jordan Montt, Julien Delplanque, Kamil Kukura, Kasper Ãsterbye, Kurt Kilpela, Laurine Dargaud, Marco Rimoldi, Marcus Denker, Martin Dias, Martin McClure, Massimo Nocentini, Max Leske, Maximilian Ignacio Willembrinck Santander, Milton Mamani Torres, Moussa Saker, Myroslava Romaniuk, Nicolas Anquetil, Norbert Hartl, Nour Djihan, Oleksandr Zaitsev, Pablo SÃ¡nchez RodrÃguez, Pablo Tesone, Pavel Krivanek, Philippe Lesueur, Pierre Misse, Rakshit P., Rob Sayers, Roland Bernard, Ronie Salgado, Sean DeNigris, Sebastian Jordan MontaÃ±o, Serge Stinckwich, Stephan Eggermont, Steven Costiou, StÃ©phane Ducasse, Sven Van Caekenberghe, Thomas Dupriez, ThÃ©o Lanord, ThÃ©o Rogliano, Todd Blanchard, Torsten Bergmann, Vincent Blondeau, WÃ©slleymberg Lisboa. > > > (If you contributed with Pharo 9 development in any way and we missed your name, please send us an email and we will add you). > > Enjoy! > > The Pharo Team > > Try Pharo: http://pharo.org/download > > Learn Pharo: http://pharo.org/documentation

July 16, 2021

Pharo 9 released - a brief experience report

by Yanni Chiu

First, great work and thanks to all contributors. Using macOS Big Sur version 11.4 on MacBook Air 2019... 1. In a new sub-directory "pharo9" (I was using a pharo8 directory, so pharo9 is to keep things separate). In pharo9, I used "curl -L https://get.pharo.org/64/ | bash" to get the latest release. Then I ran ./pharo-ui to start Pharo. Very strangely, it was able to present my pharo8 images to choose for opening. I quit without choosing any image, then went looking to find out how it was able to find the settings. In the course of that, I realized the default download had got me the 8.0 release. 2. Then I used "curl https://get.pharo.org/90+wm | bash". The image came up with a strange looking dialog across the top that indicated freetype font lib's could not be loaded. I just proceeded and was able to navigate somewhat. The Settings for fonts were completely absent. I kept browsing, but more freetype font problems kept appearing. 3. I then compared the dylib's in the pharo-vm (what I had in pharo8) vs. what I just got in pharo9 - very different lists. I copied the libfreetype.6.dylib, libfreetype.dylib, and libFT2Plugin.dylib files to the new vm, and then the Pharo9 image came up nicely. 4. I thought I was home free, and continued browsing. I happened to look at the Pillar-Core code, and I got "Cannot locate libcairo.2.dylib". Browsing a few other places did not show this problem. That's it for now. I will try a bit more later, but I'm going back to Pharo8 for today. Yanni Chiu

July 15, 2021

Re: [ANN] Pharo 9 released!

by Samuel Teixeira Santos

Awesome, comgratulations to all ðâð¥³ð

July 15, 2021

Re: [ANN] Pharo 9 released!

by Tim Mackinnon

Nice work guys - I hadnât realised it was going to be around nowâ¦ looking forward to being able to try the new things out. Tim > On 15 Jul 2021, at 16:44, Russ Whaley <whaley.russ(a)gmail.com> wrote: > > Congratulations everyone on Pharo v9. I love working in this immersive environment. > > On Thu, Jul 15, 2021 at 5:15 AM Esteban Lorenzano <estebanlm(a)netc.eu <mailto:estebanlm@netc.eu>> wrote: > Dear World and dynamic language lovers: > > The time has come for Pharo 9 <https://pharo.org/> ! > > Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. > > > > Here are the key features of Pharo 9: > > Full redesign of the Spec UI framework (new logic, application, style, GTK3 back-end) > New tools: > new playground, > new object centric inspector, > new object centric debugger. > better and new Refactorings > class comments are now written in Microdown format (Markdown compatible) > classes now can be defined using a "fluid" api (Preview) > New completion framework that adapts better to edition contexts and is customizable > Fast universal non-blocking FFI which now uses libFFI as backend. > Pharo now supports Windows, OSX, Linux (Ubuntu, Debian, Fedora, openSUSE, Arch, Raspbian) and multiple architectures (Intel/ARM 32/64bits). > Virtual Machine > Idle VM > Support for ARM 64bits > Support for Apple M1 > More than 3000 tests > Built for Ubuntu 18.04, 19.04, 20.04, 21.04, 21.10; Debian 9, 10, Testing; Fedora 32, 32, 34; openSUSE 15.1, 15.2, Tumbleweed; Manjaro; Arch > Uses SDL 2.0 as back-end by default. It supports extended event handling, including trackpad support. > General speed up due to compiler optimisations and UI simplification. > And many, many more tests. > > These are just the more prominent highlights, but the details are just as important. We have closed a massive amount of issues: around 1400 issues and 2150 pull requests. > > A more extended changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo90Change… <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo90Change…>. > > While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 9 image was contributed by more than 90 people. > > Pharo is more than code. It is an exciting project involving a great community. > > We thank all the contributors to this release: > > Aaron Bieber, Ackerley Tng, Alban Benmouffek, Ale Cossio, Alexandre Bergel, Alistair Grant, Allex Oliveira, Angela Chia-Ling, Arturo Zambrano, Asbathou Biyalou-Sama, Ben Coman, Benoit Verhaegue, Carlo Teixeira, Carlos Lopez, Carolina Hernandez, Charles A. Monteiro, Christoph Thiede, Christophe Demarey, Clotilde Toullec, Cyril Ferlicot, Damien Pollet, Daniel Aparicio, David Bajger, David SÃ¡nchez i Gregori, Denis Kudriashov, Ellis Harris, Eric Brandwein, Eric Gade, Erik Stel, ErikOnBike, Esteban Lorenzano, Esteban Villalobos, Evelyn Cusi Lopez, Evelyn Cusi Lopez, Ewan Dawson, Francis Pineda, Francis Pineda, Gabriel Omar Cotelli, Geraldine Galindo, Giovanni Corriga, Guille Polito, Himanshu jld, Johan Brichau, Jonathan van Alteren, Jordan Montt, Julien Delplanque, Kamil Kukura, Kasper Ãsterbye, Kurt Kilpela, Laurine Dargaud, Marco Rimoldi, Marcus Denker, Martin Dias, Martin McClure, Massimo Nocentini, Max Leske, Maximilian Ignacio Willembrinck Santander, Milton Mamani Torres, Moussa Saker, Myroslava Romaniuk, Nicolas Anquetil, Norbert Hartl, Nour Djihan, Oleksandr Zaitsev, Pablo SÃ¡nchez RodrÃguez, Pablo Tesone, Pavel Krivanek, Philippe Lesueur, Pierre Misse, Rakshit P., Rob Sayers, Roland Bernard, Ronie Salgado, Sean DeNigris, Sebastian Jordan MontaÃ±o, Serge Stinckwich, Stephan Eggermont, Steven Costiou, StÃ©phane Ducasse, Sven Van Caekenberghe, Thomas Dupriez, ThÃ©o Lanord, ThÃ©o Rogliano, Todd Blanchard, Torsten Bergmann, Vincent Blondeau, WÃ©slleymberg Lisboa. > > > (If you contributed with Pharo 9 development in any way and we missed your name, please send us an email and we will add you). > > Enjoy! > > The Pharo Team > > Try Pharo: http://pharo.org/download <https://pharo.org/download> > Learn Pharo: http://pharo.org/documentation <https://pharo.org/documentation> > > -- > Russ Whaley > whaley.russ(a)gmail.com <mailto:whaley.russ@gmail.com>

July 15, 2021

Re: [ANN] Pharo 9 released!

by Sven Van Caekenberghe

> On 15 Jul 2021, at 16:44, Russ Whaley <whaley.russ(a)gmail.com> wrote: > > Congratulations everyone on Pharo v9. I love working in this immersive environment. Well said, congratulations to all contributors. > On Thu, Jul 15, 2021 at 5:15 AM Esteban Lorenzano <estebanlm(a)netc.eu> wrote: > Dear World and dynamic language lovers: > > The time has come for Pharo 9 ! > > Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. > > > > Here are the key features of Pharo 9: > > â¢ Full redesign of the Spec UI framework (new logic, application, style, GTK3 back-end) > â¢ New tools: > â¢ > â¢ new playground, > â¢ new object centric inspector, > â¢ new object centric debugger. > â¢ better and new Refactorings > â¢ class comments are now written in Microdown format (Markdown compatible) > â¢ classes now can be defined using a "fluid" api (Preview) > â¢ New completion framework that adapts better to edition contexts and is customizable > â¢ Fast universal non-blocking FFI which now uses libFFI as backend. > â¢ Pharo now supports Windows, OSX, Linux (Ubuntu, Debian, Fedora, openSUSE, Arch, Raspbian) and multiple architectures (Intel/ARM 32/64bits). > â¢ Virtual Machine > â¢ > â¢ Idle VM > â¢ Support for ARM 64bits > â¢ Support for Apple M1 > â¢ More than 3000 tests > â¢ Built for Ubuntu 18.04, 19.04, 20.04, 21.04, 21.10; Debian 9, 10, Testing; Fedora 32, 32, 34; openSUSE 15.1, 15.2, Tumbleweed; Manjaro; Arch > â¢ Uses SDL 2.0 as back-end by default. It supports extended event handling, including trackpad support. > â¢ General speed up due to compiler optimisations and UI simplification. > â¢ And many, many more tests. > > These are just the more prominent highlights, but the details are just as important. We have closed a massive amount of issues: around 1400 issues and 2150 pull requests. > > A more extended changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo90Change…. > > While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 9 image was contributed by more than 90 people. > > Pharo is more than code. It is an exciting project involving a great community. > > We thank all the contributors to this release: > > Aaron Bieber, Ackerley Tng, Alban Benmouffek, Ale Cossio, Alexandre Bergel, Alistair Grant, Allex Oliveira, Angela Chia-Ling, Arturo Zambrano, Asbathou Biyalou-Sama, Ben Coman, Benoit Verhaegue, Carlo Teixeira, Carlos Lopez, Carolina Hernandez, Charles A. Monteiro, Christoph Thiede, Christophe Demarey, Clotilde Toullec, Cyril Ferlicot, Damien Pollet, Daniel Aparicio, David Bajger, David SÃ¡nchez i Gregori, Denis Kudriashov, Ellis Harris, Eric Brandwein, Eric Gade, Erik Stel, ErikOnBike, Esteban Lorenzano, Esteban Villalobos, Evelyn Cusi Lopez, Evelyn Cusi Lopez, Ewan Dawson, Francis Pineda, Francis Pineda, Gabriel Omar Cotelli, Geraldine Galindo, Giovanni Corriga, Guille Polito, Himanshu jld, Johan Brichau, Jonathan van Alteren, Jordan Montt, Julien Delplanque, Kamil Kukura, Kasper Ãsterbye, Kurt Kilpela, Laurine Dargaud, Marco Rimoldi, Marcus Denker, Martin Dias, Martin McClure, Massimo Nocentini, Max Leske, Maximilian Ignacio Willembrinck Santander, Milton Mamani Torres, Moussa Saker, Myroslava Romaniuk, Nicolas Anquetil, Norbert Hartl, Nour Djihan, Oleksandr Zaitsev, Pablo SÃ¡nchez RodrÃguez, Pablo Tesone, Pavel Krivanek, Philippe Lesueur, Pierre Misse, Rakshit P., Rob Sayers, Roland Bernard, Ronie Salgado, Sean DeNigris, Sebastian Jordan MontaÃ±o, Serge Stinckwich, Stephan Eggermont, Steven Costiou, StÃ©phane Ducasse, Sven Van Caekenberghe, Thomas Dupriez, ThÃ©o Lanord, ThÃ©o Rogliano, Todd Blanchard, Torsten Bergmann, Vincent Blondeau, WÃ©slleymberg Lisboa. > > > (If you contributed with Pharo 9 development in any way and we missed your name, please send us an email and we will add you). > > Enjoy! > > The Pharo Team > > Try Pharo: http://pharo.org/download > > Learn Pharo: http://pharo.org/documentation > > > -- > Russ Whaley > whaley.russ(a)gmail.com

July 15, 2021

Re: [ANN] Pharo 9 released!

by Russ Whaley

Congratulations everyone on Pharo v9. I love working in this immersive environment. On Thu, Jul 15, 2021 at 5:15 AM Esteban Lorenzano <estebanlm(a)netc.eu> wrote: > Dear World and dynamic language lovers: > > The time has come for Pharo 9 <https://pharo.org/> ! > > Pharo is a pure object-oriented programming language and a powerful > environment, focused on simplicity and immediate feedback. > > > Here are the key features of Pharo 9: > > > - Full redesign of the Spec UI framework (new logic, application, > style, GTK3 back-end) > - New tools: > - > - new playground, > - new object centric inspector, > - new object centric debugger. > - better and new Refactorings > - class comments are now written in Microdown format (Markdown > compatible) > - classes now can be defined using a "fluid" api (Preview) > - New completion framework that adapts better to edition contexts > and is customizable > - Fast universal non-blocking FFI which now uses libFFI as backend. > - Pharo now supports Windows, OSX, Linux (Ubuntu, Debian, Fedora, > openSUSE, Arch, Raspbian) and multiple architectures (Intel/ARM 32/64bits). > - Virtual Machine > - > - Idle VM > - Support for ARM 64bits > - Support for Apple M1 > - More than 3000 tests > - Built for Ubuntu 18.04, 19.04, 20.04, 21.04, 21.10; Debian 9, 10, > Testing; Fedora 32, 32, 34; openSUSE 15.1, 15.2, Tumbleweed; Manjaro; Arch > - Uses SDL 2.0 as back-end by default. It supports extended event > handling, including trackpad support. > - General speed up due to compiler optimisations and UI simplification. > - And many, many more tests. > > > These are just the more prominent highlights, but the details are just as > important. We have closed a massive amount of issues: around 1400 issues > and 2150 pull requests. > > A more extended changelog can be found at > https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo90Change… > . > > While the technical improvements are significant, still the most > impressive fact is that the new code that got in the main Pharo 9 image was > contributed by more than 90 people. > > Pharo is more than code. It is an exciting project involving a great > community. > > We thank all the contributors to this release: > > Aaron Bieber, Ackerley Tng, Alban Benmouffek, Ale Cossio, Alexandre > Bergel, Alistair Grant, Allex Oliveira, Angela Chia-Ling, Arturo Zambrano, > Asbathou Biyalou-Sama, Ben Coman, Benoit Verhaegue, Carlo Teixeira, Carlos > Lopez, Carolina Hernandez, Charles A. Monteiro, Christoph Thiede, > Christophe Demarey, Clotilde Toullec, Cyril Ferlicot, Damien Pollet, Daniel > Aparicio, David Bajger, David SÃ¡nchez i Gregori, Denis Kudriashov, Ellis > Harris, Eric Brandwein, Eric Gade, Erik Stel, ErikOnBike, Esteban > Lorenzano, Esteban Villalobos, Evelyn Cusi Lopez, Evelyn Cusi Lopez, Ewan > Dawson, Francis Pineda, Francis Pineda, Gabriel Omar Cotelli, Geraldine > Galindo, Giovanni Corriga, Guille Polito, Himanshu jld, Johan Brichau, > Jonathan van Alteren, Jordan Montt, Julien Delplanque, Kamil Kukura, Kasper > Ãsterbye, Kurt Kilpela, Laurine Dargaud, Marco Rimoldi, Marcus Denker, > Martin Dias, Martin McClure, Massimo Nocentini, Max Leske, Maximilian > Ignacio Willembrinck Santander, Milton Mamani Torres, Moussa Saker, > Myroslava Romaniuk, Nicolas Anquetil, Norbert Hartl, Nour Djihan, Oleksandr > Zaitsev, Pablo SÃ¡nchez RodrÃguez, Pablo Tesone, Pavel Krivanek, Philippe > Lesueur, Pierre Misse, Rakshit P., Rob Sayers, Roland Bernard, Ronie > Salgado, Sean DeNigris, Sebastian Jordan MontaÃ±o, Serge Stinckwich, Stephan > Eggermont, Steven Costiou, StÃ©phane Ducasse, Sven Van Caekenberghe, Thomas > Dupriez, ThÃ©o Lanord, ThÃ©o Rogliano, Todd Blanchard, Torsten Bergmann, > Vincent Blondeau, WÃ©slleymberg Lisboa. > > > (If you contributed with Pharo 9 development in any way and we missed your > name, please send us an email and we will add you). > > Enjoy! > > The Pharo Team > > Try Pharo: http://pharo.org/download <https://pharo.org/download> > > Learn Pharo: http://pharo.org/documentation > <https://pharo.org/documentation> > -- Russ Whaley whaley.russ(a)gmail.com

July 15, 2021

Re: [Pharo-dev] [ANN] Pharo 9 released!

by Noury Bouraqadi

Yey! Big thank you to the core team and all the community! Noury On Jul 15 2021, at 11:14 am, Esteban Lorenzano <estebanlm(a)netc.eu> wrote: > Dear World and dynamic language lovers: > > The time has come for Pharo 9 (https://pharo.org/) ! > Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. > > Here are the key features of Pharo 9: > Full redesign of the Spec UI framework (new logic, application, style, GTK3 back-end) > New tools: > > new playground, > > new object centric inspector, > > new object centric debugger. > > better and new Refactorings > > class comments are now written in Microdown format (Markdown compatible) > > classes now can be defined using a "fluid" api (Preview) > > > > New completion framework that adapts better to edition contexts and is customizable > > Fast universal non-blocking FFI which now uses libFFI as backend. > > Pharo now supports Windows, OSX, Linux (Ubuntu, Debian, Fedora, openSUSE, Arch, Raspbian) and multiple architectures (Intel/ARM 32/64bits). > > Virtual Machine > > Idle VM > > Support for ARM 64bits > > Support for Apple M1 > > More than 3000 tests > > Built for Ubuntu 18.04, 19.04, 20.04, 21.04, 21.10; Debian 9, 10, Testing; Fedora 32, 32, 34; openSUSE 15.1, 15.2, Tumbleweed; Manjaro; Arch > > > > Uses SDL 2.0 as back-end by default. It supports extended event handling, including trackpad support. > > General speed up due to compiler optimisations and UI simplification. > > And many, many more tests. > > > > These are just the more prominent highlights, but the details are just as important. We have closed a massive amount of issues: around 1400 issues and 2150 pull requests. > A more extended changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo90Change…. > While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 9 image was contributed by more than 90 people. > Pharo is more than code. It is an exciting project involving a great community. > We thank all the contributors to this release: > Aaron Bieber, Ackerley Tng, Alban Benmouffek, Ale Cossio, Alexandre Bergel, Alistair Grant, Allex Oliveira, Angela Chia-Ling, Arturo Zambrano, Asbathou Biyalou-Sama, Ben Coman, Benoit Verhaegue, Carlo Teixeira, Carlos Lopez, Carolina Hernandez, Charles A. Monteiro, Christoph Thiede, Christophe Demarey, Clotilde Toullec, Cyril Ferlicot, Damien Pollet, Daniel Aparicio, David Bajger, David SÃ¡nchez i Gregori, Denis Kudriashov, Ellis Harris, Eric Brandwein, Eric Gade, Erik Stel, ErikOnBike, Esteban Lorenzano, Esteban Villalobos, Evelyn Cusi Lopez, Evelyn Cusi Lopez, Ewan Dawson, Francis Pineda, Francis Pineda, Gabriel Omar Cotelli, Geraldine Galindo, Giovanni Corriga, Guille Polito, Himanshu jld, Johan Brichau, Jonathan van Alteren, Jordan Montt, Julien Delplanque, Kamil Kukura, Kasper Ãsterbye, Kurt Kilpela, Laurine Dargaud, Marco Rimoldi, Marcus Denker, Martin Dias, Martin McClure, Massimo Nocentini, Max Leske, Maximilian Ignacio Willembrinck Santander, Milton Mamani Torres, Moussa Saker, Myroslava Romaniuk, Nicolas Anquetil, Norbert Hartl, Nour Djihan, Oleksandr Zaitsev, Pablo SÃ¡nchez RodrÃguez, Pablo Tesone, Pavel Krivanek, Philippe Lesueur, Pierre Misse, Rakshit P., Rob Sayers, Roland Bernard, Ronie Salgado, Sean DeNigris, Sebastian Jordan MontaÃ±o, Serge Stinckwich, Stephan Eggermont, Steven Costiou, StÃ©phane Ducasse, Sven Van Caekenberghe, Thomas Dupriez, ThÃ©o Lanord, ThÃ©o Rogliano, Todd Blanchard, Torsten Bergmann, Vincent Blondeau, WÃ©slleymberg Lisboa. > > > (If you contributed with Pharo 9 development in any way and we missed your name, please send us an email and we will add you). > Enjoy! > The Pharo Team > Try Pharo: http://pharo.org/download (https://pharo.org/download) > Learn Pharo: http://pharo.org/documentation (https://pharo.org/documentation)

July 15, 2021

[ANN] Pharo 9 released!

by Esteban Lorenzano

Dear World and dynamic language lovers: The time has come for Pharo 9 (https://pharo.org/) ! Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. Here are the key features of Pharo 9: Full redesign of the Spec UI framework (new logic, application, style, GTK3 back-end) New tools: new playground, new object centric inspector, new object centric debugger. better and new Refactorings class comments are now written in Microdown format (Markdown compatible) classes now can be defined using a "fluid" api (Preview) New completion framework that adapts better to edition contexts and is customizable Fast universal non-blocking FFI which now uses libFFI as backend. Pharo now supports Windows, OSX, Linux (Ubuntu, Debian, Fedora, openSUSE, Arch, Raspbian) and multiple architectures (Intel/ARM 32/64bits). Virtual Machine Idle VM Support for ARM 64bits Support for Apple M1 More than 3000 tests Built for Ubuntu 18.04, 19.04, 20.04, 21.04, 21.10; Debian 9, 10, Testing; Fedora 32, 32, 34; openSUSE 15.1, 15.2, Tumbleweed; Manjaro; Arch Uses SDL 2.0 as back-end by default. It supports extended event handling, including trackpad support. General speed up due to compiler optimisations and UI simplification. And many, many more tests. These are just the more prominent highlights, but the details are just as important. We have closed a massive amount of issues: around 1400 issues and 2150 pull requests. A more extended changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo90Change…. While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 9 image was contributed by more than 90 people. Pharo is more than code. It is an exciting project involving a great community. We thank all the contributors to this release: Aaron Bieber, Ackerley Tng, Alban Benmouffek, Ale Cossio, Alexandre Bergel, Alistair Grant, Allex Oliveira, Angela Chia-Ling, Arturo Zambrano, Asbathou Biyalou-Sama, Ben Coman, Benoit Verhaegue, Carlo Teixeira, Carlos Lopez, Carolina Hernandez, Charles A. Monteiro, Christoph Thiede, Christophe Demarey, Clotilde Toullec, Cyril Ferlicot, Damien Pollet, Daniel Aparicio, David Bajger, David SÃ¡nchez i Gregori, Denis Kudriashov, Ellis Harris, Eric Brandwein, Eric Gade, Erik Stel, ErikOnBike, Esteban Lorenzano, Esteban Villalobos, Evelyn Cusi Lopez, Evelyn Cusi Lopez, Ewan Dawson, Francis Pineda, Francis Pineda, Gabriel Omar Cotelli, Geraldine Galindo, Giovanni Corriga, Guille Polito, Himanshu jld, Johan Brichau, Jonathan van Alteren, Jordan Montt, Julien Delplanque, Kamil Kukura, Kasper Ãsterbye, Kurt Kilpela, Laurine Dargaud, Marco Rimoldi, Marcus Denker, Martin Dias, Martin McClure, Massimo Nocentini, Max Leske, Maximilian Ignacio Willembrinck Santander, Milton Mamani Torres, Moussa Saker, Myroslava Romaniuk, Nicolas Anquetil, Norbert Hartl, Nour Djihan, Oleksandr Zaitsev, Pablo SÃ¡nchez RodrÃguez, Pablo Tesone, Pavel Krivanek, Philippe Lesueur, Pierre Misse, Rakshit P., Rob Sayers, Roland Bernard, Ronie Salgado, Sean DeNigris, Sebastian Jordan MontaÃ±o, Serge Stinckwich, Stephan Eggermont, Steven Costiou, StÃ©phane Ducasse, Sven Van Caekenberghe, Thomas Dupriez, ThÃ©o Lanord, ThÃ©o Rogliano, Todd Blanchard, Torsten Bergmann, Vincent Blondeau, WÃ©slleymberg Lisboa. (If you contributed with Pharo 9 development in any way and we missed your name, please send us an email and we will add you). Enjoy! The Pharo Team Try Pharo: http://pharo.org/download (https://pharo.org/download) Learn Pharo: http://pharo.org/documentation (https://pharo.org/documentation)

July 15, 2021

[ANN] Superluminal v2.2.0 [v2.2.0] released!

by Buenos Aires Smalltalk

July 14, 2021

Re: Mailing list web forum seems to be broken

by Richard Sargent

On Tue, Jul 13, 2021 at 5:09 AM Kenneth Payne <voxkmp(a)gmail.com> wrote: > Hi > > For some time now the forum on http://forum.world.st/Pharo-f1294836.html has not > been working properly. > Messages to this list are showing up in my mailbox but not on the website. > I believe you are seeing the effect of http://support.nabble.com/Mailing-Lists-will-be-updated-to-regular-forums-n… . > Is someone looking at this? it's not a good look for the pharo community. > > Ken > >

July 13, 2021

Mailing list web forum seems to be broken

by Kenneth Payne

Hi For some time now the forum on http://forum.world.st/Pharo-f1294836.html has not been working properly. Messages to this list are showing up in my mailbox but not on the website. Is someone looking at this? it's not a good look for the pharo community. Ken

July 13, 2021