- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Use cases for methods with optional parameters

by stepharo

Le 23/1/16 03:38, Ben Coman a Ã©crit : > Sounds interesting, but my head hurts trying to think about this more > deeply :) > so I'm going to keep at a superficial level on this for now. > So just thinking out loud... > > If you have > mother1 := foo:(bar:zork:fork) > mother2 := foo:bar:(zork:bork:) I'm not sure that this is allows in the same class. We should check that in Python or ruby. > When you search for senders of #foo:bar: what do you get back and how > to display it? We should display every caller. > > Maybe a two level tree list with the option combinations appearing at > the top level and each of their senders at the second level, hiding > any top level items that don't have children. > foo:bar: > foo:bar:zork: > foo:bar:fork: > foor:bar:bork > foo:bar:zork:fork: > foo:bar:fork:zork: > foo:bar:zork:bork: > foo:bar:bork:zork: > > Actually, full any order combination probably becomes unwieldly. > Maybe there should be a constraint that optional arguments can be > skipped but when used must be used in sequence. > > cheers -ben > > btw, how do you mean relationship? I mean knowing the mother from the children > Do you mean using a Slots > mechanism like the relationship demo in the Flexible Object layouts > paper? no > https://hal.inria.fr/hal-00641716/file/Verw11b-OOSPLA11-FlexibleObjectLayou… > > On Sat, Jan 23, 2016 at 3:29 AM, stepharo <stepharo(a)free.fr> wrote: >> Ben >> >> We were thinking also about reflection. >> >> >> So may be we should introduce a relationship between the method and its >> actual implementation. >> >> Imagine that >> mother := foo:(bar:zork:) >> mother children >> foo:bar: >> foo:bar:zork: >> >> then >> senders (foo:bar:) >> => >> sender (motherOf(foo:bar:)) >> >> where motherOf is a back pointer from the expanded method into its mother >> But it means that method using foo:bar: should somehow "mention" that they >> will >> use motherOf (foo:bar:). >> >> >> >> Le 22/1/16 01:41, Ben Coman a Ã©crit : >> >>> I don't have any use cases right now, but I'll keep my eyes open. But >>> an example (that is maybe too basic to mess with) is the >>> #at:ifAbsent: pattern. For example, the following would be >>> "deleted" >>> >>> Dictionary>>.at: key >>> ^ self at: key ifAbsent: [self errorKeyNotFound: key] >>> >>> and you would only have.... >>> >>> Dictionary>>at: key ifAbsent: aBlock >>> <optional: ifAbsent default: [ self errorKeyNotFound: key]> >>> >>> The big in-Image example would be... >>> >>> TClass>> >>> subclass: aName >>> uses: aTraitCompositionOrArray >>> instanceVariableNames: someInstanceVariableNames >>> classVariableNames: someClassVariableNames >>> poolDictionaries: someSharedPoolNames >>> package: aCategory >>> <optional: uses default: {}> >>> <optional: instanceVariableNames default: ''> >>> <optional: classVariableNames default: ''> >>> <optional: poolDictionaries default:''> >>> <optional: package 'Unclassified'> >>> >>> Now I wonder about senders & implementers searchability, and if >>> "virtual" methods are generated in all combinations of optional >>> parameters and show up in the system browser list, but show the "main" >>> method as their source. >> >> >

Jan. 23, 2016

Re: [Pharo-dev] Add to Package

by stepharo

Le 23/1/16 15:14, Esteban A. Maringolo a Ã©crit : > 2016-01-23 4:48 GMT-03:00 stepharo <stepharo(a)free.fr>: >> Hi >> >> in MC add to package should use a FastList because the logic right now is >> really stupid. > I would also add the "add repo" to the package, with a list of the > recently used repos. Or add the repo to a multiple number of packages. That too :) > > Regards! > > Esteban A. Maringolo > >

Jan. 23, 2016

Re: [Pharo-dev] OSSubprocess use

by Mariano Martinez Peck

