June 2020 - Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #341: 6495-Better-class-API
by ci-pharo-ci-jenkins2＠inria.fr June 7, 2020

June 7, 2020

There is a new Pharo build available! The status of the build #341 was: FAILURE. The Pull Request #6502 was integrated: "6495-Better-class-API" Pull request url: https://github.com/pharo-project/pharo/pull/6502 Issue Url: https://github.com/pharo-project/pharo/issues/6495 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Discoverability
by Sean P. DeNigris June 6, 2020

June 6, 2020

I had a "simple" goal: to change Calypso's class pane to a tree. After an hour or two, I didn't feel any closer! I'm wondering if it's my process or something else. A few questions: 1. Is there a heuristic for finding relevant documentation? We have lots of docs, but there seem to be a lot of separate locations for it. I think I searched on the Nabble ML mirror for "Calypso" posts on either Pharo list. After digging around, I found a discussion where Steph was working on a [] booklet, which I read and was helpful for understanding the model but didn't directly address my issue (not that it should, this is pretty low-level hacking!). Then I tackled the class comments, which are VERY thorough, but it's hard (at least for me) to piece together the overall design from the individual parts. 2. How do we make sophisticated designs discoverable? I remember one of my Aha! moments when I discovered Smalltalk was using Morphic halos on a menu item and easily finding the code it used underneath. Things like that do not generally seem possible anymore in my experience. I thought to myself, packages are already in a tree, let me dig there! I got a bit worried when I saw what seemed to be a mini-DSL for tree making instead of simple message sends: ClyFullBrowser >> #newPackageView ... treeStructure: { ClyProjectChildItem -> #prepareProjectItemsQueryFrom:in:. RPackage -> #prepareClassGroupQueryFrom:in: }; But I pressed on and tried to duplicate that logic: ClyFullBrowser >> #newClassView ... ^ self newNavigationView treeStructure: { Class -> #prepareProjectItemsQueryFrom:in: } ... And... nothing. When #prepareClassItemsQueryFrom:in: didn't exist, I got no debugger. When I created it, placing a halt in it never got triggered. Besides my immediate experiment of making the class pane a tree, my more fundamental questions are: 1. What is the best heuristic to explore the system? This would be great to put somewhere publicly. Especially, but as we can see from this post not exclusively, for new users. 2. Do we value discoverability? 3. If so, are we designing our system with this value in mind? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 5

json-server / db.json (lowdb) / faker.js in Pharo/Zinc ?
by CÃ©drick BÃ©ler June 6, 2020

June 6, 2020

Hi Sven and all, Disclaimer: just another rather not important query (mainly for fun so donât hesitate to tell me to use the node packages instead ;-) ) To show API to students, I sometimes use https://jsonplaceholder.typicode.com. Itâs nice to play with client requests. I wonder if this would be interesting to have such tools in Pharo/Zn. Maybe it exists already somehow (for Teapot eventually) ? https://medium.com/codingthesmartway-com-blog/create-a-rest-api-with-json-s… >From their GitHub, I discovered json-server + lowdb (based on lowdash) => all nodes packages. https://github.com/typicode. It uses a db file db.json and I like such simple Â« databases Â». I know they're not real db. https://github.com/typicode/lowdb To me, it could nearly be to me an elegant personal db even if I think this is mostly used to test APIâs. Indeed, Itâs often used in conjunction with node package faker (https://github.com/marak/Faker.js/ (https://github.com/marak/Faker.js/) I would like to use that to generate static websites from Ecstatic. The placeholder default website has limitations. For instance, the following request creates a new post (but then you cannot see the result if you query for posts just after) I wanted to go past the limitation of the placeholder site (the db.json cannot be written). I can of course use the node package but you know :) Might be not so straight to port though. So there are probably three open questions in this post: 1) lowdb (I know this is not a database but itâs handy and Iâd like such usage in static website generation in conjunction with Ecstatic). Any already existing experiments maybe ? I donât think Voyage can do that. 2) the API json-server based on routes (maybe a job for Teapot) ? 3) the faker package as a fun exercice. What others think ? My priority would go for having some kind of lowdb (and Iâm pretty sure there are experiments around that - It reminds me a bit sandstonedb from Ramon http://onsmalltalk.com/sandstonedb-simple-activerecord-style-persistence-in…. Cheers, CÃ©drick

2 2

About strange email related to smalltalkhub read-only on squeak-dev
by StÃ©phane Ducasse June 6, 2020

June 6, 2020

