- Pharo-dev - lists.pharo.org

Issue Tracker: enabled Projects (Boards)

by Marcus Denker

Hi, We enabled the GitHub âProjectsâ feature for the pharo repo: https://github.com/pharo-project/pharo/projects The idea is that one can add as many âKanbanâ style boards as one wants. issues and pull requests can be added, as well as simple cards that are not yet issues. This is quite nice as an issue tracker gets very confusing and overwhelming as soon as there are >500 issues. With these boards, we can create âviewsâ on this sea of issues. I created for now: -> some board related to specific parts of the system (e.g. Traits or Reflectivity) example: https://github.com/pharo-project/pharo/projects/11 -> "Pharo7 Backportingâ https://github.com/pharo-project/pharo/projects/12 -> "Simple Issues for Beginnersâ https://github.com/pharo-project/pharo/projects/14 Here the feature to be able to put things that are not yet issue tracker entries seems very useful I think this can be quite niceâ¦ we should add more Projects as soon as we find that they make sense and should move issues there. Marcus

March 18, 2019

Esteban's ChangeLog week of 11 March 2019

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 11 March 2019 to 17 March 2019. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=11/3/2019&to=17/3/2019 ChangeLog ========= 14 March 2019: -------------- * I've been working on context menus for Spec 2. This seems like an easy task... until you see how broken it was in the previous version. In fact, in older Spec menus were inexistent. Or better: the abstraction for menus were inexistent, and instead it was just a simple exposition (at Spec level) of the Morphic menu infrastructure (which itself is not very friendly). So... I needed to reimplement everything. ... and a way to test it :( Now, I want to consider the Menu interface more in detail, since today is not very clear. Look how a Menu Bar needs to be made: ---- MenuBarPresenter new addGroup: [ :group | group addItem: [ :item | item name: 'Something 1'; action: [ "doSomething"] ]; addMenu: [ :item | item name: 'Something 2'; action: [ "doSomething"] ] ]; yourself ---- which doesn't seems to be the best approach. (Anyway, I'm not changing that just now... but I'm reflecting on it, certainly) 13 March 2019: -------------- * I made a pause of my Spec 2 current work to make a fix that was pending since some time now and it was needed to easy the migration of some projects (and its usage in windows): This [PR](https://github.com/pharo-vcs/iceberg/pull/1213) will fix [tonel issue 74](https://github.com/pharo-vcs/tonel/issues/74) cheers! Esteban

March 18, 2019

Re: [Pharo-dev] OSProcess for Pharo 7

by Ben Coman

On Mon, 18 Mar 2019 at 10:20, David T. Lewis <lewis(a)mail.msen.com> wrote: > Hi Mariano, > > On Sun, Mar 17, 2019 at 08:29:59PM -0300, Mariano Martinez Peck wrote: > > > > > > ducasse wrote > > > > this is not because we do not care of Pharo that we will fix it > > > > immediately. > > > > > > Yes of course, just want to keep it on the radar (and maybe Mariano > will > > > read he he) > > > > > > > > I always do :) > > Me too :-) > > > > But honestly, I don't have enough time to carry on that myself. As you > > could see with latest Guillermo pass, I reviewed every PR and tried to > give > > my advice and support as much as possible. > > I saw Sean's earlier email (see below) which reminded me of your ideas > about > having a child process listener that could provide child exit notifications > to both OSSubprocess and OSProcess. What about this being even more generic, so child native process/threads can be viewed from the Image similar to Process Browser? I'm not entirely sure of the use case, just wild speculation something like that might be useful when Threaded-FFI arrives. cheers -ben

March 18, 2019

Re: [Pharo-dev] OSProcess for Pharo 7

by David T. Lewis

