- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Halt
by DeNigris Sean Aug. 29, 2011

Aug. 29, 2011

What is the purpose of #haltIf: aBlock? Right now, you can pass any of the following to Object>>haltIf: - aBlock taking an optional argument which is automatically set to the receiver of #halt - aSelector which looks up the call chain and halts if present - aBoolean So, whatever the condition is, it seems like you should be able to evaluate it in the calling context. When would you ever need to use a block? Can we eliminate the block behavior? Or, who has a great war story about blocks saving them from imminent doom... Thx. Sean

2 1

Re: [Pharo-project] Halt
by Marcus Denker Aug. 29, 2011

Aug. 29, 2011

On Aug 28, 2011, at 7:24 PM, Sean P. DeNigris wrote: > > 2. Using Object to halt causes bloat, and doesn't buy much (except that's > how we've always done it). Back in the days, we were virtually crucified for introducing the Beeper class along the same reasoning... The Beeper actually got very depressed due to having his very existance being questioned. "I am just the result of a random refactoring" he was complaining "maybe I should just just delete myself and everyone will be happy". (you know, reflection *is* dangerous! There has been a lot of talk to make reflection more secure... for a reason!). To cheer him up, I gave him the lead role in a real, peer reviewed Paper: http://scg.unibe.ch/archive/papers/Denk08bMetaContextLNBIP.pdf The Beeper thus was the first Class to be really "Meta" in the history of Objects. What a thrill. In an interview, the Beeper said: "You know, being meta is hard to decribe... Classes claim to be Meta all the time. But I doubt they ever really are Meta. Being Meta is special. The whole System looks different when meta!" ;-) -- Marcus Denker -- http://marcusdenker.de

8 17

Re: [Pharo-project] [ANN] glamorous inspector
by Tudor Girba Aug. 29, 2011

Aug. 29, 2011

Hi, There are a couple of improvements related to the GT Inspector: - A morph has a dedicated submorphs tab with which we can inspect the tree of morphs (see attached picture) - A parse tree has a dedicated view that provides a tree of RB nodes and previews the information as a selection on the method source code (see the attached picture) - On the top right there is a refresh button to update the inspector (it does not happen automatically) - Damien Cassou fixed the "do it" support in the evaluator so now you can use the default keys as in the workspace - Some more relevant menu items for manipulation Cheers, Doru On 24 Aug 2011, at 11:12, Tudor Girba wrote: > The GT Inspector is now available by default in the Moose image (CMD+Shift+i). > > It seems to work quite well. > > Cheers, > Doru > > > On 22 Aug 2011, at 22:59, StÃ©phane Ducasse wrote: > >> Thanks doru :) >> >> Stef >> >> On Aug 22, 2011, at 7:59 PM, Tudor Girba wrote: >> >>> Hi, >>> >>> I am happy to announce the first release of the Glamorous Inspector, a new browser for inspecting objects based on Glamour. >>> >>> More information, including a demo and screenshots, can be found here: >>> http://www.humane-assessment.com/blog/glamorous-inspector-for-smalltalk >>> >>> To download it follow the instructions from: >>> http://www.moosetechnology.org/tools/glamoroustoolkit >>> >>> You can use it by: >>> 1. "GTInspector openOn: someObject", or >>> 2. "GTInspector registerToolsOn: Smalltalk tools" and then use CMD+I (explore) >>> >>> Please let your opinion be heard :) >>> >>> Cheers, >>> Doru >>> >>> p.s. Have fun at ESUG :) >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every successful trip needs a suitable vehicle." >>> >>> >> > > -- > www.tudorgirba.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > > > -- www.tudorgirba.com "Some battles are better lost than fought."

2 2

Re: [Pharo-project] Halt
by Marcus Denker Aug. 29, 2011

Aug. 29, 2011

On Aug 29, 2011, at 11:48 AM, Sean P. DeNigris wrote: > > Sean P. DeNigris wrote: >> >> 3. Is anyone using the versions that take a string message (e.g. >> #haltOnce:). A halt brings you into a debugger, so is the extra info worth >> the added complexity? p.s. right now, the versions are cut-and-pastes of >> each other >> > > What about the versions that take a string message? Can we remove them since > we have the call stack open in a debugger anyway? > Yes, I would say remove. -- Marcus Denker -- http://marcusdenker.de

3 2

Re: [Pharo-project] Halt
by Marcus Denker Aug. 28, 2011

Aug. 28, 2011

On Aug 28, 2011, at 8:10 PM, Lukas Renggli wrote: > We have a class Halt and the class-side is empty. This seems to be the > right place to hold all the code in the protocols #debugging and > #debuggin-haltonce of Object. With a few renames we could get a really > nice DSL: > > Halt now. > Halt if: a = 2. > Halt once. > Nice! I want that. This would even allow for making the #haltIf: less overloaded and provide a explicit control flow based halt with something like this: Halt selector: #DoIt. or maybe better: Halt ifCalledFrom: #testMyWonderfulBuggyTest Marcus -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] What does FixedWaitingToBePharoed mean?
by Sean P. DeNigris Aug. 28, 2011

Aug. 28, 2011

-- View this message in context: http://forum.world.st/What-does-FixedWaitingToBePharoed-mean-tp3774520p3774… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1

[Pharo-project] PharoInbox broken?
by Sean P. DeNigris Aug. 28, 2011

Aug. 28, 2011

I'm getting an authentication error when trying to upload to PharoInbox and it is listed read-only on sqs. Sean -- View this message in context: http://forum.world.st/PharoInbox-broken-tp3774478p3774478.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 3

[Pharo-project] Plan for releases: after 1.4 I propose that we do a stabilization release
by StÃ©phane Ducasse Aug. 28, 2011

Aug. 28, 2011

Hi guys I was thinking about our process and I was thinking that it would be good to have a release where we only focus on bugs and regression testing. So what I see is that for 1.4 we will have FS Nautilus OPAL SystemAnnouncement (may be RPackage) Ring So this will be a lot. So we could have 1.5 where we take the time to let the bugs popping up and get fixed. We would concentrate also on external packages and libraries like a UIBuilder. Bootstrap. I'm not sure that the proposed idea may work but we should give a try. Stef

5 4

[Pharo-project] squeaksource is down
by Alexandre Bergel Aug. 28, 2011

Aug. 28, 2011

Can someone fix this? We are stuck in the middle of fixing the moose configuration because of this :-( Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

4 4

[Pharo-project] #name
by Sean P. DeNigris Aug. 27, 2011

Aug. 27, 2011

How is #name used by the system? I often want to use it in my classes, but I don't want to mess with whatever Object is doing with it. There are +++ senders. On the flip side, should the system use a different, more specific, intention-revealing selector to avoid this confusion? Thanks. Sean -- View this message in context: http://forum.world.st/name-tp3739677p3739677.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

9 11