- Pharo-dev - lists.pharo.org

Re: [Pharo-project] 20460: It looks like we broke doit in Spec tools.

by StÃ©phane Ducasse

Thanks ben! Stef On Dec 29, 2012, at 3:26 PM, Benjamin wrote: > Ok, I open a bug entry then > > Ben > > On Dec 29, 2012, at 3:23 PM, StÃ©phane Ducasse wrote: > >> In the code pane of sender or implementor >> "self new foo" >> >> -> self is nil >> >> Stef >> On Dec 29, 2012, at 3:07 PM, Benjamin wrote: >> >>> Can you detail the steps to reproduce please ? >>> >>> Ben :) >>> >>> >>> On Dec 29, 2012, at 2:50 PM, StÃ©phane Ducasse wrote: >>> >>>> It looks like we broke doit in Spec tools. >>>> I need help :) >>>> >>>> Stef >>>> >>> >>> >> >> > >

Dec. 29, 2012

[Pharo-project] [update 2.0] #20460

by StÃ©phane Ducasse

20460 ----- - Issue 7178: MC cache resynching http://code.google.com/p/pharo/issues/detail?id=7178 Diff information: http://ss3.gemstone.com/ss/Pharo20/Ring-Monticello-StephaneDucasse.12.diff http://ss3.gemstone.com/ss/Pharo20/Ring-Core-Kernel-StephaneDucasse.88.diff

Dec. 29, 2012

Re: [Pharo-project] 20460: It looks like we broke doit in Spec tools.

by Benjamin

Ok, I open a bug entry then Ben On Dec 29, 2012, at 3:23 PM, StÃ©phane Ducasse wrote: > In the code pane of sender or implementor > "self new foo" > > -> self is nil > > Stef > On Dec 29, 2012, at 3:07 PM, Benjamin wrote: > >> Can you detail the steps to reproduce please ? >> >> Ben :) >> >> >> On Dec 29, 2012, at 2:50 PM, StÃ©phane Ducasse wrote: >> >>> It looks like we broke doit in Spec tools. >>> I need help :) >>> >>> Stef >>> >> >> > >

Dec. 29, 2012

Re: [Pharo-project] 20460: It looks like we broke doit in Spec tools.

by StÃ©phane Ducasse

In the code pane of sender or implementor "self new foo" -> self is nil Stef On Dec 29, 2012, at 3:07 PM, Benjamin wrote: > Can you detail the steps to reproduce please ? > > Ben :) > > > On Dec 29, 2012, at 2:50 PM, StÃ©phane Ducasse wrote: > >> It looks like we broke doit in Spec tools. >> I need help :) >> >> Stef >> > >

Dec. 29, 2012

Re: [Pharo-project] 20460: It looks like we broke doit in Spec tools.

by Benjamin

Can you detail the steps to reproduce please ? Ben :) On Dec 29, 2012, at 2:50 PM, StÃ©phane Ducasse wrote: > It looks like we broke doit in Spec tools. > I need help :) > > Stef >

Dec. 29, 2012

[Pharo-project] 20460: It looks like we broke doit in Spec tools.

by StÃ©phane Ducasse

It looks like we broke doit in Spec tools. I need help :) Stef

Dec. 29, 2012

Re: [Pharo-project] Extracting a ZipArchive in 2.0

by Camillo Bruni

try to have a look at the other ensure* methods on FileReference or AbstractFileReference. I think you need #ensureFile or #ensureDirectory :) On 2012-12-27, at 17:28, Vanessa PeÃ±a Araya <van.c.pena(a)gmail.com> wrote: > Hi, > > I want to extract a ZipArchive in Pharo 2.0, as the title says. I'm trying to do it with this: > > zipArchive > extractAllTo: aDirectory > informing: bar > overwrite: false > > I'm trying the new file system but my problem is that ZipArchiveMember calls a method called "assureExistence", which does not exist... anywhere. > > Has anyone experience something like this? > > Thanks, > Vanessa. >

