September 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] Why using Sensor instead of World activeHand in Morph code?

by StÃ©phane Ducasse

Morph>>doFastReframe: ptName | newBounds | "For fast display, only higlight the rectangle during loop" newBounds := self boundsInWorld newRectButtonPressedDo: [:f | f withSideOrCorner: ptName setToPoint: Sensor cursorPoint minExtent: self minimumExtent]. Display deferUpdatesIn: Display boundingBox while: [ self bounds: newBounds]. ^newBounds. Stef

Sept. 7, 2011

Re: [Pharo-project] Fwd: A new way to render the debugger

by Noury Bouraqadi

I like it. On 7 sept. 2011, at 18:09, Benjamin wrote: > Hello guys, > > Camillo and I were looking for a way to improve the way the debugger show the stack, so we worked on a tabbed version of the list. Here is a screenshot: > > <Screen shot 2011-09-07 at 4.56.06 PM.png> > > > And so we implement the same on senders/implementors :) > > Do you like it ? (Should it be integrated ?) > > Thanks in advance for your feedback, > > > Ben > Noury Bouraqadi http://twitter.com/#!/NouryBouraqadi -- -19Ã¨mes JournÃ©es Francophones sur les SystÃ¨mes Multi-Agents (JFSMAâ11) http://www.univ-valenciennes.fr/congres/jfsma2011/ 17-19 Octobre 2011, Valenciennes, France -5th International Conference on Smalltalk Technologies http://www.fast.org.ar November 3th - 5th, 2011 Universidad Nacional de Quilmes (Argentina)

Sept. 7, 2011

Re: [Pharo-project] Fwd: A new way to render the debugger

by Michael Roberts

if you could select different rendering of that area that would be nice (e.g on context menu). i would add an option to display it in a table widget. it could allow simple filtering & sorting etc, assuming we had such a widget (essential really) . that would allow compact but powerful slicing of the data presented... cheers, Mike On Wed, Sep 7, 2011 at 7:30 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Looks good! > Now that you're into it, maybe coloring the frames that are not "interesting" would be a valuable addition. For example, putting in light gray all the frame that belong to Kernel and Collection, since it is unlikely that one will ever be interested in those. > > Cheers, > Alexandre > > > On 7 Sep 2011, at 13:09, Benjamin wrote: > >> Hello guys, >> >> Camillo and I were looking for a way to improve the way the debugger show the stack, so we worked on a tabbed version of the list. Here is a screenshot: >> >> <Screen shot 2011-09-07 at 4.56.06 PM.png> >> >> >> And so we implement the same on senders/implementors :) >> >> Do you like it ? (Should it be integrated ?) >> >> Thanks in advance for your feedback, >> >> >> Ben >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel Â http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > >

Sept. 7, 2011

Re: [Pharo-project] [BUG]Socket(Object)>>primitiveFailed:

by laurent laffont

