- Pharo-dev - lists.pharo.org

[Pharo-project] So...we freeze 1.1 ? (next steps?)

by Mariano Martinez Peck

We said that for middle May we were going to freeze 1.1. This means, no more new features or refactors. Just bug fixes. So, the next steps can be: - Release a PharoCore1.1 with the last version we have so far tagged as alpha1 (please, put this tag in the zip, .image and .changes). This may be, for example: Pharo-1.1-11360-alpha1.image - Build and release a Pharo 1.1 alpha1 based on such core (now we have almost all dev tools working well in 1.1) - Make publish all new VMs (for each OS) Then the idea is that people/developers start to play with Pharo 1.1. It may be quite unstable as this is the first release for 1.1. People should try to load their own packages, adapt them (if necessary) to 1.1, and report all issues they find (and fixes!!). But they should keep in mind this the first alpha ;) With these, we will be testing: new VMs, PharoCore, PharoDev tools, and external packages (from other people). Pharo team at the same time, continues to work, fixing and integrating. We make new versions as we have been doing so far. When we consider, we release an alpha2....then beta, then RC and finally Pharo 1.1. now...do you think there is an issue that is so important to be fixed/included in the first Pharo1.1 even being a first alpha ? Cheers Mariano

May 16, 2010

Re: [Pharo-project] ConfigurationOfExternalWebBrowser working in Squeak and Pharo trunk

by Hilaire Fernandes

Sean P. DeNigris a Ã©crit : >> What is an external web browser? >> What are its goals? > It's an alternative to Scamper. It forwards urls to the underlying OS's > browser e.g. on my mac, it opens the URL in a new Safari window. > > And how to we use the code in this package? > "ExternalWebBrowser openOnUrl: 'www.squeak.org'" Is it portable to different OS? Does it use a VM plugin? Hilaire

May 16, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Traits installer/uninstaller utility

by StÃ©phane Ducasse

On May 16, 2010, at 9:48 AM, Tudor Girba wrote: > Hi Johan, > > I took a quick look and it looks interesting. > > Just a note for discussion. Executing "AspectMapsUI open" installs the traits. One of your trait extension is adding TAMStructuralZoom to FAMIXClass. > > Now, when I browse the FAMIXClass, I get this in the browser: > > ----- > FAMIXType subclass: #FAMIXClass > uses: TAMStructuralZoom > instanceVariableNames: 'isInterface' > classVariableNames: '' > poolDictionaries: '' > category: 'Famix-Core' > ----- > > There are two problems with this: > > 1. So, now if I just want to edit the base class, I have to take care and delete the Trait before, because the Trait is part of the definition. > > This is a limitation of the browser, but we have to pay attention to it. > > 2. If you look in Monticello, the base package (FAMIX-Core in this case) is not dirty, but if you explicitly look for Changes, it gets dirty. I do not know how this could be solved. Perhaps we need extension as first class? this happens also for none trait. One day we will have to do a large pass on monticello. > > Cheers, > Doru > > > On 16 May 2010, at 02:36, Johan Fabry wrote: > >> Hi all, >> >> this is a small package that I wrote after doing a traits-based refactoring of AspectMaps (Plug: Check out AspectMaps for a cool visualization of Aspects. http://pleiad.cl/aspectmaps. It has nice screencasts. All comments welcome!) >> >> AspectMaps extends a number of classes of FAMIX to do its thing, using standard class extensions. This works OK when you are not using traits. But when using a trait, you need to redef the class, i.e. change the original package (in this case one of the moose packages). A big no-no. This kind of change should also be encapusulated in the AspectMaps package, but currently this is not possible. So, as long as traits and packages dont play well together, these kinds of refactorings are out. >> >> However not so when you are using the TraitsApplication package. This package provides a means to programmatically install/uninstall traits. Call it in a post-load action on a package (if such a thing exists), in a class initialize method, et cetera (for AspectMaps I do it in the AspectMaps>>open method). I thought this could be useful to some members of the community so I am releasing it publicly. You can find it at http://www.squeaksource.com/TraitsApplication >> >> CAVEAT: This is a quick implementation, it is non-optimal. It can be made much more elegant, but that requires time that I dont have right now :-(. I does not handle fancy trait compositions (yet). I give no guarantees other than that >> 1) it passes all of its tests >> 2) it works for me :-) >> >> So check it out. Comments are welcome! >> -- >> Johan Fabry >> jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry >> PLEIAD Lab - Computer Science Department (DCC) - University of Chile >> >> >> >> >> _______________________________________________ >> Pharo-users mailing list >> Pharo-users(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > -- > www.tudorgirba.com > > "Speaking louder won't make the point worthier." > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

