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

[Pharo-project] [update 1.3] #13004

by Marcus Denker

13004 ----- Issue 3558: Delete empty package ScriptLoader12. Issue 3552: Delete Package DeleteMe Issue 3550: MenuItemMorph>>mouseDown: has unnecessary check Issue 3468: Perform and context frame size primitive tests Issue 3441: Tests for Polymorph Issue 3378: Process remove depende to UIManager Issue 3557: [Feature]: Setting for easy select i.e. selecting in the world by dragging -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 20, 2011

Re: [Pharo-project] Issue 3550 in pharo: MenuItemMorph>>mouseDown: has unnecessary check

by pharo＠googlecode.com

Updates: Status: Closed Comment #3 on issue 3550 by marcus.d...(a)gmail.com: MenuItemMorph>>mouseDown: has unnecessary check http://code.google.com/p/pharo/issues/detail?id=3550 13004

Jan. 20, 2011

Re: [Pharo-project] splitters in table layout

by StÃ©phane Ducasse

On Jan 20, 2011, at 12:43 PM, Gary Chambers wrote: > The attached changeset will "fix" this, though perhaps not ideal... > > Perhaps it is time to refactor all the Resizer stuff! yes please for 1.3. Stef > > Regards, Gary > > > ----- Original Message ----- From: "Tudor Girba" <tudor.girba(a)gmail.com> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Thursday, January 20, 2011 11:17 AM > Subject: Re: [Pharo-project] splitters in table layout > > > What does this imply? > > Cheers, > Doru > > > On 20 Jan 2011, at 12:09, Gary Chambers wrote: > >> Missed the case where fast dragging setting is enabled.... >> >> Regards, Gary >> >> ----- Original Message ----- From: "Andreas Wacknitz" <a.wacknitz(a)gmx.de> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Tuesday, January 18, 2011 8:33 PM >> Subject: Re: [Pharo-project] splitters in table layout >> >> >> >> Am 18.01.2011 um 20:58 schrieb Tudor Girba: >> >>> Yes, you missed a changeset Gary sent in the aligning morphs thread (he actually sent two, and you should pick the second one). >>> >>> Cheers, >>> Doru >>> >> Ah, thank you. I have found two messages with changesets from January 11th, 2011. >> After I filein the second changeset alas I will get a DNU Morph>>doFastWindowReframe: when I move the splitter... >> >> Regards, >> Andreas >> >> >> > > -- > www.tudorgirba.com > > "Reasonable is what we are accustomed with." > > <EdgeGripFastReframeFix.1.cs>

Jan. 20, 2011

Re: [Pharo-project] Issue 3552 in pharo: Delete Package "DeleteMe"

by pharo＠googlecode.com

Comment #3 on issue 3552 by marcus.d...(a)gmail.com: Delete Package "DeleteMe" http://code.google.com/p/pharo/issues/detail?id=3552 in 1.3 13004 TODO: 1.2

Jan. 20, 2011

Re: [Pharo-project] Issue 3558 in pharo: Delete empty package 'ScriptLoader12'.

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3558 by marcus.d...(a)gmail.com: Delete empty package 'ScriptLoader12'. http://code.google.com/p/pharo/issues/detail?id=3558 13004

Jan. 20, 2011

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by Benjamin

