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

Re: [Pharo-project] [SPAM] Re: Gravatar and Website (was little pictures of you )

by Sven Van Caekenberghe

On 13 Aug 2010, at 14:03, laurent laffont wrote: > On Fri, Aug 13, 2010 at 12:55 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > send them the code for pharo :) > > > Kata for better code ? (sorry German) > > |md5 url| > md5 := MD5 new hashStream: (ReadStream on: 'gsa(a)arsol.net'). > url := String streamContents: [:aStream| > aStream nextPutAll: 'http://www.gravatar.com/avatar/'. > md5 do: [:aByte| > aStream nextPutAll: aByte hex asLowercase]]. > (ImageMorph fromStream: > (url asUrl retrieveContents contentStream)) openInWorld. > > Laurent I really like code that speaks for itself, like this example ! Great, Laurent. It can even be written shorter, like this: | md5 url | md5 := MD5 hashMessage: 'gsa(a)arsol.net'. url := ('http://www.gravatar.com/avatar/', md5 hex) asUrl. (ImageMorph fromStream: url retrieveContents contentStream) openInWorld. Sven

Aug. 13, 2010

[Pharo-project] binding

by StÃ©phane Ducasse

Hi Class>>binding ^ Smalltalk globals associationAt: name ifAbsent: [ nil -> self ] and it should be Class>>binding ^ self environment associationAt: name ifAbsent: [ nil -> self ] since the environment of the class could be another systemDictionary. Class>>environment environment == nil ifTrue: [^ super environment]. ^ environment http://code.google.com/p/pharo/issues/detail?id=2799 Stef

Aug. 13, 2010

Re: [Pharo-project] [Survey] Assess the cycles in your software

by Laval Jannik

Hi all, A (second) reminder for people who wants to participate. We need help from the community. Cheers, Jannik On Jul 19, 2010, at 08:36 , Laval Jannik wrote: > Hi Pharoers, and Smalltalkers in general, > > Have you seen waited to assess the cycles in your software? Now you can :) > > We request some of you to perform an experiment using DSM to see your software package structure and to fix cycles between packages. Our tool shows dependencies between packages and highlight some bad dependencies generating structure cycles. It also helps to understand dependencies. > > Your goal is to fill a survey using our tool. > I prepared a mini-tutorial about DSM and eDSM. It can help you to understand the visualization tool. > > To ease the use of our tool, I loaded it in a PharoCore1.2. And there are two archives available: > - the first contains an image with our tool with a model of Pharo loaded in it, so you can play with our tool on pharo itself. It can be downloaded here: http://dl.dropbox.com/u/7739334/dsmWithPharo.zip. Pay attention, the image is slow. > - the second contains the same thing without the model of Pharo. Here, you have to load your code, then populate a moose model and use the tool. It can be downloaded here: http://dl.dropbox.com/u/7739334/dsmWithoutPharo.zip > The two archives contain the tutorial and the survey. If you are a pharo integrator, we suggest you to take the one with Pharo model loaded, else the other. > > To use our tool, load your tool in Pharo. Then do "MoosePanel open", and import your software in Moose by "import from Smalltalk image". When it is imported, select your project in the list on the left of MoosePanel, and select "all model packages" on the list on center. > > Then, you have two choices: > - you can scan all your project: right click on "all model packages" and do DSM. > - or select "all model packages" then select some packages in the next list and right click, do DSM. > > After that, you can perform the survey (with reading of the tutorial). We need your answers for the end of August. So, you have two months to do it. > > If you have any question, just let me know. > > Best regards, > Jannik. > > --- > Jannik Laval > PhD Student - Rmod Team - INRIA > Certified Project Management Associate (IPMA) > http://www.jannik-laval.eu > http://rmod.lille.inria.fr > --- > --- Jannik Laval

Aug. 13, 2010

Re: [Pharo-project] Which options do we have to persist?

by Guillermo Polito

