February 2019 - Pharo-users

Stability of Pharo 7 vs 6?

by Tim Mackinnon

Iâm not sure if this is born out by others - but Iâm finding that Pharo 7 is a bit less stable than Pharo 6 - Iâm seeing quite a few seg-faults where the vm dies and terminates - both when the image is left running for a while, but also in fresh images where I do an Iceberg load of my projects. Iâve also seen a lot of weird things like corrupted fonts and keyboard focus/cursor keys not working properly. >From memory - I saw a lot less of this in Pharo 6 when I first moved to it. Possibly my usage is a bit different (although Iâm not sure) - but in all the cases above Iâm using OSX (HighSierra - so the same Mac OS as Pharo 6) - with the 64bit vm and running full screen. One thing that seems to help (but this is an early empirical observation) - if I save my image to a new name - this seems to help. So Iâm wondering if there might be something in the build process that has changed and is causing some sort of instability? I havenât done this long enough to really comment - but from all of the above, having a Pharo.1.image seemed to stop my problems. Possibly Iâve been unlucky - but of 7 images Iâve used in the last 2 weeks - 5 of them have had issues. I did notice that half of these images were the rc1 build 1436 setup (as I hadnât noticed that the blessed 7.0 stable image has a different version number (previously, the last builds in PL Pharo 7 development - was the stable version - unless work then went forward for a Pharo 7.1. I liked to nab the dev version so that I know the build number to report it. I now see the about Pharo in the image also lists this number). Also some of my images were retrieved via zeroConf in the terminal (again, not sure if this makes a difference - but did that a lot with P6 too). This isnât a complaint per se - as we need to move the platform forward and forge new approaches. So I really mention it to try and help diagnose the issues - or possibly understand if Iâm doing something weird. Tim

Feb. 15, 2019

Re: [Pharo-users] Streams for FileReference in Pharo 7

by Sven Van Caekenberghe

Hi Jan, I like #<< too, but I think your assumption that it can print anything on a stream is generally wrong, dangerous and unreliable. IMHO, you better stick to #print: in that case. Consider the follow, that all fail: String streamContents: [ :s | s << 'hello' << 42.5 << $! ]. String streamContents: [ :s | s << 'hello' << (1@2) << $! ]. In other words: #<< works in bizar ways (check the implementors of #putOn:). I would be inclined to change ZnEncodedStream>>#<< collection ^ self nextPutAll: collection to ZnEncodedStream>>#<< collection ^ self nextPutAll: collection asString but it would technically not be the same as the original #<< for in-memory streams. Opinions ? Sven > On 15 Feb 2019, at 09:52, Jan BlizniÄenko <jan.bliznicenko(a)fit.cvut.cz> wrote: > > Hello everyone > > I am trying to use Pharo 7 for my project and I noticed that most of my > streams related code does not work anymore. Reason is that API for streams > received from writeStream of FileReference changed and I think it changed > for the worse in my case, because << does not properly handle any other > objects than strings anymore. > > In both Pharo 6 and 7 I can write > String streamContents: [ :s | s << 'hello' << 42 << $! ]. > and get 'hello42!'. > I can write in Pharo 6 but cannot in Pharo 7 > 'hello.txt' asFileReference writeStreamDo: [ :s | s << 'hello' << 42 << $! ] > In Pharo 6, I get same result in both examples (written to the file in > second case of course), but in Pharo 7, the second example results in > exception because << does not work with anything other than strings, so it > seems I have to manually convert everything to strings. > > This change to streams seems to me like a setback for 2 reasons: > 1) API amongst streams is no longer consistent in this case > 2) streams for files lost useful functionality and to make my project > compatible with Pharo 7, I have to make lots of effort to make my code > uglier and longer > > I would like to ask for the reason of this change and whether is there > anything that can be done with it. Or do I just misuse or misunderstand > anything? Thank you. > > Best regards, > Jan > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Feb. 15, 2019

Streams for FileReference in Pharo 7

by Jan BlizniÄenko

Hello everyone I am trying to use Pharo 7 for my project and I noticed that most of my streams related code does not work anymore. Reason is that API for streams received from writeStream of FileReference changed and I think it changed for the worse in my case, because << does not properly handle any other objects than strings anymore. In both Pharo 6 and 7 I can write String streamContents: [ :s | s << 'hello' << 42 << $! ]. and get 'hello42!'. I can write in Pharo 6 but cannot in Pharo 7 'hello.txt' asFileReference writeStreamDo: [ :s | s << 'hello' << 42 << $! ] In Pharo 6, I get same result in both examples (written to the file in second case of course), but in Pharo 7, the second example results in exception because << does not work with anything other than strings, so it seems I have to manually convert everything to strings. This change to streams seems to me like a setback for 2 reasons: 1) API amongst streams is no longer consistent in this case 2) streams for files lost useful functionality and to make my project compatible with Pharo 7, I have to make lots of effort to make my code uglier and longer I would like to ask for the reason of this change and whether is there anything that can be done with it. Or do I just misuse or misunderstand anything? Thank you. Best regards, Jan -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 15, 2019

