- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Making layouts using anchors

by Igor Stasenko

On 7 April 2011 22:11, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > A screenshot ? > here > Alexandre > > -- Best regards, Igor Stasenko AKA sig.

April 7, 2011

Re: [Pharo-project] An idea about Pluggable widgets

by Nicolas Cellier

2011/4/7 Alain Plantec <alain.plantec(a)yahoo.com>: > Le 07/04/2011 19:23, Igor Stasenko a Ã©crit : >> >> button1 model: (self for: #performAction adapt: #turnRed) >> button2 model: (self for: #performAction adapt: #turnGreen) > > yes, cool! > It seems to be a good way to clean morphic > cheers > Alain > > Yes, it's delegating the job to specialized objects. Specialized objects shall know how to. That should prevent Morphs to be omniscient. My favourite name for the opposite pattern is "god programming": we all encountered the thousand lines functions with tons of imbricated if/switch logic in C or C// world, didn't we ? Somehow, Igor proposal reminds me the VW UI architecture were they pushed the wrapper pattern very far. Personnally, I found myself comfortable with it, but it had its detractors too. It would be interesting to analyze their arguments. cheers. Nicolas

April 7, 2011

Re: [Pharo-project] Metacello chapter

by Miguel CobÃ¡

El jue, 07-04-2011 a las 20:44 +0200, StÃ©phane Ducasse escribiÃ³: > On Apr 7, 2011, at 5:02 PM, Miguel CobÃ¡ wrote: > > > El jue, 07-04-2011 a las 09:18 +0200, StÃ©phane Ducasse escribiÃ³: > >> and so what? I still do not understand it. > >> may be noury should be added to the project. > > > > A pull is a notice to the original author (whose code the contributor is > > forking and modifying) to indicate that some changes are made parting > > from some point in time (the time of forking). Github permits the > > original author to review the changes and apply them to its own > > "official" codebase, therefore integrating contributions from others. > > how do I do both Those are separate scenarios: > notify a project I have changes for it? Here you are contributor and are informing the original author/developer/owner that you have some changes for it to review and possibly integrate (that is the pull request: you request the author that pull your changes in its repository). > how do I merge changes submitted? Here you are the author/developer/owner of the repo and you have a queue of pull request to review and possible to integrate changes made from some other people. Cheers > > > > The nice thing is that everyone can modify what he wants but the > > original author is the one that takes what it appears good to him for > > integrating in the official codebase. There is no need to add more > > people to a "project" because everyone can have its own copy of the > > project and only share the changes as needed. > > Yes I know the idea. > > > > > Cheers > >> > >> > >> On Apr 7, 2011, at 3:28 AM, Serge Stinckwich wrote: > >> > >>> https://github.com/SquareBracketAssociates/PharoByExample-english/pull/3 > >>> > >>> On Thu, Apr 7, 2011 at 3:10 AM, StÃ©phane Ducasse > >>> <stephane.ducasse(a)inria.fr> wrote: > >>>>> Cool. BTW, I have a pending pull request on the Socket chapter. > >>>> > >>>> what is it? > >>>> what do you mean? > >>>> what do you need? > >>>> > >>>> Stef > >>>> > >>>> > >>> > >>> > >>> > >>> -- > >>> Serge Stinckwich > >>> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > >>> Every DSL ends up being Smalltalk > >>> http://doesnotunderstand.org/ > >> > >> > > > > -- > > Miguel CobÃ¡ > > http://twitter.com/MiguelCobaMtz > > http://miguel.leugim.com.mx > > > > > > > > > > -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

April 7, 2011

Re: [Pharo-project] Issue 3424 in pharo: Improved class Tests

by pharo＠googlecode.com

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

April 7, 2011

[Pharo-project] Making layouts using anchors

by Igor Stasenko

Hi, i hacked morphs a bit to use anchors for laying out the morphs. The idea that you can force morph to make one of its edges (left, top, bottom, right) be dependent from other morph's edge. Here an example: | window morph morph2 | window := StandardWindow labelled: 'foo'. window color: Color red. morph := Morph new. morph anchorLeft: window leftAnchor + (window widthAnchor * 0.5) - 20. morph anchorRight: window leftAnchor + (window widthAnchor * 0.5) + 20. morph anchorTop: window topAnchor + 20. morph anchorBottom: window bottomAnchor - 20. morph2 := Morph new. morph2 color: Color green. morph2 anchorLeft: morph rightAnchor + 10. morph2 anchorRight: morph rightAnchor + 50. morph2 anchorTop: window topAnchor + 20. morph2 anchorBottom: window bottomAnchor - 20. window addMorph: morph2. window addMorph: morph. window openInWorld. window extent: 200@200. You can of course implement same layout using proportional layouts i.e. you can do window addMorph: fullFrame: ... but note that while its okay for first morph you add , a morph2 left edge is actually depending on first morph right edge. So, if it will be resized by other means (like stretched by inner morph), you won't be able to align sibling accordingly, and then you are forced to use table layout or something else. What i like about anchors that it reflects the natural way of thinking of UI designer i.e. : "I want this morph to align to window right edge" or "I want this morph to align to previous morph right edge with 10 pixels offset" For example, if i have two morphs, left and right, and i want to put my morph in the middle of them to fill the space between them, i can simply do: middle := Morph new. middle anchorLeft: leftMorph rightAnchor + 10. middle anchorRight: rightMorph leftAnchor - 10. so, you will get a following layout: [leftMorph] [ 10 pixels ] [ ... middle morph ..... ] [ 10 pixels ] [right morph ] with just two lines of code! P.S. Of course , anchors are in conflict with layouts, because you cannot have both. But some combination of them could still be used. -- Best regards, Igor Stasenko AKA sig.

April 7, 2011

Re: [Pharo-project] Metacello chapter

by StÃ©phane Ducasse

On Apr 7, 2011, at 5:02 PM, Miguel CobÃ¡ wrote: > El jue, 07-04-2011 a las 09:18 +0200, StÃ©phane Ducasse escribiÃ³: >> and so what? I still do not understand it. >> may be noury should be added to the project. > > A pull is a notice to the original author (whose code the contributor is > forking and modifying) to indicate that some changes are made parting > from some point in time (the time of forking). Github permits the > original author to review the changes and apply them to its own > "official" codebase, therefore integrating contributions from others. how do I do both notify a project I have changes for it? how do I merge changes submitted? > > The nice thing is that everyone can modify what he wants but the > original author is the one that takes what it appears good to him for > integrating in the official codebase. There is no need to add more > people to a "project" because everyone can have its own copy of the > project and only share the changes as needed. Yes I know the idea. > > Cheers >> >> >> On Apr 7, 2011, at 3:28 AM, Serge Stinckwich wrote: >> >>> https://github.com/SquareBracketAssociates/PharoByExample-english/pull/3 >>> >>> On Thu, Apr 7, 2011 at 3:10 AM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>>> Cool. BTW, I have a pending pull request on the Socket chapter. >>>> >>>> what is it? >>>> what do you mean? >>>> what do you need? >>>> >>>> Stef >>>> >>>> >>> >>> >>> >>> -- >>> Serge Stinckwich >>> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >>> Every DSL ends up being Smalltalk >>> http://doesnotunderstand.org/ >> >> > > -- > Miguel CobÃ¡ > http://twitter.com/MiguelCobaMtz > http://miguel.leugim.com.mx > > > >

April 7, 2011

Re: [Pharo-project] Metacello chapter

by StÃ©phane Ducasse

noury can you log on git hub so that we can add you to the project? Stef On Apr 7, 2011, at 2:59 PM, Noury Bouraqadi wrote: > I don't know how other authors work. > Not having write access to the repo, I have to fork, make my changes and then ask the admin of the repo (you + who else) to pull (=> merge) changes I made. > > Noury > On 7 avr. 2011, at 09:18, StÃ©phane Ducasse wrote: > >> and so what? I still do not understand it. >> may be noury should be added to the project. >> >> >> On Apr 7, 2011, at 3:28 AM, Serge Stinckwich wrote: >> >>> https://github.com/SquareBracketAssociates/PharoByExample-english/pull/3 >>> >>> On Thu, Apr 7, 2011 at 3:10 AM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>>> Cool. BTW, I have a pending pull request on the Socket chapter. >>>> >>>> what is it? >>>> what do you mean? >>>> what do you need? >>>> >>>> Stef >>>> >>>> >>> >>> >>> >>> -- >>> Serge Stinckwich >>> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >>> Every DSL ends up being Smalltalk >>> http://doesnotunderstand.org/ >> >> > > Noury Bouraqadi > http://car.mines-douai.fr/noury > -- > -6th National Conference on > âControl Architecture of Robotsâ > 24-25 may 2011, Grenoble area, France > http://car2011.inrialpes.fr/ > > -19th ESUG International Smalltalk Conference > 22-26 August 2011, Edinburgh, UK > http://www.esug.org/Conferences/2011 > > -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 > > > > > >

April 7, 2011

Re: [Pharo-project] Issue 3789 in pharo: convert MenuMorph reference to invoke UIManager

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #4 on issue 3789 by marcus.d...(a)gmail.com: convert MenuMorph reference to invoke UIManager http://code.google.com/p/pharo/issues/detail?id=3789 (No comment was entered for this change.)

April 7, 2011

Re: [Pharo-project] filesystem changes

by StÃ©phane Ducasse

On Apr 7, 2011, at 7:26 PM, Tudor Girba wrote: > Hi, > > I noticed that Filesystem changed significantly recently both internally and in package structure (I guess it was Colin - the user says cwp). yes we should add a configurationOfFS > This led to some red tests in Moose that I now fixed. I am writing here to document these changes in case other people are using this nice library. thanks. > From a package point of view Filesystem has now a cool structure with basically each category being in a separate package. Furthermore, the original Filesystem is now empty which might create problems if people are loading it like we do in Moose. > > To get it loading, I created a new baseline (2.0.1-baseline) in the ConfigurationOfFilesystem. tx! > There were also some refactorings at the level of the model. Now, FSFilesystem does not have subclasses anymore (e.g., FSDiskFilesystem does not exist anymore). Instead there is a composition with a Store, so you will have FSDiskStore. > > Thus, if before you used something like "FSDiskFilesystem current", now you will have to use "FSDiskStore currentFilesystem" > > That was it. > > Everything is green now in Moose land. > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Next time you see your life passing by, say 'hi' and get to know her." > > > >

April 7, 2011

Re: [Pharo-project] Issue 3370 in pharo: NewParagraph and MultiNewParagraph should be merged

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #5 on issue 3370 by marcus.d...(a)gmail.com: NewParagraph and MultiNewParagraph should be merged http://code.google.com/p/pharo/issues/detail?id=3370 (No comment was entered for this change.)

April 7, 2011