Hi Thierry, The Metacello answer here would be "it's up to you" hahahaha. I don't have a strong opinion. Most of the times I am in the similar situation, I tend to use fixed versions when the projects are really coupled and one cannot work without the other. And use #stable when they are less coupled and I would not die if that dependency is broken for some time until fixed. What would be the problem of using #stable? That I may release new versions which may break the user API, or I may introduce bugs that I didn't discover before, etc etc. It won't be fun if I update GitFileTree and suddenly I cannot commit anymore. But at the same time, you don't expect a user to be updating GitFileTree in his image. In addition, you have a CI that will tell you immediately if the build fail or your tests failed. If you ask me, I think I would use fixed versions. Then, whenever I release a new version, you give it a try, you test it, you try it in the CI, etc. If everything seems to work, then I would update your conf and point to new version. Cheers, On Sat, Jan 23, 2016 at 9:09 AM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Hi, > > I'm looking at OSSubprocess use as a requirement for GitFileTree and I > wonder if it is wise to list the dependency on OSSubprocess #stable or to > set to a specific version (v0.2)? > > Thanks, > > Thierry > > -- Mariano http://marianopeck.wordpress.com

Jan. 23, 2016

Re: [Pharo-dev] Add to Package

by Esteban A. Maringolo

2016-01-23 4:48 GMT-03:00 stepharo <stepharo(a)free.fr>: > Hi > > in MC add to package should use a FastList because the logic right now is > really stupid. I would also add the "add repo" to the package, with a list of the recently used repos. Or add the repo to a multiple number of packages. Regards! Esteban A. Maringolo

Jan. 23, 2016

Re: [Pharo-dev] Get an image from monkey job

by Ben Coman

On Sat, Jan 23, 2016 at 7:12 PM, Vincent BLONDEAU <vincent.blondeau(a)polytech-lille.net> wrote: > Hi, > > With the current configuration, it is not possible: the workspace is deleted > after the execution (so the image generated too...). > Maybe it should be nice to delete the workspace only before the job, in this > way, one can be able to retrieve the generated image and debug it? But if there are several FixReviewNeeded, wouldn't all except the last get bumped out? Maybe workspaces could be kept for a short time ~ 6 to 24 hours? I guess it all depends on CI space available. cheers -ben > Can a Pharo CI admin change this configuration? > > Cheers, > Vincent > > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of > Yuriy Tymchuk > Sent: samedi 23 janvier 2016 11:52 > To: Pharo Development List > Subject: [Pharo-dev] Get an image from monkey job > > Hi, > > sometimes some strange tests fail while money is checking the > slice/configuration. And while the failures are not related to the > contribution sometimes I want to know what happened and maybe fix it. Is it > possible to get the resulting image to investigate it? > > Cheers. > Uko > >

Jan. 23, 2016

OSSubprocess use

by Thierry Goubier

Hi, I'm looking at OSSubprocess use as a requirement for GitFileTree and I wonder if it is wise to list the dependency on OSSubprocess #stable or to set to a specific version (v0.2)? Thanks, Thierry

Jan. 23, 2016

Re: [Pharo-dev] Get an image from monkey job

by Vincent BLONDEAU

Hi, With the current configuration, it is not possible: the workspace is deleted after the execution (so the image generated too...). Maybe it should be nice to delete the workspace only before the job, in this way, one can be able to retrieve the generated image and debug it? Can a Pharo CI admin change this configuration? Cheers, Vincent -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Yuriy Tymchuk Sent: samedi 23 janvier 2016 11:52 To: Pharo Development List Subject: [Pharo-dev] Get an image from monkey job Hi, sometimes some strange tests fail while money is checking the slice/configuration. And while the failures are not related to the contribution sometimes I want to know what happened and maybe fix it. Is it possible to get the resulting image to investigate it? Cheers. Uko

Jan. 23, 2016

Get an image from monkey job

by Yuriy Tymchuk

Hi, sometimes some strange tests fail while money is checking the slice/configuration. And while the failures are not related to the contribution sometimes I want to know what happened and maybe fix it. Is it possible to get the resulting image to investigate it? Cheers. Uko

Jan. 23, 2016

Re: [Pharo-dev] 17348 Enhance shortcut learnability

