- Pharo-dev - lists.pharo.org

Re: [Pharo-project] splitters in table layout

by Gary Chambers

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

Jan. 20, 2011

Re: [Pharo-project] aligning morphs

by Gary Chambers

Not yet. (gmail issues) .Go ahead though if you wish. Regards, Gary ----- Original Message ----- From: "Tudor Girba" <tudor.girba(a)gmail.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, January 18, 2011 7:44 PM Subject: Re: [Pharo-project] aligning morphs Hi Gary, Did you publish the changes to GeneralScrollPane somewhere? Cheers, Doru On 17 Jan 2011, at 12:07, Gary Chambers wrote: > It seems you are asking for the scroll value before the layout has been > calculated. > (since the window hasn't received a fullbounds yet). > > > | m scroll | > m := PanelMorph new. > m > hResizing: #shrinkWrap; > vResizing: #spaceFill; > changeTableLayout; > listDirection: #leftToRight. > m addMorphBack: (Morph new > minWidth: 100; > hResizing: #shrinkWrap; > vResizing: #spaceFill). > scroll := GeneralScrollPane new > changeScrollerTableLayout; > scrollTarget: m. > scroll openInWindow. > scroll hScrollbar setValue: 1.0. > m addMorphBack: (Morph new > minWidth: 100; > hResizing: #shrinkWrap; > vResizing: #spaceFill). > "Recalculate bounds now for this example... not generally needed for > normal code!" > scroll fullBounds. > "****" > scroll hScrollbar value > > Is not normally an issue, as you can see from inspecting the scroller > after being opened. > > Regards, Gary > > ----- Original Message ----- From: "Tudor Girba" <tudor.girba(a)gmail.com> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Sunday, January 16, 2011 10:56 AM > Subject: Re: [Pharo-project] aligning morphs > > > Hi Gary, > > I would like to implement a Finder-like behavior the GeneralScrollPane. > For this, I would need a way to control the scrolling so that every time I > add a new morph, the scroller scrolls (similar to > ScrollBar>>animateValue:duration: from OB). > > The problem seems to be that the scrollbar value is not updated when I add > a new morph. Take a look at the code below. The result of the horizontal > scrollbar value at the end is 1.0, while it should be lower. Am I doing > something wrong, or is this a problem? > > | m scroll | > m := PanelMorph new. > m > hResizing: #shrinkWrap; > vResizing: #spaceFill; > changeTableLayout; > listDirection: #leftToRight; > m addMorphBack: (Morph new > minWidth: 100; > hResizing: #shrinkWrap; > vResizing: #spaceFill). > scroll := GeneralScrollPane new > changeScrollerTableLayout; > scrollTarget: m. > scroll openInWindow. > scroll hScrollbar setValue: 1.0. > m addMorphBack: (Morph new > minWidth: 100; > hResizing: #shrinkWrap; > vResizing: #spaceFill). > scroll hScrollbar value > > ==> 1.0 > > Cheers, > Doru > > > > On 11 Jan 2011, at 15:17, Gary Chambers wrote: > >> A slight revision as this has highlighted an edge case in the original >> class >> as to when scrollbars are needed... >> >> Regards, Gary >> >> ----- Original Message ----- From: "Tudor Girba" <tudor.girba(a)gmail.com> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Tuesday, January 11, 2011 1:53 PM >> Subject: Re: [Pharo-project] aligning morphs >> >> >> Excellent! >> >> I tried the example and it works well. I will work with it in the >> following days. >> >> Cheers, >> Doru >> >> >> On 11 Jan 2011, at 14:39, Gary Chambers wrote: >> >>> Try the attached change set with the following example... >>> Let me know if any use and we'll get it integrated. >>> >>> |m| >>> m := PanelMorph new. >>> m >>> fillStyle: Color green; >>> hResizing: #spaceFill; >>> vResizing: #spaceFill; >>> changeTableLayout; >>> layoutInset: 8. >>> m addMorph: (Morph new >>> height: 160; >>> minWidth: 100; >>> hResizing: #spaceFill; >>> vResizing: #shrinkWrap). >>> GeneralScrollPane new >>> changeScrollerTableLayout; >>> scrollTarget: m; >>> openInWindow >>> >>> >>> Regards, Gary >>> >>> ----- Original Message ----- From: "Tudor Girba" <tudor.girba(a)gmail.com> >>> To: <Pharo-project(a)lists.gforge.inria.fr> >>> Sent: Monday, January 10, 2011 8:23 PM >>> Subject: Re: [Pharo-project] aligning morphs >>> >>> >>> Wow, that would be great! I cannot wait to test it. >>> >>> Cheers, >>> Doru >>> >>> >>> On 10 Jan 2011, at 16:50, Gary Chambers wrote: >>> >>>> I may get time later in the week to have a go with GeneralScrollPane to >>>> support the feature you desire... ;-) >>>> >>>> Regards, Gary >>>> >>>> ----- Original Message ----- From: "Tudor Girba" >>>> <tudor.girba(a)gmail.com> >>>> To: <Pharo-project(a)lists.gforge.inria.fr> >>>> Cc: <Pharo-project(a)lists.gforge.inria.fr> >>>> Sent: Monday, January 10, 2011 2:23 PM >>>> Subject: Re: [Pharo-project] aligning morphs >>>> >>>> >>>> Hi Gary, >>>> >>>> Thanks for the reply. >>>> >>>> So, what would be required for scrollbars to work with spaceFill? I >>>> would really need this feature, but I do not know how to go about it. >>>> >>>> Could you or anyone else provide some hints? Of course code would be >>>> even better. But at this moment hi ts would be helpful, too :) >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> >>>> On Jan 10, 2011, at 13:04, "Gary Chambers" <gazzaguru2(a)btinternet.com> >>>> wrote: >>>> >>>>> Hi Doru, >>>>> >>>>> #spaceFill constraints are typically only used by table layouts. >>>>> ScrollPane is designed for fixed size contents, at present. >>>>> Might be nice to extend it to honour any #spaceFill of its single >>>>> target morph. >>>>> This would simplify usage of scrollers quite a bit! >>>>> >>>>> Regards, Gary >>>>> >>>>> ----- Original Message ----- From: "Tudor Girba" >>>>> <tudor.girba(a)gmail.com> >>>>> To: "Pharo-project(a)lists.gforge.inria.fr Development" >>>>> <pharo-project(a)lists.gforge.inria.fr> >>>>> Sent: Saturday, January 08, 2011 1:22 AM >>>>> Subject: [Pharo-project] aligning morphs >>>>> >>>>> >>>>> >>>>> Hi, >>>>> >>>>> I would need help with understanding the magic behind alignment in >>>>> Morphic. >>>>> >>>>> Take the example from below. Could anyone help me with what I should >>>>> do to have the morph stretch all the way horizontally? >>>>> >>>>> | scroll window morph | >>>>> scroll := ScrollPane new. >>>>> scroll >>>>> fillStyle: (SolidFillStyle color: Color blue); >>>>> vResizing: #spaceFill; >>>>> hResizing: #spaceFill. >>>>> morph := PanelMorph new. >>>>> morph >>>>> fillStyle: (SolidFillStyle color: Color yellow); >>>>> changeTableLayout; >>>>> listDirection: #topToBottom; >>>>> vResizing: #shrinkWrap; >>>>> hResizing: #spaceFill; >>>>> layoutInset: 10. >>>>> morph addMorphBack: (SimpleButtonMorph new width: 200; height: 200). >>>>> scroll scroller addMorph: morph. >>>>> window := SystemWindow new. >>>>> window addMorph: scroll fullFrame: (LayoutFrame fractions: (0 @ 0 >>>>> corner: 1 @ 1)). >>>>> window openInWorld >>>>> >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "Every thing should have the right to be different." >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Problem solving efficiency grows with the abstractness level of problem >>> understanding." >>> >>> >>> >>> <GeneralScrollPaneLayout.1.cs> >> >> -- >> www.tudorgirba.com >> >> "Some battles are better lost than fought." >> >> >> >> <GeneralScrollPaneLayout.2.cs> > > -- > www.tudorgirba.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > > > > > -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

Jan. 20, 2011

Re: [Pharo-project] Issue 3554 in pharo: CP1252TextConverter new does not work

by StÃ©phane Ducasse

On Jan 20, 2011, at 11:34 AM, Henrik Johansen wrote: > > On Jan 20, 2011, at 10:59 10AM, StÃ©phane Ducasse wrote: > >> Do we need 1252 and 1250? > > ? Do we need converters for both? If we want to be able to read files saved in either character set, then yes. In fact I just check we already have them :) This is just that soup was reloading an old version of the same class and this was not good. > >> What is the difference? I saw 1253 is for greek > > http://en.wikipedia.org/wiki/Cp1250 > http://en.wikipedia.org/wiki/Cp1252 > > 5-line summaries at the top, you can see the specific differences in the tables. > >> >> Right now I change Soup to work with 1250 instead of an old bogus 1252 >> >> Stef > > I'm not sure what "work with" means in the context of Soup. you can parse the page. > Encoding in 1250 "works" fine if the non-english text you're writing is mostly Polish/Hungarian etc. > It's a bit less suited for say, norwegian or french, as it lacks characters like Ã¦, Ã¸, Ã¥ and Å,. thanks for the info. > > Cheers, > Henry >

