December 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo testers.... WE NEED YOU!!!

by Miguel CobÃ¡

> So...here is the list, if you offer yourself, it would be cool to know: OS, > VM version, Dev or Web,Â browser you usually work, 32 o 64 bits, > I will then collect this and I will put it in the wiki. > > - Mariano Martinez Peck.Â Mac OS, Squeak 4.2.2beta1U.app,Â Dev, OB, 32 bits > - Stan Shepherd > > > WHO ELSE IS IN THE LIST ?? Me too. - Miguel CobÃ¡, Debian GNU/Linux Squeeze (testing), Pharo0.1 of 16 May 2008 [latest update: #10074], Web, OB, 32 bits > > cheers and happy new year!! > Feliz aÃ±o tambiÃ©n Mariano. Miguel CobÃ¡ http://miguel.leugim.com.mx

Dec. 31, 2009

Re: [Pharo-project] Utilities >> startUp registration??

by Lukas Renggli

This is used for "Utilities recentMethodSubmissions". Some tools in the image still use it. The #update: part was used by Monticello to track method changes, but is no longer active (but the code is still there). Lukas 2009/12/31 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > does anybody know if this is of any use? > > > startUp > Â Â Â Â SystemChangeNotifier uniqueInstance notify: self ofAllSystemChangesUsing: #event:. > > > event: anEvent > Â Â Â Â "Hook for SystemChangeNotifier" > > Â Â Â Â (anEvent isCommented and: [anEvent itemKind = SystemChangeNotifier classKind]) > Â Â Â Â Â Â Â Â ifTrue: [self noteMethodSubmission: #Comment forClass: anEvent item]. > Â Â Â Â ((anEvent isAdded or: [anEvent isModified]) and: [anEvent itemKind = SystemChangeNotifier methodKind]) > Â Â Â Â Â Â Â Â ifTrue: [anEvent itemRequestor ifNotNil: [self noteMethodSubmission: anEvent itemSelector forClass: anEvent itemClass]]. > Â Â Â Â ((anEvent isAdded or: [anEvent isModified]) and: [anEvent itemKind = SystemChangeNotifier methodKind]) ifTrue:[ > Â Â Â Â Â Â Â Â InMidstOfFileinNotification signal > Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [Utilities changed: #recentMethodSubmissions]. > Â Â Â Â ]. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 31, 2009

[Pharo-project] [update 1.1] #11130

by StÃ©phane Ducasse

11130 ----- - Cleaning Utilities... yet another step in the right direction

Dec. 31, 2009

[Pharo-project] Utilities >> startUp registration??

by StÃ©phane Ducasse

does anybody know if this is of any use? startUp SystemChangeNotifier uniqueInstance notify: self ofAllSystemChangesUsing: #event:. event: anEvent "Hook for SystemChangeNotifier" (anEvent isCommented and: [anEvent itemKind = SystemChangeNotifier classKind]) ifTrue: [self noteMethodSubmission: #Comment forClass: anEvent item]. ((anEvent isAdded or: [anEvent isModified]) and: [anEvent itemKind = SystemChangeNotifier methodKind]) ifTrue: [anEvent itemRequestor ifNotNil: [self noteMethodSubmission: anEvent itemSelector forClass: anEvent itemClass]]. ((anEvent isAdded or: [anEvent isModified]) and: [anEvent itemKind = SystemChangeNotifier methodKind]) ifTrue:[ InMidstOfFileinNotification signal ifFalse: [Utilities changed: #recentMethodSubmissions]. ].

Dec. 31, 2009

Re: [Pharo-project] Solving the documentation problem. Capturing tacit knowledge. Knowledge reuse.

by StÃ©phane Ducasse

> > I have been 'overriding' the false positives with pragmas, as implemented by > Lukas. Works well, although it would be good if they had a separate area so > they don't become bigger than the code itself. yes this is the problem metadata. Stef

Dec. 31, 2009

[Pharo-project] [update 1.1] #11129

by StÃ©phane Ducasse

11129 ----- - Remove deprecated method from 1.0. Took 10501rc1 checked all the senders of deprecated: and removed the corresponding ones in 1.1

Dec. 31, 2009

Re: [Pharo-project] Solving the documentation problem. Capturing tacit knowledge. Knowledge reuse.

by csrabak＠bol.com.br

+1 Em 31/12/2009 16:30, Adrian Lienhard < adi(a)netstyle.ch > escreveu: What about using a wiki to gather and edit comments (as suggested by Stan) and then integrate them in a second step so that they are kept together with the code (as suggested by Stef)? Just a thought... Cheers Adrian

Dec. 31, 2009

Re: [Pharo-project] Solving the documentation problem. Capturing tacit knowledge. Knowledge reuse.

by csrabak＠bol.com.br

Em 31/12/2009 16:07, Stan Shepherd < stan.shepherd414(a)gmail.com > escreveu: > csrabak wrote: > > > > [snipped] > > > for info, I ran code critics on Lukas's quasi-release > http://www.seaside.st/distributions/Seaside-3.0a5.app.zip which is > essentially web dev without O2 I believe. (Code critics I can't get > to work in web dev) > Taking out spelling, there are about 30000 items flagged, of which > 4802 long methods. > In an ideal world, it would be nice if the whole image passed code > critics. I think that for starters we should put efforts in having this state of "cleanness" in the core image first! > > > - pick one aweek and via the mailing-list make it better and > > - after we integrate it. > Well the one that's entertaining me at the moment is JSObject, but > I imagine people would rather start with a core class?. Stan, Notwithstanding the truth of you assertion, I maintain that every effort it the right direction is a worthy contribution! -- Cesar Rabak