Hi Mariano, On Sun, Mar 17, 2019 at 08:29:59PM -0300, Mariano Martinez Peck wrote: > > > > ducasse wrote > > > this is not because we do not care of Pharo that we will fix it > > > immediately. > > > > Yes of course, just want to keep it on the radar (and maybe Mariano will > > read he he) > > > > > I always do :) Me too :-) > But honestly, I don't have enough time to carry on that myself. As you > could see with latest Guillermo pass, I reviewed every PR and tried to give > my advice and support as much as possible. I saw Sean's earlier email (see below) which reminded me of your ideas about having a child process listener that could provide child exit notifications to both OSSubprocess and OSProcess. This seems to me to be the right thing to do, but it would take some work by somebody (not by me, but it could be done). Meanwhile, prompted by Sean's <bump>, I think maybe I see another way that we could handle the problem, at least in the near term. On Fri, Mar 15, 2019 at 01:42:26PM -0500, Sean P. DeNigris wrote: > Max Leske wrote > >> I was talking about OSSubProcess > > Well, I'm not working with that at the moment ;) > > [OT] Just want to bump the problem that OSProcess and OSSubProcess can't > currently be used in the same image. This is an important problem because > users can't control which library dependencies use. Mariano hinted at a > solution. It didn't seem like a ton of work, but it's beyond my > understanding. > I think I see another way that this can be handled for an image that contains both OSSubprocess and OSProcess. I loaded both into a Pharo 7 image, then added this: OSSVMProcess>>update: aParameter "If subscribed to events from the OSProcess child watcher, the changed/update: mechanism will dispatch child exit notification here. To subscribe to notification from OSProcess add the singleton OSSVMProcess as a dependent of the OSProcess accessor singleton. When any child process exits, this method will be called with parameter #childProcessStatus" "OSProcess accessor addDependent: OSSVMProcess vmProcess" (aParameter == #childProcessStatus) ifTrue: [^ self updateActiveChildrenAndNotifyDead]. I stopped the child watcher in OSSVMProcess (by commenting out the last two lines in OSSVMProcess>>initialize just to see if this would work), then added the changed/update: dependency with "OSProcess accessor addDependent: OSSVMProcess vmProcess" After restarting the image, it appears to be working, at least so far has having both OSP and OSSP handle their child process exits properly in the same image. I don't have time to play with this any more right now, but it does look like it might be a workable approach. It should be possible to have the initializer for OSSVMProcess use its normal child exit handler, but hook into the OSP handler instead if that happens to be present in the image. Dave

March 18, 2019

Re: [Pharo-dev] OSProcess for Pharo 7

by Mariano Martinez Peck

> > > > > ducasse wrote > > this is not because we do not care of Pharo that we will fix it > > immediately. > > Yes of course, just want to keep it on the radar (and maybe Mariano will > read he he) > > I always do :) But honestly, I don't have enough time to carry on that myself. As you could see with latest Guillermo pass, I reviewed every PR and tried to give my advice and support as much as possible. Best regards, -- Mariano https://twitter.com/MartinezPeck http://marianopeck.wordpress.com

March 17, 2019

Re: [Pharo-dev] OSProcess for Pharo 7

by ducasse

> ducasse wrote >> Our main problem is that >> - if more people would review PR >> - send PRs > > Thank you for the reminder of that bottleneck. I will try to do that more > now that we have moved to GH. The old process seemed too cumbersome to be > able to effectively utilize a few free moments here and there, but I suspect > that no longer to be the case. Thanks yes it works well now. > ducasse wrote >> this is not because we do not care of Pharo that we will fix it >> immediately. > > Yes of course, just want to keep it on the radar (and maybe Mariano will > read he he)

March 17, 2019

Re: [Pharo-dev] [Moose-dev] Re: Re: [Pharo-users] [ANN] Lan.d.s Alpha: All Along the Language Tower

by Nick Papoylias