Dec. 28, 2012

Re: [Pharo-project] [ENH]: MCHttpRepository Authentication (Issue 6449)

by Sean P. DeNigris

This enhancement allows you to save MC repo credentials per url. That could mean, for example, one general login for ss3 and specific ones for specific projects on ss3. The credentials can be set in your startup script and will be applied to all new instances (unless you specifically override them). You will no longer have to re-execute a script every time a new repo is added. See MCRepositoryAuthorizationTest for some examples. #testStoredCredentialsUsesMostSpecific is pretty comprehensive I'd love for someone to review this slice asap. I've already made a few because it touches a bunch of kernel packages and the slices keep going stale. Sean P. DeNigris wrote > Fix in inbox. You specify the credentials to be used for a url and all new > instances of MCHttpRepository will use those credentials. For example: > > registry := MCServerRegistry uniqueInstance. > registry on: self exampleServerUrl beUser: 'myusername' withPassword: > 'mypassword'. > > repo := MCHttpRepository location: self exampleServerUrl. > > repo user = 'myusername'. > repo password = 'mypassword'. > > Full details: > * Add MCServerRegistry, a singleton which stores credentials for > MCHttpRepository locations (see #on:beUser:withPassword:) > * Add MCHttpRepository class>>location:, which uses any stored > credentials, or empty user and password if none > -Change all senders manually setting empty credentials to use #location. > e.g. > MCHttpRepository > location: 'http://ss3.gemstone.com/ss/Pharo20' > user: '' > password: '' > or worse > MCHttpRepository new > location: self inboxRepositoryUrlString; > user: ''; > password: '' > becomes: > MCHttpRepository location: 'http://ss3.gemstone.com/ss/Pharo20'. > * Fix Gofer repo authentication > - Replace switch statement with polymorphic delegation > - Setting credentials only effects the repo for that Gofer instance; does > not change the stored credentials > * Tests - added for new behavior, fixed relevant existing; all passing > * MCHttpRepository class>>location:user:password: only effects that repo; > does not change the stored credentials -- View this message in context: http://forum.world.st/ENH-MCHttpRepository-Authentication-Issue-6449-tp4641… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 28, 2012

[Pharo-project] [update 2.0] #20459

by StÃ©phane Ducasse

20459 ----- - Issue 7170: Open up the API for secondarySelection in editor/TextMorphForEditView. Thanks Thierry Goubier http://code.google.com/p/pharo/issues/detail?id=7170 - Issue 7182: Extensions shown only when there are extensions http://code.google.com/p/pharo/issues/detail?id=7182 - improve the MCClassDefinition cache reseting protocol Diff information: http://ss3.gemstone.com/ss/Pharo20/Morphic-StephaneDucasse.1317.diff http://ss3.gemstone.com/ss/Pharo20/MonticelloGUI-StephaneDucasse.204.diff http://ss3.gemstone.com/ss/Pharo20/Monticello-StephaneDucasse.736.diff

Dec. 28, 2012

[Pharo-project] [update 2.0] #20458

by StÃ©phane Ducasse

20458 ----- Issue 7179: Fixed AsmJit extension methods http://code.google.com/p/pharo/issues/detail?id=7179 Diff information: http://ss3.gemstone.com/ss/Pharo20/NativeBoost-Win32-StephaneDucasse.33.diff http://ss3.gemstone.com/ss/Pharo20/NativeBoost-Tests-StephaneDucasse.45.diff http://ss3.gemstone.com/ss/Pharo20/NativeBoost-Examples-StephaneDucasse.17.… http://ss3.gemstone.com/ss/Pharo20/NativeBoost-Core-StephaneDucasse.96.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-StephaneDucasse.1280.diff http://ss3.gemstone.com/ss/Pharo20/AsmJit-Extension-StephaneDucasse.6.diff

Dec. 28, 2012