June 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Distribution of test method name length

by Jerry Kott

Interestingâ¦ I am curious about the purpose of this analysis (other than the âinteresting-nessâ of it). Sure, some names read like sentences, but that beats the âstrcpy()â, doesnât it? I love that in Smalltalk / Pharo, I donât have to remember cryptic function names and can make the code optimally verbose (if there is such a thing) to express intent. If that means a method is rather long, so be it. Jerry Kott This message has been digitally signed. PGP Fingerprint: A9181736DD2F1B6CC7CF9E51AC8514F48C0979A5 > On 21-06-2019, at 2:35 AM, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Fri, 21 Jun 2019 at 12:43, K K Subbu <kksubbu.ml(a)gmail.com <mailto:kksubbu.ml@gmail.com>> wrote: > Nice graph, Ben! The larger test names (selector size > 100) look more > like sentences than names ;-). > > On 21/06/19 6:50 AM, Ben Coman wrote: > > classes := Object allSubclasses select: [ :cc | cc isKindOf: > > TestCase class ]. > > methods := c flatCollect: [ :c | c allMethods ]. > > Ahh, yes. Blame evolution of the Playground code between when I used it and when I copied it here. > > > Did you mean "classes" flatCollect: here? > > > tests := methods select: [ :m | m selector beginsWith: 'test' ]. > > lengths := tests collect: [ :m | m selector size ]. > > select:thenCollect: can also be used here. > > yes. but I was checking each stage as it grew incrementally. > > > > lengths asBag keysAndValuesDo: [ :len :count | Transcript crShow: > > len; show: ','; show: count ] > > I find the in: selector very handy for quick commands without having to > use undefined temps. e.g. > ```` > (Object allSubclasses select: [ :cc | cc isKindOf: TestCase class ]) in: > [ :classes | > (classes flatCollect: [ :c | c allMethods ]) in: [ :methods | > (methods select: [ :m | m selector beginsWith: 'test' ] thenCollect: > [ :m | m selector size ]) in: [:lengths | > lengths asBag keysAndValuesDo: [ :len :count | Transcript crShow: > len; show: ','; show: count ]]]] > ```` > > cool > > cheers -ben

June 23, 2019

Re: [Pharo-users] Question: anyone using NOCompletion setting?

by Sean P. DeNigris

Marcus Denker-4 wrote > Removing the Ocompletion (for a while) would make it much easierâ¦ I can live without it for a while, especially if we can plug it back in at the end! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 21, 2019

Re: [Pharo-users] Distribution of test method name length

by Ben Coman

On Fri, 21 Jun 2019 at 12:43, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > Nice graph, Ben! The larger test names (selector size > 100) look more > like sentences than names ;-). > > On 21/06/19 6:50 AM, Ben Coman wrote: > > classes := Object allSubclasses select: [ :cc | cc isKindOf: > > TestCase class ]. > > methods := c flatCollect: [ :c | c allMethods ]. > Ahh, yes. Blame evolution of the Playground code between when I used it and when I copied it here. > Did you mean "classes" flatCollect: here? > > > tests := methods select: [ :m | m selector beginsWith: 'test' ]. > > lengths := tests collect: [ :m | m selector size ]. > > select:thenCollect: can also be used here. > yes. but I was checking each stage as it grew incrementally. > > > lengths asBag keysAndValuesDo: [ :len :count | Transcript crShow: > > len; show: ','; show: count ] > > I find the in: selector very handy for quick commands without having to > use undefined temps. e.g. > ```` > (Object allSubclasses select: [ :cc | cc isKindOf: TestCase class ]) in: > [ :classes | > (classes flatCollect: [ :c | c allMethods ]) in: [ > :methods | > (methods select: [ :m | m selector beginsWith: > 'test' ] thenCollect: > [ :m | m selector size ]) in: [:lengths | > lengths asBag keysAndValuesDo: [ :len > :count | Transcript crShow: > len; show: ','; show: count ]]]] > ```` > cool cheers -ben

June 21, 2019

Re: [Pharo-users] Distribution of test method name length

by K K Subbu

Nice graph, Ben! The larger test names (selector size > 100) look more like sentences than names ;-). On 21/06/19 6:50 AM, Ben Coman wrote: > Â Â classes := Object allSubclasses select: [ :cc | cc isKindOf: > TestCase class ]. > Â Â methods := c flatCollect: [ :c | c allMethods Â ]. Did you mean classes flatCollect: here? > Â Â tests := methods select: [ :m | m selector beginsWith: 'test' ]. > Â Â lengths := tests collect: [ :m | m selector size ]. select:thenCollect: can also be used here. > Â Â lengths asBag keysAndValuesDo: [ :len :count | Transcript crShow: > len; show: ','; show: count Â ] I find the in: selector very handy for quick commands without having to use undefined temps. e.g. ```` (Object allSubclasses select: [ :cc | cc isKindOf: TestCase class ]) in: [ :classes | (classes flatCollect: [ :c | c allMethods ]) in: [ :methods | (methods select: [ :m | m selector beginsWith: 'test' ] thenCollect: [ :m | m selector size ]) in: [:lengths | lengths asBag keysAndValuesDo: [ :len :count | Transcript crShow: len; show: ','; show: count ]]]] ```` Regards .. Subbu