On Sun, Mar 17, 2019 at 9:24 PM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I know what is it to write book. > I sent you some support and I want to be a reviewer. > Would be my pleasure Stef ! Today was a wonderful start ! Thank you, Nick > > Stef > > On 17 Mar 2019, at 20:35, Nick Papoylias <npapoylias(a)gmail.com> wrote: > > That was good to know. I updated the site with* one-click direct* > *(non-recurring) alternative*: *PayPal.Me for Lands* > <https://www.paypal.me/npapoylias> > > https://npapoylias.gitlab.io/lands-project/Support/ > > *"Alternatively you can make a direct (non-recurrent) contribution * > *through paypal.me <http://paypal.me/>: PayPal.Me for Lands > <https://www.paypal.me/npapoylias>. Adding "Lands Support" * > *as a note, plus the e-mail and address you would wish to * > *receive your perks on"* > > Cheers, > > Nick > > > > On Sun, Mar 17, 2019 at 5:26 PM Nick Papoylias <npapoylias(a)gmail.com> > wrote: > >> >> >> On Sun, Mar 17, 2019 at 2:18 PM StÃ©phane Ducasse < >> stephane.ducasse(a)inria.fr> wrote: >> >>> Hi nick >>> >>> I wanted to support your chapters via paypal but it asked me about my >>> visa and I would like >>> to pay via my paypal account. Do you know if this is possible? >>> >> >> Thanx Stef ! >> >> *Through patreon, this seems to be required for recurrent payments:* >> >> >> https://support.patreon.com/hc/en-us/articles/115001917686-Why-do-I-need-to… >> >> There are 2 alternatives through that might not have this requirement: >> >> *Alternative 1, through the Paypal button (if you did not try already):* >> >> *Step1,* from: https://npapoylias.gitlab.io/lands-project/Support/ >> >> Hit the PayPal button. >> >> *Step2*: And then in the Paypal screen, hit PayPal pay. >> >> *Alternative 2, directly from your PayPal dashboard:* >> >> "*Pay for goods or services* No fee for you. The recipient pays a fee." >> >> *using my e-mail address:* npapoylias(a)gmail.com <npapoylias(a)gmail.com> >> >> Adding in the note a message like: "Lands Support" so that it is >> distinguishable >> form other transactions. >> >> *Let me know if you encounter any problems, so that I contact them, if >> necessary.* >> And update the site, for ways to support without credit-card required. >> >> Best, >> >> Nick >> >> Else can you send me your pp account? >>> >>> Stef >>> >>> On 17 Mar 2019, at 10:21, Nick Papoylias <npapoylias(a)gmail.com> wrote: >>> >>> *Dear friends ! * >>> >>> I am quite excited to announce the availability of an alpha version >>> of my latest work around *Parsing and Programming Languages *at: >>> >>> https://npapoylias.gitlab.io/lands-project/ >>> >>> Accompanied by *~ 30 min of transcribed eye-candy:* >>> >>> https://www.youtube.com/playlist?list=PLIjPQnRzAKVHABG1-oTvwWc3Gj1Z4C91B >>> >>> Backed by* a crowdfunding campaign ! *To get the *book and stable >>> release * >>> successfully out of the door: >>> >>> https://www.patreon.com/lands_project >>> https://npapoylias.gitlab.io/lands-project/Support/ >>> >>> *Click, download, watch, enjoy !* If you like what you see, support the >>> project ! Tiers >>> start *from 5 and 10 euros per chapter for individuals.* Companies >>> supporting >>> the project can get >>> *6 to 12 days of consultancy, on-site workshops and other perks.* >>> ================= >>> >>> *What is all about ??* >>> >>> *Lan.d.s is a new solution for language design.* From >>> *general purpose languages *like *Lise* (short for (list (embedding)) >>> to >>> *Domain-Specific Languages using the MOODs framework*, and everything >>> else in between. >>> Lan.d.s is build around the formalism of >>> *Multi-Ordered Grammars, which are a possible alternative to CFGs and >>> PEGs in wider use today.* >>> >>> Multi-ordered grammars (or simply MOGs) aim for a better exploration of >>> ambiguity, >>> recursion, ordering and associativity during language design. They can >>> be >>> *parsed using the Gray Algorithm. *After parsing in order to ease the >>> production of executable code >>> Lan.d.s introduces the *Abstract Syntax Language (ASL)*, which is an OO >>> solution for compile-time meta-programming. Finally in order to promote >>> language extension and re-use, Lan.d.s employs >>> *GrammarTraits, as units of composition for both MOG rules and ASL >>> actions.* >>> >>> ================= >>> >>> Some random highlights for the impatient: >>> >>> >>> ** Object subclass: #Prediction uses: Future syntax* >>> >>> ** Languages are everywhere, they are all around you, even now in this >>> very sentence.* >>> >>> ** Study SICP with a Xerox flavor, while re-inventing some Bell-labs >>> utilities.* >>> >>> ** TOC-Board, the TOC for your next talk ;)* >>> >>> >>> Enjoy ! >>> <Theory-and-Applications-Of-Multi-Ordered-Grammars.pdf> >>> <Lands-Alpha-All-Along-The-Language-Tower.png> >>> >>> >>> -------------------------------------------- >>> StÃ©phane Ducasse >>> http://stephane.ducasse.free.fr >>> http://www.synectique.eu / http://www.pharo.org >>> 03 59 35 87 52 >>> Assistant: Julie Jonas >>> 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 >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)list.inf.unibe.ch >>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>> >> > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > http://www.synectique.eu / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > 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 > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev >

