October 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [ANN] Cryptography moved to pharo-contributions

by Ben Coman

Sorry, I missed a >>NOT<< there... On Thu, 11 Oct 2018 at 22:00, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Ben Coman wrote > > It guess it should >>NOT<< impede someone using their account as a > staging point > > for migrating from Smalltalkhub projects to a community github repo. > > Two possible options: > 1. (maybe the cleanest and what I did for Artefact) - create a repo under > one's own account, which can then be pulled to the canonical and deleted. > Yes. That is what I meant. They repo doesn't stay under your account long enough to get caught up in Metacello references. > 2. (not tested) - create a repo with a different name (e.g. > "Artefact-Contribution") to be transferred and renamed (e.g. to just > "Artefact") under the proper organization. The question is whether one can > then create an "Artefect" under their own user. > I don't think that gains much more than my suggestion to delete the "master" branch from the repo under your account once its been adopted by its new canonical location. Its (generally) only the master branch that is referenced with Metacello. So that case and your case (2.) fail Metacello the same way, i.e. that a good thing > > #2 feels too clever. #1 is only a tiny bit more work. But certainly there > should be a decent sized group of users in Pharo-contributions or wherever > else we will be accepting these or there will be a bottleneck that will > discourage such efforts... > Possible option 3. An idea crossed my mind to soften the transition to a read-only Smalltalkhub. At the time that is done, perhaps a github organisation "Smalltalkhub" could be created and some scripts scrape all public Smalltalkhub repos under that organisation. In case two users have the same named Smalltalkhub repo, these could be combined into one github repo with a branch named for each user. Of course that itself would take some effort, but cumulatively less effort overall for the community than every individual doing it themselves, and leaving nothing behind might make it feasible to turn Smalltalkhub off altogether another year later. btw, thank you to those who provided Smalltalkhub. It filled an important role for a time. cheers -ben

Oct. 11, 2018

Re: [Pharo-users] Why is the root class of tests named TestAsserter?

by Ben Coman

On Thu, 11 Oct 2018 at 21:52, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Pharo Smalltalk Users mailing list wrote > > Still I think TestAsserter is not the most intuitive name. Asserter is > not > > even an English word if I am not mistaken. > The good (and bad) thing about English (since contributes to its complexity) is all rules it adopted from many influences, so its its quite flexible about made up words. As Sean said, TestAsserter satisfies a particular rule. I can't think of a gooder alternative. cheers -ben > It came up in a few dictionaries in a google search, but clearly not the > most common. My understanding is that [Verb]-er names are usually common > names for roles (e.g. in dependency injection), but a code smell for object > names. On the other hand (and not having the code in front of me), if it is > an object which asserts, then maybe okay? Do you have any suggestions for a > better name? >

Oct. 11, 2018

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

by Steffen MÃ¤rcker

I am using MacOS 10.13.6 and the 32bit VM: Pharo 6.0 Latest update: #60546 ... the String in about is wrong, it should be 6.1. I installed it via the launcher as "Official Distribution: Pharo 6.1 - 32Bit (stable)" I just noticed, that the sources file is missing from vms/private/6521/, too. Am .10.2018, 17:02 Uhr, schrieb Sean P. DeNigris <sean(a)clipperadams.com>: > Steffen MÃ¤rcker wrote >> I did the following: >> 1) Download and start Pharo 6.1 stable via the launcher. >> 2b) Attempt to install PP2 via the scripts from GitHub: >> Metacello new >> baseline: 'PetitParser2'; >> repository: 'github://kursjan/petitparser2'; >> load. >> Metacello new >> baseline: 'PetitParser2Gui'; >> repository: 'github://kursjan/petitparser2'; >> load. > > This way worked for me in Pharo #60546 (check in World->System->About). > What > exact Pharo version/OS are you on? 32 or 64-bit > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Oct. 11, 2018

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

by Sean P. DeNigris

Steffen MÃ¤rcker wrote > I did the following: > 1) Download and start Pharo 6.1 stable via the launcher. > 2b) Attempt to install PP2 via the scripts from GitHub: > Metacello new > baseline: 'PetitParser2'; > repository: 'github://kursjan/petitparser2'; > load. > Metacello new > baseline: 'PetitParser2Gui'; > repository: 'github://kursjan/petitparser2'; > load. This way worked for me in Pharo #60546 (check in World->System->About). What exact Pharo version/OS are you on? 32 or 64-bit ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 11, 2018

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

