February 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.4] #14333

by StÃ©phane Ducasse

14333 ----- - Issue 5281: Refactor in LazyListMorph. Thanks Benjamin van Ryseghem. http://code.google.com/p/pharo/issues/detail?id=5281 Stef

Feb. 15, 2012

Re: [Pharo-project] moved repos to gemstone

by StÃ©phane Ducasse

> >> Regarding the refactoring engine: I will continue to maintain the code in the spirit of the original authors in my own repository. >> >> Of course Pharo is free to fork any open-souce repository, but then the maintainers should not complain if they end up with outdated and broken code nobody has time to maintain (as it recently happend with the one-click builder). > > well the one click thingy should just be a jenkins job on our build server, that would be fine. > >> Furthermore, it would be appreciated if the projects were renamed and and would use a different namespace. For example, I cannot load any package that depends on the official version of FS. where is such a version? > > bah, basically this shows that squeaksources sucks at comunity based multi version code :D > > to bad that we're not yet on github for that reason... > > I don't feel like changing the namespaces either since that makes including updates and changes even harder... > >> A quick comparison shows that the Pharo fork is based on outdated code and has some methods of the public API renamed. > > where's the other code located? I would like to check that. Me too especially because I committed in FS on squeak source and not in Pharo so that colin can commit. Because originally I worked on PharoTaskForces. I remember doing it on purpose to share our changes. I remember also having lost the comments I added to some methods and classesâ¦ apparently comments have no value in our world. So I reentered them. Now if colin does not care about we are doing I have no problem with that. In addition I do not see how we can control our life if we cannot publish on the repository of a part that should be central to us. Stef

Feb. 15, 2012

Re: [Pharo-project] where is RPackageOrganiser

by StÃ©phane Ducasse

On Feb 15, 2012, at 5:14 PM, Ben Coman wrote: > I am working through the draft PBE2 chapter on Glamour [1], which has the following on page 5: > > PBE2CodeNavigator>>organizer > ^ RPackageOrganizer default > > RPackageOrganizer is not in my image (Pharo-1.3-13315). How can I install this ? I have been unable to google anything useful. it is only in the moose image for the moment. You can load ConfigurationOfRPackage in PharoTaskForces and it should work well in 1.4 Stef > > cheers, -ben > > [1] https://gforge.inria.fr/scm/viewvc.php/*checkout*/PharoByExampleTwo-Eng/Gla… >

Feb. 15, 2012

[Pharo-project] [update 1.4] #14333

by StÃ©phane Ducasse

14333 ----- - Issue 5281: Refactor in LazyListMorph. Thanks Benjamin van Ryseghem. http://code.google.com/p/pharo/issues/detail?id=5281

Feb. 15, 2012

Re: [Pharo-project] moved repos to gemstone

by Camillo Bruni

On 2012-02-15, at 17:09, Lukas Renggli wrote: > Regarding the refactoring engine: I will continue to maintain the code in the spirit of the original authors in my own repository. > > Of course Pharo is free to fork any open-souce repository, but then the maintainers should not complain if they end up with outdated and broken code nobody has time to maintain (as it recently happend with the one-click builder). well the one click thingy should just be a jenkins job on our build server, that would be fine. > Furthermore, it would be appreciated if the projects were renamed and and would use a different namespace. For example, I cannot load any package that depends on the official version of FS. bah, basically this shows that squeaksources sucks at comunity based multi version code :D to bad that we're not yet on github for that reason... I don't feel like changing the namespaces either since that makes including updates and changes even harder... > A quick comparison shows that the Pharo fork is based on outdated code and has some methods of the public API renamed. where's the other code located? I would like to check that. > Lukas > > On Wednesday, February 15, 2012, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > If the corresponding project admins would agree it would be cool to move the development to ss3 on gemstone of the following projects I ported so far: > > > > - Citezen http://ss3.gemstone.com/ss/citezen > > - FSFilesystem http://ss3.gemstone.com/ss/fs > > - FSGit http://ss3.gemstone.com/ss/fs-git > > - PetitMarkdown http://www.squeaksource.com/PetitMarkdown > > - PharoRB http://ss3.gemstone.com/ss/rb-pharo > > - Refactoring Engine http://ss3.gemstone.com/ss/rb > > - Soup http://ss3.gemstone.com/ss/soup > > - XMLSupport http://ss3.gemstone.com/ss/xmlsupport > > > > I tried to add people from the old projects as admins > > Please let me know > > > > -- > Lukas Renggli (mobile) > http://www.lukas-renggli.ch

Feb. 15, 2012

[Pharo-project] where is RPackageOrganiser

by Ben Coman