Re: [Pharo-users] [ANN] P3 version 1.2

by Sven Van Caekenberghe

> On 14 Feb 2019, at 22:44, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > Thank you Sven. > > The timing is perfect. > https://blog.digitalocean.com/announcing-managed-databases-for-postgresql/ > > :) Interesting & cool; thanks for sharing. > Esteban A. Maringolo > > > El mar., 12 feb. 2019 a las 11:23, Sven Van Caekenberghe > (<sven(a)stfx.eu>) escribiÃ³: >> >> Hi, >> >> There is a new release of P3, the modern, lean and mean PostgreSQL client for Pharo. >> >> https://github.com/svenvc/P3 >> >> Version 1.2 contains the following changes: >> >> - P3PreparedStatement is now joined by a polymorphic P3FormattedStatement working client side on text strings >> - P3PreparedStatement & P3FormattedStatement now share the same double dispatch mechanism to process argument binding >> - Added convenience methods #listDatabases #listSchemas & #listTablesInSchema: to P3Client >> - Added convenience methods #firstColumnData & #firstFieldOfFirstRecord to P3Result >> - Added dynamic ENUM support via #loadEnums in P3Client >> - Add support for the 7 geometric types POINT, CIRCLE, LINE, LSEG, POLYGON & PATH with corresponding objects P3Point, P3Circle, P3Line, P3LineSegment, P3Polygon & P3Path >> - Add support for the INTERVAL type with P3Interval object >> - Added P3Client>>#serverVersion accessor >> - Add support for BIT & VARBIT types with P3FixedBitString & P3BitString objects >> - Add TIMETZ support >> - Organised P3 package with tags >> - More & better documentation & unit tests >> >> https://github.com/svenvc/P3/releases/tag/v1.2 >> >> The quality of open source software is determined by it being alive, supported and maintained. >> >> The first way to help is to simply use P3 in your projects and report back about your successes and the issues that you encounter. You can ask questions on the Pharo mailing lists. >> >> Enjoy, >> >> Sven >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> >> >> >> >> >

Feb. 14, 2019

Re: [Pharo-users] [ANN] P3 version 1.2

by Esteban Maringolo

Thank you Sven. The timing is perfect. https://blog.digitalocean.com/announcing-managed-databases-for-postgresql/ :) Esteban A. Maringolo El mar., 12 feb. 2019 a las 11:23, Sven Van Caekenberghe (<sven(a)stfx.eu>) escribiÃ³: > > Hi, > > There is a new release of P3, the modern, lean and mean PostgreSQL client for Pharo. > > https://github.com/svenvc/P3 > > Version 1.2 contains the following changes: > > - P3PreparedStatement is now joined by a polymorphic P3FormattedStatement working client side on text strings > - P3PreparedStatement & P3FormattedStatement now share the same double dispatch mechanism to process argument binding > - Added convenience methods #listDatabases #listSchemas & #listTablesInSchema: to P3Client > - Added convenience methods #firstColumnData & #firstFieldOfFirstRecord to P3Result > - Added dynamic ENUM support via #loadEnums in P3Client > - Add support for the 7 geometric types POINT, CIRCLE, LINE, LSEG, POLYGON & PATH with corresponding objects P3Point, P3Circle, P3Line, P3LineSegment, P3Polygon & P3Path > - Add support for the INTERVAL type with P3Interval object > - Added P3Client>>#serverVersion accessor > - Add support for BIT & VARBIT types with P3FixedBitString & P3BitString objects > - Add TIMETZ support > - Organised P3 package with tags > - More & better documentation & unit tests > > https://github.com/svenvc/P3/releases/tag/v1.2 > > The quality of open source software is determined by it being alive, supported and maintained. > > The first way to help is to simply use P3 in your projects and report back about your successes and the issues that you encounter. You can ask questions on the Pharo mailing lists. > > Enjoy, > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

