- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.2] #12097
by StÃ©phane Ducasse Aug. 17, 2010

Aug. 17, 2010

12097 ----- - Issue 2814: Mods for Sugar theme support and (pluggable) label getter. Thanks Gary Chambers and Hilaire Fernandes - Issue 2821: Fixes for DropListMorph/EditableDropListMorph. Thanks Gary Chambers. Stef

1 0

[Pharo-project] I will do integrate some fixes now....
by StÃ©phane Ducasse Aug. 17, 2010

Aug. 17, 2010

1 0

[Pharo-project] possible XML enh
by StÃ©phane Ducasse Aug. 17, 2010

Aug. 17, 2010

Hi I was browsing fixes in squeak and I saw http://code.google.com/p/pharo/issues/detail?id=2822 May be this can help to improve the XML package. Stef Fix printing of XMLElements; add tests for behavior. =============== Diff against XML-Parser-mtf.30 =============== Item was added: + ----- Method: XMLParserTest>>testPrintElements (in category 'tests') ----- + testPrintElements + | node | + node:= (XMLElement new) name: 'foo'; + setAttributes: (Dictionary new); + yourself. + self assert: node asString withBlanksTrimmed = '<foo/>'. + + node:= (XMLElement new) name: 'foo'; + setAttributes: (Dictionary newFromPairs: {'id'. '123'}); + yourself. + self assert: node asString withBlanksTrimmed = '<foo id="123"/>'. + + node:= (XMLElement new) name: 'foo'; + addContent: (XMLStringNode string: 'Hello World'); + setAttributes: (Dictionary new); + yourself. + self assert: node asString withBlanksTrimmed = '<foo>Hello World</foo>'. + + node:= (XMLElement new) name: 'foo'; + addContent: (XMLStringNode string: 'Hello World'); + setAttributes: (Dictionary newFromPairs: {'id'. '123'}); + yourself. + self assert: node asString withBlanksTrimmed = '<foo id="123">Hello World</foo>'. + + ! Item was changed: ----- Method: XMLElement>>isEmpty (in category 'testing') ----- isEmpty + "Answer true if the receiver is empty" + + ^self elementsAndContents isEmpty! - ^self elements isEmpty! Item was changed: ----- Method: XMLElement>>printXMLOn: (in category 'printing') ----- printXMLOn: writer + "Print the receiver in XML form" + writer startElement: self name attributeList: self attributes. (writer canonical not + and: [self isEmpty]) - and: [self isEmpty and: [self attributes isEmpty not]]) ifTrue: [writer endEmptyTag: self name] ifFalse: [ writer endTag. self elementsAndContentsDo: [:content | content printXMLOn: writer]. writer endTag: self name]!

2 1

[Pharo-project] Ideas of AutomaticMethodCategorizer ???
by Mariano Martinez Peck Aug. 17, 2010

Aug. 17, 2010