June 21, 2019

Distribution of test method name length

by Ben Coman

Working on the Exercism project to shorten generated test method names, for comparison I reviewed the length of test method names in Pharo 7. So just for curiousity value, here is that graph (done in Excel)... [image: image.png] Data generated by... classes := Object allSubclasses select: [ :cc | cc isKindOf: TestCase class ]. methods := c flatCollect: [ :c | c allMethods ]. tests := methods select: [ :m | m selector beginsWith: 'test' ]. lengths := tests collect: [ :m | m selector size ]. lengths asBag keysAndValuesDo: [ :len :count | Transcript crShow: len; show: ','; show: count ] cheers -ben

June 21, 2019

Re: [Pharo-users] Information on Spec development

by Alexandre Bergel

Thanks for sharing this. You guys are doing an amazing job. I do not mind having a couple of warning times to time. Cheers, Alexandre > On Jun 20, 2019, at 11:29 AM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Hello everyone! > > This is an important update about the development of Spec. > > As you might have heard, we are working on Spec to release a new > version in Pharo 8. One goal is to unify all Pharo interfaces behind > one GUI framework and a second goal is to allow multiple back-ends > (Morphic but also GTK, Bloc, ...). To reach those goals we have been > updating the current version of Spec. We see now, however, that > updating Spec directly creates troubles with migration. For example, > we currently have a lot of deprecation warnings in Iceberg, because we > can't update it without breaking Pharo 7 compatibility. > > After some discussions between the engineers working on Spec, here is > our plan to improve the situation: We will copy all classes of Spec > and rename them with the "Sp" prefix. (We will also ensure that every > class of Spec started with the same prefix for consistency). For > extensions methods, we will rename them to have a version different > from Spec 1 (The spec from Pharo 7). Once done we will integrate this > new version in Pharo 8. From there we will wait some weeks to let > users who started to use the updated Spec change their projects to use > this new Spec2. Finally, we will revert all changes that happened on > Spec 1 and deprecate the packages. We hope this will make things > easier for everyone. > > Have a nice day! > > -- > Cyril Ferlicot > https://ferlicot.fr >

June 20, 2019

Information on Spec development

by Cyril Ferlicot

Hello everyone! This is an important update about the development of Spec. As you might have heard, we are working on Spec to release a new version in Pharo 8. One goal is to unify all Pharo interfaces behind one GUI framework and a second goal is to allow multiple back-ends (Morphic but also GTK, Bloc, ...). To reach those goals we have been updating the current version of Spec. We see now, however, that updating Spec directly creates troubles with migration. For example, we currently have a lot of deprecation warnings in Iceberg, because we can't update it without breaking Pharo 7 compatibility. After some discussions between the engineers working on Spec, here is our plan to improve the situation: We will copy all classes of Spec and rename them with the "Sp" prefix. (We will also ensure that every class of Spec started with the same prefix for consistency). For extensions methods, we will rename them to have a version different from Spec 1 (The spec from Pharo 7). Once done we will integrate this new version in Pharo 8. From there we will wait some weeks to let users who started to use the updated Spec change their projects to use this new Spec2. Finally, we will revert all changes that happened on Spec 1 and deprecate the packages. We hope this will make things easier for everyone. Have a nice day! -- Cyril Ferlicot https://ferlicot.fr

June 20, 2019

Re: [Pharo-users] Question: anyone using NOCompletion setting?

by Alexandre Bergel

Marcus, this is an excellent idea! Alexandre > On Jun 19, 2019, at 4:15 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 18 Jun 2019, at 19:34, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> I use it sometimes. IIRC there was a paper that it was objectively better at >> finding the "right" thing. Are you thinking of removing it? >> >> > > I would like to re-implement sorting of results in a more pluggable wayâ¦ so that e.g. > people can add more sorting ideas. > > But doing that in one step seems hardâ¦ it would be much easier if we could simplify the system > first. > > Removing the Ocompletion (for a while) would make it much easierâ¦ > > Marcus > >

June 20, 2019

seaside hosting

by Jeff Gray

Are there options for hosting seaside apps? I had a look round but didn't see much. I could run it from home I suppose. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 20, 2019

sqlite garage

by Jeff Gray

anyone using Garage for accessing SQLite? I am using Garage for MySQL in Pharo 7 on windows and it all works seamlessly but I don't know what connection string to use to connect to a database file that I have in my pharo directory. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 20, 2019