Dec. 31, 2009

Re: [Pharo-project] Beginner question :) search and replace in String

by csrabak＠bol.com.br

Em 31/12/2009 15:52, Adrian Kuhn <akuhn(a)iam.unibe.ch> escreveu: > > > > This brings to the forum an interesting debate! Clearly Levente's > > solution is the String redirection for Lukas' solution. > > Do this method eases programming for newcomers? Or it creates > > burden as presented in Stan's posting? > > AK is IIUC very knowledgeable of tools used in Squeak/Pharo and > > even though, had difficulty to find this particular method!! > Good point! > To replace parts of a string, I want to send a message to the > string not to the > regex. So without doubt, string should understand such a > messages. (I dont know to which posting of Stan you're referring > though). OK, so the redirection of the messages to String makes sense. I would only gripe about the protocol it appears right now: *vb-regex is the _implementation_ of the method's functionality, but from a [programer] user POV it would be more likely to another one (perhaps "searching and replace"). > Also, I would expect short message names for common > operations. Alas none of > > #copyWithRegex:matchesReplacedWith: asRegex + > ##copy:replacingMatchesWith: copyReplaceAll:with: > is particular short. And to make things words, none of these shows > up when auto > completing #repl... because they all start with copy. Plus strings > are nested in such a deep hierarchy that reading all understood > messages won't scale. Alas, I normally stay away of these discussions because I'm intoxicated by other programming idioms (like sed/AWK/Perl/Python/Ruby) which uses a very compact syntax for these operations and are now a lingua franca. > Personally, I would love to have a #gsub:with: on String. It is > short and uses established vocabulary. Yes it would be an adaptation of the above idioms to Smalltalk.

Dec. 31, 2009

Re: [Pharo-project] Fwd: New Year Edition :)

by Stan Shepherd

Happy new year, bonne annÃ©e etc to all. Thanks for everything in 2009. Cheers, ...Stan StÃ©phane Ducasse wrote: > > Hi > > I uploaded a core-image 11128 > https://gforge.inria.fr/frs/shownotes.php?release_id=4734 > > Stef > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- View this message in context: http://n2.nabble.com/Fwd-New-Year-Edition-tp4237122p4237716.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 31, 2009