Yes, that's step #3 :P On Fri, Aug 13, 2010 at 7:20 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Guillermo > > if you can write some pages to structure a bit this happy mess it would be > excellent. > We need more structure in our documentation. > > stef > > On Aug 12, 2010, at 6:56 PM, Guillermo Polito wrote: > > > I want to document this a bit and I don't know if there's something > written somewhere. > > > > I already know SqueakDBX, Magma, Omnibase. Is there something else? > > What about ORMs? Glorp? > > > > If you can provide me also links, metacello configs, and what's the > status of them for each version of pharo, it shoud be great! :D > > > > 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. 13, 2010

Re: [Pharo-project] Remove ParagraphEditor

by Guillermo Polito

On Fri, Aug 13, 2010 at 7:08 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Good initiative! > May be we should chop them into pieces :) > > We can do it, but it's very important the order in which you install them in order to don't break the image :D. > Did you attach them to the bug entry? > I will have a look at them. > Yesterday I submitted it to the inbox :P. > > Fernando do you have a bit of time to have a look at that too? > > Stef > > On Aug 11, 2010, at 8:07 PM, Guillermo Polito wrote: > > > Hi! > > > > I've prepared a changeset where there are the following changes > > > > - replace ParagraphEditor by SmalltalkEditor > > - replace TextMorphEditor by SmalltalkEditor or TextEditor where it > corresponds(or I suppose so) > > - some changes in SmalltalkEditor and some classes like Workspace, > Inspector, ObjectExplorer... following the current versions of them in CUIS > > - lazy inicialization of keybindings in SmalltalkEditor and TextEditor > > - removal of ParagraphEditor and TextEditor > > > > I'm a little scared to submit this change to the inbox because I would > like more people to try it... > > > > To install it you have to close every window, open the File browser, > install the changeset and close the filebrowser, because if not there may > remain references to AnObsoleteParagraphEditor. > > > > Cheers! > > > <ParagraphEditorRemoval.1.cs>_______________________________________________ > > 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. 13, 2010

Re: [Pharo-project] Remove ParagraphEditor

by Guillermo Polito

I did it in 1.2 On Fri, Aug 13, 2010 at 11:08 AM, Francisco Ortiz PeÃ±aloza < patchinko(a)gmail.com> wrote: > Guille, > > over which version should i install it? I tried Pharo 1.1 without no luck.. > > On Fri, Aug 13, 2010 at 7:08 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > Good initiative! > > May be we should chop them into pieces :) > > > > Did you attach them to the bug entry? > > I will have a look at them. > > > > Fernando do you have a bit of time to have a look at that too? > > > > Stef > > > > On Aug 11, 2010, at 8:07 PM, Guillermo Polito wrote: > > > >> Hi! > >> > >> I've prepared a changeset where there are the following changes > >> > >> - replace ParagraphEditor by SmalltalkEditor > >> - replace TextMorphEditor by SmalltalkEditor or TextEditor where it > corresponds(or I suppose so) > >> - some changes in SmalltalkEditor and some classes like Workspace, > Inspector, ObjectExplorer... following the current versions of them in CUIS > >> - lazy inicialization of keybindings in SmalltalkEditor and TextEditor > >> - removal of ParagraphEditor and TextEditor > >> > >> I'm a little scared to submit this change to the inbox because I would > like more people to try it... > >> > >> To install it you have to close every window, open the File browser, > install the changeset and close the filebrowser, because if not there may > remain references to AnObsoleteParagraphEditor. > >> > >> Cheers! > >> > <ParagraphEditorRemoval.1.cs>_______________________________________________ > >> 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 >

Aug. 13, 2010

Re: [Pharo-project] Remove ParagraphEditor

by Francisco Ortiz PeÃ±aloza