Hi folks...while browsing AutomaticMethodCategorizer I found the place where the rules are defined. It is cool becuase we can add the rules we want. I am all ears. For now, it is doing this: defaultCategorizationRules "The order is relevant, the categorizer uses the first rule matching - DF" ^OrderedCollection new add: MethodCategorizationRule forAccessors; add: (MethodCategorizationRule whenSelectorMatches: 'initialize*' categorizeIn: #initialization); add: (MethodCategorizationRule whenSelectorMatches: 'is*' categorizeIn: #testing); add: (MethodCategorizationRule whenSelectorMatches: 'has*' categorizeIn: #testing); add: (MethodCategorizationRule whenSelectorMatches: '=' categorizeIn: #comparing); add: (MethodCategorizationRule whenSelectorMatches: 'hash' categorizeIn: #comparing); add: (MethodCategorizationRule whenSelectorMatches: 'default*' categorizeIn: #defaults); add: (MethodCategorizationRule whenSelectorMatches: 'printOn:' categorizeIn: #printing); add: (MethodCategorizationRule whenSelectorMatches: 'accept:' categorizeIn: #'visitor accepting'); add: (MethodCategorizationRule whenSelectorMatches: 'visit*:' categorizeIn: #visiting); add: (MethodCategorizationRule whenSelectorMatches: 'value' categorizeIn: #evaluating); add: (MethodCategorizationRule whenSelectorMatches: 'test*' andClassInheritsFrom: TestCase categorizeIn: #tests); add: MethodCategorizationRule usingMostUsedCategoryInSuperClasses; add: MethodCategorizationRule usingMostUsedCategoryInImage; yourself We should improve this guy.... ideas to add/change? Cheers Mariano

3 9

[Pharo-project] Call for presentation for OSDC (free conference on dynamic languages)
by StÃ©phane Ducasse Aug. 17, 2010

Aug. 17, 2010

http://www.osdc.fr/ http://act.osdc.fr/osdc2010fr/index.html http://act.osdc.fr/osdc2010fr/sponsorship.html 9 and 10 October at Paris. Stef

1 0

[Pharo-project] [ANN] Pharo Metacello Universes
by Miguel Enrique CobÃ¡ MartÃnez Aug. 17, 2010

Aug. 17, 2010

Hi all, I have created three new repositories on squeaksource: http://www.squeaksource.com/UniverseForPharo10 http://www.squeaksource.com/UniverseForPharo11 http://www.squeaksource.com/UniverseForPharo12 They are the repositories for the current versions of Pharo. The idea is that each new release add a new UniverseForXXX repository and populates it with the current UniverseForXXX packages of the stable release. Right now they are mostly empty, but should be populated by the community and the ConfigurationOfXXX maintainers. Most ConfigurationOfXXX packages in http://www.squeaksource.com/MetacelloRepository should be copied to UniverseForPharo10. Which versions? The last known version that is working correctly on Pharo 1.0. This will be the official universe for Pharo1.0. No ConfigurationOfXXX should be stored on UniverseForPharo10 if it is not working correctly on Pharo10. Then two things can follow: - If the package already has ConfigurationOfXXX package versions that work in Pharo 1.1, those versions should be copied to UniverseForPharo11. - If the ConfigurationOfXXX only works for Pharo1.0 and the maintainer want to create the configuration for Pharo 1.1, he/she must copy the last working configuration for the package from UniverseForPharo10 to UniverseForPharo11. There he/she can start modifying the package until it works correctly in Pharo1.1 (use the blessing: tags wisely to avoid marking a broken configuration as released) This will permit to populate the UniverseForPharo11 based on the last working package versions from UniverseForPharo10. From that point they will likely diverge because of maintenance releases to the packages in any UniverseForXXX repository. The same will must be done to migrate from UniverseForPharo11 to UniverseForPharo12. You get the idea. With time, MetacelloRepository should be deprecated in favor of this UniverseForXXX repositories. Anyone is free to copy a working version from a previous Universe to a new Universe. They have read/write permissions to all. This setup will avoid the problems we are having right now with the in-image changes that are rendering the ConfigurationOfXXX unusable in distinct releases of Pharo. What this means to the end user: - For released version of Pharo They will have to use gofer this way: Gofer new squeaksource: 'UniverseForPharo10'; "Or UniverseForPharo11" project: 'ConfigurationOfMagma'; load. ConfigurationOfMagma project latestVersion load. - For next releases of Pharo Gofer loadFromUniverse: 'Magma'. "Or with GoferProjectLoader" ConfigurationOfMagma project latestVersion load. All this depends on conventions to find the appropriate universe for each pharo release, and also in the support from tools (like gofer in this example or the GoferProjectLoader if it is part of the core image). The universe functionality of the tools right now rely on the SystemVersion current majorMinorVersion string for deciding which repository to connect to. This could be improved surely but for now it works. I'm loading a new version of Gofer to PharoInbox with this functionality added so if you want to load directly from the universes with gofer do: Gofer upgrade. Gofer loadFromUniverse: 'YourPackageAlreadyInAUniverse'. But wait to this change to be treated by Stephane or Lukas before attempt it. Right now there is only Magma in the three repositories, but it shouldn't be hard for the maintainers of the other Configurations to help populate the universes from Pharo1.0, Pharo1.1 and Pharo1.2. This will benefit us as a community because the universes for the released pharo versions will be mostly untouched (only maintenance releases) and people will have the freedom to modify the configuration in the unstable (currently UniverseForPharo12) universe without affecting the users of the stable versions. Also, this will avoid to have a lot of conditionals inside the ConfigurationOfXXX classes, because a given class will target a specific Pharo release (the version on the newest universes could even delete the methods for the old universe, because will likely won't work in the new universe, deleting unnecessary and legacy code from the configuration) Comments and improvements welcome -- Miguel CobÃ¡ http://miguel.leugim.com.mx

7 22

[Pharo-project] Refactor -> Rename class
by Nicolas Paez Aug. 17, 2010

Aug. 17, 2010

I am using this feature I think that the "rename..." menu option should by default work like refactor, at this moment it just renames the class with updating dependent stuff, if you want to apply refactor you have to drill down to the refactor class suboption. I think "remove class..." and "rename class..." (in a refactor way) are the more frequent actions applied on a class. I don't mind if the option is duplicated in the menu if it makes thing easy. Regards, NicolÃ¡s

4 3

[Pharo-project] What is the situation regarding iPhone
by Hilaire Fernandes Aug. 17, 2010

Aug. 17, 2010

Can we legally distribute through the apple store Pharo Smalltalk applications? Hilaire -- Dr. Geo, to discover geometry on Linux, Windows, MAC and XO http://community.ofset.org/index.php/DrGeo

3 5

Aug. 16, 2010

12096 ----- - Add Preferences empty class else I have to manually create before merging. This way we can merge and worked to turn the preference in setting. - Issue 1921: Class>>Binding Fix. Thanks Andreas Raab. Guillermo Polito. I integrated it with the previous change I did.

1 0

Re: [Pharo-project] Contributors page (was little pictures of you)
by laurent laffont Aug. 16, 2010

Aug. 16, 2010

Hi, I've started a Contributors page http://pharo-project.org/about/contributors . Tell me if you like it or not before going further. If you want to be on this page, just send me a photo (120px wide at least) and links, short text you want to put here. Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ On Wed, Aug 11, 2010 at 12:47 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > Hi guys > > the pharo web site does not support that yet :) > but I would love to have some pictures of you because this is not that fun > to talk daily with people > when we do not even know their faces so we could start to build a pharo fun > community. > Let me know what you think. > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

13 33