December 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] We need to do something, seriously!!!! [WAS] Fwd: Issue 1721: Refactoring appears to be broken in web dev image. e.g. OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols

by Lukas Renggli

> Thanks Lukas to be agree. I like your scripts, but the problem is that you > use your own forked repository to get an stable version. I would love to > have THAT, but in the original repositories. Examples: omnibrowser, > unsorted, etc.Â Do you know how we can fix this ? Well, if you want to do a stable distribution you need to fork, even if you just copy the versions to a separate repository. We learned this with Seaside 3.0alpha1 the hard way. Servers disappear, repositories disappear, versions get deleted, versions get renamed or replaced. When we release a Seaside version we always copy all the dependencies to a single place that we control, e.g. <http://builder.seaside.st/distributions/004-Seaside3.0.0-a5/>. Forking is not something bad. Fork early and fork often. Forking is good. Monticello is excellent at merging. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 30, 2009

Re: [Pharo-project] We need to do something, seriously!!!! [WAS] Fwd: Issue 1721: Refactoring appears to be broken in web dev image. e.g. OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols

by Dale Henrichs

Dec. 30, 2009

Re: [Pharo-project] We need to do something, seriously!!!! [WAS] Fwd: Issue 1721: Refactoring appears to be broken in web dev image. e.g. OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols

by Lukas Renggli

> Yes lukas now damien was nice to build the images because I could not do them. > But damien is doing Java daily. Yes, I know. This is definitely not the fault of Damien, he is doing an excellent job in integrating, merging and fixing the obvious bugs. The problem is that nobody that uses the image 12 hours daily is taking responsibility. > So I do not know what to do. > Â Â Â Â - first we should add simple trait creation to the OB > Â Â Â Â - now frankly I do not know how we could manage moose without the package browser. Then somebody that uses OB and Traits daily should commit on that. I am not a trait user, so I can't help here. The same for the package browser: I am pretty happy with OB, the package browser of OB-Refactory, and Gofer to manage the 75 Seaside packages. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 30, 2009

Re: [Pharo-project] Pharo-beginner mailing list ?

by Mariano Martinez Peck

Is there a specific mailing list for the PBE readers? ifFalse: this could be a good place where the readers can ask :) I saw sbe-discussion(a)iam.unibe.ch but I am not sure what that mailing list it is about. Is it for final users of for the authors ? Cheers Mariano On Wed, Dec 30, 2009 at 6:56 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > yes ;) I was just explained why I said one hour :) > > > On Wed, Dec 30, 2009 at 6:46 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> ok let us wait to get more feedback on the idea... >> >> Stef >> On Dec 30, 2009, at 6:39 PM, Mariano Martinez Peck wrote: >> >> > >> > >> > On Wed, Dec 30, 2009 at 6:29 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> >> wrote: >> > >> > How do we subscribe? >> > >> > On 30 Dec 2009, at 14:09, StÃ©phane Ducasse wrote: >> > >> > > My point is that some people may be bored by too technical discussions >> > > Miguel I agree on the number of list. We should check if there is >> > > enough people. >> > > @Adrian: the forum idea is nice but I do not why it did not work for >> > > Smalltalk. >> > > I went to the site you mentioned but I could not get how it works. >> > > >> > >> +1 I would create it. It is not more than 1 hour or so of work. >> > > 3min :) >> > >> > Yes, but after creating the list, I think you should also: >> > >> > - Send an ANN to this list, ESUG and even Squeak mailing lists. >> > - Add that information to http://www.pharo-project.org/community >> > - Add gmane and nabble bots to it >> > - Some people can post in their blogs about it >> > >> > Cheers, >> > >> > Mariano >> > >> > >> > >> > -- >> > Johan Fabry >> > jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry<http://dcc.uchile.cl/%7Ejfabry> >> > PLEIAD Lab - Computer Science Department (DCC) - University of Chile >> > >> > >> > >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >

Dec. 30, 2009

Re: [Pharo-project] I have a problem with 11126

by Igor Stasenko