I am working through the draft PBE2 chapter on Glamour [1], which has the following on page 5: PBE2CodeNavigator>>organizer ^ RPackageOrganizer default RPackageOrganizer is not in my image (Pharo-1.3-13315). How can I install this ? I have been unable to google anything useful. cheers, -ben [1] https://gforge.inria.fr/scm/viewvc.php/*checkout*/PharoByExampleTwo-Eng/Gla…

Feb. 15, 2012

Re: [Pharo-project] moved repos to gemstone

by Lukas Renggli

Regarding the refactoring engine: I will continue to maintain the code in the spirit of the original authors in my own repository. Of course Pharo is free to fork any open-souce repository, but then the maintainers should not complain if they end up with outdated and broken code nobody has time to maintain (as it recently happend with the one-click builder). Furthermore, it would be appreciated if the projects were renamed and and would use a different namespace. For example, I cannot load any package that depends on the official version of FS. A quick comparison shows that the Pharo fork is based on outdated code and has some methods of the public API renamed. Lukas On Wednesday, February 15, 2012, Camillo Bruni <camillobruni(a)gmail.com> wrote: > If the corresponding project admins would agree it would be cool to move the development to ss3 on gemstone of the following projects I ported so far: > > - Citezen http://ss3.gemstone.com/ss/citezen > - FSFilesystem http://ss3.gemstone.com/ss/fs > - FSGit http://ss3.gemstone.com/ss/fs-git > - PetitMarkdown http://www.squeaksource.com/PetitMarkdown > - PharoRB http://ss3.gemstone.com/ss/rb-pharo > - Refactoring Engine http://ss3.gemstone.com/ss/rb > - Soup http://ss3.gemstone.com/ss/soup > - XMLSupport http://ss3.gemstone.com/ss/xmlsupport > > I tried to add people from the old projects as admins > Please let me know > -- Lukas Renggli (mobile) http://www.lukas-renggli.ch

Feb. 15, 2012

Re: [Pharo-project] Traits in PHP

by StÃ©phane Ducasse

On Feb 15, 2012, at 4:55 PM, Damien Cassou wrote: > On Wed, Feb 15, 2012 at 11:45 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Indeed. Now I would love that we rethink our trait implementation and tool support but no time. > > Give me a position, I will take care of that :-) we have one :) and indeed it would be reeeallllllly cool. Stef >

Feb. 15, 2012

Re: [Pharo-project] annoying press "ok" when running tests (not headless)

by StÃ©phane Ducasse

On Feb 15, 2012, at 1:58 PM, Tudor Girba wrote: > Hi, > > It's not UIManager, but UITheme. I made it dependent on the UITheme in > the sense that I moved all the rendering code as an extension. I > thought this is the official way to get things working with Polymorph. > Did I get it wrong? I do not know. I'm still confused by the responsibility of UITheme vs UIManager vsâ¦ Now you do not want that every tools add method to UITheme because imagine that we do that then how each theme can be modular? so far I do not have the right answer. Now GrowlMorph should have setting and get initialized from the UITheme settings > > Cheers, > Doru > > > On Wed, Feb 15, 2012 at 1:54 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> On Feb 15, 2012, at 1:47 PM, Tudor Girba wrote: >> >>> Indeed, this is a project that is since too long on my to do list. >>> >>> I worked on Growl a bit as well, but we need to bring it further. I >>> just pushed the to do towards the top of the list :) I would be happy >>> to collaborate on this issue. >> >> Would be good. >> Doru could you fix the fact that if I remember correctly you make it dependent on the UIManager? >> or something like that? >> But we could really add it to the image so that we have vanishing messages :) >> >>> >>> Cheers, >>> Doru >>> >>> >>> On Wed, Feb 15, 2012 at 1:38 PM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>> There is a Growl in Pharo. I improved it :) >>>> >>>> Stef >>>> >>>> On Feb 15, 2012, at 12:42 PM, Camillo Bruni wrote: >>>> >>>>> gargl.... >>>>> >>>>> we should have some non-interactive inform: like Growl on Mac. >>>>> The popups should just open but not block the interaction IMO. >>>>> >>>>> >>>>> On 2012-02-14, at 23:50, Igor Stasenko wrote: >>>>> >>>>>> i started tests and leaved image for a while, but when i went back >>>>>> hoping that it already finished, i discovered that it waiting for me >>>>>> to press ok >>>>>> and did not ran even 20% of all tests. >>>>>> >>>>>> Somewhere in GoferOperationTest>>testMerge >>>>>> it says 'No changes' and waits for the user to press 'ok' >>>>>> >>>>>> >>>>>> -- >>>>>> Best regards, >>>>>> Igor Stasenko. >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >> >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Feb. 15, 2012

Re: [Pharo-project] Traits in PHP

by Damien Cassou

On Wed, Feb 15, 2012 at 11:45 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Indeed. Now I would love that we rethink our trait implementation and tool support but no time. Give me a position, I will take care of that :-) -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Feb. 15, 2012