May 16, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Traits installer/uninstaller utility

by Tudor Girba

Hi Johan, I took a quick look and it looks interesting. Just a note for discussion. Executing "AspectMapsUI open" installs the traits. One of your trait extension is adding TAMStructuralZoom to FAMIXClass. Now, when I browse the FAMIXClass, I get this in the browser: ----- FAMIXType subclass: #FAMIXClass uses: TAMStructuralZoom instanceVariableNames: 'isInterface' classVariableNames: '' poolDictionaries: '' category: 'Famix-Core' ----- There are two problems with this: 1. So, now if I just want to edit the base class, I have to take care and delete the Trait before, because the Trait is part of the definition. This is a limitation of the browser, but we have to pay attention to it. 2. If you look in Monticello, the base package (FAMIX-Core in this case) is not dirty, but if you explicitly look for Changes, it gets dirty. I do not know how this could be solved. Perhaps we need extension as first class? Cheers, Doru On 16 May 2010, at 02:36, Johan Fabry wrote: > Hi all, > > this is a small package that I wrote after doing a traits-based > refactoring of AspectMaps (Plug: Check out AspectMaps for a cool > visualization of Aspects. http://pleiad.cl/aspectmaps. It has nice > screencasts. All comments welcome!) > > AspectMaps extends a number of classes of FAMIX to do its thing, > using standard class extensions. This works OK when you are not > using traits. But when using a trait, you need to redef the class, > i.e. change the original package (in this case one of the moose > packages). A big no-no. This kind of change should also be > encapusulated in the AspectMaps package, but currently this is not > possible. So, as long as traits and packages dont play well > together, these kinds of refactorings are out. > > However not so when you are using the TraitsApplication package. > This package provides a means to programmatically install/uninstall > traits. Call it in a post-load action on a package (if such a thing > exists), in a class initialize method, et cetera (for AspectMaps I > do it in the AspectMaps>>open method). I thought this could be > useful to some members of the community so I am releasing it > publicly. You can find it at http://www.squeaksource.com/TraitsApplication > > CAVEAT: This is a quick implementation, it is non-optimal. It can be > made much more elegant, but that requires time that I dont have > right now :-(. I does not handle fancy trait compositions (yet). I > give no guarantees other than that > 1) it passes all of its tests > 2) it works for me :-) > > So check it out. Comments are welcome! > -- > Johan Fabry > jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry > PLEIAD Lab - Computer Science Department (DCC) - University of Chile > > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users -- www.tudorgirba.com "Speaking louder won't make the point worthier."

May 16, 2010

Re: [Pharo-project] PharoTips architecture

by Javier PimÃ¡s

2010/5/15 Mariano Martinez Peck <marianopeck(a)gmail.com> > Sorry Javier for "talking" too much about your project ;) I am just > curious. > > 1) How to store tips? How are you going to store the tips? just class > side variable with all stuff? > > sort of by now. For the sake of simplicity I just made tips be strings, but we may change that eventually. > 2) it would be great to be able to give properties to each tip. At least, > to tell each tips in which context it should appear (not mandatory). For > example, the tip "Do you want to save your workspaces to disk and manage > easily multiple of them? Check out "Tools" -> "ScriptManager?<http://code.google.com/p/pharo/w/edit/ScriptManager>" > should appe ar when using a workspace. > > so...a Tip may be dispatched against zero or more contexts > I like the idea. All GUIs in the world should be context sensitive, we should exploit the fact that doing it in smalltalk is easy. 3) Define contexts: only type of windows ? or also capture events. For > example, I can define a context is when browsing a class. That would be > cool. > If we think of contexts as tags or something like that, anything that is done in the GUI could signal a context, like clicking a menu. > > 4) How to intercept these "contexts" without changing the PharoCore? Is is > possible right now? what about using Announcments ? It would be cool to > have inside PharoCore a way to notify these kind of stuffs > This is something where I'd really like to hear ideas, I'm not experienced with morphic nor announcements, nor browsers' imlementation or even menues. > 5) This is related to 1) How can a package define its own tips ? Suppose > the example I gave in 2) I want to put it in the package > ScriptManaget-PharoTips. It would be great to be able to define them there > and then somehow to register them in the PharoTip "database". > > What a nice idea. Maybe you could add a line to initialize class method of some class inside that package. If I'm correct this method is called when a class is loaded from monticello. We could even even have a tip about it, or should I say a meta-tip. > Ok...sorry. I know I flow too much hahaha. I went beyond the simple tool > you wanted to do. The thing is that I am really interesting in this project > and I think having this would be great. > Excelent, I like your ideas, they are really innovative and go in the same line of the ones I had in my mind. Also, thank's for taking some time to improve this little toy. Regards, Javier. > Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Javier PimÃ¡s Ciudad de Buenos Aires