2009/12/30 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Igor I push the latest bit out. > I did not remove trailerClass because the classVariable was still there. > Let me know if it should be there or not (not time to check - wife shouting for diner :) > Once you remove #new, you can remove everything else in any order you prefer, including trailerClass & classvar. > Stef > On Dec 30, 2009, at 6:10 PM, StÃ©phane Ducasse wrote: > >> I'm back from christmas shpping mess. >> ok I will do it. >> >> >> On Dec 30, 2009, at 5:20 PM, Igor Stasenko wrote: >> >>> 2009/12/30 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>> hi igor >>>> >>>> >>>> up to 11125 it works well and after when I was trying to do the last two cs using MC >>>> >>>> in 11125 I get >>>> >>>> new >>>> Â Â Â ^ self trailerClass basicNew initialize >>>> trailerClass >>>> Â Â Â ^ TrailerClass ifNil: [ OldMethodTrailer ] >>>> >>>> in 11126 when I try to load these packages. >>>> >>>> I get Â CompiledMethodTrailer new >>>> Â Â Â Â Â Â Â Â Â Â Â Â does understand trailerClass >>>> >>>> >>> >>> You seem stepped on same trap as Andreas did. Â :) >>> MC minds own method removal order, >>> and removes #trailerClass before #new, >>> which then leads to DNU. >>> >>> Split cleanup into two stages: >>> - in first update, remove just #new >>> - in second , remove #trailerClass and the rest of stuff >>> >>> so, MC will have no chances to interfere with removal order. >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Dec. 30, 2009

Re: [Pharo-project] We need to do something, seriously!!!! [WAS] Fwd: Issue 1721: Refactoring appears to be broken in web dev image. e.g. OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols

by Mariano Martinez Peck