Hi all This is the week-end and we worked super well yesterday during the sprint. Lot of good enhancements - Thanks a lot to all the participants. I not really happy to be forced to do it on a sunny saturday but Iâm doing it to clarify points. Esteban sent me this text that was posted on Squeak-Dev (I personally do not read squeak related forums because I have not the time and my focus is Pharo, its consortium, my team, my research and my family). We have to react because - We do not really at ***all** understand this email - We did not kicked anybody from our mailing-list from ages - so ron is lying. In the past we even had discussion with ron - so we do not really understand. May be we got problem to log on our mailing-lists. We have no idea because we are working and not looking at such things. - When we migrated smalltalkhub to readonly we payed attention to make sure that private projects stay private. We did not migrated smalltalkhub for fun. We MUST do it or it will be done by our infrastructure! - Now the cryptography packages are MIT and they are public anyway. So again we do not understand anything. We do not get why Ron contacted us because we announced the migration publicly way in advance and we will keep the Smalltalkhub frozen repo for at least next 5 years. I feel really sorry to hear such kind of email because we do not want to fight with anybody. Our goal is to make sure that people can work with Pharo and expand their business and knowledge. We are working hard to make sure that people can invent their future with Pharo and people that know us personally know that we are not lying. S > Hi all, > > I've tried to work with the Pharo group but they keep kicking me out of their mailing list. I've already mentioned this a number of times to the Pharo group but nobody seems to care. > > BOLD BOLD BOLD PLEASE TAKE THIS SERIOUSLY BOLD BOLD BOLD > > I am not a lawyer but we used very good lawyers to make the squeaksource repository a safe place to do cryptography work. If you are working on cryptography DO NOT POST your code anywhere except squeaksource. Especially if you are in the USA. The ONLY repository that is approved to host our cryptography code in the USA and therefore not subject to criminal violations is squeaksource. It is a CRIME in the USA to move code and make it available on the internet for everyone to download! It must be hosted on squeaksoruce.com or another location that is also properly registered. > > IF YOU COPIED CRYPTOGRAPHY CODE TO ANOTHER REPOSITORY THAT IS NOT REGISTERED I would recommend you delete it immediately. > > END BOLD! > > Please feel free to post this to the Pharo mailing list because they apparently do not want to hear from me! > > All the best, > > Ron Teitelbaum -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

6 8

[Pharo 9.0] Build #340: pushOuterVectors-use-tempVectorVarNames
by ci-pharo-ci-jenkins2＠inria.fr June 5, 2020

June 5, 2020

There is a new Pharo build available! The status of the build #340 was: SUCCESS. The Pull Request #6478 was integrated: "pushOuterVectors-use-tempVectorVarNames" Pull request url: https://github.com/pharo-project/pharo/pull/6478 Issue Url: https://github.com/pharo-project/pharo/issues/pushOuterVectors Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1140: 6418-Backport-5643-into-Pharo8
by ci-pharo-ci-jenkins2＠inria.fr June 5, 2020

June 5, 2020

There is a new Pharo build available! The status of the build #1140 was: SUCCESS. The Pull Request #6429 was integrated: "6418-Backport-5643-into-Pharo8" Pull request url: https://github.com/pharo-project/pharo/pull/6429 Issue Url: https://github.com/pharo-project/pharo/issues/6418 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #339: Created a simple and a complex test for the changes file flushing issue
by ci-pharo-ci-jenkins2＠inria.fr June 5, 2020

June 5, 2020

There is a new Pharo build available! The status of the build #339 was: FAILURE. The Pull Request #6492 was integrated: "Created a simple and a complex test for the changes file flushing issue" Pull request url: https://github.com/pharo-project/pharo/pull/6492 Issue Url: https://github.com/pharo-project/pharo/issues/6491 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #338: 6049-It-should-not-be-possible-to-use-super-as-something-else-than-the-receiver-of-a-message
by ci-pharo-ci-jenkins2＠inria.fr June 5, 2020

June 5, 2020

There is a new Pharo build available! The status of the build #338 was: SUCCESS. The Pull Request #6482 was integrated: "6049-It-should-not-be-possible-to-use-super-as-something-else-than-the-receiver-of-a-message" Pull request url: https://github.com/pharo-project/pharo/pull/6482 Issue Url: https://github.com/pharo-project/pharo/issues/6049 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #337: emitStore-do-not-use-Object-new
by ci-pharo-ci-jenkins2＠inria.fr June 5, 2020

June 5, 2020

There is a new Pharo build available! The status of the build #337 was: FAILURE. The Pull Request #6477 was integrated: "emitStore-do-not-use-Object-new" Pull request url: https://github.com/pharo-project/pharo/pull/6477 Issue Url: https://github.com/pharo-project/pharo/issues/emitStore Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

June 5, 2020

Hi sven Are the dictionaries for the query part conserving the order? Because this would be really nice. S. -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

2 2