- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Unsubscribing for Announcements

by Schwab,Wilhelm K

Two comments: (1) there needs to be a way to unregister interest; (2) the registrations need to be weak so that (1) is largely optional. If Dolphin has a weakness, it is that failure of an MVP triad to open can leave the system in a confused state. Morphic appears to be a little more robust about that, though in fairness, I do not push Pharo's GUI nearly as hard as I have Dolphin's. If in doubt, some type of #ifCurtailed: or similar protection around the assembly of a complex morph might be a good idea. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Sean P. DeNigris [sean(a)clipperadams.com] Sent: Monday, January 17, 2011 1:18 AM To: pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Unsubscribing for Announcements I really like Announcements! It's so much easier to update complex GUIs when you can pass state :) I hit one glitch when unsubscribing... The CollaborActive book suggests unsubscribing in #delete. For complex UIs, this doesn't seem to work because #delete is only called for the one morph that was deleted, not for its submorphs (which may need to unsubscribe). I tried this: MyMorph>>delete super delete. "Must come first. Deleting a submorph before self = emergency evaluator" aSubmorphThatNeedsToUnsubscribe delete. SubmorphMentionedAbove>>delete self inventory announcer unsubscribe: self. super delete. But it seems like a lot of work and coupling. Is there no hook that is guaranteed to be called when a morph is going away - i.e. it or a morph in the owner chain is being deleted? Thanks. Sean -- View this message in context: http://forum.world.st/Unsubscribing-for-Announcements-tp3220751p3220751.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 18, 2011

Re: [Pharo-project] [squeak-dev] more Info in aboutSqueak

by Alexander LazareviÄ

2011/1/17 Alexander LazareviÄ <laza(a)blobworks.com> > This very simple and needs to be polished further. > I brushed it up a little and I think it is in an usable state now. - use TextStream to have better formatting - fixed menus - preserve order of categories - split/added some more reports: - separate image parameters - separate vm options - source files - tiny benchmarks (to give a ballpark) - VM config (INI-file on windows only) Alex

Jan. 18, 2011

Re: [Pharo-project] Surprising binary messages!

by Pietro Maggi

On Tue, Jan 18, 2011 at 12:40 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> I'm just starting to learn smalltalk (thanks to PbE), but I'm pretty >> sure I know why this happens :-) > > Excellent! I like that our energy helps people. > It really does! Thanks to all the Pharo/Squeak community for the great effort. -- Pietro

Jan. 18, 2011

Re: [Pharo-project] Issue 3545 in pharo: FEATURE: Multiple Worlds

by pharo＠googlecode.com

Comment #1 on issue 3545 by sean.p.d...(a)gmail.com: FEATURE: Multiple Worlds http://code.google.com/p/pharo/issues/detail?id=3545 Fix in inbox: SLICE-Issue-3545-FEATURE-Multiple-Worlds-SeanDeNigris.1 Added multiple world support as discussed @ http://forum.world.st/Multiple-Worlds-was-Re-Can-I-use-Projects-in-Pharo-td… Cleaned up changeset from that post and PasteUpMorph (e.g. removed references to project) Add a world: WorldManager instance createOrSwitchToWorldNamed: 'JustAnotherWorld'. Return to the default world: WorldManager instance createOrSwitchToWorldNamed: 'Pharo'. This may need to be cleaned up e.g. should worlds be named, or numbered (like Mac Spaces)? Either way, maybe that attribute (or both) should be encapsulated in PasteUpMorph. But it's working, so we might as well play with it. Also, there were methods with no senders in the image (WorldManager>>switchToWorldNamed:, #createWorldNamed:, #switchToWorldNamed:, switchToWorldNamed:ifAbsent:, #worlds). I'm not sure if these methods were intended to be part of a user API or if they should be removed. Sean

Jan. 18, 2011

Re: [Pharo-project] Surprising binary messages!

by StÃ©phane Ducasse

> > I'm just starting to learn smalltalk (thanks to PbE), but I'm pretty > sure I know why this happens :-) Excellent! I like that our energy helps people. > Smalltalk has no knowledge of mathematics order, just operation order. > In this case + and / are both binary operators so the operations are > evaluated with the usual order, from left to right: > > (6 + 4) / 2 > > The answer 5 is correct. > > Regards > > Pietro >

Jan. 18, 2011

Re: [Pharo-project] Surprising binary messages!

by Igor Stasenko

On 18 January 2011 12:29, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > 5 is the surprising answer of the expression: > 6 + 4 / 2 > > It should be 8 > But, I got 5 in both 1.1 and 1.2. > this is first thing all smalltalkers learn: smalltalk syntax does not using math operators precedence rules. because #+ and #/ is just selectors and you can put any behavior to it not nearly related to math. > Noury > > > -- Best regards, Igor Stasenko AKA sig.

Jan. 18, 2011

Re: [Pharo-project] Metacello Help book in Pharo-Dev

by StÃ©phane Ducasse

ha! ok then On Jan 18, 2011, at 11:15 AM, Torsten Bergmann wrote: >> The problem is that we have 25 pages of metacello explanation before that >blog (which will be added to the book chapter). > > Hi Stef, > > I do not mean to add the blog contents! His latest blog post shows > a Pharo help book that is available as monticello documentation: > > See this screenshot: > http://gemstonesoup.files.wordpress.com/2011/01/screenshot.png > http://gemstonesoup.files.wordpress.com/2011/01/screenshot.png > http://gemstonesoup.files.wordpress.com/2011/01/profstef-tutorial.png > > and I ask if it would make sense to add it to Pharo-dev > by default or if one only gets it if he knows about Metacello > and how to load this book. > > Since it includes the API-Doc I think this would mean to > include Metacello too into Pharo-dev... > > Bye > T. > > > > > > -- > GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit > gratis Handy-Flat! http://portal.gmx.net/de/go/dsl >

Jan. 18, 2011

Re: [Pharo-project] Surprising binary messages!

by StÃ©phane Ducasse

but this is normal. It was always like that. No operator precedence just messages binary are evaluated from right to left 6 + 4 10 / 2 5 > 5 is the surprising answer of the expression: > 6 + 4 / 2 > > It should be 8 > But, I got 5 in both 1.1 and 1.2. > > Noury > >

Jan. 18, 2011

Re: [Pharo-project] Surprising binary messages!

by Pietro Maggi

On Tue, Jan 18, 2011 at 12:29 PM, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > 5 is the surprising answer of the expression: > 6 + 4 / 2 > > It should be 8 > But, I got 5 in both 1.1 and 1.2. > > Noury > Hi, I'm just starting to learn smalltalk (thanks to PbE), but I'm pretty sure I know why this happens :-) Smalltalk has no knowledge of mathematics order, just operation order. In this case + and / are both binary operators so the operations are evaluated with the usual order, from left to right: (6 + 4) / 2 The answer 5 is correct. Regards Pietro

Jan. 18, 2011

Re: [Pharo-project] Surprising binary messages!

by Tudor Girba

Why should it be 8? #+ and #/ have the same priority and they will be evaluated from left to right. Cheers, Doru On 18 Jan 2011, at 12:29, Noury Bouraqadi wrote: > 5 is the surprising answer of the expression: > 6 + 4 / 2 > > It should be 8 > But, I got 5 in both 1.1 and 1.2. > > Noury > > -- www.tudorgirba.com "The coherence of a trip is given by the clearness of the goal."

Jan. 18, 2011