March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] I stumbled upon

by stephane ducasse

> > > the above fucntions would get: > capitalized > "Return a copy with the first letter capitalized" > ^ self withFirstLetterTransformed: [:value | value asUppercase ]. > > and > withFirstCharacterDownshifted withFirstCharacterLowercase? > "Return a copy with the first letter downShifted (in lower case)" > > ^ self withFirstLetterTransformed: [:value | value asLowercase ]. > > Well I also know that capitalized is a very "old" thing but the second > name is more specific. So what about: > withFistCharacterUpshifted .... as counterpart? does not fly :) > we have first for accessing the first element of any collection > but first: is not for setting the first element. > > first:n yields the first n Elements of a collection. > > That's not a good name then. > firstElements:n would be a better name IMHO. indeed. > And then we could have > first: someValue > and so we would have in the end: > > result first: (aTranformBlock value: result first). > > > would change the first Element of "any" collection. AFAIKT Lisp has such > a conventionâ¦ > > my first changes to not to any harm to existing Code, but of course > changing the meaning of first: wouldâ¦. Did you check what are the senders of first:? STef

March 30, 2013

[Pharo-project] [update 3.0] #30018

by Marcus Denker

March 30, 2013

Re: [Pharo-project] OSProcess problem with Windows

by stephane ducasse

is the same expression working on the machine? > Hi, > > When I try > OSProcess command: 'cd "C:\Users\Jannik Laval\Desktop\Pharo2.0-one-click.app\Contents\Resources\Help\en"' > > There is an error. > Can anyone help me ? > > Thanks > > -- > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu >

March 30, 2013

[Pharo-project] icons in Nautilus?

by Alexandre Bergel

Hi! I am just wondering what these icons means in Nautilus ?? a method extension that is not properly packaged? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 30, 2013

Re: [Pharo-project] [ANN] Pomodoro for Pharo 2.0

by phil＠highoctane.be

I like the icon :-) 2013/3/30 Sean P. DeNigris <sean(a)clipperadams.com> > philippeback wrote > > Of course not, I am using yours :-) > > </awkward moment> ;) > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/ANN-Pomodoro-for-Pharo-2-0-tp4678427p4678981.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

March 30, 2013

Re: [Pharo-project] starting a debugger on a caught error

by phil＠highoctane.be

self haltOnce and enabling the halt once in the world menu should help. That's how I debug these things on my side. Phil 2013/3/30 Ben Coman <btc(a)openinworld.com> > I am trying to debug a red-square-of-death for a Morph. I have found > where Morph errors are handled in Morph>>fullDrawOn: > where it goes... > [ "stuff to draw morphs" ] on: Error do: [ :err | "stuff to draw red > square" ]. > > In the do: block I'd like to open a debugger on the error. I see > Exception has #debug, so I changed the block to... > [ :err | err inspect. "stuff to draw red square" ] > ...and then in the inspector I do (self debug) > ...but this brings up the emergency evaluator. > > > Below is a contrived example that exhibits the same behaviour. > > doIt on... > (1 / 0. self inform: 'x'.) > and of course a debugger appears. > doIt on... > [ 1 / 0. self inform: 'x' . ] on: Error do: [:err | err inspect ] > ...and then (self debug) in the inspector you get the emergency evaluator. > Anyone know how can I get the debugger to come up on 'err' in the last > example? > > cheers -ben > > >

March 30, 2013

Re: [Pharo-project] Monkey Bait

by Sean P. DeNigris

Okay, thanks. And now I see how Fix Review Needed... I guess you have to click on Resolved first to see those statuses... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Monkey-Bait-tp4678991p4678994.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 30, 2013

Re: [Pharo-project] Monkey Bait

by Marcus Denker

On Mar 30, 2013, at 4:30 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Mar 30, 2013, at 4:29 PM, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > >> What status triggers the monkey? i.e. the new FixReviewNeeded >> >> > > The monkey is not yet trained for FogBugz. > If you have code that is ready for review (and soon the money), you need to put it on "review needed". FogBugz has 3 major states: Active, Resolved and Closed. To get from Active to a resolved state you need to press the "resolve" button, when you edit you can only move between the active states. Marcus

March 30, 2013

Re: [Pharo-project] Monkey Bait

by Marcus Denker

On Mar 30, 2013, at 4:29 PM, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > What status triggers the monkey? i.e. the new FixReviewNeeded > > The monkey is not yet trained for FogBugz. Marcus

March 30, 2013

[Pharo-project] Monkey Bait

by Sean P. DeNigris

What status triggers the monkey? i.e. the new FixReviewNeeded ----- Cheers, Sean -- View this message in context: http://forum.world.st/Monkey-Bait-tp4678991.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 30, 2013