May 16, 2010

Re: [Pharo-project] [ANN] Traits installer/uninstaller utility

by Schwab,Wilhelm K

Johan, Best of luck with it! Taking a really quick look at your web site, this looks like something that could take a lot of time rendering graphics. Is drawing time a problem for you? Did you do anything in particular to avoid bottlenecks? I ask because I am starting to port some of my graphical code to Pharo; some of it is going from home-grown to using gnuplot, but elsewhere I was able to simply pass (Windows speak) an HDC into a function in a DLL and do a lot of rendering fairly quickly as a result. I am still looking for how to approach that in Pharo+Linux. I am starting to make my own .so's with success, but have yet to produce graphics that way. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Johan Fabry Sent: Saturday, May 15, 2010 7:37 PM To: A friendly place where any question about pharo is welcome; pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] [ANN] Traits installer/uninstaller utility Hi all, this is a small package that I wrote after doing a traits-based refactoring of AspectMaps (Plug: Check out AspectMaps for a cool visualization of Aspects. http://pleiad.cl/aspectmaps. It has nice screencasts. All comments welcome!) AspectMaps extends a number of classes of FAMIX to do its thing, using standard class extensions. This works OK when you are not using traits. But when using a trait, you need to redef the class, i.e. change the original package (in this case one of the moose packages). A big no-no. This kind of change should also be encapusulated in the AspectMaps package, but currently this is not possible. So, as long as traits and packages dont play well together, these kinds of refactorings are out. However not so when you are using the TraitsApplication package. This package provides a means to programmatically install/uninstall traits. Call it in a post-load action on a package (if such a thing exists), in a class initialize method, et cetera (for AspectMaps I do it in the AspectMaps>>open method). I thought this could be useful to some members of the community so I am releasing it publicly. You can find it at http://www.squeaksource.com/TraitsApplication CAVEAT: This is a quick implementation, it is non-optimal. It can be made much more elegant, but that requires time that I dont have right now :-(. I does not handle fancy trait compositions (yet). I give no guarantees other than that 1) it passes all of its tests 2) it works for me :-) So check it out. Comments are welcome! -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry 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

May 16, 2010

[Pharo-project] [ANN] Traits installer/uninstaller utility

by Johan Fabry

