August 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo 1.3 release
by Marcus Denker Aug. 31, 2011

Aug. 31, 2011

On Aug 30, 2011, at 5:15 PM, Mariano Martinez Peck wrote: > so what is missing now? just an ANN email? > No, as much as I know we do not have yet a One-Click with current VMs... > On Tue, Aug 30, 2011 at 3:59 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Aug 30, 2011, at 4:21 PM, laurent laffont wrote: > > > On Tue, Aug 30, 2011 at 2:24 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Nice and clear info. The only thing that I see left that may be confusing is > > the ci shortcut on the home page. Since there are currently two ci servers, > > I think the ci link should take you to another page explaining the > > difference and where they're headed. > > > > > > Is hudson will be dropped or will stay around ? > > > > Hudson will be discontinued at some point. But we need to move everything Jenkins before. > > > -- > Marcus Denker -- http://marcusdenker.de > > > > > > -- > Mariano > http://marianopeck.wordpress.com > -- Marcus Denker -- http://marcusdenker.de

6 8

[Pharo-project] Gofer/Metacello problem in 1.4 [WAS] Re: DBXTalk and Pharo 1.4
by Mariano Martinez Peck Aug. 31, 2011

Aug. 31, 2011

On Tue, Aug 30, 2011 at 9:14 PM, Laszlo Zsolt Kiss <lzskiss(a)gmail.com>wrote: > hi. > first i load the ConfigurationOfOpenDBX and the 1.4 version is missing from > the spec.: > > stable: spec > <symbolicVersion: #stable> > > spec for: #'pharo1.2.x' version: '1.0'. > spec for: #'pharo1.3.x' version: '1.0'. > > then i added the next line to the spec: > > spec for: #'pharo1.4.x' version: '1.0'. > > then i probally do it this: > > (((Smalltalk globals at: #ConfigurationOfOpenDBXDriver) perform: #project) > perform: #version: with: #stable) load. > > i gived back a warring: > > "The method Gofer addVersion: has been deprecated. > Instead of #addVersion: simply use #version: > Hi. Yes, I can reproduce this problem :( > > Select Proceed to continue, or close this window to cancel the operation." > > I proceed this warrning. > > Then gived back an error message, I think this error came from the > Metacello. > I attached the PharoDebug file. > > The error is in the method #updateProject where it does: (GoferPackageReference name: mgr packageName repository: mgr repositoryGroup) versionReference. GoferPackageReference dnu #name:repository: instead, it is implemented in GoferResolvedReference Dale any idea? Versions: Gofer-Core-StephaneDucasse.135. Metacello version is ...... ConfigurationOfMetacello project currentVersion raises dnu #setName So...I guess Pharo 1.4 is using a very new version of Gofer, which brings lot of changes that break Metacello ? Thanks! Byte > Laszlo Zsolt > > Ps: the image is clean #14112 and the CogVM is the last.. > > inez Peck <marianopeck(a)gmail.com> > >> >> >> On Tue, Aug 30, 2011 at 9:53 AM, Laszlo Zsolt Kiss <lzskiss(a)gmail.com>wrote: >> >>> Hi Developers! >>> >>> Can I use any way this combination: DBXTalk with Pharo 1.4? >>> >> >> Hi. Yes, sure. Did you try it? You shouldn't have any problem. >> Please let us know if you do have. >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > -- Mariano http://marianopeck.wordpress.com

3 5

[Pharo-project] #deprecate: & #deprecate:in: will be deprecated in 1.4
by Sean P. DeNigris Aug. 31, 2011

Aug. 31, 2011

http://code.google.com/p/pharo/issues/detail?id=4718 I put a fix in the inbox that updates all existing calls to use #deprecate:on:in: -- View this message in context: http://forum.world.st/deprecate-deprecate-in-will-be-deprecated-in-1-4-tp37… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1

[Pharo-project] The Keys to the Kingdom
by Sean P. DeNigris Aug. 31, 2011

Aug. 31, 2011