March 17, 2019

Re: [Pharo-dev] [Moose-dev] Re: [Pharo-users] [ANN] Lan.d.s Alpha: All Along the Language Tower

by StÃ©phane Ducasse

I know what is it to write book. I sent you some support and I want to be a reviewer. Stef > On 17 Mar 2019, at 20:35, Nick Papoylias <npapoylias(a)gmail.com> wrote: > > That was good to know. I updated the site with one-click direct > (non-recurring) alternative: PayPal.Me for Lands <https://www.paypal.me/npapoylias> > > https://npapoylias.gitlab.io/lands-project/Support/ <https://npapoylias.gitlab.io/lands-project/Support/> > > "Alternatively you can make a direct (non-recurrent) contribution > through paypal.me <http://paypal.me/>: PayPal.Me for Lands <https://www.paypal.me/npapoylias>. Adding "Lands Support" > as a note, plus the e-mail and address you would wish to > receive your perks on" > > Cheers, > > Nick > > > > On Sun, Mar 17, 2019 at 5:26 PM Nick Papoylias <npapoylias(a)gmail.com <mailto:npapoylias@gmail.com>> wrote: > > > On Sun, Mar 17, 2019 at 2:18 PM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: > Hi nick > > I wanted to support your chapters via paypal but it asked me about my visa and I would like > to pay via my paypal account. Do you know if this is possible? > > Thanx Stef ! > > Through patreon, this seems to be required for recurrent payments: > > https://support.patreon.com/hc/en-us/articles/115001917686-Why-do-I-need-to… > <https://support.patreon.com/hc/en-us/articles/115001917686-Why-do-I-need-to…> > > There are 2 alternatives through that might not have this requirement: > > Alternative 1, through the Paypal button (if you did not try already): > > Step1, from: https://npapoylias.gitlab.io/lands-project/Support/ <https://npapoylias.gitlab.io/lands-project/Support/> > > Hit the PayPal button. > > Step2: And then in the Paypal screen, hit PayPal pay. > > Alternative 2, directly from your PayPal dashboard: > > "Pay for goods or services No fee for you. The recipient pays a fee." > > using my e-mail address: npapoylias(a)gmail.xn--com-kla <mailto:npapoylias@gmail.com> > > Adding in the note a message like: "Lands Support" so that it is distinguishable > form other transactions. > > Let me know if you encounter any problems, so that I contact them, if necessary. > And update the site, for ways to support without credit-card required. > > Best, > > Nick > > Else can you send me your pp account? > > Stef > >> On 17 Mar 2019, at 10:21, Nick Papoylias <npapoylias(a)gmail.com <mailto:npapoylias@gmail.com>> wrote: >> >> Dear friends ! >> >> I am quite excited to announce the availability of an alpha version >> of my latest work around Parsing and Programming Languages at: >> >> https://npapoylias.gitlab.io/lands-project/ <https://npapoylias.gitlab.io/lands-project/> >> >> Accompanied by ~ 30 min of transcribed eye-candy: >> >> https://www.youtube.com/playlist?list=PLIjPQnRzAKVHABG1-oTvwWc3Gj1Z4C91B <https://www.youtube.com/playlist?list=PLIjPQnRzAKVHABG1-oTvwWc3Gj1Z4C91B> >> >> Backed by a crowdfunding campaign ! To get the book and stable release >> successfully out of the door: >> >> https://www.patreon.com/lands_project <https://www.patreon.com/lands_project> >> https://npapoylias.gitlab.io/lands-project/Support/ <https://npapoylias.gitlab.io/lands-project/Support/> >> >> Click, download, watch, enjoy ! If you like what you see, support the project ! Tiers >> start from 5 and 10 euros per chapter for individuals. Companies supporting >> the project can get 6 to 12 days of consultancy, on-site workshops and other perks. >> >> ================= >> >> What is all about ?? >> >> Lan.d.s is a new solution for language design. From general purpose >> languages like Lise (short for (list (embedding)) to Domain-Specific >> Languages using the MOODs framework, and everything else in between. >> Lan.d.s is build around the formalism of Multi-Ordered Grammars, >> which are a possible alternative to CFGs and PEGs in wider use today. >> >> Multi-ordered grammars (or simply MOGs) aim for a better exploration of ambiguity, >> recursion, ordering and associativity during language design. They can be parsed using the >> Gray Algorithm. After parsing in order to ease the production of executable code >> Lan.d.s introduces the Abstract Syntax Language (ASL), which is an OO >> solution for compile-time meta-programming. Finally in order to promote >> language extension and re-use, Lan.d.s employs GrammarTraits, as units of >> composition for both MOG rules and ASL actions. >> >> ================= >> >> Some random highlights for the impatient: >> >> >> * Object subclass: #Prediction uses: Future syntax >> >> * Languages are everywhere, they are all around you, even now in this very sentence. >> >> * Study SICP with a Xerox flavor, while re-inventing some Bell-labs utilities. >> >> * TOC-Board, the TOC for your next talk ;) >> >> >> Enjoy ! >> <Theory-and-Applications-Of-Multi-Ordered-Grammars.pdf><Lands-Alpha-All-Along-The-Language-Tower.png> > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> > http://www.synectique.eu <http://www.synectique.eu/> / http://www.pharo.org <http://www.pharo.org/> > 03 59 35 87 52 > Assistant: Julie Jonas > 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 > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> > https://www.list.inf.unibe.ch/listinfo/moose-dev <https://www.list.inf.unibe.ch/listinfo/moose-dev> -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas 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