Hi all, this is a small package that I wrote after doing a traits-based refactoring of AspectMaps (Plug: Check out AspectMaps for a cool visualization of Aspects. http://pleiad.cl/aspectmaps. It has nice screencasts. All comments welcome!) AspectMaps extends a number of classes of FAMIX to do its thing, using standard class extensions. This works OK when you are not using traits. But when using a trait, you need to redef the class, i.e. change the original package (in this case one of the moose packages). A big no-no. This kind of change should also be encapusulated in the AspectMaps package, but currently this is not possible. So, as long as traits and packages dont play well together, these kinds of refactorings are out. However not so when you are using the TraitsApplication package. This package provides a means to programmatically install/uninstall traits. Call it in a post-load action on a package (if such a thing exists), in a class initialize method, et cetera (for AspectMaps I do it in the AspectMaps>>open method). I thought this could be useful to some members of the community so I am releasing it publicly. You can find it at http://www.squeaksource.com/TraitsApplication CAVEAT: This is a quick implementation, it is non-optimal. It can be made much more elegant, but that requires time that I dont have right now :-(. I does not handle fancy trait compositions (yet). I give no guarantees other than that 1) it passes all of its tests 2) it works for me :-) So check it out. Comments are welcome! -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

May 16, 2010

[Pharo-project] Making OCompletion work in Pharo 1.1

by Mariano Martinez Peck

Hi Romain. I was testing a little OCompletion in Pharo 1.1 and I found a bug in ECUntypedModel >> initializeSelectors as it is doing: [ Smalltalk keysDo: [ :each | selectors add: (ECGlobalEntry contents: each type: #globalVar) ]. Smalltalk, SmalltalkImage and SystemDirectory were refectorized. Running OCompletion tests, I have one red. I changed to: [ Smalltalk environment keysDo: [ :each | selectors add: (ECGlobalEntry contents: each type: #globalVar) ]. (notice I added environment) and with this, the test is green and OCompletion seems to be working. What do you think? can I commit ? Cheers Mariano

May 16, 2010

[Pharo-project] Pharo logo

by Geoffroy Couprie

Hello, Where can I find a vectorial version of the Pharo logo? The media files downloadable on pharo-project.org are only in PNG and TIF. I would like to use the logo for a custom UITheme :) Best regards, Geoffroy

May 15, 2010

Re: [Pharo-project] Help testing Pharo 1.1 in big screens!

by Igor Stasenko

On 16 May 2010 01:10, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Now you have to build expose so that with one click we can see the desktop and one click the windows come back in place :) > Yeah, its little bit distracting.. instead of coding, eventually, you'll find yourself sitting and watching images :)) > On May 15, 2010, at 11:58 PM, Igor Stasenko wrote: > >> This one is little bit fixed, (request a list with 1 image, instead of 8) >> and delay 1 minute after error. >> >> >> [ >> >> Â Â Â [[ >> Â Â Â Â Â Â Â | rx str url form | >> Â Â Â Â Â Â Â str := (HTTPSocket httpGet: >> 'http://www.socwall.com/browse/index.php?wpLimit=1&wpSortby=8') >> contents. >> Â Â Â Â Â Â Â rx := '.*(http\://.+tb_.+\.jpg).*' asRegex. >> Â Â Â Â Â Â Â url := (rx matches: str) >> Â Â Â Â Â Â Â Â Â Â Â ifTrue: [ >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â str := (rx subexpression: 2) >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â copyWithRegex: 'tb_' matchesReplacedWith: '' ] >> Â Â Â Â Â Â Â Â Â Â Â ifFalse: [ nil ]. >> Â Â Â Â Â Â Â form := nil. >> Â Â Â Â Â Â Â url ifNotNil: [ >> Â Â Â Â Â Â Â Â Â Â Â form := ImageReadWriter formFromStream: (HTTPSocket httpGet: url). >> Â Â Â Â Â Â Â Â Â Â Â World backgroundImage: form layout: #scaled >> Â Â Â Â Â Â Â ]. >> >> Â Â Â ] on: Error do: [:ex| ]. >> Â Â Â Â Â Â Â 1 minute asDelay wait. >> Â Â Â Â ] repeat. >> >> ] newProcess name: 'Random background changer'; priority: Processor >> userBackgroundPriority; resume >> >> >> >> >> 2010/5/16 Mariano Martinez Peck <marianopeck(a)gmail.com>: >>> Igor, you are my hero. This is fucking great hahahahaha >>> >>> I will use is it for my images!!! Â ahhh you should cache them so that when >>> you are offline you can random the ones you already downloaded ahahahahhaha >>> >>> excellent :) >>> >>> mariano >>> >>> On Sat, May 15, 2010 at 11:48 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >>>> >>>> Guys, this is plain boring :) >>>> >>>> Here is more interesting example (just evaluate it to see what happens) ;) >>>> >>>> [ >>>> >>>> Â Â Â Â [[ >>>> Â Â Â Â Â Â Â Â | rx str url form | >>>> Â Â Â Â Â Â Â Â str := (HTTPSocket httpGet: >>>> 'http://www.socwall.com/browse/index.php?wpSortby=8') contents. >>>> Â Â Â Â Â Â Â Â rx := '.*(http\://.+tb_.+\.jpg).*' asRegex. >>>> Â Â Â Â Â Â Â Â url := (rx matches: str) >>>> Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: [ >>>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â str := (rx subexpression: 2) >>>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â copyWithRegex: 'tb_' matchesReplacedWith: >>>> '' ] >>>> Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [ nil ]. >>>> Â Â Â Â Â Â Â Â form := nil. >>>> Â Â Â Â Â Â Â Â url ifNotNil: [ >>>> Â Â Â Â Â Â Â Â Â Â Â Â form := ImageReadWriter formFromStream: (HTTPSocket >>>> httpGet: url). >>>> Â Â Â Â Â Â Â Â Â Â Â Â World backgroundImage: form layout: #scaled >>>> Â Â Â Â Â Â Â Â ]. >>>> >>>> Â Â Â Â 1 minute asDelay wait. >>>> Â Â Â Â ] on: Error do: [:ex| ] ] repeat. >>>> >>>> ] newProcess name: 'Random background changer'; priority: Processor >>>> userBackgroundPriority; resume >>>> >>>> >>>> >>>> >>>> >>>> 2010/5/15 Mariano Martinez Peck <marianopeck(a)gmail.com>: >>>>> >>>>> >>>>> On Fri, May 14, 2010 at 8:20 PM, StÃ©phane Ducasse >>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>> >>>>>> Yes start a section :) >>>>>> under tips and trick >>>>>> >>>>> >>>>> Done: >>>>> >>>>> http://book.pharo-project.org/book/table-of-contents/CustomizingPharo/Putti… >>>>> >>>>> >>>>> >>>>>> >>>>>> On May 14, 2010, at 8:15 PM, Mariano Martinez Peck wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, May 14, 2010 at 12:14 PM, Gary Chambers >>>>>>> <gazzaguru2(a)btinternet.com> wrote: >>>>>>> Fine for me spanned over two monitors (World extent 3580@1014) in >>>>>>> Vista. >>>>>>> >>>>>>> Note that there is a shorter message form for setting the background >>>>>>> image: >>>>>>> >>>>>>> World backgroundImage: (ImageReadWriter formFromFileNamed: >>>>>>> 'pharoBackground.png') layout: #scaled >>>>>>> >>>>>>> Alternatively, as before, having a .jpg file in your image/changes >>>>>>> directory with the name matching the theme name will load upon theme >>>>>>> change >>>>>>> (Watery 2.jpg for instance) >>>>>>> >>>>>>> It would be really cool a chaper in http://book.pharo-project.org/ >>>>>>> Â about "Customizing your own image" >>>>>>> and we put there all these little and nice tricks. >>>>>>> >>>>>>> >>>>>>> Regards, Gary >>>>>>> >>>>>>> ----- Original Message ----- From: "StÃ©phane Ducasse" >>>>>>> <stephane.ducasse(a)inria.fr> >>>>>>> To: <Pharo-project(a)lists.gforge.inria.fr> >>>>>>> Cc: "A friendly place where any question about pharo is welcome" >>>>>>> <pharo-users(a)lists.gforge.inria.fr> >>>>>>> Sent: Thursday, May 13, 2010 7:44 PM >>>>>>> Subject: Re: [Pharo-project] Help testing Pharo 1.1 in big screens! >>>>>>> >>>>>>> >>>>>>> >>>>>>> On my 30 inches screen >>>>>>> opening in full show some little square due to the limit of the png >>>>>>> :) >>>>>>> >>>>>>> Thanks mariano. >>>>>>> >>>>>>> >>>>>>> On May 13, 2010, at 8:39 PM, Mariano Martinez Peck wrote: >>>>>>> >>>>>>> Hi folks. I re-try (yes, yes, I re-insist hahaha) to have a >>>>>>> background >>>>>>> picture for the PharoDev 1.1. The last time I tried, we had a problem >>>>>>> with >>>>>>> the picture because in big screens instead of making it bigger, it >>>>>>> put it >>>>>>> several times, or it cut it. Now, thanks to Gary, it should work >>>>>>> well. >>>>>>> >>>>>>> So, if you are a lucky guy an have a big screen, can you please take >>>>>>> the >>>>>>> latests PharoCore 1.1 image, for example this: >>>>>>> >>>>>>> >>>>>>> >>>>>>> https://gforge.inria.fr/frs/download.php/26995/PharoCore-1.1-11357-UNSTABLE… >>>>>>> >>>>>>> >>>>>>> How to test it ? >>>>>>> >>>>>>> - Download this in the same directory where the .image is: >>>>>>> https://gforge.inria.fr/frs/download.php/26996/pharoBackground.png >>>>>>> >>>>>>> Then evaluate: >>>>>>> >>>>>>> World backgroundMorph: >>>>>>> Â Â ((UITheme builder >>>>>>> Â Â Â Â newAlphaImage: (ImageReadWriter formFromFileNamed: >>>>>>> 'pharoBackground.png') help: nil) >>>>>>> Â Â Â Â autoSize: false; >>>>>>> Â Â Â Â layout: #scaled; >>>>>>> Â Â Â Â lock) >>>>>>> >>>>>>> >>>>>>> What to test ? >>>>>>> >>>>>>> - You should stretch the pharo image, make it very big, and the >>>>>>> background picture should stretch also together with the image. >>>>>>> - If you notice a performance decrease with it (I don't think so) >>>>>>> - If you like it or not. >>>>>>> - If the resolution is good enough in big screens >>>>>>> >>>>>>> >>>>>>> Thanks! >>>>>>> >>>>>>> Mariano >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> 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 >>> >> >> >> >> -- >> 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 > -- Best regards, Igor Stasenko AKA sig.

May 15, 2010