September 2015 - Pharo-users

Re: [Pharo-users] Morph: event handler on wrong morph/submorph

by Federico.Balaguer

Thanks for the reply. Federico -- View this message in context: http://forum.world.st/Morph-event-handler-on-wrong-morph-submorph-tp4852370… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 28, 2015

Re: [Pharo-users] Morph: event handler on wrong morph/submorph

by Federico.Balaguer

Thanks a lot! Federico -- View this message in context: http://forum.world.st/Morph-event-handler-on-wrong-morph-submorph-tp4852370… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 28, 2015

Re: [Pharo-users] not yet / should be implemented

by Thierry Goubier

Le 28/09/2015 21:53, Peter UhnÃ¡k a Ã©crit : > On Mon, Sep 28, 2015 at 9:36 PM, Thierry Goubier > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: > > Le 28/09/2015 21:09, Peter UhnÃ¡k a Ã©crit : > > What is the difference? > > âââââââââââââââââââââââââââââââââââââ > *ShouldBeImplemented* > * > * > I am ShouldBeImplemented, an exception signaled when some method > should > have been implemented but was not. > > > Usually in a abstract class to signal that a concrete subclass > should have implemented that method... defines the API all > subclasses must answer to. > > > Well the abstract class uses SubclassResponsibility; > SBI is autogenerated by debugger and Class Refactoring > Realize. Yes, you're right. I tend to mix the two :( > Hum, should be and not yet have different semantics. > > > Oh, so it's actually ShouldHaveBeenImplemented (past tense --- as in: > "it was supposed to be already done"). > > so > > ShouldBeImplemented - this was supposed to be already implemented > NotYetImplemented - this will be implemented in very soon Would be interesting to see that in code, to have a feel about how to use it. Thierry > Okay, now understand it. > > Thanks :) > > Peter

Sept. 28, 2015

Re: [Pharo-users] Morph: event handler on wrong morph/submorph

by Nicolai Hess

2015-09-28 18:59 GMT+02:00 Federico.Balaguer <federico.balaguer(a)gmail.com>: > Hello, > > I found a problem with BotArena > (http://smalltalkhub.com/#!/~FedericoBalaguer/BotArena) on Pharo 4. > > BotArena is an interactive robot simulation environment that we use in my > university to teach OOP basics. BotArena was developed as an instantiation > of BOSS (http://smalltalkhub.com/#!/~CAR/BOSS/) > > BotArena (as well as BOSS) has a window (Morph) that has three buttons and > a > grid view that is subclass of BorderedMorph. The GridView can handle > RedButtons, a click on the grid adds a new robot to the simulation. > > The problem that raised on Pharo4 is that, after a RedButton event, any > event (focus to another pharo window or clicking on one of the buttons of > BotArena) will be handled by the GridView. > > It seems like the GridView retains the focus after the (first) RedButton > event was handled. > > Could someone help me to sort this one out? > Quick solution: use self on: #click send: #mouseDownEvt: to: self. in BotArenaGridView for registering the event dispatcher. The problem is a change I did in 40422. I tried to fix another issue with for the #click action. Now we have to find a solution that works for both, #mouseDown and #click. nicolai > > Thanks! Federico > > > > -- > View this message in context: > http://forum.world.st/Morph-event-handler-on-wrong-morph-submorph-tp4852370… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Sept. 28, 2015

Re: [Pharo-users] not yet / should be implemented

by Peter UhnÃ¡k

> > Oh, so it's actually ShouldHaveBeenImplemented (past tense --- as in: "it > was supposed to be already done"). > quoting from the comment "exception signaled when some method *should have been implemented* but was not" So I guess I'm blind because I read it several times but the brain didn't see it.

Sept. 28, 2015

Re: [Pharo-users] not yet / should be implemented

by Peter UhnÃ¡k

On Mon, Sep 28, 2015 at 9:36 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Le 28/09/2015 21:09, Peter UhnÃ¡k a Ã©crit : > >> What is the difference? >> >> âââââââââââââââââââââââââââââââââââââ >> *ShouldBeImplemented* >> * >> * >> I am ShouldBeImplemented, an exception signaled when some method should >> have been implemented but was not. >> > > Usually in a abstract class to signal that a concrete subclass should have > implemented that method... defines the API all subclasses must answer to. > Well the abstract class uses SubclassResponsibility; SBI is autogenerated by debugger and Class Refactoring > Realize. > Hum, should be and not yet have different semantics. > Oh, so it's actually ShouldHaveBeenImplemented (past tense --- as in: "it was supposed to be already done"). so ShouldBeImplemented - this was supposed to be already implemented NotYetImplemented - this will be implemented in very soon Okay, now understand it. Thanks :) Peter

Sept. 28, 2015

Re: [Pharo-users] Pharo - database without database

by Adam

Hello, Yes, I was confused by some old discussion. New licence is different. Thanks for correction. Adam. Dne Po 28. zÃ¡ÅÃ 2015 12:17:19, Stephan Eggermont napsal(a): > On 27-09-15 18:47, Adam wrote: > > 1) Object memory limit: Current object memory of Pharo is limited to 4GB. > > Free version of GemStone/S is also limited to 4GB, so I would rather > > stick with Pharo until I reach this level. And in the future this limit > > grow due to 64bit version of VM. > > The information on GemStone seems incorrect. > https://gemtalksystems.com/licensing/ > What I read there is that the Limited (email address required) license > supports 50 GB of (on-disk) objects, with a 2GB shared page cache. > > Stephan