Guille, over which version should i install it? I tried Pharo 1.1 without no luck.. On Fri, Aug 13, 2010 at 7:08 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Good initiative! > May be we should chop them into pieces :) > > Did you attach them to the bug entry? > I will have a look at them. > > Fernando do you have a bit of time to have a look at that too? > > Stef > > On Aug 11, 2010, at 8:07 PM, Guillermo Polito wrote: > >> Hi! >> >> I've prepared a changeset where there are the following changes >> >> - replace ParagraphEditor by SmalltalkEditor >> - replace TextMorphEditor by SmalltalkEditor or TextEditor where it corresponds(or I suppose so) >> - some changes in SmalltalkEditor and some classes like Workspace, Inspector, ObjectExplorer... following the current versions of them in CUIS >> - lazy inicialization of keybindings in SmalltalkEditor and TextEditor >> - removal of ParagraphEditor and TextEditor >> >> I'm a little scared to submit this change to the inbox because I would like more people to try it... >> >> To install it you have to close every window, open the File browser, install the changeset and close the filebrowser, because if not there may remain references to AnObsoleteParagraphEditor. >> >> Cheers! >> <ParagraphEditorRemoval.1.cs>_______________________________________________ >> 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. 13, 2010

Re: [Pharo-project] Contributors page (was little pictures of you)

by Francois Stephany

I've started to work on a project to list usable Pharo/Squeak packages. Kind of http://ruby-toolbox.com/ for open source smalltalks. The basic idea is to have a list of packages with a description and how to load them (basically via Metacello configuration). People could comment packages to let other know if it works for them in their favorite dialect. If a convention toward package management with Metacello is reached we could imagine that data is automatically fetched from Metacello description. But lets start simple first... Crawling Squeaksource to find libraries is a not a delicious experience (at least for me). It's probably premature to talk about this project here now (especially given my time constraints these days) but this thread motivates me to give it a serious try. Cheers, Francois -- francois.stephany(a)agilitic.com http://www.agilitic.com +32 (0)484/580.322 On 13/08/10 15:27, Adrian Lienhard wrote: > Yea, that's a good question. I think it's primarily for us. Who else would be interested? Someone taking a technology decision? "Sure, I'm going to use Pharo â these guys look so cute!" ;). Not likely. > > So, the Google wiki could be a better place. Unless we want to argue that the website is not only for new people learning about Pharo but also for us to build the community. > > Adrian > > On Aug 13, 2010, at 14:35 , Carla F. Griggio wrote: > >> Hmmm maybe this is turning into something different than the original >> intention? (or at least what it seemed the original intention to me) >> >> I think that 'having a page' is making this a little more formal than it >> first looked like :P Because it's not the same if its a page in the website >> that can be used as a reference to people visiting the website (people other >> than us), than something 'internal' only used to know our faces. I think >> that's why you ended up thinking about 'who's in and who's out'. >> >> So why do you want this on the pharo-project.org website? Do you really want >> it to be some reference to the public of that website, or just something >> informal for us to use? >> >> On Fri, Aug 13, 2010 at 9:13 AM, Adrian Lienhard<adi(a)netstyle.ch> wrote: >> >>> >>> On Aug 13, 2010, at 14:01 , Norbert Hartl wrote: >>> >>>> >>>> On 13.08.2010, at 07:58, laurent laffont wrote: >>>> >>>>> On Fri, Aug 13, 2010 at 4:59 AM, Serge Stinckwich< >>> serge.stinckwich(a)gmail.com> wrote: >>>>> Nice ! But you know i'm not a big contributor to Pharo. >>>>> >>>>> >>>>> The page is "Contributors", not "Big contributors" :) I wonder if I >>> should change it to "Contributors& Users". Users are really important >>> because it shows Pharo is used in real world. >>>>> >>>>> One of the first question when I show Pharo is: who use it ? It seems >>> people don't care if it's good or not. Knowing that there's users bring >>> confidence. >>>>> >>>> So, who is supposed on this page? :) I'm also no big contributor if one >>> at all. >>> >>> I would define it like this: everyone who is part of the Pharo community in >>> that he contributes or is engaged in discussions. >>> >>> So if there is somebody who hasn't contributed but who we know from the >>> mailing list or conferences, its also nice to have him on the page. On the >>> other hand, if it is somebody who we don't know because he doesn't >>> participate, there's no point in adding him. >>> >>> Adrian >>> >>> >>>> >>>> Norbert >>>> >>>>> Laurent >>>>> >>>>> Maybe for people who have a Gravatar account, you can use their >>>>> pictures, so people have control on their own pictures. >>>>> Regards >>>>> >>>>> 2010/8/13 laurent laffont<laurent.laffont(a)gmail.com>: >>>>>> Hi, >>>>>> I've started a Contributors >>>>>> page http://pharo-project.org/about/contributors. >>>>>> Tell me if you like it or not before going further. >>>>>> If you want to be on this page, just send me a photo (120px wide at >>> least) >>>>>> and links, short text you want to put here. >>>>>> Cheers, >>>>>> Laurent Laffont >>>>>> >>>>>> http://pharocasts.blogspot.com/ >>>>>> http://magaloma.blogspot.com/ >>>>>> >>>>>> >>>>>> On Wed, Aug 11, 2010 at 12:47 PM, StÃ©phane Ducasse >>>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>>> >>>>>>> Hi guys >>>>>>> >>>>>>> the pharo web site does not support that yet :) >>>>>>> but I would love to have some pictures of you because this is not that >>> fun >>>>>>> to talk daily with people >>>>>>> when we do not even know their faces so we could start to build a >>> pharo >>>>>>> fun community. >>>>>>> Let me know what you think. >>>>>>> >>>>>>> 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 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Serge Stinckwich >>>>> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >>>>> Every DSL ends up being Smalltalk >>>>> http://doesnotunderstand.org/ >>>>> >>>>> _______________________________________________ >>>>> 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

