July 2008 - Pharo-dev - lists.pharo.org

[Pharo-project] Turning _ into :=

by Alexandre Bergel

Hi! Is there currently a strategy to turn _ into :=? Does it have to be done manually? I am working on a part of the system that contains _. Shall I post into PhaboInbox a path that turns this underscores into standard assignments? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 13, 2008

Re: [Pharo-project] new slices

by Adrian Lienhard

Hi Stef, I will have some time tomorrow (Sunday) to do a new update. All packages that I moved to the TreatedInbox are packages that we don't want to integrate. So this was simply a cleanup of the Inbox. Adrian On Jul 10, 2008, at 14:52 , StÃ©phane Ducasse wrote: > Ok > I could do it this evening. did you generate the new scripts when > you moved stuff to > the treatedInBox? > > Stef > > >> Hi Stef, >> >> ok, I will do the next update. I will probably have time on Sunday >> or beginning of next week. >> >> Adrian >> >> On Jul 9, 2008, at 20:11 , StÃ©phane Ducasse wrote: >> >>> Hi adrian >>> >>> did you create new scriptloader entries? >>> how do I sync with you? >>> Do you do the next update? It would be good this way we check for >>> real that >>> your password is working. >>> >>> Stef >>> >>> On Jul 9, 2008, at 5:31 PM, Norbert Hartl wrote: >>> >>>> On Wed, 2008-07-09 at 18:19 +0300, Adrian Lienhard wrote: >>>>> I moved all files related to this issue from the PharoInbox to >>>>> PharoInboxTreated. >>>>> Adrian >>>>> >>>> Great!!! Are you preparing a new update stream? >>>> >>>> Norbert >>>>> On Jul 9, 2008, at 17:54 , Norbert Hartl wrote: >>>>> >>>>>> On Wed, 2008-07-09 at 17:04 +0300, Adrian Lienhard wrote: >>>>>>> I went through those changes and changed all to Verified >>>>>>> except for >>>>>>> one case. I have set http://code.google.com/p/pharo/issues/detail? >>>>>>> id=33 (this is SLICE-squeak7082fixRecentBrowser) to WontFix >>>>>>> because I >>>>>>> think this should not go into Pharo. Norbert, do you agree? >>>>>>> >>>>>> I wasn't sure myself as the mantis tickets are very unclear. It >>>>>> seemed that 7075 introduced some bug which is reverted in >>>>>> 7082. But it sounded to me as 7082 was more than just the >>>>>> revert so I corporated the changes while leaving 7075 as >>>>>> wontfix. >>>>>> >>>>>> I would agree. >>>>>> >>>>>> Norbert >>>>>>> Cheers, >>>>>>> Adrian >>>>>>> >>>>>>> On Jul 5, 2008, at 01:05 , Norbert Hartl wrote: >>>>>>> >>>>>>>> with my newest uploads there are slices waiting for >>>>>>>> review: >>>>>>>> >>>>>>>> SLICE-squeak7074fixAsFloat >>>>>>>> SLICE-squeak7080 >>>>>>>> SLICE-squeak7081 >>>>>>>> SLICE-squeak7082fixRecentBrowser >>>>>>>> SLICE-squeak7083 >>>>>>>> >>>>>>>> And >>>>>>>> >>>>>>>> SLICE-squeakUpdate7073 >>>>>>>> >>>>>>>> is already in the updates and can be deleted. >>>>>>>> >>>>>>>> Norbert >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >> >> >> _______________________________________________ >> 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

July 12, 2008

RE: [Pharo-project] about creating a task for the next milestone

by Ramon Leon

> I used SIXX (in fact Smallwiki had an implementation using SIXX). > But I still would like to have some other nice solution like > ImageSegments and smartRefStream I have as well and still do for some things, but sixx files are huge compared to ReferenceStreams or SmartRefStreams and much more expensive generate so as far as I can see there's currently nothing able to compete with ReferenceStreams. SmartRefStream probably does need rewritten a bit to throw exceptions instead of prompting the user, but otherwise it seems to work rather well. Ramon Leon http://onsmalltalk.com

July 12, 2008

Re: [Pharo-project] about creating a task for the next milestone

by StÃ©phane Ducasse

On Jul 12, 2008, at 6:11 AM, Bill Schwab wrote: > Stef, > > I am very interested in serializers, but I (right or wrong) do not > have > good feeling about ReferenceStream and friends. When I last tested > them > (a while back), the output was BIG, and I was not comfortable about > the > location[*] of the conversion methods, nor with the timing: as > usual, if > I goof, please raise an error, don't put browsers in front of my end > users =:0 Indeed :) > That said, I am expecting to port some of my code, and completely > rewrite other parts using things like Magritte. A variation on > ReferenceStream might turn out to be of use to me. However, I am also > considering something, again along the lines of Magritte (if not > part or > an extension thereof) to make my persistence independent of the > internal > representation of objects. With extensive unit testing, I think I > could > make that work, and should at least investigate it. > > Dolphin's STB and in particular its handling of layout changes is > pretty > good. I also found some things to like about SIXX and might try to > blend the two. > > However clunky, I want to get my BibTeX system up and running, and > then > I will probably turn attention to an out-filer that writes code that > Pharo can read. Some gnashing of teeth later, I will start to port > sub-systems, redesigning some as I go. I used SIXX (in fact Smallwiki had an implementation using SIXX). But I still would like to have some other nice solution like ImageSegments and smartRefStream > > > Bill > > [*] IIRC, they end up in ReferenceStream itself, rather than in the > class that "needs help." It struck me as asking for trouble. > > > > > 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 07/11/08 3:34 AM >>> > Hello guys > > I was reading the class ReferenceStream and sisters/mother. > The ones that are in System-Object Storage. > > I think that these classes are important. > They have a good class comments, even if we could improve. > I would really like to use them as a test-bed for a canonical > documentation > effort: > - unit tests > - simple how to use > > I would also like to see if they can be rebuild on top of Nile. > So I would like to know if some of you are interested working on this > task. > > stef > > > > > _______________________________________________ > 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 >