On Wed, Sep 7, 2011 at 9:45 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > > On Sep 7, 2011, at 9:32 PM, laurent laffont wrote: > > > On Wed, Sep 7, 2011 at 9:04 PM, Sven Van Caekenberghe <sven(a)beta9.be> > wrote: > > Hi Laurent, > > > > On 07 Sep 2011, at 20:24, laurent.laffont(a)gmail.com wrote: > > > > > here insert explanation of what you were doing, suspect changes you've > > > made and so forth. > > > > > > Haha I haven't seen the mail will go the list :) First time I use the > mail out function. > > > > Anyway some explanations because this has corrupted my image. > > > > On SmallHarbour we use a modified VM (only SecurityPlugin - > https://gitorious.org/~laurentlaffont/cogvm/smallharbour ) so an image > can open only a given set of ports. Each image / account has an allocated > port number, so when an image starts a .st file is given as argument which > stop all seaside adaptors and then start Zinc Seaside adaptor on a given > port. > > > > The problem is: if I have saved a image with a socket opened on port XX, > then try to start it on SmallHarbour on port YY - given that XX is forbidden > - image crashes. > > It would be good that it does not crash :) > do not mean crash or shutdown nicely. > I mean if you are not in headless does it crash? > Yes it crashes only in headless mode - the (not so?) funny thing is that daemontools restart it immediately, then crash, restart, crash, restart .... huge PharoDebug.log :) With display the debugger pops up with the stack trace that was sent. Laurent > > > > > > > What were you doing ? > > Is this something reproduceable ? > > > > Yes. > > > > > > Is this in a standard 1.3 or did you somehow upgrade Zn to the latest > version ? > > > > It's a 3 weeks old Pier 2 image from Lukas Jenkins server so I first want > to get latest one and check if the problem is still here. > > > > > > Doing so might help (the primitive failed on close, flush is now > swallowed). > > > > > > OK thanks. > > > > Laurent. > > > > > > Sven > > > > > > > > > > >

Sept. 7, 2011

Re: [Pharo-project] [BUG]Socket(Object)>>primitiveFailed:

by StÃ©phane Ducasse

On Sep 7, 2011, at 9:32 PM, laurent laffont wrote: > On Wed, Sep 7, 2011 at 9:04 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > Hi Laurent, > > On 07 Sep 2011, at 20:24, laurent.laffont(a)gmail.com wrote: > > > here insert explanation of what you were doing, suspect changes you've > > made and so forth. > > > Haha I haven't seen the mail will go the list :) First time I use the mail out function. > > Anyway some explanations because this has corrupted my image. > > On SmallHarbour we use a modified VM (only SecurityPlugin - https://gitorious.org/~laurentlaffont/cogvm/smallharbour ) so an image can open only a given set of ports. Each image / account has an allocated port number, so when an image starts a .st file is given as argument which stop all seaside adaptors and then start Zinc Seaside adaptor on a given port. > > The problem is: if I have saved a image with a socket opened on port XX, then try to start it on SmallHarbour on port YY - given that XX is forbidden - image crashes. It would be good that it does not crash :) do not mean crash or shutdown nicely. I mean if you are not in headless does it crash? > > > What were you doing ? > Is this something reproduceable ? > > Yes. > > > Is this in a standard 1.3 or did you somehow upgrade Zn to the latest version ? > > It's a 3 weeks old Pier 2 image from Lukas Jenkins server so I first want to get latest one and check if the problem is still here. > > > Doing so might help (the primitive failed on close, flush is now swallowed). > > > OK thanks. > > Laurent. > > > Sven > > > >

Sept. 7, 2011

Re: [Pharo-project] [COTDC] 80#3 - TestRunnerBrowser

by laurent laffont

Today: TestRunnerBrowser Laurent On Tue, Sep 6, 2011 at 7:59 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > > Today: RBSubclassOfClassToRename > > Laurent > > > On Mon, Sep 5, 2011 at 9:55 PM, laurent laffont <laurent.laffont(a)gmail.com > > wrote: > >> Today: CategoryEnvironment >> >> >> Comment Of The Day Contest - One Day One Comment >> Rules: >> #1: Each day a not commented class is elected. Each day the best comment >> will be integrated with name of the author(s). >> #2: If you cannot comment it, deprecate it. >> Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest >> >> Laurent >> > > >

Sept. 7, 2011

Re: [Pharo-project] [BUG]Socket(Object)>>primitiveFailed:

by laurent laffont

On Wed, Sep 7, 2011 at 9:04 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > Hi Laurent, > > On 07 Sep 2011, at 20:24, laurent.laffont(a)gmail.com wrote: > > > here insert explanation of what you were doing, suspect changes you've > > made and so forth. > > Haha I haven't seen the mail will go the list :) First time I use the mail out function. Anyway some explanations because this has corrupted my image. On SmallHarbour we use a modified VM (only SecurityPlugin - https://gitorious.org/~laurentlaffont/cogvm/smallharbour ) so an image can open only a given set of ports. Each image / account has an allocated port number, so when an image starts a .st file is given as argument which stop all seaside adaptors and then start Zinc Seaside adaptor on a given port. The problem is: if I have saved a image with a socket opened on port XX, then try to start it on SmallHarbour on port YY - given that XX is forbidden - image crashes. What were you doing ? > Is this something reproduceable ? > Yes. > > Is this in a standard 1.3 or did you somehow upgrade Zn to the latest > version ? > It's a 3 weeks old Pier 2 image from Lukas Jenkins server so I first want to get latest one and check if the problem is still here. Doing so might help (the primitive failed on close, flush is now swallowed). > > OK thanks. Laurent. > Sven > > > >

Sept. 7, 2011

[Pharo-project] About at: in diplayProgress bar and multiLineRequest: queryString centerAt: aPoint initialAnswer: defaultAnswer answerHeight: answerHeight

by StÃ©phane Ducasse

Hi guys we will deprecate the usage of a location in progress bar and multiLineRequest: queryString centerAt: aPoint initialAnswer: defaultAnswer answerHeight: answerHeight because: - it is not really good that tools have to make reference to Sensor (which we should avoid and we will chase reference to Sensor) or to World activeHand cursorPosition and let the UIManager decides where to place the widgets - apparently multiLineRequest: queryString centerAt: aPoint initialAnswer: defaultAnswer answerHeight: answerHeight does not use the argument of centerAt: Let me know what you think. Such change will help clarifying layers. Stef

Sept. 7, 2011

Re: [Pharo-project] [BUG]Socket(Object)>>primitiveFailed:

by Sven Van Caekenberghe

Hi Laurent, On 07 Sep 2011, at 20:24, laurent.laffont(a)gmail.com wrote: > here insert explanation of what you were doing, suspect changes you've > made and so forth. What were you doing ? Is this something reproduceable ? Is this in a standard 1.3 or did you somehow upgrade Zn to the latest version ? Doing so might help (the primitive failed on close, flush is now swallowed). Sven

Sept. 7, 2011

Re: [Pharo-project] Fwd: A new way to render the debugger

by Alexandre Bergel

Looks good! Now that you're into it, maybe coloring the frames that are not "interesting" would be a valuable addition. For example, putting in light gray all the frame that belong to Kernel and Collection, since it is unlikely that one will ever be interested in those. Cheers, Alexandre On 7 Sep 2011, at 13:09, Benjamin wrote: > Hello guys, > > Camillo and I were looking for a way to improve the way the debugger show the stack, so we worked on a tabbed version of the list. Here is a screenshot: > > <Screen shot 2011-09-07 at 4.56.06 PM.png> > > > And so we implement the same on senders/implementors :) > > Do you like it ? (Should it be integrated ?) > > Thanks in advance for your feedback, > > > Ben > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 7, 2011