April 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] How to make Metacello ignore package cache?

by Dale Henrichs

I'm not exactly sure why you are getting the error, but the standard way to deal with a package-cache issue (or at least eliminate the package-cache as the real culprit) is to clear the package-cage in the Monticello browser ... An alternative (or next step) would be to try the following: Metacello new configuration: 'MyConfig'; repository: 'github://hernanmd/MyPackage/repository'; get the `get` forces a reload of ConfigurationOfMyConfig from the source repository ... If that doesn't work, please supply a complete Transcript of your Metacello `get` episode, so that I can try to figure out what is going wrong ... Dale On 4/26/19 10:40 AM, HernÃ¡n Morales Durand wrote: > Hi guys, > > Is there any way to tell Metacello to ignore the local package cache > after a failed load? > > Say I tried to load: > > Metacello new > configuration: 'MyConfig'; > repository: 'github://hernanmd/MyPackage'; > load. > > Then I figure the "repository" path is missing and I add it: > > Metacello new > configuration: 'MyConfig'; > repository: 'github://hernanmd/MyPackage/repository'; > load. > > And I get this exception: Could not resolve: ConfigurationOfMyConfig > [ConfigurationOfMyConfig] in > D:\Hernan\Pharo703\pharo-local\package-cache > https://github.com/hernanmd/MyPackage.git[master] > > It doesn't matter if I use #onConflictUseIncoming or > > MetacelloPlatform current defaultPackageCache flushCache. > > I cannot find a way to specify to ignore the cache. > Any ideas? > > Cheers, > > HernÃ¡n >

April 26, 2019

How to make Metacello ignore package cache?

by HernÃ¡n Morales Durand

Hi guys, Is there any way to tell Metacello to ignore the local package cache after a failed load? Say I tried to load: Metacello new configuration: 'MyConfig'; repository: 'github://hernanmd/MyPackage'; load. Then I figure the "repository" path is missing and I add it: Metacello new configuration: 'MyConfig'; repository: 'github://hernanmd/MyPackage/repository'; load. And I get this exception: Could not resolve: ConfigurationOfMyConfig [ConfigurationOfMyConfig] in D:\Hernan\Pharo703\pharo-local\package-cache https://github.com/hernanmd/MyPackage.git[master] It doesn't matter if I use #onConflictUseIncoming or MetacelloPlatform current defaultPackageCache flushCache. I cannot find a way to specify to ignore the cache. Any ideas? Cheers, HernÃ¡n

April 26, 2019

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini -also in 7.03

by Stephan Eggermont

TedVanGaalen <tedvga(a)gmail.com> wrote: > Hi Stephan > I am a bit confused, not really at home in your VM world, > so please send me a link for the VM + an Image that you'd like me to try on > my mac. > Thanks > Ted > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > See github issue. Vm from files.pharo.org

April 26, 2019

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini -also in 7.03

by TedVanGaalen

Hi Stephan, Pending: (Which VM?) If you still think trying a VM with Pharo 7 on my Mac is important for you to conquer the bug in the VM, then please tell me which VM I should try out on my Mac. Regards TedvG -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 26, 2019

Re: [Pharo-users] How do you rotate a morph by degrees

by Steve Quezadas

Yes, that "addFlexOf" thing seems to be the message I needed to add to get the morph to rotate. Forgive the naive question. On Thu, Apr 25, 2019 at 9:19 AM K K Subbu <kksubbu.ml(a)gmail.com> wrote: > On 25/04/19 7:29 PM, Steve Quezadas wrote: > > I am trying to rotate an instance of a [Transformation morph]. I am > > sending an "angle:" message, which should work since "angle:" is listed > > as a method in it's parent class, yet when I sent a message, it claims > > "it does not understand #angle". Shouldn't messagepassing forward the > > message to it's parent class? > > Did you mean "TransformationMorph"? > > I just tried the one-liner below in Pharo 7 (64b Linux) and it worked > > (TransformationMorph new asFlexOf: ('Hello' asMorph)) angle: (Float pi / > 4); openInHand. > > Regards .. Subbu > >

April 26, 2019

Re: [Pharo-users] Baseline subclasses

by Dale Henrichs