Feb. 14, 2019

Re: [Pharo-users] Status of XML Support's move to GitHub

by Tim Mackinnon

Isnât tonel an open format? Would this not encourage other dialects to adopt it as well? The sooner the better? We know that filetree wasnât really a great idea as a format (as Windows issues show). Iâd say in this case move to it and letâs move forward. Hopefully all together. Tim Sent from my iPhone > On 14 Feb 2019, at 18:43, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> On 14 Feb 2019, at 19:02, Torsten Bergmann <astares(a)gmx.de> wrote: >> >> Hi, >> >> but Tonel allows to use the package also on Windows platform as Tonel is more compact. Otherwise we will run into long filename git >> trouble again. This would limit it's use. >> >> A filetree/cypress might make sense for other dialects - but due to the above would it be possibly to have these formats >> as a separate branch and keep the master in Tonel? > > Sure, there is a reason for Tonel, it *is* better, but in this case it might not be the best choice. > >> I know this makes it harder in maintaining - but I'm not sure the XML packages changes so often. > > No, I don't think they do. > >> @Sven: thank for taking action. Can we have a link in the README pointing also to the original STHub Repo? > > I did. > >> Maybe we should move the canonical project to the more central https://github.com/pharo-contributions like it was >> done with other repos and add Sven (and others interested) to this team. > > Once somebody tries to do a real conversion with history. > >> Thanks >> T. >> >> >>> Gesendet: Donnerstag, 14. Februar 2019 um 18:08 Uhr >>> Von: "Paul DeBruicker" <pdebruic(a)gmail.com> >>> An: pharo-users(a)lists.pharo.org >>> Betreff: Re: [Pharo-users] Status of XML Support's move to GitHub >>> >>> Hi Sven, >>> >>> Can we use filetree/cypress for this for now? IF the intention is for your >>> copy to become the canonical github one at least. Squeak and GemStone >>> don't yet have tonel and the smalltalkhub/PharoExtras repo is where code is >>> currently loaded from for those platforms. >>> >>> >>> Thanks for giving it some thought. >>> >>> Paul >>> >>> >>> >>> Sven Van Caekenberghe-2 wrote >>>> Hi again, >>>> >>>>> On 10 Jan 2019, at 16:31, Sven Van Caekenberghe < >>> >>>> sven@ >>> >>>>> wrote: >>>>> >>>>> Hi, >>>>> >>>>> What is the status of XML Support's move to GitHub ? >>>>> Many people were pro, has anything been done ? >>>>> It would be very nice. >>>>> >>>>> Sven >>>> >>>> I did https://github.com/svenvc/XML-Support-Pharo as a direct copy of the >>>> code from SmalltalkHub to GitHub, Tonel, Pharo and Travis CI. >>>> >>>> This is just the bare minimum, a proof of concept, with new, much >>>> simplified baselines. It was the last project that I depend on and I >>>> wanted it in GitHub for my own purposes. The default load of XMLParser >>>> includes XMLWriter, the tests and the GT extensions. >>>> >>>> All 5100+ tests are green. I am using Pharo 7.0.1 64-bit. Code seems to >>>> load reasonably fast. >>>> >>>> I want to stress that this is not a fork, nor the end of this conversion. >>>> >>>> I have a lot of respect for this high quality, solid code base and want >>>> this important piece of code to move forward. >>>> >>>> I hope others will help. >>>> >>>> Sven >>> >>> >>> >>> >>> >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >>> >> > >

Feb. 14, 2019

Re: [Pharo-users] Status of XML Support's move to GitHub

by Sven Van Caekenberghe