Strange ... For PluggableShoutMorph, all the expected behavior is now in PluugableTextMorph, so I will try to remove everything, just to see if it works ^^ (but first let's finish the list stuff ;) ) Ben On Jan 20, 2011, at 11:51 AM, StÃ©phane Ducasse wrote: > Yes we should do that. > let it and deprecate all the methods or remove the methods if they are in the superclass. > Ben apparently monticello is bogus and the methods we moved from *soup to soup were removed from the class :( > > Stef > > On Jan 20, 2011, at 11:19 AM, Benjamin wrote: > >> Yes, code depends of this class, but this class inherits from PluggableTextMorph, so we can just remove everything in it, and just keep the name to keep the system working (and maybe move this class in the package Deprecated) >> >> >> Ben >> >> On Jan 20, 2011, at 11:09 AM, Tudor Girba wrote: >> >>> Yes, but I guess code still depends on this class. So, at the very least the class should still be preserved for one version. >>> >>> Cheers, >>> Doru >>> >>> >>> On 20 Jan 2011, at 11:05, Benjamin wrote: >>> >>>> In fact, PluggableShoutMorph shouldn't be used anymore, but PluggableTextMorph instead now that PluggableTextMorph handle the text styling :) >>>> >>>> >>>> Ben >>>> >>>> >>>> On Jan 20, 2011, at 9:34 AM, Tudor Girba wrote: >>>> >>>>> We probably need to remove that variable from PluggableShoutMorph. This variable does not exist in Pharo 1.2 12292. >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>> On 20 Jan 2011, at 09:11, laurent laffont wrote: >>>>> >>>>>> Other error: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/71/console >>>>>> >>>>>> >>>>>> duplicatedVariableError: styler is already defined in PluggableTextMorph >>>>>> >>>>>> >>>>>> Laurent >>>>>> >>>>>> On Thu, Jan 20, 2011 at 8:38 AM, Tudor Girba <tudor.girba(a)gmail.com> wrote: >>>>>> Thanks Laurent and Alain for testing this. >>>>>> >>>>>> Cheers, >>>>>> Doru >>>>>> >>>>>> >>>>>> On 20 Jan 2011, at 08:21, Alain Plantec wrote: >>>>>> >>>>>>> the same here, it works. >>>>>>> Now I can load Petit. >>>>>>> Thanks >>>>>>> Alain >>>>>>> >>>>>>> Le 20/01/2011 08:08, laurent laffont a Ã©crit : >>>>>>>> It works ! It works ! >>>>>>>> >>>>>>>> Laurent >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> www.tudorgirba.com >>>>>> >>>>>> "Live like you mean it." >>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "Presenting is storytelling." >>>>> >>>>> >>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "It's not how it is, it is how we see it." >>> >>> >> >> > >

Jan. 20, 2011

Re: [Pharo-project] Issue 3501 in pharo: Remove 1.1 deprecated methods and publish them in a separate package

by pharo＠googlecode.com

Comment #4 on issue 3501 by marcus.d...(a)gmail.com: Remove 1.1 deprecated methods and publish them in a separate package http://code.google.com/p/pharo/issues/detail?id=3501 Issue 2733 has been merged into this issue.

Jan. 20, 2011

Re: [Pharo-project] Issue 2733 in pharo: Remove deprecated methods from 1.1 in 1.3

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 3501 Comment #9 on issue 2733 by marcus.d...(a)gmail.com: Remove deprecated methods from 1.1 in 1.3 http://code.google.com/p/pharo/issues/detail?id=2733 (No comment was entered for this change.)

Jan. 20, 2011

Re: [Pharo-project] splitters in table layout

by Gary Chambers

The attached changeset will "fix" this, though perhaps not ideal... Perhaps it is time to refactor all the Resizer stuff! Regards, Gary ----- Original Message ----- From: "Tudor Girba" <tudor.girba(a)gmail.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Thursday, January 20, 2011 11:17 AM Subject: Re: [Pharo-project] splitters in table layout What does this imply? Cheers, Doru On 20 Jan 2011, at 12:09, Gary Chambers wrote: > Missed the case where fast dragging setting is enabled.... > > Regards, Gary > > ----- Original Message ----- From: "Andreas Wacknitz" <a.wacknitz(a)gmx.de> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Tuesday, January 18, 2011 8:33 PM > Subject: Re: [Pharo-project] splitters in table layout > > > > Am 18.01.2011 um 20:58 schrieb Tudor Girba: > >> Yes, you missed a changeset Gary sent in the aligning morphs thread (he >> actually sent two, and you should pick the second one). >> >> Cheers, >> Doru >> > Ah, thank you. I have found two messages with changesets from January > 11th, 2011. > After I filein the second changeset alas I will get a DNU > Morph>>doFastWindowReframe: when I move the splitter... > > Regards, > Andreas > > > -- www.tudorgirba.com "Reasonable is what we are accustomed with."

Jan. 20, 2011

Re: [Pharo-project] Issue 3544 in pharo: Rename Morphic-Themes into Themes

by pharo＠googlecode.com

Comment #1 on issue 3544 by marcus.d...(a)gmail.com: Rename Morphic-Themes into Themes http://code.google.com/p/pharo/issues/detail?id=3544 do we do that in 1.3?

Jan. 20, 2011