This incredible piece of feedback was hiding at http://code.google.com/p/pharo/wiki/HowToContribute . We should all have this pinned to the wall behind our computer: Sometimes I make some "exercise" on Smalltalk/Squeak for the fun, sometimes I try to build tools in Squeak to solve some practical problem or personal need. I'm not a programmer, just a curious guy, completely ignorant about programming, who, some years ago, found Smalltalk/Squeak to be the only human programming language I could cope with. But every time I try to do something with Squeak I stumble on this inevitable conclusion: it is one of the most entropic things I ever met in my life. The reason for this may lay partly on structural reasons - I wouldn't know, because I'm an ignorant, as I stated before. But there is a second reason I know for sure: the owners' and contributors' inability to step out of the developer's perspective, to put a distance towards themselves (and towards the result of their work). As a result, Squeak is probably the worst documented language in the world. Documentation and comments on the code are completely entropic, self-centered, tautological; it is experts talking to all-knowing experts - like those stupid old-fashioned dictionaries where every word definition tends to be built with the defined word. Until now I had a look to Pharo system browser only for a few minutes, but that was enough for me to get the impression that you are trying to get over this dreadful limitation, to jump over the limits of an strictly enclosed community, rehearsing new tentative styles to comment code and classes. If I got it right and this is true, congratulations and thank you very much for your effort. -- View this message in context: http://forum.world.st/The-Keys-to-the-Kingdom-tp3780556p3780556.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 4

[Pharo-project] Symbol>value:
by niko.schwarz＠googlemail.com Aug. 31, 2011

Aug. 31, 2011

Hi, Symbol responds to #value:, but not to #value:value:. At some point, Symbol and Block were decided to have the invocation protocol in common. I find this great. Therefore, I think, Symbol should also respond to #value:value:, as follows: value: anObject value: anotherObject ^ anObject perform: self with: anotherObject Of course, it should also respond to #value:value:value: and #value:value:value:value: Niko -- http://scg.unibe.ch/staff/Schwarz twitter.com/nes1983 Tel: +41786126354

13 22

[Pharo-project] The Keys to the Kingdom
by Torsten Bergmann Aug. 31, 2011

Aug. 31, 2011

Yes, and I think these special thanks are addressed to Stef and Laurent. Stef started with the idea not to include code that is not documented - which was a little bit unrealistic but lead to Laurents idea of a "Comment of the day" game. The archive is your friend: http://lists.gforge.inria.fr/pipermail/pharo-project/2011-February/041356.h… Looks like we should continue to play this game ;) Bye T. -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone

3 2

[Pharo-project] Please comment: Issue 4725: extend the string protocol
by Torsten Bergmann Aug. 31, 2011

Aug. 31, 2011

Stef wrote >hence I would like to introduce some extensions: > >- chomp (ruby like) #chomp is not a very intention revealing name. What about #withoutTerminatingNewline Bye T. -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone

1 0

Aug. 31, 2011

http://code.google.com/p/pharo/issues/detail?id=4725 I always feel a bit lost when using string manipulation in pharo... hence I would like to introduce some extensions: - chomp (ruby like) - #padLeft: #padRight: (as a replacement for the broken padded:to:with:) - #copyFrom:to: extensions with several specialized methods (the classical way would be to support negative indices, but this will most likely break existing tools) camillo could you illustrate your request. Some tests would be the ideal way to describe them.

1 0

[Pharo-project] Addition to "About Pharo" dialog
by GermÃ¡n Arduino Aug. 31, 2011

Aug. 31, 2011

Hi Guys: Is just me that think that is useful to have the VM version at hand (may be in the "About Pharo" dialog)? In my case, using different computers, and having differents vm's is so useful and I added a little code to have this info in such Dialog. If may be of interest I cand send a slice. Let me know. Cheers. -- ================================================= GermÃ¡n S. ArduinoÂ <gsa @ arsol.net>Â Â Twitter: garduino Arduino Software & Web HostingÂ Â http://www.arduinosoftware.com PasswordsProÂ http://www.passwordspro.com =================================================

11 29

[Pharo-project] Deprecation policy
by Sean P. DeNigris Aug. 31, 2011

Aug. 31, 2011

I want to add a comment to #deprecated:on:in: This is my understanding (it is implemented inconsistently in 1.4 update #14112): For methods: 1. Have the method call deprecated:on:in: as its first step - the versionString should be e.g. 'Pharo1.4' (although I found #Pharo1.4, see the problem; and '1.4', those were mine, hee hee). Is it redundant to say 'PharoXxx'? 2. Move the method to protocol e.g. deprecated14 for Pharo 1.4 For classes: 1. Move to Category e.g. 'Deprecated14' for Pharo 1.4 2? Should #deprecated:on:in: be called from the methods? It's inconsistent in the image and seems unnecessary, except maybe for some class-side methods. Is all this correct? Thanks. Sean -- View this message in context: http://forum.world.st/Deprecation-policy-tp3777647p3777647.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

3 6