Ahhh! Interesting solution to your problem ... funky but using tested features! On 4/25/19 1:23 AM, Norbert Hartl wrote: > Dale, > > looking at my code I really like the idea solving my white label > problem with polymorphism. It makes things much easier IMHO. So ended > up doing something like having something like this > > BaselineOfCoreProduct > â¦ > Â Â spec group: âwhiteLabelâ with: #( âBaselineOfWhiteLabelProductâ ) > â¦ > > and doing > > Â Â Metacello new > Â Â Â Â baseline: #CoreProduct > Â Â Â Â load: âwhiteLabelâ; > Â Â Â Â baseline: #WhiteLabelProduct; > Â Â Â Â load > > This way each baseline is still in its own package. The project is not > for public consumption so we have to do that in our deployment process > nowhere else. > > Norbert > > >> Am 25.04.2019 um 09:51 schrieb Norbert Hartl <norbert(a)hartl.name >> <mailto:norbert@hartl.name>>: >> >> >> >>> Am 25.04.2019 um 01:13 schrieb Dale Henrichs >>> <dale.henrichs(a)gemtalksystems.com >>> <mailto:dale.henrichs@gemtalksystems.com>>: >>> >>> >>> On 4/24/19 3:08 PM, Norbert Hartl wrote: >>>> I donât have an idea how to achieve this with a group. It is about >>>> changing the number of dependencies of one package. >>> >>> There's load order and there's grouping... >>> >>> If you are using #linear loads for a BaselineOf then hard >>> dependencies (Metacello requires:) dictate load Â order and load >>> order is important. >>> >>> If you are using #atomic loads, then load order for packages is not >>> important ... for #atomic loads you only need to specify which set >>> of packages you want to have loaded together ... so if you have a >>> baseline where you don't use #requires: anywhere and simply define >>> different groups for each set of package to want to have loaded >>> together (one for productA and another for productB) ... you should >>> be able to get what you want ... >>> >>> If this is a public baseline, then you have to warn users of your >>> project that the only legally loadable entities are the set of >>> groups that you've created, then things should work well ... ... I'd >>> think:) >>> >>>> >>>> So no way of making Metacello load a package with one name and load >>>> a baseline with another name? >>> >>> Not sure what you are thinking about here ... i think I need a >>> concrete example of what you mean hereâ¦ >>> >> Sorry, I wasnât clear. I was talking about the possibility to have a >> basline loaded where the package name and the name of the baseline >> are not the same. So letâs say I have the two baselines in the >> BaselineOfCoreProduct. Then I would need to do something like >> >> Metacello new >> Â Â package: âBaselineOfCoreProductâ; >> Â Â baseline: #BaselineOfWhiteLabelProduct; >> Â Â load >> >> That would be sufficient. Having all the baselines in one package >> would be a smaller problem then. >> >> Norbert >

April 25, 2019

Re: [Pharo-users] Deep Recursion break/protection

by Esteban Maringolo

On Thu, Apr 25, 2019 at 10:41 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 25 Apr 2019, at 15:27, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > However I ran these examples in Dolphin and Pharo 7, and in Dolphin it > > triggers an memory exhaustion exception right away, and in Pharo it > > grows in memory use, slower than with the previous example, but with > > the same behavior (unresponsive image once the memory fills the > > available OS memory). > > Too bad, this is a VM issue anyway. I think this is user related (those who accidentally create deep recursions), but should this be reported on the vm-list? Regards, Esteban A. Maringolo

April 25, 2019

Re: [Pharo-users] How do you rotate a morph by degrees

by K K Subbu

On 25/04/19 7:29 PM, Steve Quezadas wrote: > I am trying to rotate an instance of a [Transformation morph]. I am > sending an "angle:" message, which should work since "angle:" is listed > as a method in it's parent class, yet when I sent a message, it claims > "it does not understand #angle". Shouldn't messagepassing forward the > message to it's parent class? Did you mean "TransformationMorph"? I just tried the one-liner below in Pharo 7 (64b Linux) and it worked (TransformationMorph new asFlexOf: ('Hello' asMorph)) angle: (Float pi / 4); openInHand. Regards .. Subbu

April 25, 2019

Re: [Pharo-users] How do you rotate a morph by degrees

by Sean P. DeNigris

test email wrote > Shouldn't messagepassing forward the message to it's > parent class? Yes. Perhaps if you pasted the exact code causing the error and a screenshot of the error it would help. Just a shot in the dark: you said "it does not understand #angle", but the message is #angle: (added colon) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 25, 2019

How do you rotate a morph by degrees

by Steve Quezadas

I am trying to rotate an instance of a [Transformation morph]. I am sending an "angle:" message, which should work since "angle:" is listed as a method in it's parent class, yet when I sent a message, it claims "it does not understand #angle". Shouldn't messagepassing forward the message to it's parent class? - Steve

April 25, 2019