- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Request-info bot on github

by Thomas Dupriez

Ok. I wrote a new comment and another bot removed the label. :) Thomas On 26/03/2019 17:11, Marcus Denker wrote: > I think you should not edit but put a new comment. The bot seems to only get to see new comments, not edit actions of existing comments. > >> On 26 Mar 2019, at 17:06, Thomas Dupriez <tdupriez(a)ens-paris-saclay.fr> wrote: >> >> Hello, just asking if this behaviour is normal: >> >> - I created an issue with an empty body. >> - The request-info bot posted a message to it, saying it was empty and asking for more details. It also added the "more-information-needed" label. >> - I updated the body of the issue >> - Now the issue no longer has an empty body, but it still has the message from the bot and the label. >> >> The issue in question: https://github.com/pharo-project/pharo/issues/3025 >> >> Thomas >> >> >

March 26, 2019

Re: [Pharo-dev] Request-info bot on github

by Marcus Denker

I think you should not edit but put a new comment. The bot seems to only get to see new comments, not edit actions of existing comments. > On 26 Mar 2019, at 17:06, Thomas Dupriez <tdupriez(a)ens-paris-saclay.fr> wrote: > > Hello, just asking if this behaviour is normal: > > - I created an issue with an empty body. > - The request-info bot posted a message to it, saying it was empty and asking for more details. It also added the "more-information-needed" label. > - I updated the body of the issue > - Now the issue no longer has an empty body, but it still has the message from the bot and the label. > > The issue in question: https://github.com/pharo-project/pharo/issues/3025 > > Thomas > >

March 26, 2019

Request-info bot on github

by Thomas Dupriez

Hello, just asking if this behaviour is normal: - I created an issue with an empty body. - The request-info bot posted a message to it, saying it was empty and asking for more details. It also added the "more-information-needed" label. - I updated the body of the issue - Now the issue no longer has an empty body, but it still has the message from the bot and the label. The issue in question: https://github.com/pharo-project/pharo/issues/3025 Thomas

March 26, 2019

[Pharo 8.0] Build #185: 3011-cleanup-delete-unsent-private-method-from-Slots-classes

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #185 was: SUCCESS. The Pull Request #3012 was integrated: "3011-cleanup-delete-unsent-private-method-from-Slots-classes" Pull request url: https://github.com/pharo-project/pharo/pull/3012 Issue Url: https://github.com/pharo-project/pharo/issues/3011 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 26, 2019

Re: [Pharo-dev] Special Issue on Smalltalk Technologies

by CÃ©drick BÃ©ler

Tu penses que je peux tenter de publier un papier un peu sur les principes du SIS ? Je pense je pourrais tenter aussi un truc avec mon Ã©tudiants et Jannik sur lâaspect CPS. @++ Cedrick Ps je revois pour simplifier lâapproche et commencer Ã faire Ã©merger des scnenario EnvoyÃ© de mon iPhone > Le 26 mars 2019 Ã 11:37, ducasse <stepharo(a)netcourrier.com> a Ã©crit : > > Special Issue on Smalltalk Technologies > https://www.journals.elsevier.com/science-of-computer-programming > Guest Editors: > LoÃ¯c Lagadec (Coordinator) > Ensta Bretagne, Lab-STICC > Anne Etien > UniversitÃ© de Lille, CRIStAL, UMR9189 > Jannik Laval > UniversitÃ© LumiÃ¨re Lyon 2, DISP, EA 4570 > > Theme > Smalltalk is an exciting objectâoriented language in which even primitive values are uniformly handled as normal objects, described by classes that one can browse, inspect and extend. Smalltalk was born during the seventies, still the ideas behind the currently available implementations are often at the edge of innovation. > Smalltalk benefits from being a highly expressive language in which complex and powerful systems can emerge from the composition of simple building blocks. Thanks to its dynamic nature, fast prototyping and agile software development are made possible. Smalltalk is not only a simple and pure dynamic object-oriented language, but is also a programmable system with processes, its own user interface and a complete Interactive Development Environment (IDE). > Smalltalk is a reflexive system, with all its elements being implemented in Smalltalk, which benefits from powerful metaâprogramming facilities. This means that elements can be extended, customized or adapted according to particular contexts, that the Smalltalk IDE itself can be used to implement, validate and debug the Smalltalk system extensions, and that a program is able to query and to change its own structure and behaviour. > In this context, the research topics that relate to Smalltalk technologies are large, and need to receive more attention and research effort, considering that Smalltalk has established itself as a test bed for software engineering theories and tools. > > > > TOPICS include: > ï§ Aspect-oriented programming, > ï§ Design patterns, > ï§ Experience reports, > ï§ Frameworks, > ï§ Implementation, new dialects or languages implemented in Smalltalk, > ï§ Interaction with other languages, > ï§ Meta-programming and Meta-modelling, > ï§ Tools > > > Important Dates: > â¢ Apr. 30, 2019 Full paper submission due > â¢ Aug.31, 2019 Paper acceptance decision > â¢ Sep.15, 2019 Camera-ready paper due >

March 26, 2019

Special Issue on Smalltalk Technologies

by ducasse