March 17, 2019

Re: [Pharo-dev] Roassal Animations

by Tim Mackinnon

+10, Iâve loved them them too. > On 17 Mar 2019, at 19:40, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> On 17 Mar 2019, at 20:10, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >> >> Most of the animations are available in the Roassal3 code: >> >> https://github.com/ObjectProfile/Roassal3 > > Yes, OK, but maybe there is some webpage somewhere that collects the Twitter posts, they were really good advertisements. > >> On Sun, Mar 17, 2019 at 7:23 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> Hi, >> >> Who has seen these Roassal Animations on Twitter recently ? >> >> These are crazy cool and super slick. >> >> Is there a place where they are all collected, maybe with their code ? >> >> Sven >> >> >> >> >> -- >> Serge Stinckwicâhâ >> Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) >> âSorbonne University (SU) >> French National Research Institute for Sustainable Development (IRD)â >> Uâniversity of YaoundÃ© Iâ, Cameroun >> "Programs must be written for people to read, and only incidentally for machines to execute." >> https://twitter.com/SergeStinckwich >> â > >

March 17, 2019

Re: [Pharo-dev] Roassal Animations

by Sven Van Caekenberghe

> On 17 Mar 2019, at 20:10, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > Most of the animations are available in the Roassal3 code: > > https://github.com/ObjectProfile/Roassal3 Yes, OK, but maybe there is some webpage somewhere that collects the Twitter posts, they were really good advertisements. > On Sun, Mar 17, 2019 at 7:23 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > Who has seen these Roassal Animations on Twitter recently ? > > These are crazy cool and super slick. > > Is there a place where they are all collected, maybe with their code ? > > Sven > > > > > -- > Serge Stinckwicâhâ > Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) > âSorbonne University (SU) > French National Research Institute for Sustainable Development (IRD)â > Uâniversity of YaoundÃ© Iâ, Cameroun > "Programs must be written for people to read, and only incidentally for machines to execute." > https://twitter.com/SergeStinckwich > â

March 17, 2019