[Pharo-project] Fwd: [ANN] 10245
Some more happy people :) - Announcements-lr.10 from souce.lukas-renggli.ch Is when:do: not missing for compatibility with VW? - Polymorph Fix for button for currently selected window in tasklist not being differentiated when using Watery 2 theme. - ContextPart argument - merged Issue 608: saveAsNewVersion uses deprecated method - Issue 614: MessageTally broken when invoked from non-GUI process (e.g., in Seaside code) Now we should really kill more items for the milestone 1.0. Stef (now breakfast :) ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] Fwd: [squeak-dev] recategorize a bunch
Begin forwarded message: From: Eliot Miranda eliot.mira...@gmail.com Date: March 1, 2009 8:08:46 AM CEST To: The general-purpose Squeak developers list squeak-...@lists.squeakfoundation.org Subject: Re: [squeak-dev] recategorize a bunch Reply-To: The general-purpose Squeak developers list squeak-...@lists.squeakfoundation.org On Sat, Feb 28, 2009 at 7:42 PM, Sebastian Sastre ssas...@seaswork.com wrote: hi there, while loading some stuff of mine form an image to another, I was annoyed/surprised by not finding some methods. Then I've figured out that all not imported methods where missing because somehow they happen to be under a category named *-changed some others under *-compilation-issues. There is a way I can query the system (monticello?) to get the whole and set them another category (so I can save the packageproperly)? Let's say that SystemNavigationallMethodsInCatergory: answers MethodReference instances instead of 'Classdselector' string thingies, and if it doesn't that it can by defining it as SystemNavigation methods for query allMethodsInCategory: category | aCollection | aCollection := Set new. Cursor wait showWhile: [self allBehaviorsDo: [:x | ((category = ClassOrganizer allCategory ifTrue: [x organization allMethodSelectors] ifFalse: [x organization listAtCategoryNamed: category])) do: [:sel | aCollection add: (MethodReference new setStandardClass: x methodSymbol: sel)]]]. ^aCollection. then you want to say (SystemNavigation default allMethodsInCategory: #'* whatever the category * was called') do: [:mr| mr actualClass organization classify: mr methodSymbol under: #'what I would like the category to be'] thanks, sebastian ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Fwd: [ANN] 10245
Hi Stef, Some more happy people :) - Announcements-lr.10 from souce.lukas-renggli.ch Is when:do: not missing for compatibility with VW? I published a new version containing when:do: Announcements-tg.11. Cheers, Doru - Polymorph Fix for button for currently selected window in tasklist not being differentiated when using Watery 2 theme. - ContextPart argument - merged Issue 608: saveAsNewVersion uses deprecated method - Issue 614: MessageTally broken when invoked from non-GUI process (e.g., in Seaside code) Now we should really kill more items for the milestone 1.0. Stef (now breakfast :) ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com Yesterday is a fact. Tomorrow is a possibility. Today is a challenge. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] Preference refactoring again
Hi all, joined Zoo package is a attempt to translate in code what we discussed here before about preference refactoring. The framework is made of 3 classes: PreferenceCollector, PreferenceDefinition and PreferenceValue. In Zoo there are also 2 classes for testing: PrefProvider and PrefChangeListener. PrefProvider class declares some preferences and PrefChangeListener is here to test preference change notification. PrefChangeListenerinitialize super initialize. PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientButtonLookIsNow: . PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientLook: PrefChangeListener classtest self test PrefChangeListener new inspect. PrefProvider gradientButtonLook: PrefProvider gradientButtonLook value not. PrefProvider gradientButtonLook: PrefProvider gradientButtonLook value not. PrefProvider gradientButtonLook: PrefProvider gradientButtonLook value not. From PreferenceCollector comment: -- A PreferenceCollector automatically collects all preferences. A preference is represented by a PreferenceDefinition. All PreferenceDefinition are stored in the preferences instance variable. Instance Variables preferences:OrderedCollection of PreferenceDefinition preferences - contains all PreferenceDefinition which are automatically built from pragma found in preference getters ADDING A PREFERENCE PreferenceCollector makes use of the SystemChangeNotifier in order to automate the adding, the removing and the updating of preferences. See #PreferenceCollectorevent: to see how preferences update is implemented. Editing a new method with a preference pragma or inserting a preference pragma in an existing method are the two ways for preference definition adding. The only way to remove a preference definition is to remove the corresponding method. Example of a blackAndWhite preference. Methods below are defined by the preference provider APreferencePrivider class. Note that the value stored in BlackAndWhite class variable is an instance of PreferenceValue. In this example, the default value is directly given with the pragma: - APreferencePrivider classblackAndWhite preference: 'Use black and white' type: #Boolean set: #blackAndWhite: defaultValue: false description: 'Use black and white' ^ BlackAndWhite ifNil: [BlackAndWhite := PreferenceValue value: false location: self selector: #blackAndWhite] APreferencePrivider classblackAndWhite: aBoolean self blackAndWhite value: aBoolean - If a default value can't be specified in the pragma, another way consists in using a selector which represents the message to send to the class in order to get the default value: - APreferencePrivider classstandardFont preference: 'The default system font' type: #LogicalFont set: #standardFont: default: #defaultStandardFont description: 'The default system font' ^ StandardFont ifNil: [StandardFont := PreferenceValue value: self defaultStandardFont location: self selector: #standardFont] APreferencePrivider classstandardFont: aFont self standardFont value: aFont APreferencePrivider classdefaultStandardFont ^ LogicalFont familyName: 'Arial' fallbackFamilyNames: nil pointSize: 12 stretchValue: 5 weightValue: 400 slantValue: 0 - LISTENING TO A PREFERENCE VALUE CHANGE Any object can register itself as a preference value change listener. See #PreferenceCollector classwhenChanged: inClass:notify:using:. Each time a preference value is changed, #preference: inClass:changedWith: is sent to the PreferenceCollector class. Example of code a listener can implement in order to be notified each time a gradientButtonLook preference defined by a PrefProvider class is changed. In this example, the listener ask to be notified by a send of #gradientButtonLookIsNow: message. The argument given to gradientButtonLookIsNow: is the new preference value. - PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientButtonLookIsNow:. - What do you think ? cheers Alain Zoo-alain_plantec.10.mcz Description: Binary data ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] About pharo cut and paste email on Squeak-dev
Hi guys I think that we should pay attention that people do not say stupid stuff on us on squeak-dev (even if this is not that important ;) ). Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] Fwd: Some personal thoughts and questions about Pharo
For the ones that were not there at that time. Study history as always been a way to understand the present :) Begin forwarded message: From: Matthew Fulmer tapp...@gmail.com Date: February 28, 2009 6:26:00 AM CEST To: Marcus Denker den...@iam.unibe.ch, St?phane Ducasse stephane.duca...@inria.fr Cc: Matthew Fulmer tapp...@gmail.com Subject: Some personal thoughts and questions about Pharo Hi. I stumbled across a rather interesting email while I was researching to write up my campaign platform for the squeak election. Stef wrote this email 4 years ago, and it challenged a lot of what I thought about Pharo: http://lists.squeakfoundation.org/pipermail/squeak-dev/2005-January/087532.html It prompted me to write this email, and lay out exactly what I think about Pharo, both good, bad, and not understood. From what I can tell, this email was written just before you guys started the 3.9 team. Firstly, I see that you have really cared about bug response latency for a long time. I'm really glad you care and do something about it. Second, you solved this problem back then by releasing 3.9, and now you are solving it thru Pharo. Why did you choose to fork this time? If I may be blunt, I've long suspected that there are exactly two reasons why you forked: 1. Edgar J. De. Cleene 2. Andreas Raab Thirdly, I've heard Stef mention a number of times that Marcus got burned, and therefore doesn't read squeak-dev, or no longer runs for board, or several things most squeak people do. However, this is by far the earliest mention of said burning I've ever seen. I had assumed the burning was people (Edgar and Andreas) complaining about Traits, but this was long before that. What is it that happened to Marcus? If you are still bitter about something that happened over 4 years ago, perhaps it is time to forgive and re-join the squeak community. As 3.11 release team leader, and Squeak board nominee, I'm really excited about what you guys are doing with Pharo. From my perspective, one thing you have done is take up the reigns for harvesting bugs, and left the release team free to consider a long-standing issue in the community: who is responsible for merging bug fixes from one distribution to another, and how can we make their lives easier Another valuable thing you have done is show the community that one image does not fit all; the monolithic image does not work for anybody. Squeakland showed it does not work for end-users Croquet showed it does not work for researchers. And now Pharo shows that it does not work for developers. I really think that Pharo finishes painting that picture in the minds of the community, and you have thus paved the way for the release team and the squeak board to get away from the monolithic image, and toward modularity. I really think the community is ready now, and it's all thanks to you guys. I intend to exploit this opportunity. I sent this email in private, because I don't think it would be appropriate to ask some of these questions publicly. However, feel free to reply to any of this in public, as you see fit. -- Matthew Fulmer -- http://mtfulmer.wordpress.com/ ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Preference refactoring again
sounds cool. For me the most important aspect is that preferenceCollector (our current preference class should be a removable layer on top of the system that are declaring preference. Is is correct that PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientButtonLookIsNow: . means that PrefProvider will receive the message gradientButtonLookIsNow: This way we can push preference to the tools and thety do not have to query the information in the Collector at run-time (hence we could remove Preference and have a more OO design). Sorry not to reply earlier (I was breaking yet another wall in our kitchen) Stef On Mar 1, 2009, at 10:05 AM, Alain Plantec wrote: Hi all, joined Zoo package is a attempt to translate in code what we discussed here before about preference refactoring. The framework is made of 3 classes: PreferenceCollector, PreferenceDefinition and PreferenceValue. In Zoo there are also 2 classes for testing: PrefProvider and PrefChangeListener. PrefProvider class declares some preferences and PrefChangeListener is here to test preference change notification. PrefChangeListenerinitialize super initialize. PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientButtonLookIsNow: . PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientLook: PrefChangeListener classtest self test PrefChangeListener new inspect. PrefProvider gradientButtonLook: PrefProvider gradientButtonLook value not. PrefProvider gradientButtonLook: PrefProvider gradientButtonLook value not. PrefProvider gradientButtonLook: PrefProvider gradientButtonLook value not. From PreferenceCollector comment: -- A PreferenceCollector automatically collects all preferences. A preference is represented by a PreferenceDefinition. All PreferenceDefinition are stored in the preferences instance variable. Instance Variables preferences:OrderedCollection of PreferenceDefinition preferences - contains all PreferenceDefinition which are automatically built from pragma found in preference getters ADDING A PREFERENCE PreferenceCollector makes use of the SystemChangeNotifier in order to automate the adding, the removing and the updating of preferences. See #PreferenceCollectorevent: to see how preferences update is implemented. Editing a new method with a preference pragma or inserting a preference pragma in an existing method are the two ways for preference definition adding. The only way to remove a preference definition is to remove the corresponding method. Example of a blackAndWhite preference. Methods below are defined by the preference provider APreferencePrivider class. Note that the value stored in BlackAndWhite class variable is an instance of PreferenceValue. In this example, the default value is directly given with the pragma: - APreferencePrivider classblackAndWhite preference: 'Use black and white' type: #Boolean set: #blackAndWhite: defaultValue: false description: 'Use black and white' ^ BlackAndWhite ifNil: [BlackAndWhite := PreferenceValue value: false location: self selector: #blackAndWhite] APreferencePrivider classblackAndWhite: aBoolean self blackAndWhite value: aBoolean - If a default value can't be specified in the pragma, another way consists in using a selector which represents the message to send to the class in order to get the default value: - APreferencePrivider classstandardFont preference: 'The default system font' type: #LogicalFont set: #standardFont: default: #defaultStandardFont description: 'The default system font' ^ StandardFont ifNil: [StandardFont := PreferenceValue value: self defaultStandardFont location: self selector: #standardFont] APreferencePrivider classstandardFont: aFont self standardFont value: aFont APreferencePrivider classdefaultStandardFont ^ LogicalFont familyName: 'Arial' fallbackFamilyNames: nil pointSize: 12 stretchValue: 5 weightValue: 400 slantValue: 0 - LISTENING TO A PREFERENCE VALUE CHANGE Any object can register itself as a preference value change listener. See #PreferenceCollector classwhenChanged: inClass:notify:using:. Each time a preference value is changed, #preference: inClass:changedWith: is sent to the PreferenceCollector class. Example of code a listener can implement in order to be notified each time a gradientButtonLook preference defined by a PrefProvider class is changed. In this example, the listener ask to be notified by a send of
[Pharo-project] Fwd: Some personal thoughts and questions about Pharo
Begin forwarded message: From: Stéphane Ducasse stephane.duca...@inria.fr Date: February 28, 2009 2:07:42 PM CEST To: Matthew Fulmer tapp...@gmail.com Cc: Marcus Denker den...@iam.unibe.ch Subject: Re: Some personal thoughts and questions about Pharo Hi matthew Hi. I stumbled across a rather interesting email while I was researching to write up my campaign platform for the squeak election. Stef wrote this email 4 years ago, and it challenged a lot of what I thought about Pharo: http://lists.squeakfoundation.org/pipermail/squeak-dev/2005-January/087532.html It prompted me to write this email, and lay out exactly what I think about Pharo, both good, bad, and not understood. Ok I think that this is important to have a look at what we did and wrote in the past to understand our attitude today. Lot of people judge without really knowing. This is not the best email I sent. but it just gives a facett of the problem From what I can tell, this email was written just before you guys started the 3.9 team. I imagine. Firstly, I see that you have really cared about bug response latency for a long time. I'm really glad you care and do something about it. Yes. We cared also about transparency and trust. The idea is that I already said that to the squeakfoundation and I gave up long time ago. If we do not give a chance to knowlegdaebale people to get a look then we failed. Once janko which I trust sent a fix for network and I thought that we should integrate it but bert had a look and said it was not good. So this makes me thing a lot. So if an opensource movement we do not have communication then nothing good can happen. For 3.10 I proposed to ralph to help but he declined. They thought we had no process and when I explained him what we were doing he said that this is what he planed to do. I think that people thiught that ralph was Jesus but he was not. Second, you solved this problem back then by releasing 3.9, and now you are solving it thru Pharo. Why did you choose to fork this time? If I may be blunt, I've long suspected that there are exactly two reasons why you forked: 1. Edgar J. De. Cleene 2. Andreas Raab You are not blunt Been called a randomrefactorer is blunt. I do not want to tell more on that but we are a solid group of people all getting the same feeling nd this is not because we are wash-brained. Just our experiences are following the same line. Ask mike why andreas does not talk to him. Thirdly, I've heard Stef mention a number of times that Marcus got burned, and therefore doesn't read squeak-dev, or no longer runs for board, or several things most squeak people do. However, this is by far the earliest mention of said burning I've ever seen. I had assumed the burning was people (Edgar and Andreas) complaining about Traits, but this was long before that. marcus was burnt to the point of been sick of smalltalk. The problem is that marucs dreamt with us at bern about beauty and a better world and that people like andreas were most of the time negative and playing for themselves. Look at Tweak Andreas forked it even people working in Sophie did not have access to his branch. What is it that happened to Marcus? If you are still bitter about something that happened over 4 years ago, perhaps it is time to forgive and re-join the squeak community. No we are not bitter. The squeak community has no vision except toying with the past. If I would be you I would not lose my time there. We harvested since squeak 3.6 and we did our best but it failed and it will fail. As 3.11 release team leader, and Squeak board nominee, I'm really excited about what you guys are doing with Pharo. From my perspective, one thing you have done is take up the reigns for harvesting bugs, and left the release team free to consider a long-standing issue in the community: who is responsible for merging bug fixes from one distribution to another, and how can we make their lives easier No we did the only thing that make us breath again and not jump into ruby or python or just hack in our little corner stuff in VW or other. Pharo is not an accident this is a survival reflex. You know when you want to fix sometihng that a guy shout at you because you push a fix in his package Then after a while you stop this is why there are some fonts problem in 39 because we stop to harvest anything related to andreas. Another valuable thing you have done is show the community that one image does not fit all; the monolithic image does not work for anybody. Squeakland showed it does not work for end-users Croquet showed it does not work for researchers. No Croquet shows nothing. Ask lombardi because he gave a presentation last year at ESUG and we felt he was just alone lost. And we are researcher much more than they :). Look at our publication records. Now we want a good Smalltalk and make
Re: [Pharo-project] Fwd: [ANN] 10245
I copied it to the repository of Lukas as well. Does anyone actually see a reason for not having the when:do: method in as an alias to on:do:? I do not see it. Cheers, Doru On 1 Mar 2009, at 10:19, Stéphane Ducasse wrote: Where? It was not on lukas source and in the pharo inbox Then there is the question to be sure if we want it. On Mar 1, 2009, at 9:56 AM, Tudor Girba wrote: Hi Stef, Some more happy people :) - Announcements-lr.10 from souce.lukas-renggli.ch Is when:do: not missing for compatibility with VW? I published a new version containing when:do: Announcements-tg.11. Cheers, Doru - Polymorph Fix for button for currently selected window in tasklist not being differentiated when using Watery 2 theme. - ContextPart argument - merged Issue 608: saveAsNewVersion uses deprecated method - Issue 614: MessageTally broken when invoked from non-GUI process (e.g., in Seaside code) Now we should really kill more items for the milestone 1.0. Stef (now breakfast :) ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com Yesterday is a fact. Tomorrow is a possibility. Today is a challenge. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com Be rather willing to give than demanding to get. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [squeak-dev] [Idea] method source with it
Lukas Renggli reng...@... writes: Is it possible to configurate the search engine to case no sensitive ? Not at the moment, I noticed myself several times that this would be useful. If I find time, I will have a look at it tomorrow. Suppose you have more than 1 match of what you are looking in the same method, is there a way to go one after the other putting the color over the world ? Not without hacking into ParagraphEditor. There is unfortunately no easy way to highlight several occurrences. Lukas What I did once upon a time in VW: - add a #backgroundColor-ColorValue text emphasis - implement graphic rendering for this emphasis - change the runs for every piece of matching text to add #backgroundColor-(ColorValue yellow) (for example) A little bit more ellaborate than this basic idea: don't add directly the #backgroundColor emphasis... ...but rather use an indirect one, like #searchedText. Then let some custom-preferences translate to a real emphasis. Advantages: - customisable - easy to remove all #searchedText preserving other text formatting Nicolas ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [squeak-dev] [Idea] method source with it
Not at the moment, I noticed myself several times that this would be useful. If I find time, I will have a look at it tomorrow. No problem. I was just asking :) Update in this order: 1. AST-lr.164 2. Refactoring-Core-lr.40 3. OB-Refactory-lr.141 4. OB-Regex-lr.15 To get case insensitive matching when building environments/scopes make sure that the expression ends with /i. All the commands include a regular expression example now, that should help you get started. Note, that this versions also reorganize the menus a bit, after a discussion with Stephane and David. Environments are now called scopes, but other than that it is the same. Lukas Suppose you have more than 1 match of what you are looking in the same method, is there a way to go one after the other putting the color over the world ? Not without hacking into ParagraphEditor. There is unfortunately no easy way to highlight several occurrences. :( Ok. Thanks anyway for the tip. Lukas -- Lukas Renggli http://www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Lukas Renggli http://www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] What are the ERROR messages in the Transcript Window in 10243?
Seems a problem in OB: OBDBSuperSend sends #superSenderSelectors, which is not implemented. Adrian On Feb 28, 2009, at 19:06 , Rob Rothwell wrote: Maybe I just wasn't able to follow the conversation properly, but if you open a Transcript in 10243 (dev) and, say, search for the class Morph, you will get: ERROR: Morph classoverridesSelectors ERROR: Morph classsuperSenderSelectors ERROR: Morph classconflictsSelectors ERROR: Morph classoverridesSelectors ERROR: Morph classsuperSenderSelectors ERROR: Morph classconflictsSelectors In fact, anytime you do anything (save a method, etc...), it seems you get these messages, and yet things seem to be working. Rob ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Fwd: [ANN] 10245
On Sun, 2009-03-01 at 10:47 +0100, Tudor Girba wrote: I copied it to the repository of Lukas as well. Does anyone actually see a reason for not having the when:do: method in as an alias to on:do:? I do not see it. Because then there is on:do: subscribe:do: when:do: with all for: and send:to: variants. Counting the methods, the aliases are then on par with the methods provided. It is 6:6. Honestly I don't like having even another alias. my 2 cents Norbert On 1 Mar 2009, at 10:19, Stéphane Ducasse wrote: Where? It was not on lukas source and in the pharo inbox Then there is the question to be sure if we want it. On Mar 1, 2009, at 9:56 AM, Tudor Girba wrote: Hi Stef, Some more happy people :) - Announcements-lr.10 from souce.lukas-renggli.ch Is when:do: not missing for compatibility with VW? I published a new version containing when:do: Announcements-tg.11. Cheers, Doru - Polymorph Fix for button for currently selected window in tasklist not being differentiated when using Watery 2 theme. - ContextPart argument - merged Issue 608: saveAsNewVersion uses deprecated method - Issue 614: MessageTally broken when invoked from non-GUI process (e.g., in Seaside code) Now we should really kill more items for the milestone 1.0. Stef (now breakfast :) ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com Yesterday is a fact. Tomorrow is a possibility. Today is a challenge. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com Be rather willing to give than demanding to get. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Preference refactoring again
Stéphane Ducasse a écrit : sounds cool. For me the most important aspect is that preferenceCollector (our current preference class should be a removable layer on top of the system that are declaring preference. Is is correct that PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientButtonLookIsNow: . means that PrefProvider will receive the message gradientButtonLookIsNow: no, but see the code below: --- PrefListenerinitialize super initialize. PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientButtonLookIsNow: . --- it means that a PrefListener instance will receive the #gradientButtonLookIsNow: message each time the preference #gradientButtonLook defined in class PrefProvider is changed. PrefListener and PrefProvider represent can be any class in the system. So, in order to read a preference value an object get it from the provider class by message sending, the provider is a class in a package which defines preferences (no need for PreferenceCollector to get the preference value). This way we can push preference to the tools yes and thety do not have to query the information in the Collector at run-time yes, Each package have its own preference set in it represented by a set of methods with pragma. When such a package is loaded, its preferences are automatically stored by PreferenceCollector. When a package is removed, its preferences are automatically removed from PreferenceCollector. PreferenceCollector is only here for supporting tools (cool UI ...) and for change notifications. (hence we could remove Preference and have a more OO design). I guess yes. Sorry not to reply earlier (I was breaking yet another wall in our kitchen) bon courage :) alain Stef On Mar 1, 2009, at 10:05 AM, Alain Plantec wrote: Hi all, joined Zoo package is a attempt to translate in code what we discussed here before about preference refactoring. The framework is made of 3 classes: PreferenceCollector, PreferenceDefinition and PreferenceValue. In Zoo there are also 2 classes for testing: PrefProvider and PrefChangeListener. PrefProvider class declares some preferences and PrefChangeListener is here to test preference change notification. PrefChangeListenerinitialize super initialize. PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientButtonLookIsNow: . PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientLook: PrefChangeListener classtest self test PrefChangeListener new inspect. PrefProvider gradientButtonLook: PrefProvider gradientButtonLook value not. PrefProvider gradientButtonLook: PrefProvider gradientButtonLook value not. PrefProvider gradientButtonLook: PrefProvider gradientButtonLook value not. From PreferenceCollector comment: -- A PreferenceCollector automatically collects all preferences. A preference is represented by a PreferenceDefinition. All PreferenceDefinition are stored in the preferences instance variable. Instance Variables preferences:OrderedCollection of PreferenceDefinition preferences - contains all PreferenceDefinition which are automatically built from pragma found in preference getters ADDING A PREFERENCE PreferenceCollector makes use of the SystemChangeNotifier in order to automate the adding, the removing and the updating of preferences. See #PreferenceCollectorevent: to see how preferences update is implemented. Editing a new method with a preference pragma or inserting a preference pragma in an existing method are the two ways for preference definition adding. The only way to remove a preference definition is to remove the corresponding method. Example of a blackAndWhite preference. Methods below are defined by the preference provider APreferencePrivider class. Note that the value stored in BlackAndWhite class variable is an instance of PreferenceValue. In this example, the default value is directly given with the pragma: - APreferencePrivider classblackAndWhite preference: 'Use black and white' type: #Boolean set: #blackAndWhite: defaultValue: false description: 'Use black and white' ^ BlackAndWhite ifNil: [BlackAndWhite := PreferenceValue value: false location: self selector: #blackAndWhite] APreferencePrivider classblackAndWhite: aBoolean self blackAndWhite value: aBoolean - If a default value can't be specified in the pragma, another way consists in using a selector which represents the message to send to the class in order to get the default value: - APreferencePrivider classstandardFont preference: 'The default system font' type: #LogicalFont set: #standardFont: default:
Re: [Pharo-project] Fwd: [ANN] 10245
On Mar 1, 2009, at 10:47 AM, Tudor Girba wrote: I copied it to the repository of Lukas as well. I did not see it when I did the release. Does anyone actually see a reason for not having the when:do: method in as an alias to on:do:? I do not see it. Cheers, Doru On 1 Mar 2009, at 10:19, Stéphane Ducasse wrote: Where? It was not on lukas source and in the pharo inbox Then there is the question to be sure if we want it. On Mar 1, 2009, at 9:56 AM, Tudor Girba wrote: Hi Stef, Some more happy people :) - Announcements-lr.10 from souce.lukas-renggli.ch Is when:do: not missing for compatibility with VW? I published a new version containing when:do: Announcements-tg.11. Cheers, Doru - Polymorph Fix for button for currently selected window in tasklist not being differentiated when using Watery 2 theme. - ContextPart argument - merged Issue 608: saveAsNewVersion uses deprecated method - Issue 614: MessageTally broken when invoked from non-GUI process (e.g., in Seaside code) Now we should really kill more items for the milestone 1.0. Stef (now breakfast :) ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com Yesterday is a fact. Tomorrow is a possibility. Today is a challenge. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com Be rather willing to give than demanding to get. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Preference refactoring again
Stéphane your previous question makes me think of a better solution with requires only one mandatory class and which makes use of standard event notification (without PreferenceCollector). I've joined 4 packages : - PrefCore contains PreferenceValue which is now the only mandatory class. 2 packages for testing: - PrefProvider contains PrefProvider class which declares some preferences - PrefUser contains PrefChangeListener (try PrefChangeListener test). 1 package for UI: - PrefTool contains PreferenceCollector and PreferenceDefinition. They are optional. Code below do not makes use of PreferenceCollector anymore: PrefChangeListenerinitialize super initialize. gradientLook := PrefProvider gradientButtonLook value. reading of the preference value Using of standard event notification engine PrefProvider when: #gradientButtonLook send: #gradientButtonLookIsNow: to: self. PrefProvider when: #gradientButtonLook send: #gradientLook: to: self. Now, the preference system only need PreferenceValue. PreferenceCollector and PreferenceDefinition are optional and can be brought by a preference supporting tool (UI). Previous version implied a dependency from PrefChangeListener to PreferenceCollector which was bad. PrefChangeListenerinitialize super initialize. gradientLook := PrefProvider gradientButtonLook value. PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientButtonLookIsNow: . PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientLook: alain Stéphane Ducasse a écrit : sounds cool. For me the most important aspect is that preferenceCollector (our current preference class should be a removable layer on top of the system that are declaring preference. Is is correct that PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientButtonLookIsNow: . means that PrefProvider will receive the message gradientButtonLookIsNow: no, but see the code below: --- PrefListenerinitialize super initialize. PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientButtonLookIsNow: . --- it means that a PrefListener instance will receive the #gradientButtonLookIsNow: message each time the preference #gradientButtonLook defined in class PrefProvider is changed. PrefListener and PrefProvider represent can be any class in the system. So, in order to read a preference value an object get it from the provider class by message sending, the provider is a class in a package which defines preferences (no need for PreferenceCollector to get the preference value). This way we can push preference to the tools yes and thety do not have to query the information in the Collector at run-time yes, Each package have its own preference set in it represented by a set of methods with pragma. When such a package is loaded, its preferences are automatically stored by PreferenceCollector. When a package is removed, its preferences are automatically removed from PreferenceCollector. PreferenceCollector is only here for supporting tools (cool UI ...) and for change notifications. (hence we could remove Preference and have a more OO design). I guess yes. Sorry not to reply earlier (I was breaking yet another wall in our kitchen) bon courage :) alain Stef On Mar 1, 2009, at 10:05 AM, Alain Plantec wrote: Hi all, joined Zoo package is a attempt to translate in code what we discussed here before about preference refactoring. The framework is made of 3 classes: PreferenceCollector, PreferenceDefinition and PreferenceValue. In Zoo there are also 2 classes for testing: PrefProvider and PrefChangeListener. PrefProvider class declares some preferences and PrefChangeListener is here to test preference change notification. PrefChangeListenerinitialize super initialize. PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientButtonLookIsNow: . PreferenceCollector whenChanged: #gradientButtonLook inClass: PrefProvider notify: self using: #gradientLook: PrefChangeListener classtest self test PrefChangeListener new inspect. PrefProvider gradientButtonLook: PrefProvider gradientButtonLook value not. PrefProvider gradientButtonLook: PrefProvider gradientButtonLook value not. PrefProvider gradientButtonLook: PrefProvider gradientButtonLook value not. From PreferenceCollector comment: -- A PreferenceCollector automatically collects all preferences. A preference is represented by a PreferenceDefinition. All PreferenceDefinition are stored in the preferences instance variable. Instance Variables preferences:OrderedCollection of PreferenceDefinition
[Pharo-project] Swazoo 2.2 released
Dear Smalltalkers, After one year I'm glad to announce a new release 2.2 of Swazoo Smalltalk Web Server, currently just for Squeak and VisualWorks. What is new? * upload streaming 30 times better for large file uploads * additional improvements of streamed upload performance, as a result of a nice competition with Göran Krampe doing the same on the Commance * two important classes renamed to avoid namespace clashes: Site to SwazooSite, Resource to SwazooResource * more reliable post data parsing * more and better tests * benchmarking support added. Detailed release notes: http://www.swazoo.org/release-notes-2.2.html Download page: http://www.swazoo.org/download.html Special thanks to Paolo Bonzini, Lautaro Fernández, Julian Fitzell, Göran Krampe, Philippe Marschall and Stefan Schmiedl for your valuable inputs to this release! Best regards Janko Mivšek Swazoo maintainer ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Fwd: [ANN] 10245
Bill, On Sun, 2009-03-01 at 09:23 -0500, Schwab,Wilhelm K wrote: Norbert, I agree re aliases, but only to a point. When trying to be compatible with other dialects, the aliases spare many other users from independently having to add them. When it is reasonable, I have no problem with it. This is another example of how nice it would be to have Dolphin's ability to apply multiple categories to a method; aliases can be flagged as such. Then they can be tested and maintained rather than having myriad ad hoc attempts to fill a gap between dialects. We have seen some complaints about lack of backward compatibility with Squeak. I have no desire to be hostile, but Pharo is the cleaning that Squeak has needed for several years; there will be side effects. If Pharo becomes what I think it will, there will be a time when things get back-ported to Squeak from Pharo. The difference is on one of purpose and degree. Are we trying desperately to fix Squeak and yet ensure that all of Pharo's improvements work perfectly on it? I consider that unlikely to work. If we are instead providing a few methods here or there that eliminate small incompatibilities, it is probably appropriate to add them and categorize them appropriately. I agree. Coming from AXAnnouncements I already had to exchange when:do: with subscribe:do:. I'm just wondering why there are then three sets of these methods. Having VW compatibility is good. But then I should consider deprecating one of the others. Where does subscribe:do: come from? Norbert -Original Message- From: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Norbert Hartl Sent: Sunday, March 01, 2009 8:13 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Fwd: [ANN] 10245 On Sun, 2009-03-01 at 10:47 +0100, Tudor Girba wrote: I copied it to the repository of Lukas as well. Does anyone actually see a reason for not having the when:do: method in as an alias to on:do:? I do not see it. Because then there is on:do: subscribe:do: when:do: with all for: and send:to: variants. Counting the methods, the aliases are then on par with the methods provided. It is 6:6. Honestly I don't like having even another alias. my 2 cents Norbert On 1 Mar 2009, at 10:19, Stéphane Ducasse wrote: Where? It was not on lukas source and in the pharo inbox Then there is the question to be sure if we want it. On Mar 1, 2009, at 9:56 AM, Tudor Girba wrote: Hi Stef, Some more happy people :) - Announcements-lr.10 from souce.lukas-renggli.ch Is when:do: not missing for compatibility with VW? I published a new version containing when:do: Announcements-tg.11. Cheers, Doru - Polymorph Fix for button for currently selected window in tasklist not being differentiated when using Watery 2 theme. - ContextPart argument - merged Issue 608: saveAsNewVersion uses deprecated method - Issue 614: MessageTally broken when invoked from non-GUI process (e.g., in Seaside code) Now we should really kill more items for the milestone 1.0. Stef (now breakfast :) ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com Yesterday is a fact. Tomorrow is a possibility. Today is a challenge. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com Be rather willing to give than demanding to get. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] changing default font
hi there, sorry for the noob question but I see pharo has freetype in the image but it's only accuny font among options. Shouldn't freetype read the fonts on the system and offer those too? thanks, sebastian ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] changing default font
It suddendly started to work, I think it was SqueakFFIPrims.dll that was missing cheers, sebastian -Mensaje original- De: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] En nombre de Sebastian Sastre Enviado el: Sunday, March 01, 2009 12:06 Para: Pharo-project@lists.gforge.inria.fr Asunto: [Pharo-project] changing default font hi there, sorry for the noob question but I see pharo has freetype in the image but it's only accuny font among options. Shouldn't freetype read the fonts on the system and offer those too? thanks, sebastian ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] changing default font
And if you get tired of setting your fonts individually, you can set them all at once: font := LogicalFont familyName: 'Andika Basic' pointSize: 10. codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. Preferences setListFontTo: font. Preferences setMenuFontTo: font. Preferences setCodeFontTo: codeFont. Preferences setButtonFontTo: font. Preferences setSystemFontTo: font. font := LogicalFont familyName: 'Andika Basic' pointSize: 11. Preferences setWindowTitleFontTo: font. Just replace the font names with those of your choice! Rob On Sun, Mar 1, 2009 at 10:56 AM, Sebastian Sastre ssas...@seaswork.comwrote: It suddendly started to work, I think it was SqueakFFIPrims.dll that was missing cheers, sebastian -Mensaje original- De: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] En nombre de Sebastian Sastre Enviado el: Sunday, March 01, 2009 12:06 Para: Pharo-project@lists.gforge.inria.fr Asunto: [Pharo-project] changing default font hi there, sorry for the noob question but I see pharo has freetype in the image but it's only accuny font among options. Shouldn't freetype read the fonts on the system and offer those too? thanks, sebastian ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] What are the ERROR messages in the Transcript Window in 10243?
Should I post an issue? Thank your, Rob On Sun, Mar 1, 2009 at 7:54 AM, Adrian Lienhard a...@netstyle.ch wrote: Seems a problem in OB: OBDBSuperSend sends #superSenderSelectors, which is not implemented. Adrian On Feb 28, 2009, at 19:06 , Rob Rothwell wrote: Maybe I just wasn't able to follow the conversation properly, but if you open a Transcript in 10243 (dev) and, say, search for the class Morph, you will get: ERROR: Morph classoverridesSelectors ERROR: Morph classsuperSenderSelectors ERROR: Morph classconflictsSelectors ERROR: Morph classoverridesSelectors ERROR: Morph classsuperSenderSelectors ERROR: Morph classconflictsSelectors In fact, anytime you do anything (save a method, etc...), it seems you get these messages, and yet things seem to be working. Rob ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Some issues with Pharo-dev build #10243
On Fri, Feb 27, 2009 at 9:34 PM, David Röthlisberger squ...@webcitas.ch wrote: Hm, not sure whether this is convenient. I mean every commit to the OB repository has to be tested very carefully then, and I cannot commit experimental features anymore, because they automatically get loaded with #loadOBAlpha as it is right now. What is the motiviation to not longer build pharo-dev with the OB versions published in Universe? I don't know, was just trying things to see what is best :-). Please continue to push the versions you want into SqueakSource as you always did. -- Damien Cassou http://damiencassou.seasidehosting.st ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] can't load seaside 2.9a2
On Sat, Feb 28, 2009 at 2:41 PM, Sebastian Sastre ssas...@seaswork.com wrote: first of all thanks for making Pharo. I can see there is a lot to do but I'm so glad to see an open smalltalk evoluting in such a direction. I wanted to give a try with a web app I'm porting to seaside 2.9a2 but it won't load (I mean seaside 2.9a2). It's complaining about problems related to MIMEDocuments. Looks like the ones in squeak 3.10.2 are first class objects instead of strings, the mime database and such. I'm missing some update? thanks and all the best This is a known bug and it's getting fixed. Please subscribe to the following issue if you want to know when it is fixed. http://code.google.com/p/pharo/issues/detail?id=520 -- Damien Cassou http://damiencassou.seasidehosting.st ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] issue 467 update - obsolete Classes
Hi, I added some code to the issue 467 so all obsolete classes can be removed (part of Milestone-1.0) Cheers, -- Pavel ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] issue 467 update - obsolete Classes
Thanks! I will check that. Now I'm getting sick :( Stef On Mar 1, 2009, at 6:11 PM, Pavel Krivanek wrote: Hi, I added some code to the issue 467 so all obsolete classes can be removed (part of Milestone-1.0) Cheers, -- Pavel ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] can't load seaside 2.9a2
Damien it should be fixed. At least I integrated in 10245 the latest fixes of mike. So may be now you just need to load the Kom package which is in the inbox. If you give a try let us know. Stef On Mar 1, 2009, at 6:09 PM, Damien Cassou wrote: On Sat, Feb 28, 2009 at 2:41 PM, Sebastian Sastre ssas...@seaswork.com wrote: first of all thanks for making Pharo. I can see there is a lot to do but I'm so glad to see an open smalltalk evoluting in such a direction. I wanted to give a try with a web app I'm porting to seaside 2.9a2 but it won't load (I mean seaside 2.9a2). It's complaining about problems related to MIMEDocuments. Looks like the ones in squeak 3.10.2 are first class objects instead of strings, the mime database and such. I'm missing some update? thanks and all the best This is a known bug and it's getting fixed. Please subscribe to the following issue if you want to know when it is fixed. http://code.google.com/p/pharo/issues/detail?id=520 -- Damien Cassou http://damiencassou.seasidehosting.st ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] changing default font
great script thanks! hey Pharo project already has an official blog? I mean, I image how good this simple things would help to propagate the pharo ideavirus when posted in cool posts by a team of developers. Ideally a team of authors with a an editor (to filter possible misconceptions about pharo project policy) could do good stuff a lot more fun than manuals and FAQs. I'm happy to see that pharo has a lot to be a winner cheers, sebastian _ De: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] En nombre de Rob Rothwell Enviado el: Sunday, March 01, 2009 13:19 Para: Pharo-project@lists.gforge.inria.fr Asunto: Re: [Pharo-project] changing default font And if you get tired of setting your fonts individually, you can set them all at once: font := LogicalFont familyName: 'Andika Basic' pointSize: 10. codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. Preferences setListFontTo: font. Preferences setMenuFontTo: font. Preferences setCodeFontTo: codeFont. Preferences setButtonFontTo: font. Preferences setSystemFontTo: font. font := LogicalFont familyName: 'Andika Basic' pointSize: 11. Preferences setWindowTitleFontTo: font. Just replace the font names with those of your choice! Rob On Sun, Mar 1, 2009 at 10:56 AM, Sebastian Sastre ssas...@seaswork.com wrote: It suddendly started to work, I think it was SqueakFFIPrims.dll that was missing cheers, sebastian -Mensaje original- De: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] En nombre de Sebastian Sastre Enviado el: Sunday, March 01, 2009 12:06 Para: Pharo-project@lists.gforge.inria.fr Asunto: [Pharo-project] changing default font hi there, sorry for the noob question but I see pharo has freetype in the image but it's only accuny font among options. Shouldn't freetype read the fonts on the system and offer those too? thanks, sebastian ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] towards pharo 1.0 (from pavel)
Hi Stef, there are some opened issues so we may start with them: 310 and 311 - the goal is to be able to unload all tests. As Adrian sugested, we may place it the package Tests - at least for now. 346 - easy and safe to integrate 348 - very important issue. Maybe you should place in one update fix for MorphicUIManagerinteractiveParserFor: and in the next the rest of the patch to prevent loading problems There was one wrong step in the development of Pharo during removing of MVC. Pharo deleted all MVC related code however in some cases it was the sign to use the UIManager. 71, 59 - very critical patch but I will have to check if the patches are suitable for the latest pharo I suggest to remove the unused class variable Current from the ColorTheme (issue 467) firstly - that cleans a lot of obsoleteClasses. I think that we need one important step in the development of Pharo - the next image that will not contain any code that can be unloaded. That should help us to increase the Pharo quality because now most packges are on the logical level in contradistiction to KernelImage where all packages are standalone unloadable entities. The ideal state is when we have the minimal core image with logical packages (like Collections) and the rest will be all unloadable packages. Cheers, -- Pavel On Sun, Mar 1, 2009 at 9:57 AM, stephane ducasse stephane.duca...@free.fr wrote: The KernelImage ZOO including the building environment is here: http://squeak.cz/public/pub/KernelImage/current/ Of course it is not perfect - the smallest image works only in Linux and MorphicCore needs a lot of fixes so people should start with MorphicExt and so on but it is usable starting point if someone is interested... -- Pavel Hi pavel do you have some fixes, cs list that we could slowly integrate to pharo? Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [squeak-dev] [Idea] method source with it
Lukas: good news! thanks for it. I tried to test it but doesn't work for me.
I updated the packages you said but after then, I am trying to open a system
browser and I get the following error.
I guess I must update another package, but I don't know. Anyway, don't
worry. I can test it then when all of these changes are included in pharo
image.
thanks again.
MessageNotUnderstood: OBMetaNodefilters
OBMetaNode(Object)doesNotUnderstand: #filters
OBPackageBrowser classdefaultMetaNode
OBPackageBrowser class(OBBrowser class)new
OBPackageBrowser class(OBBrowser class)open
OBPackageBrowserAdaptor class(OBSystemBrowserAdaptor class)open
DEVToolSet class(StandardToolSet class)openClassBrowser
[] in ToggleMenuItemMorph(MenuItemMorph)invokeWithEvent: {[(selArgCount :=
selector numArgs) = 0 ifTrue: [target perform: selector] ...]}
BlockContextensure:
CursorWithMask(Cursor)showWhile:
ToggleMenuItemMorph(MenuItemMorph)invokeWithEvent:
ToggleMenuItemMorph(MenuItemMorph)mouseUp:
ToggleMenuItemMorph(MenuItemMorph)handleMouseUp:
MouseButtonEventsentTo:
ToggleMenuItemMorph(Morph)handleEvent:
MorphicEventDispatcherdispatchDefault:with:
MorphicEventDispatcherdispatchEvent:with:
ToggleMenuItemMorph(Morph)processEvent:using:
MorphicEventDispatcherdispatchDefault:with:
MorphicEventDispatcherdispatchEvent:with:
MenuMorph(Morph)processEvent:using:
OBMetaNode(Object)doesNotUnderstand: #filters
OBPackageBrowser classdefaultMetaNode
OBPackageBrowser class(OBBrowser class)new
OBPackageBrowser class(OBBrowser class)open
OBPackageBrowserAdaptor class(OBSystemBrowserAdaptor class)open
DEVToolSet class(StandardToolSet class)openClassBrowser
[] in ToggleMenuItemMorph(MenuItemMorph)invokeWithEvent: {[(selArgCount :=
selector numArgs) = 0 ifTrue: [target perform: selector] ...]}
BlockContextensure:
CursorWithMask(Cursor)showWhile:
ToggleMenuItemMorph(MenuItemMorph)invokeWithEvent:
ToggleMenuItemMorph(MenuItemMorph)mouseUp:
ToggleMenuItemMorph(MenuItemMorph)handleMouseUp:
MouseButtonEventsentTo:
ToggleMenuItemMorph(Morph)handleEvent:
MorphicEventDispatcherdispatchDefault:with:
MorphicEventDispatcherdispatchEvent:with:
ToggleMenuItemMorph(Morph)processEvent:using:
MorphicEventDispatcherdispatchDefault:with:
MorphicEventDispatcherdispatchEvent:with:
MenuMorph(Morph)processEvent:using:
doesNotUnderstand: aMessage
Handle the fact that there was an attempt to send the given message to
the receiver but the receiver does not understand this message (typically
sent from the machine when a message is sent to the receiver and no method
is defined for that selector).
Testing: (3 activeProcess)
MessageNotUnderstood new
message: aMessage;
receiver: self;
signal.
^ aMessage sentTo: self.
On Sun, Mar 1, 2009 at 8:36 AM, Lukas Renggli reng...@gmail.com wrote:
Not at the moment, I noticed myself several times that this would be
useful. If I find time, I will have a look at it tomorrow.
No problem. I was just asking :)
Update in this order:
1. AST-lr.164
2. Refactoring-Core-lr.40
3. OB-Refactory-lr.141
4. OB-Regex-lr.15
To get case insensitive matching when building environments/scopes
make sure that the expression ends with /i. All the commands include
a regular expression example now, that should help you get started.
Note, that this versions also reorganize the menus a bit, after a
discussion with Stephane and David. Environments are now called
scopes, but other than that it is the same.
Lukas
Suppose you have more than 1 match of what you are looking in the same
method, is there a way to go one after the other putting the color
over
the
world ?
Not without hacking into ParagraphEditor. There is unfortunately no
easy way to highlight several occurrences.
:( Ok. Thanks anyway for the tip.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--
Lukas Renggli
http://www.lukas-renggli.ch
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] changing default font
Hi sebastian So far we only have the web site and the code.google site. I'm not really a blogger (I'm writing too much other stuff --- soon you will see :). But if somebody would like to have a blog I would happily read and comment. I'm happy to see that pharo has a lot to be a winner I can start now :) My personal wish for pharo is not really to win but to make itself in a clean, lean robust new invention of Smalltalk. I stress invention here because may be it will not be 100% Smalltalk but a Smalltalk with better stuff: first class variables, better MOP who knows. Anyway thanks for your nice words. Stef great script thanks! hey Pharo project already has an official blog? I mean, I image how good this simple things would help to propagate the pharo ideavirus when posted in cool posts by a team of developers. Ideally a team of authors with a an editor (to filter possible misconceptions about pharo project policy) could do good stuff a lot more fun than manuals and FAQs. I'm happy to see that pharo has a lot to be a winner cheers, sebastian De: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr ] En nombre de Rob Rothwell Enviado el: Sunday, March 01, 2009 13:19 Para: Pharo-project@lists.gforge.inria.fr Asunto: Re: [Pharo-project] changing default font And if you get tired of setting your fonts individually, you can set them all at once: font := LogicalFont familyName: 'Andika Basic' pointSize: 10. codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. Preferences setListFontTo: font. Preferences setMenuFontTo: font. Preferences setCodeFontTo: codeFont. Preferences setButtonFontTo: font. Preferences setSystemFontTo: font. font := LogicalFont familyName: 'Andika Basic' pointSize: 11. Preferences setWindowTitleFontTo: font. Just replace the font names with those of your choice! Rob On Sun, Mar 1, 2009 at 10:56 AM, Sebastian Sastre ssas...@seaswork.com wrote: It suddendly started to work, I think it was SqueakFFIPrims.dll that was missing cheers, sebastian -Mensaje original- De: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] En nombre de Sebastian Sastre Enviado el: Sunday, March 01, 2009 12:06 Para: Pharo-project@lists.gforge.inria.fr Asunto: [Pharo-project] changing default font hi there, sorry for the noob question but I see pharo has freetype in the image but it's only accuny font among options. Shouldn't freetype read the fonts on the system and offer those too? thanks, sebastian ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] from #foo:bar: to foo: arg1 bar: arg2
Hi does one of you get to know a method for doing that? #foo:bar: - foo: arg1 bar: arg2 Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] split/join
I think that there was a split/join package somewhere. Does anybody know where it is? At one point it was planned to get added to squeak and nothing happened. Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] from #foo:bar: to foo: arg1 bar: arg2
may be we should add it somewhere in symbol because this is handy when you want to generate methods on the fly. signatureFromSelector: aSelector self new signatureFromSelector: #foo:bar: self new signatureFromSelector: #foo self new signatureFromSelector: #foo: | count | ^ String streamContents: [:str| count := 1. (ReadStream on: aSelector) do: [:each | each = $: ifTrue: [ str nextPut: each. str nextPutAll: ' arg', count printString, ' '. count := count + 1] ifFalse: [str nextPut: each] ]] On Mar 1, 2009, at 7:18 PM, Stéphane Ducasse wrote: Hi does one of you get to know a method for doing that? #foo:bar: - foo: arg1 bar: arg2 Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] from #foo:bar: to foo: arg1 bar: arg2
The refactoring browser has this: genericPatternForSelector: aSymbol ^ String streamContents: [ :stream | aSymbol keywords keysAndValuesDo: [ :index :value | stream space; nextPutAll: value. aSymbol last = $: ifTrue: [ stream space; nextPutAll: 'arg'; print: index ] ] ] Lukas On Sun, Mar 1, 2009 at 7:18 PM, Stéphane Ducasse stephane.duca...@inria.fr wrote: Hi does one of you get to know a method for doing that? #foo:bar: - foo: arg1 bar: arg2 Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Lukas Renggli http://www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] changing default font
Rob Rothwell wrote: And if you get tired of setting your fonts individually, you can set them all at once: we should add something like that as font themes to the preferences? Michael font := LogicalFont familyName: 'Andika Basic' pointSize: 10. codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. Preferences setListFontTo: font. Preferences setMenuFontTo: font. Preferences setCodeFontTo: codeFont. Preferences setButtonFontTo: font. Preferences setSystemFontTo: font. font := LogicalFont familyName: 'Andika Basic' pointSize: 11. Preferences setWindowTitleFontTo: font. Just replace the font names with those of your choice! ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] changing default font
I kind of like the idea, but I'm not sure what the UI would look like? Is it the option of choosing the same font for multiple purposes that is attractive? I also do something like: Preferences addBooleanPreference: #ScanAtStartup categories: #(FreeType) default: false balloonHelp: 'select to rescan the font folder during startup' . Along with: FreeTypeFontProviderstartUp: resuming Preferences ScanAtStartup ifFalse: [^self]. resuming ifTrue:[ self current updateFromSystem] Just so I don't have to wait for it to scan my font folder during start up each time. So...I guess I managed to figure out SOMETHING about Preferences, but I don't know how to add other UI elements like radio buttons, drop down lists, etc... which would be useful in this case. If it is really something that you think would be useful, I'll give it a shot if anyone can point me towards some Preferences examples that would be similar, otherwise, I'll just keep loading my Personalization package that, upon loading, executes Personalize fonts! Rob On Sun, Mar 1, 2009 at 1:42 PM, Michael Rueger m.rue...@acm.org wrote: Rob Rothwell wrote: And if you get tired of setting your fonts individually, you can set them all at once: we should add something like that as font themes to the preferences? Michael font := LogicalFont familyName: 'Andika Basic' pointSize: 10. codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. Preferences setListFontTo: font. Preferences setMenuFontTo: font. Preferences setCodeFontTo: codeFont. Preferences setButtonFontTo: font. Preferences setSystemFontTo: font. font := LogicalFont familyName: 'Andika Basic' pointSize: 11. Preferences setWindowTitleFontTo: font. Just replace the font names with those of your choice! ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] changing default font
Rob Rothwell wrote: I kind of like the idea, but I'm not sure what the UI would look like? Is it the option of choosing the same font for multiple purposes that is attractive? Not necessarily just the same font name but as with the UI themes a group of settings that work well together. You could predefine in some script themes like large, small, fixed width, 50+ ;-) and then select them from the preference panel just like you select the UI theme. Michael ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] towards pharo 1.0 (from pavel)
Thanks for the feedback, Pavel. I tagged these issues with Milestone-1.0 and reopened issue 71 since it seems still open according to the comment below. Cheers, Adrian On Mar 1, 2009, at 18:18 , Stéphane Ducasse wrote: Hi Stef, there are some opened issues so we may start with them: 310 and 311 - the goal is to be able to unload all tests. As Adrian sugested, we may place it the package Tests - at least for now. 346 - easy and safe to integrate 348 - very important issue. Maybe you should place in one update fix for MorphicUIManagerinteractiveParserFor: and in the next the rest of the patch to prevent loading problems There was one wrong step in the development of Pharo during removing of MVC. Pharo deleted all MVC related code however in some cases it was the sign to use the UIManager. 71, 59 - very critical patch but I will have to check if the patches are suitable for the latest pharo I suggest to remove the unused class variable Current from the ColorTheme (issue 467) firstly - that cleans a lot of obsoleteClasses. I think that we need one important step in the development of Pharo - the next image that will not contain any code that can be unloaded. That should help us to increase the Pharo quality because now most packges are on the logical level in contradistiction to KernelImage where all packages are standalone unloadable entities. The ideal state is when we have the minimal core image with logical packages (like Collections) and the rest will be all unloadable packages. Cheers, -- Pavel On Sun, Mar 1, 2009 at 9:57 AM, stephane ducasse stephane.duca...@free.fr wrote: The KernelImage ZOO including the building environment is here: http://squeak.cz/public/pub/KernelImage/current/ Of course it is not perfect - the smallest image works only in Linux and MorphicCore needs a lot of fixes so people should start with MorphicExt and so on but it is usable starting point if someone is interested... -- Pavel Hi pavel do you have some fixes, cs list that we could slowly integrate to pharo? Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] changing default font
Oh...I get it! What would be nice about Fonts (unlike window appearances), is that you could EASILY define your own custom themes as well, just by saving your current settings. Then you could save them somehow for re-use when the next version of the image came out! Again, this would be hard for many things, but easy for fonts! Rob On Sun, Mar 1, 2009 at 2:13 PM, Michael Rueger m.rue...@acm.org wrote: Rob Rothwell wrote: I kind of like the idea, but I'm not sure what the UI would look like? Is it the option of choosing the same font for multiple purposes that is attractive? Not necessarily just the same font name but as with the UI themes a group of settings that work well together. You could predefine in some script themes like large, small, fixed width, 50+ ;-) and then select them from the preference panel just like you select the UI theme. Michael ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] changing default font
Actually I was thinking simple :) I had in mind a well writen blog post with that script, talking how cool and fun the environment is with those and maybe mentioning why good UI helps do better software. Just that could be teasing about pharo to an outsider. Of course the a blog should be for branding and well indexed (a nice sitemap could do it). Better branding always help and it means valuable actions that sometimes are beyond the image ;) best, sebastian -Mensaje original- De: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] En nombre de Michael Rueger Enviado el: Sunday, March 01, 2009 15:43 Para: Pharo-project@lists.gforge.inria.fr Asunto: Re: [Pharo-project] changing default font Rob Rothwell wrote: And if you get tired of setting your fonts individually, you can set them all at once: we should add something like that as font themes to the preferences? Michael font := LogicalFont familyName: 'Andika Basic' pointSize: 10. codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. Preferences setListFontTo: font. Preferences setMenuFontTo: font. Preferences setCodeFontTo: codeFont. Preferences setButtonFontTo: font. Preferences setSystemFontTo: font. font := LogicalFont familyName: 'Andika Basic' pointSize: 11. Preferences setWindowTitleFontTo: font. Just replace the font names with those of your choice! ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] split/join
Here it is: http://www.squeaksource.com/RubyShards.html - on On Mar 1, 2009, at 19:22, Stéphane Ducasse wrote: I think that there was a split/join package somewhere. Does anybody know where it is? At one point it was planned to get added to squeak and nothing happened. Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] changing default font
Good idea. We can set up a blog on the Pharo web site. Will add this to my todo list... Adrian On Mar 1, 2009, at 20:32 , Sebastian Sastre wrote: Actually I was thinking simple :) I had in mind a well writen blog post with that script, talking how cool and fun the environment is with those and maybe mentioning why good UI helps do better software. Just that could be teasing about pharo to an outsider. Of course the a blog should be for branding and well indexed (a nice sitemap could do it). Better branding always help and it means valuable actions that sometimes are beyond the image ;) best, sebastian -Mensaje original- De: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] En nombre de Michael Rueger Enviado el: Sunday, March 01, 2009 15:43 Para: Pharo-project@lists.gforge.inria.fr Asunto: Re: [Pharo-project] changing default font Rob Rothwell wrote: And if you get tired of setting your fonts individually, you can set them all at once: we should add something like that as font themes to the preferences? Michael font := LogicalFont familyName: 'Andika Basic' pointSize: 10. codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. Preferences setListFontTo: font. Preferences setMenuFontTo: font. Preferences setCodeFontTo: codeFont. Preferences setButtonFontTo: font. Preferences setSystemFontTo: font. font := LogicalFont familyName: 'Andika Basic' pointSize: 11. Preferences setWindowTitleFontTo: font. Just replace the font names with those of your choice! ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] changing default font
That's the best possible place :D cheers sebastian -Mensaje original- De: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] En nombre de Adrian Lienhard Enviado el: Sunday, March 01, 2009 16:41 Para: Pharo-project@lists.gforge.inria.fr Asunto: Re: [Pharo-project] changing default font Good idea. We can set up a blog on the Pharo web site. Will add this to my todo list... Adrian On Mar 1, 2009, at 20:32 , Sebastian Sastre wrote: Actually I was thinking simple :) I had in mind a well writen blog post with that script, talking how cool and fun the environment is with those and maybe mentioning why good UI helps do better software. Just that could be teasing about pharo to an outsider. Of course the a blog should be for branding and well indexed (a nice sitemap could do it). Better branding always help and it means valuable actions that sometimes are beyond the image ;) best, sebastian -Mensaje original- De: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] En nombre de Michael Rueger Enviado el: Sunday, March 01, 2009 15:43 Para: Pharo-project@lists.gforge.inria.fr Asunto: Re: [Pharo-project] changing default font Rob Rothwell wrote: And if you get tired of setting your fonts individually, you can set them all at once: we should add something like that as font themes to the preferences? Michael font := LogicalFont familyName: 'Andika Basic' pointSize: 10. codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. Preferences setListFontTo: font. Preferences setMenuFontTo: font. Preferences setCodeFontTo: codeFont. Preferences setButtonFontTo: font. Preferences setSystemFontTo: font. font := LogicalFont familyName: 'Andika Basic' pointSize: 11. Preferences setWindowTitleFontTo: font. Just replace the font names with those of your choice! ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] split/join
Oscar Nierstrasz wrote: Here it is: http://www.squeaksource.com/RubyShards.html Here it is http://bugs.squeak.org/view.php?id=4874 Keith ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] A point a.k.a excuse to you
Hi guys I probably should not have forwarded to you the email I replied to matthew but I was thinking that other people can know that I was personally touched by the situation in Squeak. I'm sorry about. We got a lot of bird names and others. Recently somebody was implying that marcus was bashing squeak because he sent an email on the pharo mailing-list stating that the situation for keyboard was worse in squeak. I'm fed up. I'm interested in pharo because I want to create free and good energy. We did a lot in the past and I want to continue. Now I unregistered from the squeak mailing-list and I will not justify anymore why I quit. Now I want pharo to be cool. Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] A point a.k.a excuse to you
Hi Stephane, I would not take it that seriously. Just focus that good energy you have and use it in getting things done in pharo and adding real value to it. Much it will receiver in return I'm sure of that. best, sebastian -Mensaje original- De: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] En nombre de Stephane Ducasse Enviado el: Sunday, March 01, 2009 18:29 Para: Pharo Development Asunto: [Pharo-project] A point a.k.a excuse to you Hi guys I probably should not have forwarded to you the email I replied to matthew but I was thinking that other people can know that I was personally touched by the situation in Squeak. I'm sorry about. We got a lot of bird names and others. Recently somebody was implying that marcus was bashing squeak because he sent an email on the pharo mailing-list stating that the situation for keyboard was worse in squeak. I'm fed up. I'm interested in pharo because I want to create free and good energy. We did a lot in the past and I want to continue. Now I unregistered from the squeak mailing-list and I will not justify anymore why I quit. Now I want pharo to be cool. Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] A point a.k.a excuse to you
On 01.03.2009, at 22:29, Stéphane Ducasse wrote: Hi guys I probably should not have forwarded to you the email I replied to matthew but I was thinking that other people can know that I was personally touched by the situation in Squeak. I'm sorry about. We got a lot of bird names and others. Recently somebody was implying that marcus was bashing squeak because he sent an email on the pharo mailing-list stating that the situation for keyboard was worse in squeak. Someone send a question to both squeak-dev and pharo-list... my mail program then puts both adresses in the reply. Normally I remember to delete the squeak-dev list, but I forgot it in that case (really, only realized it later). Then, for the question of the bug-tracking, yes, I could not resist... It would be nice if people would *not* send emails to both pharo and squeak lists. Marcus -- Marcus Denker -- den...@acm.org http://www.marcusdenker.de ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] A point a.k.a excuse to you
Stéphane Ducasse-2 wrote: ... and I will not justify anymore why I quit. Now I want pharo to be cool. Stef Good on ya mate! :) -- View this message in context: http://n2.nabble.com/A-point-a.k.a-excuse-to-you-tp2406159p2406200.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] split/join
What is split/join? Alexandre On 1 Mar 2009, at 19:22, Stéphane Ducasse wrote: I think that there was a split/join package somewhere. Does anybody know where it is? At one point it was planned to get added to squeak and nothing happened. Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Issue #112: Enhanced colors
Talking about colors, Mondrian for Squeak includes few color normalizers... Cheers, Alexandre On 27 Feb 2009, at 15:18, Stéphane Ducasse wrote: http://code.google.com/p/pharo/issues/detail?id=112 Who thinks that we should add these colors? These are more than 100 additional named colors like #paleGoldenrod, #mediumOrchid, #thistle, etc. I'd vote against adding them since I don't see their merit. Other opinions? we could keep them as a package. Having colors is useful for us Cheers, Adrian ___ http://www.adrian-lienhard.ch/ ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] A point a.k.a excuse to you
tx Stef On Mar 1, 2009, at 10:46 PM, Sebastian Sastre wrote: Hi Stephane, I would not take it that seriously. Just focus that good energy you have and use it in getting things done in pharo and adding real value to it. Much it will receiver in return I'm sure of that. best, sebastian -Mensaje original- De: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] En nombre de Stephane Ducasse Enviado el: Sunday, March 01, 2009 18:29 Para: Pharo Development Asunto: [Pharo-project] A point a.k.a excuse to you Hi guys I probably should not have forwarded to you the email I replied to matthew but I was thinking that other people can know that I was personally touched by the situation in Squeak. I'm sorry about. We got a lot of bird names and others. Recently somebody was implying that marcus was bashing squeak because he sent an email on the pharo mailing-list stating that the situation for keyboard was worse in squeak. I'm fed up. I'm interested in pharo because I want to create free and good energy. We did a lot in the past and I want to continue. Now I unregistered from the squeak mailing-list and I will not justify anymore why I quit. Now I want pharo to be cool. Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] MIMEdatabase fix?
Stéphane Ducasse wrote: With my changes to Pharo (which of course first need to be integrated), I will integrate them this evening. A quick test with loading the following packages into both the latest Pharo and a Squeak 3.9.1 image seemed to work :-) from http://www.squeaksource.com/KomHttpServer DynamicBindings-gc.7 NamedProcess-RJT.2 KomServices-gc.19 from http://squeaksource.com/PharoInbox KomHttpServer-michael_rueger.45 from http://squeaksource.com/Seaside Seaside2.8a1-pmm.583 Michael ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] A point a.k.a excuse to you
2009/3/1 Stéphane Ducasse stephane.duca...@inria.fr: Hi guys I probably should not have forwarded to you the email I replied to matthew but I was thinking that other people can know that I was personally touched by the situation in Squeak. I'm sorry about. We got a lot of bird names and others. Recently somebody was implying that marcus was bashing squeak because he sent an email on the pharo mailing-list stating that the situation for keyboard was worse in squeak. I'm fed up. I'm interested in pharo because I want to create free and good energy. We did a lot in the past and I want to continue. Now I unregistered from the squeak mailing-list and I will not justify anymore why I quit. Now I want pharo to be cool. Stephane, i don't know who were tempting your patience, but this is not really matters. I don't think that such little noise should be a reason for quitting from the list. Smalltalkers are few, and most of them are kind people. I think you are interesting in things which happening around. And you willingly losing a source of information just because someone put blames on marcus. Come on.. just ignore it. I was a witness of quitting a Tim Rowledge from squeak community and from squeak board.. We were discussed one little thing, arguing with each other.. and then boom.. he says that he fed up and quits. And since then i feel a responsibility for starting a discussion which was led to such outcome. I think that decision whether quit or not and why, should be based on more pragmatic matters and should be well weightened, rather than based on a mere random insult :) Stef ___ Pharo-project mailing list Pharo-project@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] SortedCollectionmedian
I notice that the current median is: median Return the middle element, or as close as we can get. ^ self at: self size + 1 // 2 Any reason not to make that accurate and return the average of the middle two values for collections containing an even number of items? Or...better yet...should statistics functions be removed and placed into another package with other useful items like mode, range, standardDeviation, etc...? Just wondering! Rob ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Preference refactoring again
Hi Alain, this sounds very interesting. I have never been a big fan of the current Preference Browser. I am now trying to grasp (still learning here) how this new Pharo Preference Mechanism works. It would be great if the mechanism could be explained in detail in something like the new Pharo By Example manual :) Alain Plantec wrote: I've joined 4 packages : - PrefCore contains PreferenceValue which is now the only mandatory class. 2 packages for testing: - PrefProvider contains PrefProvider class which declares some preferences - PrefUser contains PrefChangeListener (try PrefChangeListener test). 1 package for UI: - PrefTool contains PreferenceCollector and PreferenceDefinition. They are optional. -- View this message in context: http://n2.nabble.com/Preference-refactoring-again-tp2403814p2407403.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] A point a.k.a excuse to you
On Sun, Mar 01, 2009 at 08:47:53PM -0500, Schwab,Wilhelm K wrote: My sense is that Matthew is doing the right thing, with the best of intentions, but might be trying it too soon. I would appreciate it if you would expand on that. Pharo is establishing a spirit of finding the common problem and solving it such that we can all have what we want. I believe you are correct, but not everybody sees Pharo that way. Edgar and Keith in particular, sometimes see it as non-appreciation of their work, which is similar in spirit, but not as well managed. Others have more vague objections I don't yet understand. As Gandhi put it, First they ignore you, then they ridicule you, then they fight you, then you win. Some of those pressuring you have probably just moved on from ridicule. Let me apologize on behalf of the squeak-dev community. Not all of us feel so harshly toward you, but I did not speak up enough to convince you of our appreciation. You deserve better, and I'm sorry we did not deliver it. Making Pharo the best it can be will be a win for everyone, even if some do not see it that way at the time. I plan to work with Pharo soon, probably once summer starts and school is out, to get Keith's tools debugged and working in the context of Pharo, especially Monticello 1.6 (My patches to MC1.5 to enable real atomic loading (= no more problems upgrading Polymorph), and Bob (the automated image builder and regression tester). I know this is deep stuff, but I believe an automated image builder will have several advantages, both for you, as Pharo developers, and for me, as an enthusiast for cross-squeak compatibility: - making releases is faster - Regression bugs are caught faster - the scripts serve as poor-man's code sharing between squeak distributions until we have real package-level sharing of core code between core You may or may not know, but I am a core Cobalt developer, and I hope to bring Pharo and Cobalt much closer together. These two projects are hosting many core changes to the image, with little regard to backward compatibility. We may even get tweak to the level where it is a compelling replacement for Morphic, and I want Pharo to benefit from that if it does indeed happen. Too many improvements to Squeak happen in the dark (Newspeak, Spoon), and we can ill afford to estrange the truly open projects from each other (Pharo and Cobalt, IMO). Thanks for doing this! Yes, thank you Stef and Marcus for rekindling the passion for Smalltalk in many people. With luck, squeak.org may be a free, open, and useful product again. Too long has it been stuck, with nobody to bring it forward. Pharo has done much to re-awaken the love of smalltalk in many people, and that, if nothing else, is a gift beyond measure. As Squeak.org release team leader, you have my goodwill and my support. I will do what I can to spread the gifts of your efforts to the rest of squeak, and bring their efforts to you. -- Matthew Fulmer -- http://mtfulmer.wordpress.com/ ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] A point a.k.a excuse to you
On Sun, Mar 01, 2009 at 11:12:23PM -0500, Matthew Fulmer wrote: I know this is deep stuff, but I believe an automated image builder will have several advantages, both for you, as Pharo developers, and for me, as an enthusiast for cross-squeak compatibility: - making releases is faster - Regression bugs are caught faster - the scripts serve as poor-man's code sharing between squeak distributions until we have real package-level sharing of core code between core That should have been sharing of core code between squeak distributions -- Matthew Fulmer -- http://mtfulmer.wordpress.com/ ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] {Spam?} Re: A point a.k.a excuse to you
Matthew,
By the right thing too soon, I think there are influential people who are not
yet ready to allow Squeak to change. I do not necessarily agree that Stef et
al. have rekindled interest in Smalltalk so much as they have given many new
hope for Squeak to realize its potential to be a clean fast and robust open
source Smalltalk.
Bill
-Original Message-
From: pharo-project-boun...@lists.gforge.inria.fr
[mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Matthew Fulmer
Sent: Sunday, March 01, 2009 11:12 PM
To: pharo-project@lists.gforge.inria.fr
Subject: {Spam?} Re: [Pharo-project] A point a.k.a excuse to you
On Sun, Mar 01, 2009 at 08:47:53PM -0500, Schwab,Wilhelm K wrote:
My sense is that Matthew is doing the right thing, with the best of
intentions, but might be trying it too soon.
I would appreciate it if you would expand on that.
Pharo is establishing a spirit of finding the common problem and solving it
such that we can all have what we want.
I believe you are correct, but not everybody sees Pharo that
way. Edgar and Keith in particular, sometimes see it as
non-appreciation of their work, which is similar in spirit, but
not as well managed.
Others have more vague objections I don't yet understand.
As Gandhi put it, First they ignore you, then they ridicule
you, then they fight you, then you win. Some of those
pressuring you have probably just moved on from ridicule.
Let me apologize on behalf of the squeak-dev community. Not all
of us feel so harshly toward you, but I did not speak up enough to
convince you of our appreciation. You deserve better, and I'm
sorry we did not deliver it.
Making Pharo the best it can be will be a win for everyone, even if some do
not see it that way at the time.
I plan to work with Pharo soon, probably once summer starts and
school is out, to get Keith's tools debugged and working in the
context of Pharo, especially Monticello 1.6 (My patches to MC1.5
to enable real atomic loading (= no more problems upgrading
Polymorph), and Bob (the automated image builder and regression
tester).
I know this is deep stuff, but I believe an automated image
builder will have several advantages, both for you, as Pharo
developers, and for me, as an enthusiast for cross-squeak
compatibility:
- making releases is faster
- Regression bugs are caught faster
- the scripts serve as poor-man's code sharing between squeak
distributions until we have real package-level sharing of core
code between core
You may or may not know, but I am a core Cobalt developer, and I
hope to bring Pharo and Cobalt much closer together. These two
projects are hosting many core changes to the image, with little
regard to backward compatibility. We may even get tweak to the
level where it is a compelling replacement for Morphic, and I
want Pharo to benefit from that if it does indeed happen. Too
many improvements to Squeak happen in the dark (Newspeak,
Spoon), and we can ill afford to estrange the truly open
projects from each other (Pharo and Cobalt, IMO).
Thanks for doing this!
Yes, thank you Stef and Marcus for rekindling the passion for
Smalltalk in many people. With luck, squeak.org may be a free,
open, and useful product again. Too long has it been stuck, with
nobody to bring it forward. Pharo has done much to re-awaken the
love of smalltalk in many people, and that, if nothing else, is
a gift beyond measure. As Squeak.org release team leader, you
have my goodwill and my support. I will do what I can to spread
the gifts of your efforts to the rest of squeak, and bring their
efforts to you.
--
Matthew Fulmer -- http://mtfulmer.wordpress.com/
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Dynamic dead code alpha version
Stéphane Ducasse wrote: Hi I continued to code a little tool based on code of Alain to detect deadcode, so far I'm too sick to have clear idea why it freezes on Morph. This kinda reminds me of that moment in the horror film when you want to yell Don't go in there! at the characters on the screen. Colin ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Dynamic dead code alpha version
I continued to code a little tool based on code of Alain to detect deadcode, so far I'm too sick to have clear idea why it freezes on Morph. This kinda reminds me of that moment in the horror film when you want to yell Don't go in there! at the characters on the screen. lol Except that you should do it from within the film itself and sit down watching ourselves. :) Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] MIMEdatabase fix?
excellent! I'm happy. With my changes to Pharo (which of course first need to be integrated), I will integrate them this evening. A quick test with loading the following packages into both the latest Pharo and a Squeak 3.9.1 image seemed to work :-) from http://www.squeaksource.com/KomHttpServer DynamicBindings-gc.7 NamedProcess-RJT.2 KomServices-gc.19 from http://squeaksource.com/PharoInbox KomHttpServer-michael_rueger.45 from http://squeaksource.com/Seaside Seaside2.8a1-pmm.583 Michael ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] SortedCollectionmedian
On Mar 2, 2009, at 1:34 AM, Rob Rothwell wrote: I notice that the current median is: median Return the middle element, or as close as we can get. ^ self at: self size + 1 // 2 Any reason not to make that accurate and return the average of the middle two values for collections containing an even number of items? Or...better yet...should statistics functions be removed and placed into another package with other useful items like mode, range, standardDeviation, etc...? I think that it would be good. A nice package with a nice documentation and associated tests. Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