Aug. 13, 2010

Re: [Pharo-project] [ANN] Pharo Metacello Universes

by Mariano Martinez Peck

> > > > > Metacello > > ------------- > > This is the most difficult part. > > - Right now, Metacello hardcodes repository paths in the references to > > other projects. This isn't bad, but an alternative should be provided. > > That is, when referencing external projects like: > > > > project: 'Refactoring-Core' with: [ > > spec > > className: 'ConfigurationOfRefactoringBrowser'; > > loads: #('Refactoring-Core' ); > > file: 'ConfigurationOfRefactoringBrowser'; > > repository: 'http://www.squeaksource.com/MetacelloRepository' ]; > > > But a spec is an object so we could have a visitor going over and doing the > automatic > rewrite for us. > > maybe repositoryOverrides: does exactly that...I don't know > > Of course nothing prevents for a configuration to reference a project > > outside the "universe" repository, but that is a decision of the > > maintainer. > > No this is a dogma. NO NO NO reference outside the repository. > NOT A SINGLE ONE. NEVER. > We want 100% self contained distribution. > +99999 > > Stef > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 13, 2010

Re: [Pharo-project] [ANN] Pharo Metacello Universes

by Mariano Martinez Peck

> > > > > > and > > > > http://www.squeaksource.com/Pharo11Metacello > > > > I didn't send any email because I was not sure about certain points. I > > want to discuss them now: > > > > 1) Problem: know which project version must be used for a particular > > pharo version. There are two solutions: > > > > a) When a developer commites ConfigurationOf to a particular repo, it > > makes sure the #lastVersion answer the correct one. > > b) When a developer commites ConfigurationOf to a particular repo, it > > makes sure the #load will load the correct version. > > > I think that for Pharo 1.0 and Pharo 1.1 there is little we can do as > they are already outhere. No...I think it is possible. It doesn't care they are out there. Continue reaeding my answer. > The will continue referencing > MetacelloRepository forever. And in that repo there are all the possible > dependencies they need. So they need no change in the infrastructure. > > Now, if we forget about 1.0 and 1.1 and concentrate in 1.2, then we can > make a big change. I propose: > I wouldn't forget about 1.0 and 1.1 > > 1. Add to the image (maybe SystemVersion current metacelloRepository) a > getter that returns the standardized string pointing to the correct > metacello repository for the image: > > SystemVersion>>metacelloRepository > ^ 'MetaRepoForPharo12' > > And then all the series of Pharo releases based on that PharoCore image > will point to MetaRepoPharo12 (PharoCore 1.2, PharoCore 1.2.1, PharoCore > 1.2.2, Pharo 1.2, Pharo 1.2.1, Pharo 1.2.4, etc. They are the same > release family and supposedly "binary" compatible). > > For PharoCore 1.3, that string should be changed to > > SystemVersion>>metacelloRepository > ^ 'MetaRepoForPharo13' > > and so on. > > That is the base image and derived images for Pharo. > > Now to the tools, Gofer, GoferProjectLoader and Metacello. > > Gofer > ------ > add a universe method (this name is overloaded so a better name is > wanted, maybe metacelloRepository or pharoRepository) so that we can do: > > Gofer new > universe; "or metacelloRepository or pharoRepository" > project: 'ConfigurationOfMagma"; > load. > > The universe (or whatever its name be) just uses SystemVersion current > metacelloRepository to get everything from the correct repository. > > GoferProjectLoader > ------------------ > This could be improved to get every package (that is, a metacello > configuration) from the correct repository by delegating to gofer new > universe and avoiding to resolve itself the repository for the image. > Also, if GoferProjectLoader is part of the core image, then maybe gofer > shouldn't have the universe functionality, but GoferProjectLoader should > have it, and only use gofer to fetch the monticello packages. This way I > think is cleaner, because Gofer is only used as a medium to get things > and knows nothing about universes and repositories depending on a given > image release. > > All you mention here has sense to LOAD projects. And I agree this changes could be only for Pharo 1.2 (like the change in SystemVersion). But someone should be able to do everything by code. For example, in Pharo 1.0 I could do: Gofer new repository: 'pharoRepository10" project: 'ConfigurationOfMagma"; load. But I think this is a further step. We need to FIRST think how to WRITE the configuration. And how to load it with Metacello. I don't care Gofer neither Loader for the first step. > Metacello > ------------- > This is the most difficult part. > - Right now, Metacello hardcodes repository paths in the references to > other projects. This isn't bad, but an alternative should be provided. > That is, when referencing external projects like: > > project: 'Refactoring-Core' with: [ > spec > className: 'ConfigurationOfRefactoringBrowser'; > loads: #('Refactoring-Core' ); > file: 'ConfigurationOfRefactoringBrowser'; > repository: 'http://www.squeaksource.com/MetacelloRepository' ]; > > it should understand the alternative: > > project: 'Refactoring-Core' with: [ > spec > universe; "Or metacelloRepository or whatever" > className: 'ConfigurationOfRefactoringBrowser'; > loads: #('Refactoring-Core' ); > file: 'ConfigurationOfRefactoringBrowser' ]; > > So that a configuration could resolve all their references from the same > pharo repository. This implies of course that the maintainer assures > that all the referenced ConfigurationOfXXX are actually available in the > repository referenced by SystemVersion current metacelloRepository. > > But we need to change that...in addition, there are confs that also work in squeak...soo.. > Of course nothing prevents for a configuration to reference a project > outside the "universe" repository, but that is a decision of the > maintainer. > > I think that this is the least disruptive way of integrating Metacello > Repositories to next Pharo release. > > This preserves backwards compatibility and eases the way of installing > packages in future releases. > > What do you think? > I think that we should do is a piece of code that does the following: - Take a ConfiguraitonOfXXX and do a "publish in Pharo Repository" - This can propmt which Pharo version, or directly which PharoRepository - Then it will ask which VERSION should be loaded in the already selected Pharo version - It should be asked WHICH group (optional) Once this is done, the code has to do the following: - Iterates all the project and packages referenced and COPY ALL OF THEM into the same repository. Or maybe we can have another repo. This will copy all the .mzc of the project and its dependencies. With this you will make sure that you have EVERYTHING you need to load it. - take that ConfigurationOfXXX and automatically compile a class side #load that based in your answers, does the correct job. In addition, this method should do a repositoryOverride: with the selected repository. Example: load | version | version := self project version: selectedVersion. version repositoryOverrides: selectedPharoRepository. version load: selectedGroup. Maybe it can implement a particular load: that recieves the common parameter Then, if you are in Pharo 1.0 the only thing you have to do is to explore the repository PharoRepository10 and browse the confs....you select the one you want and load it (with Gofer or Monticello Browser). Once that is done, you just evaluate: ConfiguarationOfXXX load. and that's all. What do you think ? Dale? > > Cheers > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 13, 2010