Thanks Lukas to be agree. I like your scripts, but the problem is that you use your own forked repository to get an stable version. I would love to have THAT, but in the original repositories. Examples: omnibrowser, unsorted, etc. Do you know how we can fix this ? On Wed, Dec 30, 2009 at 7:25 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Yes lukas now damien was nice to build the images because I could not do > them. > But damien is doing Java daily. > Of course this is not Damien fault. Everybody here do as much as possible. > And you do not like the package browser and we need it :). > > So I do not know what to do. > - first we should add simple trait creation to the OB > - now frankly I do not know how we could manage moose without the > package browser. > > Yes, most of the problems in a dev image are related usually with the system browser :( > Stef > > On Dec 30, 2009, at 7:16 PM, Lukas Renggli wrote: > > >> I have already said it several times. Most of the people don't care how > >> nice, fast, clean, open source and well programmed is the Pharo Core > image > >> if they cannot use the Dev or Web image. > > > > This is what I am telling for years already. I don't know how other > > people think about this, but to me it feels very embarrassing to have > > to advertise my own way of building images over and over again? > > > > Here is it again: I am using the scripts > > <http://code.google.com/p/pharo/wiki/ImageBuildScripts> to get from a > > Pharo 1.0rc1 a fast and stable development and deployment image. The > > image loads a well tested and fast OB, a working and well tested > > refactoring engine, working syntax highlighting, working code > > completion, and several other tools I use daily and that I cannot work > > without. I am not telling it is bug free, but with my personal > > workflow I can use it without getting interrupted by bugs all the > > time. And when I encounter a bug, I fix it. > > > > I don't think that somebody can build a stable distribution without > > using it 12 hours daily. Have a look at PharoCore, it is only rock > > solid because Stef is using it all day long to integrate fixes. Have a > > look at Squeak Trunk, it only sees improvement because Andreas is > > using it all day long. Have a look at Debian, Gentoo, ... > > > > Lukas > > > > -- > > Lukas Renggli > > http://www.lukas-renggli.ch > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 30, 2009

[Pharo-project] [update 1.1] #11126 - 27 (final methodTrailer cool cleanup

by StÃ©phane Ducasse

BIG THANKS igor!!! 11127 ----- - Issue 1690: New Method Trailer part 7 (cs 9)

Dec. 30, 2009

Re: [Pharo-project] I have a problem with 11126

by StÃ©phane Ducasse

Igor I push the latest bit out. I did not remove trailerClass because the classVariable was still there. Let me know if it should be there or not (not time to check - wife shouting for diner :) Stef On Dec 30, 2009, at 6:10 PM, StÃ©phane Ducasse wrote: > I'm back from christmas shpping mess. > ok I will do it. > > > On Dec 30, 2009, at 5:20 PM, Igor Stasenko wrote: > >> 2009/12/30 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> hi igor >>> >>> >>> up to 11125 it works well and after when I was trying to do the last two cs using MC >>> >>> in 11125 I get >>> >>> new >>> ^ self trailerClass basicNew initialize >>> trailerClass >>> ^ TrailerClass ifNil: [ OldMethodTrailer ] >>> >>> in 11126 when I try to load these packages. >>> >>> I get CompiledMethodTrailer new >>> does understand trailerClass >>> >>> >> >> You seem stepped on same trap as Andreas did. :) >> MC minds own method removal order, >> and removes #trailerClass before #new, >> which then leads to DNU. >> >> Split cleanup into two stages: >> - in first update, remove just #new >> - in second , remove #trailerClass and the rest of stuff >> >> so, MC will have no chances to interfere with removal order. >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 30, 2009

Re: [Pharo-project] We need to do something, seriously!!!! [WAS] Fwd: Issue 1721: Refactoring appears to be broken in web dev image. e.g. OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols

by StÃ©phane Ducasse

Yes lukas now damien was nice to build the images because I could not do them. But damien is doing Java daily. And you do not like the package browser and we need it :). So I do not know what to do. - first we should add simple trait creation to the OB - now frankly I do not know how we could manage moose without the package browser. Stef On Dec 30, 2009, at 7:16 PM, Lukas Renggli wrote: >> I have already said it several times. Most of the people don't care how >> nice, fast, clean, open source and well programmed is the Pharo Core image >> if they cannot use the Dev or Web image. > > This is what I am telling for years already. I don't know how other > people think about this, but to me it feels very embarrassing to have > to advertise my own way of building images over and over again? > > Here is it again: I am using the scripts > <http://code.google.com/p/pharo/wiki/ImageBuildScripts> to get from a > Pharo 1.0rc1 a fast and stable development and deployment image. The > image loads a well tested and fast OB, a working and well tested > refactoring engine, working syntax highlighting, working code > completion, and several other tools I use daily and that I cannot work > without. I am not telling it is bug free, but with my personal > workflow I can use it without getting interrupted by bugs all the > time. And when I encounter a bug, I fix it. > > I don't think that somebody can build a stable distribution without > using it 12 hours daily. Have a look at PharoCore, it is only rock > solid because Stef is using it all day long to integrate fixes. Have a > look at Squeak Trunk, it only sees improvement because Andreas is > using it all day long. Have a look at Debian, Gentoo, ... > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 30, 2009

Re: [Pharo-project] We need to do something, seriously!!!! [WAS] Fwd: Issue 1721: Refactoring appears to be broken in web dev image. e.g. OBClassNode(Object)>>doesNotUnderstand: #dynamicProtocols

by Lukas Renggli

> I have already said it several times. Most of the people don't care how > nice, fast, clean, open source and well programmed is the Pharo Core image > if they cannot use the Dev or Web image. This is what I am telling for years already. I don't know how other people think about this, but to me it feels very embarrassing to have to advertise my own way of building images over and over again? Here is it again: I am using the scripts <http://code.google.com/p/pharo/wiki/ImageBuildScripts> to get from a Pharo 1.0rc1 a fast and stable development and deployment image. The image loads a well tested and fast OB, a working and well tested refactoring engine, working syntax highlighting, working code completion, and several other tools I use daily and that I cannot work without. I am not telling it is bug free, but with my personal workflow I can use it without getting interrupted by bugs all the time. And when I encounter a bug, I fix it. I don't think that somebody can build a stable distribution without using it 12 hours daily. Have a look at PharoCore, it is only rock solid because Stef is using it all day long to integrate fixes. Have a look at Squeak Trunk, it only sees improvement because Andreas is using it all day long. Have a look at Debian, Gentoo, ... Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 30, 2009