by Steffen MÃ¤rcker

> Can you give more details? IIRC I have PP2 loaded in several 6. I did the following: 1) Download and start Pharo 6.1 stable via the launcher. 2a) Attempt to install PetitParser2 via the CatalogBrowser: "Information There was an error while trying to install PetitParser2. Installation was cancelled." 2b) Attempt to install PP2 via the scripts from GitHub: Metacello new baseline: 'PetitParser2'; repository: 'github://kursjan/petitparser2'; load. Metacello new baseline: 'PetitParser2Gui'; repository: 'github://kursjan/petitparser2'; load. "Could not resolve: [BaselineOfPetitParser2] in [...]" Interestingly, it works in Pharo 7 dev, but there the GUI-Tools won't load because of some issues with their dependencies. I hope this helps. As I am not familiar with Pharo, I'd appreciate any hints. Best, Steffen

Oct. 11, 2018

Re: [Pharo-users] [ANN] Cryptography moved to pharo-contributions

by Sean P. DeNigris

Ben Coman wrote > It guess it should impede someone using their account as a staging point > for migrating from Smalltalkhub projects to a community github repo. Two possible options: 1. (maybe the cleanest and what I did for Artefact) - create a repo under one's own account, which can then be pulled to the canonical and deleted. 2. (not tested) - create a repo with a different name (e.g. "Artefact-Contribution") to be transferred and renamed (e.g. to just "Artefact") under the proper organization. The question is whether one can then create an "Artefect" under their own user. #2 feels too clever. #1 is only a tiny bit more work. But certainly there should be a decent sized group of users in Pharo-contributions or wherever else we will be accepting these or there will be a bottleneck that will discourage such efforts... ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 11, 2018

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

by Sean P. DeNigris

Steffen MÃ¤rcker wrote > 1. PP2 does not load into Pharo 6.1 stable. Can you give more details? IIRC I have PP2 loaded in several 6.1 images. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 11, 2018

Re: [Pharo-users] GTInspector and code completion

by Marcus Denker

> On 11 Oct 2018, at 15:40, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 11 Oct 2018, at 15:02, Hilaire <hilaire(a)drgeo.eu <mailto:hilaire@drgeo.eu>> wrote: >> >> Hi, >> >> In my working P7, when inspecting a Text object I don't have completion >> in the code evaluator. >> >> For example self allBolt does not auto-complete. >> >> On some other objects it works. >> >> The EyesInspector code evaluator provides the completion, but it is not >> as nice as GTInspector is. >> >> Am I missing something ? > > No, there is an issue tracker entry open since 2016: > > https://pharo.fogbugz.com/f/cases/18340/GTInspector-no-class-name-completio… <https://pharo.fogbugz.com/f/cases/18340/GTInspector-no-class-name-completio…> > Hmmâ¦ this is about class name completionâ¦ the problem of doing the right thing for âselfâ might be different. I will add to the list of things to look at in the context of code completion. Marcus

Oct. 11, 2018

Re: [Pharo-users] Why is the root class of tests named TestAsserter?

by Sean P. DeNigris

Pharo Smalltalk Users mailing list wrote > Still I think TestAsserter is not the most intuitive name. Asserter is not > even an English word if I am not mistaken. It came up in a few dictionaries in a google search, but clearly not the most common. My understanding is that [Verb]-er names are usually common names for roles (e.g. in dependency injection), but a code smell for object names. On the other hand (and not having the code in front of me), if it is an object which asserts, then maybe okay? Do you have any suggestions for a better name? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 11, 2018

Re: [Pharo-users] GTInspector and code completion

by Marcus Denker

> On 11 Oct 2018, at 15:02, Hilaire <hilaire(a)drgeo.eu> wrote: > > Hi, > > In my working P7, when inspecting a Text object I don't have completion > in the code evaluator. > > For example self allBolt does not auto-complete. > > On some other objects it works. > > The EyesInspector code evaluator provides the completion, but it is not > as nice as GTInspector is. > > Am I missing something ? No, there is an issue tracker entry open since 2016: https://pharo.fogbugz.com/f/cases/18340/GTInspector-no-class-name-completio… <https://pharo.fogbugz.com/f/cases/18340/GTInspector-no-class-name-completio…> Marcus

Oct. 11, 2018