> On 14 Feb 2019, at 19:02, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > but Tonel allows to use the package also on Windows platform as Tonel is more compact. Otherwise we will run into long filename git > trouble again. This would limit it's use. > > A filetree/cypress might make sense for other dialects - but due to the above would it be possibly to have these formats > as a separate branch and keep the master in Tonel? Sure, there is a reason for Tonel, it *is* better, but in this case it might not be the best choice. > I know this makes it harder in maintaining - but I'm not sure the XML packages changes so often. No, I don't think they do. > @Sven: thank for taking action. Can we have a link in the README pointing also to the original STHub Repo? I did. > Maybe we should move the canonical project to the more central https://github.com/pharo-contributions like it was > done with other repos and add Sven (and others interested) to this team. Once somebody tries to do a real conversion with history. > Thanks > T. > > >> Gesendet: Donnerstag, 14. Februar 2019 um 18:08 Uhr >> Von: "Paul DeBruicker" <pdebruic(a)gmail.com> >> An: pharo-users(a)lists.pharo.org >> Betreff: Re: [Pharo-users] Status of XML Support's move to GitHub >> >> Hi Sven, >> >> Can we use filetree/cypress for this for now? IF the intention is for your >> copy to become the canonical github one at least. Squeak and GemStone >> don't yet have tonel and the smalltalkhub/PharoExtras repo is where code is >> currently loaded from for those platforms. >> >> >> Thanks for giving it some thought. >> >> Paul >> >> >> >> Sven Van Caekenberghe-2 wrote >>> Hi again, >>> >>>> On 10 Jan 2019, at 16:31, Sven Van Caekenberghe < >> >>> sven@ >> >>>> wrote: >>>> >>>> Hi, >>>> >>>> What is the status of XML Support's move to GitHub ? >>>> Many people were pro, has anything been done ? >>>> It would be very nice. >>>> >>>> Sven >>> >>> I did https://github.com/svenvc/XML-Support-Pharo as a direct copy of the >>> code from SmalltalkHub to GitHub, Tonel, Pharo and Travis CI. >>> >>> This is just the bare minimum, a proof of concept, with new, much >>> simplified baselines. It was the last project that I depend on and I >>> wanted it in GitHub for my own purposes. The default load of XMLParser >>> includes XMLWriter, the tests and the GT extensions. >>> >>> All 5100+ tests are green. I am using Pharo 7.0.1 64-bit. Code seems to >>> load reasonably fast. >>> >>> I want to stress that this is not a fork, nor the end of this conversion. >>> >>> I have a lot of respect for this high quality, solid code base and want >>> this important piece of code to move forward. >>> >>> I hope others will help. >>> >>> Sven >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >

Feb. 14, 2019

Re: [Pharo-users] Status of XML Support's move to GitHub

by Torsten Bergmann

Hi, but Tonel allows to use the package also on Windows platform as Tonel is more compact. Otherwise we will run into long filename git trouble again. This would limit it's use. A filetree/cypress might make sense for other dialects - but due to the above would it be possibly to have these formats as a separate branch and keep the master in Tonel? I know this makes it harder in maintaining - but I'm not sure the XML packages changes so often. @Sven: thank for taking action. Can we have a link in the README pointing also to the original STHub Repo? Maybe we should move the canonical project to the more central https://github.com/pharo-contributions like it was done with other repos and add Sven (and others interested) to this team. Thanks T. > Gesendet: Donnerstag, 14. Februar 2019 um 18:08 Uhr > Von: "Paul DeBruicker" <pdebruic(a)gmail.com> > An: pharo-users(a)lists.pharo.org > Betreff: Re: [Pharo-users] Status of XML Support's move to GitHub > > Hi Sven, > > Can we use filetree/cypress for this for now? IF the intention is for your > copy to become the canonical github one at least. Squeak and GemStone > don't yet have tonel and the smalltalkhub/PharoExtras repo is where code is > currently loaded from for those platforms. > > > Thanks for giving it some thought. > > Paul > > > > Sven Van Caekenberghe-2 wrote > > Hi again, > > > >> On 10 Jan 2019, at 16:31, Sven Van Caekenberghe < > > > sven@ > > > > wrote: > >> > >> Hi, > >> > >> What is the status of XML Support's move to GitHub ? > >> Many people were pro, has anything been done ? > >> It would be very nice. > >> > >> Sven > > > > I did https://github.com/svenvc/XML-Support-Pharo as a direct copy of the > > code from SmalltalkHub to GitHub, Tonel, Pharo and Travis CI. > > > > This is just the bare minimum, a proof of concept, with new, much > > simplified baselines. It was the last project that I depend on and I > > wanted it in GitHub for my own purposes. The default load of XMLParser > > includes XMLWriter, the tests and the GT extensions. > > > > All 5100+ tests are green. I am using Pharo 7.0.1 64-bit. Code seems to > > load reasonably fast. > > > > I want to stress that this is not a fork, nor the end of this conversion. > > > > I have a lot of respect for this high quality, solid code base and want > > this important piece of code to move forward. > > > > I hope others will help. > > > > Sven > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Feb. 14, 2019