by stepharo

Hi henrik did you publish the code? Stef PS: I start playing magic with my third son and he is building fun decks that kill me :) Le 13/1/16 16:38, stepharo a Ã©crit : > Sweet! > I was thinking to put it below and smaller but this is cool. > > Stef > > Le 12/1/16 21:03, Henrik Nergaard a Ã©crit : >> >> Hi Stef, >> >> Something like this? (see attachment) >> >> Best regards, >> >> Henrik >> >> *From:*Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *On >> Behalf Of *stepharo >> *Sent:* Monday, January 11, 2016 4:52 PM >> *To:* Pharo Development List <pharo-dev(a)lists.pharo.org> >> *Subject:* Re: [Pharo-dev] 17348 Enhance shortcut learnability >> >> Henrik >> >> Thanks. What I would love to get is >> >> another little morph below the shortcut with the name of the menu >> like that we can learn that the tools xxx is launched with >> shortcut cmd X >> >> I think that we should have a preference that does not flush the >> counters at startup >> >> Stef >> >> Le 11/1/16 12:14, Henrik Nergaard a Ã©crit : >> >> Somehow it integrated >> >> ______________ >> >> Name: SLICE-Issue-17348-Enhance-shortcut-learnability-tr.2 >> >> Author: tr >> >> Time: 8 January 2016, 4:18:55.135106 pm >> >> UUID: 0aa30f76-84f3-0449-acde-172e56ea3615 >> >> Ancestors: SLICE-Issue-17348-Enhance-shortcut-learnability-tr.1 >> >> Dependencies: Morphic-Base-tr.526 >> >> better version >> >> instead of: >> >> ____________ >> >> Name: >> SLICE-Issue-17348-Enhance-shortcut-learnability-HenrikNergaard.2 >> >> Author: HenrikNergaard >> >> Time: 8 January 2016, 11:01:18.490743 pm >> >> UUID: 2a6f1c3f-a0b3-524d-9095-02fb42ab8358 >> >> Ancestors: SLICE-Issue-17348-Enhance-shortcut-learnability-tr.1 >> >> Dependencies: Morphic-Base-HenrikNergaard.526 >> >> Refactor of initial code. >> >> I have updated and merged a new slice (in Image 50521) which >> should fix it. The correct version that should be integrated is: >> >> Name: >> SLICE-Issue-17348-Enhance-shortcut-learnability-HenrikNergaard.5 >> >> Author: HenrikNergaard >> >> Time: 11 January 2016, 12:17:08.504781 am >> >> UUID: f0271c17-07a7-0d4e-a6eb-d2fef9b2853c >> >> Ancestors: >> SLICE-Issue-17348-Enhance-shortcut-learnability-HenrikNergaard.4 >> >> Dependencies: Morphic-Base-HenrikNergaard.530 >> >> remove unused variable. >> >> Best regards, >> >> Henrik >> >> *From:*Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *On >> Behalf Of *Marcus Denker >> *Sent:* Monday, January 11, 2016 11:35 AM >> *To:* Pharo Development List <pharo-dev(a)lists.pharo.org> >> *Subject:* Re: [Pharo-dev] 17348 Enhance shortcut learnability >> >> Hello, >> >> I wil reopen the issue and put your comment there. >> >> Marcus >> >> On 11 Jan 2016, at 09:56, Nicolai Hess >> <nicolaihess(a)gmail.com> wrote: >> >> Can please someone translate / change the text in the >> >> Shortcut reminder Morph settings.( that got integrated in 50521) >> >> see my comment on >> https://pharo.fogbugz.com/f/cases/17348/Enhance-shortcut-learnability#BugEv… >> >> and I asked for resubmitting the changes with proper author >> initials >> >> instead of "tr" and if he signed the license agreement. >> >> Anyone knows more about "tr" ? >> >> And I am not sure if the right version is integrated. >> >> nicolai >> >

Jan. 23, 2016

Add to Package

by stepharo

Hi in MC add to package should use a FastList because the logic right now is really stupid. Any taker? stef

Jan. 23, 2016