Special Issue on Smalltalk Technologies https://www.journals.elsevier.com/science-of-computer-programming <https://www.journals.elsevier.com/science-of-computer-programming> Guest Editors: LoÃ¯c Lagadec (Coordinator) Ensta Bretagne, Lab-STICC Anne Etien UniversitÃ© de Lille, CRIStAL, UMR9189 Jannik Laval UniversitÃ© LumiÃ¨re Lyon 2, DISP, EA 4570 Theme Smalltalk is an exciting objectâoriented language in which even primitive values are uniformly handled as normal objects, described by classes that one can browse, inspect and extend. Smalltalk was born during the seventies, still the ideas behind the currently available implementations are often at the edge of innovation. Smalltalk benefits from being a highly expressive language in which complex and powerful systems can emerge from the composition of simple building blocks. Thanks to its dynamic nature, fast prototyping and agile software development are made possible. Smalltalk is not only a simple and pure dynamic object-oriented language, but is also a programmable system with processes, its own user interface and a complete Interactive Development Environment (IDE). Smalltalk is a reflexive system, with all its elements being implemented in Smalltalk, which benefits from powerful metaâprogramming facilities. This means that elements can be extended, customized or adapted according to particular contexts, that the Smalltalk IDE itself can be used to implement, validate and debug the Smalltalk system extensions, and that a program is able to query and to change its own structure and behaviour. In this context, the research topics that relate to Smalltalk technologies are large, and need to receive more attention and research effort, considering that Smalltalk has established itself as a test bed for software engineering theories and tools. TOPICS include: ï§ Aspect-oriented programming, ï§ Design patterns, ï§ Experience reports, ï§ Frameworks, ï§ Implementation, new dialects or languages implemented in Smalltalk, ï§ Interaction with other languages, ï§ Meta-programming and Meta-modelling, ï§ Tools Important Dates: â¢ Apr. 30, 2019 Full paper submission due â¢ Aug.31, 2019 Paper acceptance decision â¢ Sep.15, 2019 Camera-ready paper due

March 26, 2019

PR2789, Rubric integration revert

by Stephan Eggermont

Unless someone is working on fixing it today, I want this PR reverted. Issues 2865, 2963, 2964, 2980, 3013 Stephan

March 26, 2019

Re: [Pharo-dev] How to manage your code with Iceberg

by ducasse

thanks Sean I did not see that stefan did a pass too. So I will check the diff. Stef > On 25 Mar 2019, at 16:41, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > StÃ©phane Ducasse wrote >> https://github.com/SquareBracketAssociates/Booklet-ManagingCode > > I submitted a comprehensive grammar pass. I just want to point out that this > was only possible due to the incredible amount of work people have done to > move us into the git/GH world. In the past, my experience was that > submitting a fix often took at least as long as doing the actual fixing (and > significantly longer for small fixes)! > > Past: > 1. save the packages individually > 2. Publish the code > a. if the repo allowed writing, put them there > b. if read-only, come up with some alternative, like creating your own > monolithic staging area repo, or other DIY solution > c. if the repo was abandoned, you'd probably be better off giving up and > finding a new profession, because you may end up manually copying the repo > with no API way to establish the link > 3. create a mailing list thread for discussion > 4. Wait and hope > > Present: > 1. Save all project changes in one step > 2. Click "Create PR" > Bonus #1: Go have a beer > Bonus #2: you can keep working with your new changes by loading from your > fork until the canonical accepts the PR > > So: /thank you/ to everyone involved in git/GH/Iceberg support!!! > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

March 25, 2019

Re: [Pharo-dev] How to manage your code with Iceberg

by Sean P. DeNigris

StÃ©phane Ducasse wrote > https://github.com/SquareBracketAssociates/Booklet-ManagingCode I submitted a comprehensive grammar pass. I just want to point out that this was only possible due to the incredible amount of work people have done to move us into the git/GH world. In the past, my experience was that submitting a fix often took at least as long as doing the actual fixing (and significantly longer for small fixes)! Past: 1. save the packages individually 2. Publish the code a. if the repo allowed writing, put them there b. if read-only, come up with some alternative, like creating your own monolithic staging area repo, or other DIY solution c. if the repo was abandoned, you'd probably be better off giving up and finding a new profession, because you may end up manually copying the repo with no API way to establish the link 3. create a mailing list thread for discussion 4. Wait and hope Present: 1. Save all project changes in one step 2. Click "Create PR" Bonus #1: Go have a beer Bonus #2: you can keep working with your new changes by loading from your fork until the canonical accepts the PR So: /thank you/ to everyone involved in git/GH/Iceberg support!!! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

March 25, 2019

Re: [Pharo-dev] [ANN] Pharo Days 2019 is online!

by Esteban Lorenzano

Hi, Currently we have 57 registrations. Letâs make it 60! Or 70! (Round numbers are better :P) Esteban > On 25 Mar 2019, at 15:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Great, looking forward to meeting everyone. > > Esteban, maybe it is also worth mentioning the number of registrations so far ... > >> On 25 Mar 2019, at 14:56, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> Hi, >> >> We have finished the schedule for upcoming Pharo Days 2019, here a link for the google calendar: >> >> https://calendar.google.com/calendar?cid=MDIxdnExNjZpb2VqaWhyN25zYXQwcGpxaW… >> >> >> <Pharo Days 2019_021vq166ioejihr7nsat0pjqic(a)group.calendar.google.com.ics> >> >> Do not forget to register! >> >> Esteban >

March 25, 2019