Re: [Pharo-users] Status of XML Support's move to GitHub

by Sven Van Caekenberghe

Paul, Like I said, this is just a simple first POC for Pharo only. Of course, the real version should probably not use Tonel, and include the history. I just do not want to take this on, I have already too many public things to support. It is however my opinion that supporting multiple architectures and all kinds of older/historic variants make things exponentially more complex, and this is holding us back - I sometimes feel this in my other projects as well. But this is a general remark, not about XML Support (which has a different history). Sven > On 14 Feb 2019, at 18:08, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > > Hi Sven, > > Can we use filetree/cypress for this for now? IF the intention is for your > copy to become the canonical github one at least. Squeak and GemStone > don't yet have tonel and the smalltalkhub/PharoExtras repo is where code is > currently loaded from for those platforms. > > > Thanks for giving it some thought. > > Paul > > > > Sven Van Caekenberghe-2 wrote >> Hi again, >> >>> On 10 Jan 2019, at 16:31, Sven Van Caekenberghe < > >> sven@ > >> > wrote: >>> >>> Hi, >>> >>> What is the status of XML Support's move to GitHub ? >>> Many people were pro, has anything been done ? >>> It would be very nice. >>> >>> Sven >> >> I did https://github.com/svenvc/XML-Support-Pharo as a direct copy of the >> code from SmalltalkHub to GitHub, Tonel, Pharo and Travis CI. >> >> This is just the bare minimum, a proof of concept, with new, much >> simplified baselines. It was the last project that I depend on and I >> wanted it in GitHub for my own purposes. The default load of XMLParser >> includes XMLWriter, the tests and the GT extensions. >> >> All 5100+ tests are green. I am using Pharo 7.0.1 64-bit. Code seems to >> load reasonably fast. >> >> I want to stress that this is not a fork, nor the end of this conversion. >> >> I have a lot of respect for this high quality, solid code base and want >> this important piece of code to move forward. >> >> I hope others will help. >> >> Sven > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 14, 2019

Re: [Pharo-users] Status of XML Support's move to GitHub

by Paul DeBruicker

Hi Sven, Can we use filetree/cypress for this for now? IF the intention is for your copy to become the canonical github one at least. Squeak and GemStone don't yet have tonel and the smalltalkhub/PharoExtras repo is where code is currently loaded from for those platforms. Thanks for giving it some thought. Paul Sven Van Caekenberghe-2 wrote > Hi again, > >> On 10 Jan 2019, at 16:31, Sven Van Caekenberghe < > sven@ > > wrote: >> >> Hi, >> >> What is the status of XML Support's move to GitHub ? >> Many people were pro, has anything been done ? >> It would be very nice. >> >> Sven > > I did https://github.com/svenvc/XML-Support-Pharo as a direct copy of the > code from SmalltalkHub to GitHub, Tonel, Pharo and Travis CI. > > This is just the bare minimum, a proof of concept, with new, much > simplified baselines. It was the last project that I depend on and I > wanted it in GitHub for my own purposes. The default load of XMLParser > includes XMLWriter, the tests and the GT extensions. > > All 5100+ tests are green. I am using Pharo 7.0.1 64-bit. Code seems to > load reasonably fast. > > I want to stress that this is not a fork, nor the end of this conversion. > > I have a lot of respect for this high quality, solid code base and want > this important piece of code to move forward. > > I hope others will help. > > Sven -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 14, 2019