Jan. 20, 2011

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

by StÃ©phane Ducasse

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 3554 in pharo: CP1252TextConverter new does not work

by Henrik Johansen

On Jan 20, 2011, at 10:59 10AM, StÃ©phane Ducasse wrote: > Do we need 1252 and 1250? ? Do we need converters for both? If we want to be able to read files saved in either character set, then yes. > What is the difference? I saw 1253 is for greek http://en.wikipedia.org/wiki/Cp1250 http://en.wikipedia.org/wiki/Cp1252 5-line summaries at the top, you can see the specific differences in the tables. > > Right now I change Soup to work with 1250 instead of an old bogus 1252 > > Stef I'm not sure what "work with" means in the context of Soup. Encoding in 1250 "works" fine if the non-english text you're writing is mostly Polish/Hungarian etc. It's a bit less suited for say, norwegian or french, as it lacks characters like Ã¦, Ã¸, Ã¥ and Å,. Cheers, Henry

Jan. 20, 2011

Re: [Pharo-project] Issue 3440 in pharo: Cycle in Monticello removed

by pharo＠googlecode.com

Updates: Status: Fixed Labels: Milestone-1.3 Comment #2 on issue 3440 by marcus.d...(a)gmail.com: Cycle in Monticello removed http://code.google.com/p/pharo/issues/detail?id=3440 (No comment was entered for this change.)

Jan. 20, 2011

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

by Benjamin

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 3441 in pharo: Tests for Polymorph

by pharo＠googlecode.com

Updates: Status: Fixed Labels: Milestone-1.3 Comment #2 on issue 3441 by marcus.d...(a)gmail.com: Tests for Polymorph http://code.google.com/p/pharo/issues/detail?id=3441 (No comment was entered for this change.)

Jan. 20, 2011

Re: [Pharo-project] Issue 3526 in pharo: Update bug reporting instructions now that new issues are automatically posted to mailing list

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3526 by marcus.d...(a)gmail.com: Update bug reporting instructions now that new issues are automatically posted to mailing list http://code.google.com/p/pharo/issues/detail?id=3526 DONE

Jan. 20, 2011

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

by Tudor Girba

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