July 12, 2008

[Pharo-project] connexion sluggisness

by StÃ©phane Ducasse

hi guys I just arrived to a place where the net does not work.... Yes it exists. :) So I'm trying to discuss with the provider arghhhh. So do not expect me to be reactive.... Right now I'm in public library which has a nice open wifi. Stef

July 12, 2008

Re: [Pharo-project] about creating a task for the next milestone

by Bill Schwab

Stef, I am very interested in serializers, but I (right or wrong) do not have good feeling about ReferenceStream and friends. When I last tested them (a while back), the output was BIG, and I was not comfortable about the location[*] of the conversion methods, nor with the timing: as usual, if I goof, please raise an error, don't put browsers in front of my end users =:0 That said, I am expecting to port some of my code, and completely rewrite other parts using things like Magritte. A variation on ReferenceStream might turn out to be of use to me. However, I am also considering something, again along the lines of Magritte (if not part or an extension thereof) to make my persistence independent of the internal representation of objects. With extensive unit testing, I think I could make that work, and should at least investigate it. Dolphin's STB and in particular its handling of layout changes is pretty good. I also found some things to like about SIXX and might try to blend the two. However clunky, I want to get my BibTeX system up and running, and then I will probably turn attention to an out-filer that writes code that Pharo can read. Some gnashing of teeth later, I will start to port sub-systems, redesigning some as I go. Bill [*] IIRC, they end up in ReferenceStream itself, rather than in the class that "needs help." It struck me as asking for trouble. 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 07/11/08 3:34 AM >>> Hello guys I was reading the class ReferenceStream and sisters/mother. The ones that are in System-Object Storage. I think that these classes are important. They have a good class comments, even if we could improve. I would really like to use them as a test-bed for a canonical documentation effort: - unit tests - simple how to use I would also like to see if they can be rebuild on top of Nile. So I would like to know if some of you are interested working on this task. stef _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 12, 2008

Re: [Pharo-project] How to follow which packages have been integrated ,

by Victor Rodriguez

On Mon, Jul 7, 2008 at 5:40 PM, Serge Stinckwich <serge.stinckwich(a)doesnotunderstand.org> wrote: [snip] > For example, StÃ©phane renamed my package deposed in PharoInbox (and > now in PharoTreated) : Collections-zz.85.mcz into > Collections-stephaneducasse.86.mcz (in Pharo) ... It's almost > impossible to follow what packages have been integrated or not. There is a very easy way to fix this: include the issue number in the package name. So how is this for a proposal: there should be an issue filed for everything that goes into the image, and every package that goes into the inbox should include in the name the issue number. Best Regards, Victor Fodirguez. > It's not a negative remark from me, i just observe that it doesn't > scale well ... > -- > Serge Stinckwich > Smalltalkers do: [:it | All with: Class, (And love: it)] > http://blog.doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 11, 2008

[Pharo-project] about creating a task for the next milestone

by StÃ©phane Ducasse

Hello guys I was reading the class ReferenceStream and sisters/mother. The ones that are in System-Object Storage. I think that these classes are important. They have a good class comments, even if we could improve. I would really like to use them as a test-bed for a canonical documentation effort: - unit tests - simple how to use I would also like to see if they can be rebuild on top of Nile. So I would like to know if some of you are interested working on this task. stef

July 11, 2008

Re: [Pharo-project] new slices

by StÃ©phane Ducasse

Ok thanks alain. I think that you should also ping mike for his new event hierarchy because I would like to know if miro can be based on it :) Stef On Jul 10, 2008, at 11:27 PM, Alain Plantec wrote: > On Thursday 10 July 2008 18:23:56 StÃ©phane Ducasse wrote: >> Yes I do not know the status of Etoy removal. >> It seems that alain went on holidays ? > > hello, > I'm here! About Etoy removal, nothing new. > I can work on it next week, but I prefer avoiding doing again what > Gary has already done. > Gary ? > > alain >> >>>> >>> Yep, I thought about that, too. I don't like to do unnecessary work. >>> I thought it would be good to be _ free at the earliest possible >>> date. >>> So I hope etoys goes away soon :) Than I give the unimplemented >>> calls >>> another shot. >>> >>> Norbert >>>> >> >> >> _______________________________________________ >> 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 >

July 11, 2008

Re: [Pharo-project] new slices

by Alain Plantec

On Thursday 10 July 2008 18:23:56 StÃ©phane Ducasse wrote: > Yes I do not know the status of Etoy removal. > It seems that alain went on holidays ? hello, I'm here! About Etoy removal, nothing new. I can work on it next week, but I prefer avoiding doing again what Gary has already done. Gary ? alain > > >> > > Yep, I thought about that, too. I don't like to do unnecessary work. > > I thought it would be good to be _ free at the earliest possible date. > > So I hope etoys goes away soon :) Than I give the unimplemented calls > > another shot. > > > > Norbert > >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

July 10, 2008