August 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Early days of an MVP framework

by Gary Chambers

Another example (adoptPaneColor is required if not opened in a window it seems or the tab label 'button' background is not recomputed properly to fit the text). (UITheme builder newColumn: { UITheme builder newTabGroup: { 'First page' -> (UITheme builder newPanel fillStyle: Color red; hResizing: #spaceFill; vResizing: #spaceFill). 'Second page' -> (UITheme builder newPanel fillStyle: Color green; hResizing: #spaceFill; vResizing: #spaceFill)}. (UITheme builder newRow: { UITheme builder newCancelButton. UITheme builder newOKButton}) listDirection: #rightToLeft}) extent: 200@300; openInHand; adoptPaneColor Regards, Gary ----- Original Message ----- From: "Gary Chambers" <gazzaguru2(a)btinternet.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Monday, August 09, 2010 11:07 AM Subject: Re: [Pharo-project] Early days of an MVP framework > Any Morph can use a layoutPolicy. > Available are > none (position based) > Prorportional (frame/fractions/offsets) > Table (overly complex too) > Row (one of mine, quicker for simple rows) > Stack (mine, overlay morphs on top of each other) > > TEasilyThemed provides some methods like... > > newRow: {aMorph, anotherMorph} > newColumn: > > Something like this works... > > (UITheme builder > newColumn: { > UITheme builder newPanel > fillStyle: Color red; > hResizing: #spaceFill; > vResizing: #spaceFill. > UITheme builder newRow: { > UITheme builder newOKButton. > UITheme builder newCancelButton}}) > extent: 200@300; > openInHand > > (can use openInWindow also)... > > Rather busy today, hope this helps in the meantime... > > Regards, Gary > > ----- Original Message ----- > From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> > To: <pharo-project(a)lists.gforge.inria.fr> > Sent: Sunday, August 08, 2010 11:46 PM > Subject: [Pharo-project] Early days of an MVP framework > > >> Gary, >> >> I was on an unstoppable roll (salvaged early on by Andreas' bitblt >> coaching), until I needed to repeat a "complex" GUI component and >> wanted/insisted on doing so with some reuse. Seaside gives us components >> on web pages; we need them for GUI code too. I tried turning my >> presenter-like structures into factories that would add morphs to a >> single shell, but it fell apart when it came time to set the framing >> values. I was not particularly interested in fixing it, because if I >> could do that, I would simply build proper composite widgets using the >> fix. >> >> The problem appears to be in SystemWindow, which does some incredibly >> complicated things, all of which (correct me if I am wrong) would be >> unnecessary if only there were a good set of layout managers. I can get >> very simple-minded about things, but it would make a whole lot more sense >> to me to create rows and columns of widgets, adding splitters between >> them until the whole things behaves as intended, rather than writing code >> (present only in a top-level shell) that tries to split things up into >> rows using its own judgment. Not good. I realize you did not create the >> situation, and have done wonders to make it work far better than when you >> found it. >> >> Some time ago, I built an emulated widget framework for Dolphin, which I >> needed because the combination of Dolphin's view resources and Windows >> itself was too slow for what I was trying to do. That project included a >> somewhat strange set of layout classes, but the basics are present, and >> it is not Object Arts' IP. I ported the classes to Pharo and did some >> work on stub View and Presenter classes that I had added to Pharo largely >> to passify my code that I was importing from Dolphin. The layouts think >> in terms of emulated widgets, and I see no reason to change their minds: >> I might want to replicate the framework. However, dynamic typing and a >> couple of extra methods allow them to work with just about anything. My >> goals are modest. Being able to compose rows and columns would do a lot >> for me. Add splitters and the ability to fix the size of some items, and >> I could almost anything I would need. >> >> View class>>example >> | row column dot square out shell | >> dot := ( Form dotOfSize:100 ) asFormOfDepth:32. >> square := ( Form squareOfSize:100 ) asFormOfDepth:32. >> out := Array writeStream. >> >> row := ContainerView row. >> 2 timesRepeat:[ >> column := row addSubview:ContainerView column. >> 2 timesRepeat:[ >> out nextPut:( >> column addSubview:ImageView new >> ). >> ]. >> ]. >> >> out contents with:{ dot copy. square copy. square copy. dot copy. } >> do:[ :view :form | >> view morph image:form. >> ]. >> >> row rectangle:( 0@0 extent:400@400 ). >> row layout. >> >> shell := StandardWindow labelled:'Hello MVP'. >> ^shell addMorph:row morph frame:( 0@0 extent:1@1 ); yourself. >> >> >> The above code produces an array of dots and squares, as intended. One >> quirk is that the grid does not resize as the shell resizes, a >> consequence of my not having hooked it up to resize events. I might get >> some interesting meltdowns once I begin to do that =:0 I used your >> PanelMorph as the "view" associated with ContainerView. What, >> ContainView isn't a view??? No. The code is biased toward Morphic, but >> hopefully the same code should extend to wx, GTK, etc. Dolphin's views >> have a handle instance variable to control the external resource; these >> views have an instance variable pointing to their morph. Handling of sub >> views works pretty much as in Dolphin: any view/morph can have children, >> but adding them is "legal" only for composites. >> >> Most systems I have seen treat coordinates relative to the parent/owner, >> but not Morphic. I remember seeing plans to make the change, but nothing >> after that. The view instances provide a natural place to fix things, so >> I took the plunge. If we switch to some other graphical realization, we >> can simply remove the the transformation. >> >> Are the existing splitters as strange as SystemWindow? By that I mean, >> would it be reasonable to add them between other morphs and look for >> events from them, or will they have to be replaced? I will eventually >> need splitters, but I could initially live without them if I can get >> reliable composition where I need it. >> >> There are very few view classes at present. MorphView can wrap almost >> anything, so it might be better to create a rich set of presenters >> instead. Dolphin's view resources are going to be interesting to >> replace. There are some complexities that I suspect are in deference to >> Windows, and some that might be avoidable. For our purposes, it might be >> enough to use SIXX to serialize a bunch of message sends and gzip the >> results to save memory. Another option might be to rely on class >> methods; having full closures won't hurt; they might allow sufficient >> hooking that resources in the Dolphin sense won't even be necessary. The >> desire for them quickly arises because views get realized in places know >> nothing about how the views should be configured; at least I think that >> is what happened to me after just a couple of hours. I am far less >> interested in having a graphical view editor than I am in being able to >> write **GOOD** code that assembles things as I want. If the result >> happens to allow a graphical editor too, so much the better. >> >> Any interest? >> >> Bill >> >> >> ----------------------------- >> >> View >> MorphViev >> ImageView >> ContainerView >> >> ViewGadgetLayoutAbstract >> ScrollerGadgetLayout >> NullViewGadgetLayout >> FixedStretchFixedGadgetLayout >> ProportionalGadgetLayout >> PreferredExtentsGadgetLayout >> GridGadgetRowsLayout >> VerticalListLayout >> >> >> _______________________________________________ >> 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

Aug. 9, 2010

Re: [Pharo-project] Early days of an MVP framework

by Gary Chambers

Any Morph can use a layoutPolicy. Available are none (position based) Prorportional (frame/fractions/offsets) Table (overly complex too) Row (one of mine, quicker for simple rows) Stack (mine, overlay morphs on top of each other) TEasilyThemed provides some methods like... newRow: {aMorph, anotherMorph} newColumn: Something like this works... (UITheme builder newColumn: { UITheme builder newPanel fillStyle: Color red; hResizing: #spaceFill; vResizing: #spaceFill. UITheme builder newRow: { UITheme builder newOKButton. UITheme builder newCancelButton}}) extent: 200@300; openInHand (can use openInWindow also)... Rather busy today, hope this helps in the meantime... Regards, Gary ----- Original Message ----- From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> To: <pharo-project(a)lists.gforge.inria.fr> Sent: Sunday, August 08, 2010 11:46 PM Subject: [Pharo-project] Early days of an MVP framework > Gary, > > I was on an unstoppable roll (salvaged early on by Andreas' bitblt > coaching), until I needed to repeat a "complex" GUI component and > wanted/insisted on doing so with some reuse. Seaside gives us components > on web pages; we need them for GUI code too. I tried turning my > presenter-like structures into factories that would add morphs to a single > shell, but it fell apart when it came time to set the framing values. I > was not particularly interested in fixing it, because if I could do that, > I would simply build proper composite widgets using the fix. > > The problem appears to be in SystemWindow, which does some incredibly > complicated things, all of which (correct me if I am wrong) would be > unnecessary if only there were a good set of layout managers. I can get > very simple-minded about things, but it would make a whole lot more sense > to me to create rows and columns of widgets, adding splitters between them > until the whole things behaves as intended, rather than writing code > (present only in a top-level shell) that tries to split things up into > rows using its own judgment. Not good. I realize you did not create the > situation, and have done wonders to make it work far better than when you > found it. > > Some time ago, I built an emulated widget framework for Dolphin, which I > needed because the combination of Dolphin's view resources and Windows > itself was too slow for what I was trying to do. That project included a > somewhat strange set of layout classes, but the basics are present, and it > is not Object Arts' IP. I ported the classes to Pharo and did some work > on stub View and Presenter classes that I had added to Pharo largely to > passify my code that I was importing from Dolphin. The layouts think in > terms of emulated widgets, and I see no reason to change their minds: I > might want to replicate the framework. However, dynamic typing and a > couple of extra methods allow them to work with just about anything. My > goals are modest. Being able to compose rows and columns would do a lot > for me. Add splitters and the ability to fix the size of some items, and > I could almost anything I would need. > > View class>>example > | row column dot square out shell | > dot := ( Form dotOfSize:100 ) asFormOfDepth:32. > square := ( Form squareOfSize:100 ) asFormOfDepth:32. > out := Array writeStream. > > row := ContainerView row. > 2 timesRepeat:[ > column := row addSubview:ContainerView column. > 2 timesRepeat:[ > out nextPut:( > column addSubview:ImageView new > ). > ]. > ]. > > out contents with:{ dot copy. square copy. square copy. dot copy. } do:[ > :view :form | > view morph image:form. > ]. > > row rectangle:( 0@0 extent:400@400 ). > row layout. > > shell := StandardWindow labelled:'Hello MVP'. > ^shell addMorph:row morph frame:( 0@0 extent:1@1 ); yourself. > > > The above code produces an array of dots and squares, as intended. One > quirk is that the grid does not resize as the shell resizes, a consequence > of my not having hooked it up to resize events. I might get some > interesting meltdowns once I begin to do that =:0 I used your PanelMorph > as the "view" associated with ContainerView. What, ContainView isn't a > view??? No. The code is biased toward Morphic, but hopefully the same > code should extend to wx, GTK, etc. Dolphin's views have a handle > instance variable to control the external resource; these views have an > instance variable pointing to their morph. Handling of sub views works > pretty much as in Dolphin: any view/morph can have children, but adding > them is "legal" only for composites. > > Most systems I have seen treat coordinates relative to the parent/owner, > but not Morphic. I remember seeing plans to make the change, but nothing > after that. The view instances provide a natural place to fix things, so > I took the plunge. If we switch to some other graphical realization, we > can simply remove the the transformation. > > Are the existing splitters as strange as SystemWindow? By that I mean, > would it be reasonable to add them between other morphs and look for > events from them, or will they have to be replaced? I will eventually > need splitters, but I could initially live without them if I can get > reliable composition where I need it. > > There are very few view classes at present. MorphView can wrap almost > anything, so it might be better to create a rich set of presenters > instead. Dolphin's view resources are going to be interesting to replace. > There are some complexities that I suspect are in deference to Windows, > and some that might be avoidable. For our purposes, it might be enough to > use SIXX to serialize a bunch of message sends and gzip the results to > save memory. Another option might be to rely on class methods; having > full closures won't hurt; they might allow sufficient hooking that > resources in the Dolphin sense won't even be necessary. The desire for > them quickly arises because views get realized in places know nothing > about how the views should be configured; at least I think that is what > happened to me after just a couple of hours. I am far less interested in > having a graphical view editor than I am in being able to write **GOOD** > code that assembles things as I want. If the result happens to allow a > graphical editor too, so much the better. > > Any interest? > > Bill > > > ----------------------------- > > View > MorphViev > ImageView > ContainerView > > ViewGadgetLayoutAbstract > ScrollerGadgetLayout > NullViewGadgetLayout > FixedStretchFixedGadgetLayout > ProportionalGadgetLayout > PreferredExtentsGadgetLayout > GridGadgetRowsLayout > VerticalListLayout > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 9, 2010

Re: [Pharo-project] Keyboard Shortcuts: Keymapping now loads in Pharo core 1.2

by Tim Mackinnon

On 2010-08-08 23:52:45 +0100, Sean P. DeNigris said: > To get the ball moving, I ported one of the keyboard shortcut packages, > Keymapping, to Pharo. Maybe if we start playing with it, we'll see what > works and what doesn't, and use it to create something great. > > The Metacello configuration is at http://www.squeaksource.com/Keymapping > > Sean That's awesome - I want to have a look before ESUG (I recall you're going - so maybe we can get some interest on this), as I'm quite keen to get some better shortcuts for the more used refactorings (like extract method, extract temp, inline temp...) - so then the experience becomes more like using eclipse. I'm also keen to get some additional keystrokes for things like - delete line, indent line/selection etc. - so hopefully this can support that as well. Tim

Aug. 9, 2010

Re: [Pharo-project] TextMorph without being able to be edited?

by StÃ©phane Ducasse

Yes! On Aug 9, 2010, at 11:07 AM, Fernando olivero wrote: > Try NewTextMorph! > > t := NewTextMorph new. > t > borderWidth: 1; > borderColor: Color red; > color: Color white; > padding: 5 ; > readOnly: true; > autoFit: true ; > text: 'I present my text as read only ' asText ; > openInWorld. > > Fernando > On Aug 7, 2010, at 12:26 PM, Carla F. Griggio wrote: > >> Hi again, everyone! >> >> I think this might be really really silly, but I couldn't find a way to show a TextMorph without the ability to edit it's text. >> If I use a StringMorph to show a paragraph, it looks horrible, but if I use a TextMorph and click on it, a blue border appears and I'm able to edit the text, I don't want that to happen. >> >> Is there another morph for showing text that only shows text and nothing else? Or a property of TextMorph that I'm missing? >> >> >> Thanks! >> Carla >> <ATT00001..txt> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 9, 2010

Re: [Pharo-project] TextMorph without being able to be edited?

by Fernando olivero

Try NewTextMorph! t := NewTextMorph new. t borderWidth: 1; borderColor: Color red; color: Color white; padding: 5 ; readOnly: true; autoFit: true ; text: 'I present my text as read only ' asText ; openInWorld. Fernando On Aug 7, 2010, at 12:26 PM, Carla F. Griggio wrote: > Hi again, everyone! > > I think this might be really really silly, but I couldn't find a way to show a TextMorph without the ability to edit it's text. > If I use a StringMorph to show a paragraph, it looks horrible, but if I use a TextMorph and click on it, a blue border appears and I'm able to edit the text, I don't want that to happen. > > Is there another morph for showing text that only shows text and nothing else? Or a property of TextMorph that I'm missing? > > > Thanks! > Carla > <ATT00001..txt>

Aug. 9, 2010

Re: [Pharo-project] SocketStream enh

by StÃ©phane Ducasse

May be you missed this call but this is an important one. On Aug 8, 2010, at 6:43 PM, StÃ©phane Ducasse wrote: > Hi lukas and others.... > > I will integrate the following SocketStream tests and before I would love to see if this > does not impact seaside > > http://code.google.com/p/pharo/issues/detail?id=2767 and related fixes. > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 9, 2010

Re: [Pharo-project] 10 year old slides "Stable Squeak"

by StÃ©phane Ducasse

pharo father :) Stef On Aug 9, 2010, at 9:50 AM, Marcus Denker wrote: > ... while slowly improving the archive of ESUG, I found these 10 year old slides: > > http://www.slideshare.net/esug/stable-squeak-world-tour > > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 9, 2010

[Pharo-project] 10 year old slides "Stable Squeak"

by Marcus Denker

... while slowly improving the archive of ESUG, I found these 10 year old slides: http://www.slideshare.net/esug/stable-squeak-world-tour Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Aug. 9, 2010

Re: [Pharo-project] List of Downloadable Tools

by Miguel Enrique CobÃ¡ MartÃnez

El sÃ¡b, 07-08-2010 a las 22:07 -0300, Guillermo Polito escribiÃ³: > Hi! I was looking for a Pharo Dev 1.2 image and I didn't find it... > I guess it doesn't exists, so I want to make my own downloading a few > tools like OB, eCompletion in a 1.2 Core image. So I began looking > for gofer or metacello scripts to do it :P. I searched in the > Collaboractive Book, the PBE, the mailing list... > > Finally looking some mails and browsing the MetacelloRepository, I > figured out something like "ConfigurationOfOmniBrowser project > lastVersion load" that succeded with a little help :P. > > Soo, after some time doing this a few questions come to my mind: > > -Is there an up to date list of the tools we pharoers count on and how > to load them? I mean OB, eCompletion, FFI, Mondrian... > -Is there a list of the tools current Dev images have? I found a > ConfigurationOfPharo and I thought It should behave like that. In the pharo download page (http://pharo-project.org/pharo-download) you get: Pharo 1.1 image (stable): http://gforge.inria.fr/frs/download.php/27300/Pharo-1.1-11411dev10.07.1.zip then unzipping it you find inside the installScript.st, that is used to build the developer image from a PharoCore released image. This scripts evaluates: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. ((Smalltalk at: #ConfigurationOfPharo) project version: '1.1') perform: #silently: with: true; perform: #load. And indeed the ConfigurationOfPharo is the one used to build the image. There you'll find the list of packages that are loaded in the image. Cheers > > Maybe there's a wiki or a webpage I'm missing. > > Thanks! > Guille > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Aug. 9, 2010

Re: [Pharo-project] List of Downloadable Tools

by Guillermo Polito

And the other questions? anybody? :( I can do some little work on the Collaboractive book (Mariano, I can't edit and I know you do it usually :P. Can I ask you for a user?), but I would like to have not just the list of the tools, but also a little explaing of each one... Here is the (copypasted) list of packages in the ConfigurationOfPharo I would like to have a little description: *project: 'OB Dev' with: [ spec className: 'ConfigurationOfOmniBrowser'; loads: #('Dev'); file: 'ConfigurationOfOmniBrowser'; repository: 'http://www.squeaksource.com/MetacelloRepository' ]; project: 'OB Dev Tests' copyFrom: 'OB Dev' with: [ spec loads: #('Dev Tests') ]; project: 'AutomaticMethodCategorizer' with: [ spec className: 'ConfigurationOfAutomaticMethodCategorizer'; file: 'ConfigurationOfAutomaticMethodCategorizer'; repository: ' http://www.squeaksource.com/MetacelloRepository' ]; project: 'ScriptManager' with: [ spec className: 'ConfigurationOfScriptManager'; file: 'ConfigurationOfScriptManager'; loads: 'ALL'; repository: ' http://www.squeaksource.com/MetacelloRepository' ]; project: 'Shout' with: [ spec className: 'ConfigurationOfShout'; loads: #('Core'); file: 'ConfigurationOfShout'; repository: ' http://www.squeaksource.com/MetacelloRepository' ]; project: 'Shout Tests' copyFrom: 'Shout' with: [ spec loads: #('Tests') ]; project: 'OCompletion' with: [ spec className: 'ConfigurationOfOCompletion'; loads: #('Core'); file: 'ConfigurationOfOCompletion'; repository: ' http://www.squeaksource.com/MetacelloRepository' ]; project: 'OCompletion Tests' copyFrom: 'OCompletion' with: [ spec loads: #('Tests') ]; project: 'PharoNonCorePackages' with: [ spec className: 'ConfigurationOfPharoNonCore'; file: 'ConfigurationOfPharoNonCore'; repository: ' http://www.squeaksource.com/MetacelloRepository' ]; project: 'NewInspector' with: [ spec className: 'ConfigurationOfNewInspector'; file: 'ConfigurationOfNewInspector'; repository: ' http://www.squeaksource.com/MetacelloRepository' ]; project: 'RefactoringBrowser' with: [ spec className: 'ConfigurationOfRefactoringBrowser'; loads: #('Core'); file: 'ConfigurationOfRefactoringBrowser'; repository: ' http://www.squeaksource.com/MetacelloRepository' ]; project: 'RefactoringBrowser Tests' copyFrom: 'RefactoringBrowser' with: [ spec loads: #('Tests') ]; project: 'Nile' with: [ spec className: 'ConfigurationOfNile'; loads: #('Core'); file: 'ConfigurationOfNile'; repository: ' http://www.squeaksource.com/MetacelloRepository' ]; project: 'Nile Tests' copyFrom: 'Nile' with: [ spec loads: #('Tests') ]; project: 'ProfStef' with: [ spec className: 'ConfigurationOfProfStef'; loads: #('Core' 'Browser'); file: 'ConfigurationOfProfStef'; repository: ' http://www.squeaksource.com/MetacelloRepository' ]; project: 'ProfStef Tests' copyFrom: 'ProfStef' with: [ spec loads: #('Tests')]; project: 'Metacello' with: [ spec className: 'ConfigurationOfMetacello'; file: 'ConfigurationOfMetacello'; loads: #('Metacello-Core' 'Tutorial' 'UI' 'Metacello-ProfStef' 'Metacello-Help'); repository: ' http://www.squeaksource.com/MetacelloRepository' ]; project: 'Metacello Tests' copyFrom: 'Metacello' with: [ spec loads: #('Tests') ].* And another question: Is somewhere written a tutorial of metacello and/or gofer? I only know that ProfStef has something about metacello (I'll look at it). Cheers! 2010/8/8 laurent laffont <laurent.laffont(a)gmail.com> > 2010/8/8 Guillermo Polito <guillermopolito(a)gmail.com> > > Hi! I was looking for a Pharo Dev 1.2 image and I didn't find it... I >> guess it doesn't exists, so I want to make my own downloading a few tools >> like OB, eCompletion in a 1.2 Core image. So I began looking for gofer or >> metacello scripts to do it :P. I searched in the Collaboractive Book, the >> PBE, the mailing list... >> >> Finally looking some mails and browsing the MetacelloRepository, I figured >> out something like "*ConfigurationOfOmniBrowser project lastVersion load*" >> that succeded with a little help :P. >> >> Soo, after some time doing this a few questions come to my mind: >> >> -Is there an up to date list of the tools we pharoers count on and how to >> load them? I mean OB, eCompletion, FFI, Mondrian... >> -Is there a list of the tools current Dev images have? I found a >> ConfigurationOfPharo and I thought It should behave like that. >> > > IIRC Pharo (Dev) = PharoCore + ConfigurationOfPharo loaded > > > >> >> Maybe there's a wiki or a webpage I'm missing. >> > > Could you create it in Pharo Collaboractive book ? > > > Cheers, > > Laurent > > >> >> Thanks! >> Guille >> >> _______________________________________________ >> 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 >

Aug. 9, 2010