Sept. 28, 2015

Re: [Pharo-users] not yet / should be implemented

by Thierry Goubier

Le 28/09/2015 21:09, Peter UhnÃ¡k a Ã©crit : > What is the difference? > > âââââââââââââââââââââââââââââââââââââ > *ShouldBeImplemented* > * > * > I am ShouldBeImplemented, an exception signaled when some method should > have been implemented but was not. Usually in a abstract class to signal that a concrete subclass should have implemented that method... defines the API all subclasses must answer to. > This is more like a placeholder during development. > âââââââââââââââââââââââââââââââââââââ > *NotYetImplemented* > > I am NotYetImplement, an exception signaled when a method is a stub for > code that will be implemented in the future. Pre-defines an API with a TODO: Implement Later. > This is used in incremental development, for example when doing Test > First development. > It is similar to ShouldBeImplemented, with a slightly different meaning. > âââââââââââââââââââââââââââââââââââââ > > There seem to be some slight semantic difference but I'm failing to see it. > I can even say "The method should be implemented, but is not yet > implemented." It's saying the same thing with different words. Hum, should be and not yet have different semantics. Thierry > > Thanks, > Peter

Sept. 28, 2015

not yet / should be implemented

by Peter UhnÃ¡k

What is the difference? âââââââââââââââââââââââââââââââââââââ *ShouldBeImplemented* I am ShouldBeImplemented, an exception signaled when some method should have been implemented but was not. This is more like a placeholder during development. âââââââââââââââââââââââââââââââââââââ *NotYetImplemented* I am NotYetImplement, an exception signaled when a method is a stub for code that will be implemented in the future. This is used in incremental development, for example when doing Test First development. It is similar to ShouldBeImplemented, with a slightly different meaning. âââââââââââââââââââââââââââââââââââââ There seem to be some slight semantic difference but I'm failing to see it. I can even say "The method should be implemented, but is not yet implemented." It's saying the same thing with different words. Thanks, Peter

Sept. 28, 2015

Re: [Pharo-users] Morph: event handler on wrong morph/submorph

by Federico.Balaguer

Hello Stephan, the following line will open the tool I was referring to: BGSArenaWindow expertViewOn: (OnTheFlyConfigurableSimulation endlessWalkingBrush). There is two ways to add a new robot: 1. Click on the Add Robot button, which has no problem 2. Click on the grid Regards. Federico -- View this message in context: http://forum.world.st/Morph-event-handler-on-wrong-morph-submorph-tp4852370… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Sept. 28, 2015