- Pharo-dev - lists.pharo.org

[Pharo-project] Resent messages?

by Bill Schwab

Hello all, Did some messages get posted more than once? It beats losing them, but leaves me wondering whether it is my goofy email server or something about the list conversion. FWIW. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029

June 1, 2008

Re: [Pharo-project] Replacing 'ReadStream on smth:' by 'smth readStream'

by Bill Schwab

Stef, My email server crashed yesterday and was out of action for several hours. From emails I found this morning, it looks like Damien and I will cook up a plan on the Wiki. With luck, we will be able to get the RB to do the tedious work, and also leave a simple defined procedure for converting "old" code that we did not have loaded during the transformation. Transformed code should work as it always did; new code will be able to benefit from consistent semantics and exception handling. There will also be silently truncating methods for the situations (and they indeed exist) that call for them. More to come. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029 >>> stephane.ducasse(a)inria.fr 05/31/08 4:22 PM >>> On May 30, 2008, at 10:46 PM, Bill Schwab wrote: > Stef, > > Whether or not I agree depends on what you mean. While I think I > see where Damien is going, my read is that #on: is actually > negotiable, given that we should be able to either fix (or simply > replace and than alias) ReadStream - two different ways of solving > the same problem. But if you concerned about breaking some things > that Damien and I are committed to fixing as part of the change, > then I submit that we will be helpless when we move from the > relatively calm world of streams to the chaos of morphic. You lost me. :) > Which part bothers you? None :) > The plan is to rennovate (sometimes messy) and *then* slowly evolve > the resulting stable system, right? The plan is to move but be careful. This is why I would like you guys to tell us what you want to do (or are doing) so that we can document the changes and everybody can participate and help also fixing if necessary. I just want more organized communication when we have a "big" change. No more. Stef _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 1, 2008

Re: [Pharo-project] new to pharo

by Alain Plantec

On Saturday 31 May 2008 14:24:05 you wrote: > Alain, > > You have COMPLETELY missed the focus of my response; thanks for > objecting so we can clarify it. My point was that it is a great start > on explaining something that is indeed mysterious to many (including > myself!), and deserves to be built up into a Wiki page for future > reference vs. "lost" in an archived list. Excuse me, it seems that I have to improve my english alain > > Please continue questioning the experts, and document what they tell > you. We will have it right when the answer is a link to a page complete > with a FAQ. > > Bill > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > >

June 1, 2008

Re: [Pharo-project] [ANN][Pharo-dev] First release

by Damien Cassou

>>> I hope to have a server soon for the universe >> >> I think it will be difficult to maintain a universe server (each time >> you update a package on the squeak universe, you will have to do it >> again for pharo). A Universe is a set of packages. You want another set. If I change the Squeak set, the Pharo set won't be updated. This has some advantages (we control what appears in our universe), but has the big disadvantage of duplicating my effort to update the Squeak Universe. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 1, 2008

Re: [Pharo-project] [ANN][Pharo-dev] First release

by StÃ©phane Ducasse

You lost me. >> yes we are. >> I hope to have a server soon for the universe > > I think it will be difficult to maintain a universe server (each time > you update a package on the squeak universe, you will have to do it > again for pharo).

May 31, 2008

Re: [Pharo-project] new to pharo

by StÃ©phane Ducasse

http://gforge.inria.fr/plugins/wiki/index.php?HowToContribute&id=1299&type=g

May 31, 2008

Re: [Pharo-project] new to pharo

by StÃ©phane Ducasse

>> >> >> I agree, the process is not that easy and intuitive. >> >> 1 - Take the latest pharo image, and click on update on the left tab >> 2 - Open Monticello >> 3 - Load your .cs file >> 4 - you should see some package with a * before them in Monticello >> 5 - Create a package named SLICE-Remove isMorphic message >> 6 - add to your SLICE package all the packages that have a * before >> their >> name as required >> 7 - Save your SLICE package in PharoInBox >> > > I don't understand these instructions: > > How do you do step 6? what does adding packages to packages > mean? alex meant all the dirty packages (because of your changes) that contain your changes > > > Slices sounds like MC2. Does Pharo use MC2? We would like but MC2 does not seem ready yet. But we will definitively give a try. Stef > > > -- > Matthew Fulmer -- http://mtfulmer.wordpress.com/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 31, 2008

Re: [Pharo-project] new to pharo

by StÃ©phane Ducasse

It is on the wiki :) How to submit changes (ok this wiki is terrible... we will change) Stef On May 31, 2008, at 1:31 AM, Bill Schwab wrote: > I think this needs to be carved onto the side of a monument somewhere, > perhaps with a gigantic and stylized image of Avi or Colin smiting a > helpless enemy :) Failing that, perhaps it should go on a wiki?? > > Bill > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 846-1285 > FAX: (352) 392-7029 > > >>>> alexandre(a)bergel.eu 5/30/2008 4:27:18 PM >>> > Hi Alain, > > I agree, the process is not that easy and intuitive. > > 1 - Take the latest pharo image, and click on update on the left tab > 2 - Open Monticello > 3 - Load your .cs file > 4 - you should see some package with a * before them in Monticello > 5 - Create a package named SLICE-Remove isMorphic message > 6 - add to your SLICE package all the packages that have a * before > their name as required > 7 - Save your SLICE package in PharoInBox > > Cheers, > Alexandre > > On 30 May 2008, at 20:39, Alain Plantec wrote: > >> >>>> ok, I'm starting by chasing all senders to the isMorphic message >> I've a .cs that touch a lot of methods everywhere**. >> now, what is the procedure ? >> can I put my .cs somewhere, give it to somebody, make a .mcz with >> it ? (I do not known how) >> sorry for all these stupid questions, I try to understand the update > >> process. >> thanks >> alain >> >> >> ** >> for all #isMorphic senders: >> "self isMorphic ifTrue: [XXXXX] ifFalse: [YYYYY]" >> is replaced with >> "XXXXX" >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > 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 >

May 31, 2008

Re: [Pharo-project] Replacing 'ReadStream on smth:' by 'smth readStream'

by StÃ©phane Ducasse

On May 30, 2008, at 10:46 PM, Bill Schwab wrote: > Stef, > > Whether or not I agree depends on what you mean. While I think I > see where Damien is going, my read is that #on: is actually > negotiable, given that we should be able to either fix (or simply > replace and than alias) ReadStream - two different ways of solving > the same problem. But if you concerned about breaking some things > that Damien and I are committed to fixing as part of the change, > then I submit that we will be helpless when we move from the > relatively calm world of streams to the chaos of morphic. You lost me. :) > Which part bothers you? None :) > The plan is to rennovate (sometimes messy) and *then* slowly evolve > the resulting stable system, right? The plan is to move but be careful. This is why I would like you guys to tell us what you want to do (or are doing) so that we can document the changes and everybody can participate and help also fixing if necessary. I just want more organized communication when we have a "big" change. No more. Stef

May 31, 2008

Re: [Pharo-project] Replacing 'ReadStream on smth:' by 'smth readStream'

by StÃ©phane Ducasse

excellent! > I knew the tests argument did not hold because there are so few tests > in Squeak, I was joking :-). I'm trying to do the changes carrefully, > that's why I commited things package after package instead of doing it > globally. Stef

May 31, 2008