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

Re: [Pharo-project] Pharo Kernel OSProcess evaluator

by Igor Stasenko

Pavel, could you provide some details, about where and how it could be used. And maybe some examples. Because its not clear , what is it. Because i think that most people get used to having an UI and using headless images is something much more complicated (since you cannot see what happens). On 10 August 2011 23:28, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > link: https://ci.lille.inria.fr/pharo/view/Pharo-Kernel/job/Pharo%20Kernel%20OSPr… > > On Wed, Aug 10, 2011 at 11:27 PM, Pavel Krivanek > <pavel.krivanek(a)gmail.com> wrote: >> Hi, >> >> I created a new job on CI server that creates a Pharo Kernel image >> with OSProcess loaded and simple console based evaluator. Of course >> something like Coral would be better ;-) >> >> Cheers >> -- Pavel >> > > -- Best regards, Igor Stasenko AKA sig.

Aug. 10, 2011

Re: [Pharo-project] got a surprising behavior

by Igor Stasenko

On 10 August 2011 23:33, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I got a really strange behavior: > Â Â Â Â I integrated > > Â Â Â Â - Â Issue 4607: Â Refactor Debugger >> content:notifying:. Thanks Camillo Bruni. > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4607 > > Â Â Â Â - Issue 4606: Fix drawing shadow of morphs. Thanks Igor Stasenko. > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4606 > > and I could not type enter on workspace > I could everywhere else. > > I could reopen a workspace and it worked and suddenly stopped again. > what i can say that apparently it has nothing to do with shadows. so blame mr. Camillo Bruni :) > > stef > -- Best regards, Igor Stasenko AKA sig.

Aug. 10, 2011

[Pharo-project] [update 1.4] #14080

by StÃ©phane Ducasse

14080 ----- - Issue 4607: Refactor Debugger >> content:notifying:. Thanks Camillo Bruni. http://code.google.com/p/pharo/issues/detail?id=4607 - Issue 4606: Fix drawing shadow of morphs. Thanks Igor Stasenko. http://code.google.com/p/pharo/issues/detail?id=4606 - Issue 4607: Minor-fix-to-the-old-MCMergeBrowser. Thanks Camillo Bruni. http://code.google.com/p/pharo/issues/detail?id=4601 more to come as soon as I get some sleep :) Stef

Aug. 10, 2011

[Pharo-project] got a surprising behavior

by StÃ©phane Ducasse

Hi guys I got a really strange behavior: I integrated - Issue 4607: Refactor Debugger >> content:notifying:. Thanks Camillo Bruni. http://code.google.com/p/pharo/issues/detail?id=4607 - Issue 4606: Fix drawing shadow of morphs. Thanks Igor Stasenko. http://code.google.com/p/pharo/issues/detail?id=4606 and I could not type enter on workspace I could everywhere else. I could reopen a workspace and it worked and suddenly stopped again. stef

Aug. 10, 2011

Re: [Pharo-project] Pharo Kernel OSProcess evaluator

by Pavel Krivanek

link: https://ci.lille.inria.fr/pharo/view/Pharo-Kernel/job/Pharo%20Kernel%20OSPr… On Wed, Aug 10, 2011 at 11:27 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > I created a new job on CI server that creates a Pharo Kernel image > with OSProcess loaded and simple console based evaluator. Of course > something like Coral would be better ;-) > > Cheers > -- Pavel >

Aug. 10, 2011

[Pharo-project] Pharo Kernel OSProcess evaluator

by Pavel Krivanek

Hi, I created a new job on CI server that creates a Pharo Kernel image with OSProcess loaded and simple console based evaluator. Of course something like Coral would be better ;-) Cheers -- Pavel

Aug. 10, 2011

Re: [Pharo-project] Strange bug in text selection

by StÃ©phane Ducasse

On Aug 10, 2011, at 5:21 PM, Igor Stasenko wrote: > which leads to #basicNew: primitive fail, because it passing a > negative number (no surprise, it fails). > > According to stack trace, > a > Text>> copyFrom:to: > is called with arguments: > > start = 100 > stop = 44 > (instead of having start = 44 , stop = 100) > > > it is called from MultiNewParagraph>>buildSelectionBlocksFrom:to: method. > I don't know whether we should fix this method, or maybe it is better > to fix #copyFrom:to: > to accept inverted ranges (a simple check if stop < start then swap > the end points) Igor I saw that someboyd (luarent may be) was proposing a solution > yet it hard to reproduce, it works ok most of the times :( > > To reproduce the bug, try to do following: > - open a new workspace window, type an arbitrary text there > - then drag a window to the bottom of desktop, so only title bar of > workspace remain visible > - release drag > - click on the title bar and start dragging it back to make text visible > > -- > Best regards, > Igor Stasenko AKA sig. >

Aug. 10, 2011

Re: [Pharo-project] Strange bug in text selection

by Lukas Renggli

Related, but likely a different bug: Text selections makes colors disappear http://code.google.com/p/pharo/issues/detail?id=4615 Lukas On 10 August 2011 17:21, Igor Stasenko <siguctua(a)gmail.com> wrote: > which leads to #basicNew: primitive fail, because it passing a > negative number (no surprise, it fails). > > According to stack trace, > a > Text>> copyFrom:to: > is called with arguments: > > start = 100 > stop = 44 > (instead of having start = 44 , stop = 100) > > > it is called from MultiNewParagraph>>buildSelectionBlocksFrom:to: method. > I don't know whether we should fix this method, or maybe it is better > to fix #copyFrom:to: > to accept inverted ranges (a simple check if stop < start then swap > the end points) > > > yet it hard to reproduce, it works ok most of the times :( > > To reproduce the bug, try to do following: > Â - open a new workspace window, type an arbitrary text there > Â - then drag a window to the bottom of desktop, so only title bar of > workspace remain visible > Â - release drag > Â - click on the title bar and start dragging it back to make text visible > > -- > Best regards, > Igor Stasenko AKA sig. > > -- Lukas Renggli www.lukas-renggli.ch

Aug. 10, 2011

[Pharo-project] Strange bug in text selection

by Igor Stasenko

which leads to #basicNew: primitive fail, because it passing a negative number (no surprise, it fails). According to stack trace, a Text>> copyFrom:to: is called with arguments: start = 100 stop = 44 (instead of having start = 44 , stop = 100) it is called from MultiNewParagraph>>buildSelectionBlocksFrom:to: method. I don't know whether we should fix this method, or maybe it is better to fix #copyFrom:to: to accept inverted ranges (a simple check if stop < start then swap the end points) yet it hard to reproduce, it works ok most of the times :( To reproduce the bug, try to do following: - open a new workspace window, type an arbitrary text there - then drag a window to the bottom of desktop, so only title bar of workspace remain visible - release drag - click on the title bar and start dragging it back to make text visible -- Best regards, Igor Stasenko AKA sig.

Aug. 10, 2011

[Pharo-project] We need to condense changes in 1.4

by Igor Stasenko

I think it is time to condense changes, because file is grown too large (28Mb) -- Best regards, Igor Stasenko AKA sig.

Aug. 10, 2011