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

Re: [Pharo-project] Ideas of AutomaticMethodCategorizer ???

by Alexandre Bergel

new* -> 'instance creation' write* -> 'writing' add* -> 'adding - removing' remove* -> 'adding - removing' Alexandre On 15 Aug 2010, at 14:55, Mariano Martinez Peck wrote: > 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 > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 15, 2010

[Pharo-project] Pharocasts: Display Picasa photos

by laurent laffont

Learn: - how to get data from an URL - parse XML documents - build a GUI to display photos with Polymorph - how to prototype quickly with debugger and inspector http://pharocasts.blogspot.com/2010/08/see-how-to-get-data-from-url-parse-x… Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

Aug. 15, 2010

Re: [Pharo-project] Where I commit changes to AutomaticMethodCategorizer for example?

by Mariano Martinez Peck

On Sun, Aug 15, 2010 at 9:14 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > 1 - ask him > May be he is not even doing smalltalk anymore. > 2- What is the license of the code > OK. I will. > 3- fork. > PharoCategorizer > Pharoxxxx > > I am starting to be tired about having XXXForPharo or PharoXXX. It seems to be evident that at some point we need a www.pharosource.com for those Pharo specific projects/forks. Thanks! Mariano > Stef > > On Aug 15, 2010, at 8:52 PM, Mariano Martinez Peck wrote: > > > Hi. I am trying to work in the Pharo 1.2 but I an finding different > problems. For example, AutomaticMethodCategorizer uses Preferences, and I > need to update it. > > The project has global read in squeaksource, thus I cannot commit. In > addition, I don't think Diego will let me commit that as I will break the > code for squeak (ok...I can add Smalltalk at:Preferences ifTrue...but > that's crap). > > > > So....what do I do ? I commit that package in Pharo repository? > PharoNonCore? > > > > thanks > > > > Mariano > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 15, 2010

Re: [Pharo-project] Where I commit changes to AutomaticMethodCategorizer for example?

by StÃ©phane Ducasse

1 - ask him May be he is not even doing smalltalk anymore. 2- What is the license of the code 3- fork. PharoCategorizer Pharoxxxx Stef On Aug 15, 2010, at 8:52 PM, Mariano Martinez Peck wrote: > Hi. I am trying to work in the Pharo 1.2 but I an finding different problems. For example, AutomaticMethodCategorizer uses Preferences, and I need to update it. > The project has global read in squeaksource, thus I cannot commit. In addition, I don't think Diego will let me commit that as I will break the code for squeak (ok...I can add Smalltalk at:Preferences ifTrue...but that's crap). > > So....what do I do ? I commit that package in Pharo repository? PharoNonCore? > > thanks > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 15, 2010

Re: [Pharo-project] Ideas of AutomaticMethodCategorizer ???

by StÃ©phane Ducasse

On Aug 15, 2010, at 8:55 PM, Mariano Martinez Peck wrote: > 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. yes I would really like to have consistent categories. Now we should pay attention that the automaticmethodcategory does not do anythin when the category is * something. Stef > > 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); #initialize > 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 > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 15, 2010

[Pharo-project] Ideas of AutomaticMethodCategorizer ???

by Mariano Martinez Peck

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

Aug. 15, 2010

[Pharo-project] Where I commit changes to AutomaticMethodCategorizer for example?

by Mariano Martinez Peck

Hi. I am trying to work in the Pharo 1.2 but I an finding different problems. For example, AutomaticMethodCategorizer uses Preferences, and I need to update it. The project has global read in squeaksource, thus I cannot commit. In addition, I don't think Diego will let me commit that as I will break the code for squeak (ok...I can add Smalltalk at:Preferences ifTrue...but that's crap). So....what do I do ? I commit that package in Pharo repository? PharoNonCore? thanks Mariano

Aug. 15, 2010

Re: [Pharo-project] Preferences removal Re: [update 1.2] #12092

by StÃ©phane Ducasse

On Aug 15, 2010, at 7:03 PM, Tudor Girba wrote: > As far as I know, this happens because now a TextMorph has a styler strategy. By default, the styler is the NullStyler but it can be set from outside to be something else (like a ShoutStyler). > > Like that you have the two concerns (editing, and highlighting) nicely supported by the framework without requiring subclassing. > > So, I would say that the simplest way to go around this problem and still be somewhat backward compatible would be to renamed styler to shoutStyler in the PluggableShoutMorph. why not but having a 1.2 version would solve the problem too. > > Cheers, > Doru > > > On 15 Aug 2010, at 18:48, Mariano Martinez Peck wrote: > >> >> >> On Sun, Aug 15, 2010 at 6:41 PM, Lukas Renggli <renggli(a)gmail.com> wrote: >> > Lukas, Shout won't load in Pharo 1.2 because of issue >> > >> > http://code.google.com/p/pharo/issues/detail?id=2734 >> >> I am using PharoCore 1.1 until PharoCore 1.2 gets a release candidate. >> >> I guess PluggableTextMorph should be fixed, or why was this instance >> variable added? Is this coming from Squeak? >> >> I have no idea. I asked several times if someone can fix it... >> I am trying to start building PharoDev on top of PharoCore 1.2 but I have this problem. >> >> >> >> Lukas >> >> > >> > :( >> > >> >> >> >> Lukas >> >> >> >> > >> >> > >> >> > The problem are the external pacakges. I have 100 references to >> >> > Preferences in Pharo dev....almost EVERY external package uses Preferences. >> >> > So....we really need help of the external package maintainers to update >> >> > them. And I am not sure how easy is that. >> >> > What should be easy is to have a Preferences class that supports the >> >> > simple API that everyone was using: add a preference. And make >> >> > Preferenceclass return true or false for that preference. That should be 90% >> >> > of all usages, I guess.. >> >> > We can do that by just having a dictionary and overriding >> >> > doesNotUnderstand:. We should not provide all this magic that used to be >> >> > there, e.g.compiling on the fly methods for accessed perferences (which >> >> > funnily had an empty source pointer...). >> >> > I mean...is there a mapping between each previous preference a the new >> >> > ones? >> >> > >> >> > >> >> > In 1.1, Preferences are returning the values from the Settings framework >> >> > for backward compatibillity. >> >> > But I don't think that Preferences added are shown in the Settings? This >> >> > would require Settings to be generated, which is possible but I thinknot >> >> > really what we want. >> >> > One could of course build this specification for the Preferences... and >> >> > maybe there was even code there for that ;-) I started the cleanup bu >> >> > removingunsent messages... but after a while that got really boring. And >> >> > Preferences was a near 2000 LOC abdomination of a class. >> >> > I checked in 1.1Dev, and most of the references are from the Core, which >> >> > we removed in 1.2... >> >> > Marcus >> >> > >> >> > >> >> > --Marcus Denker >> >> > -- http://www.marcusdenker.de <http://www.marcusdenker.de/> >> >> > INRIA Lille -- Nord Europe. Team RMoD. >> >> > >> >> > >> >> > >> >> >> >> -- >> >> Lukas Renggli >> >> www.lukas-renggli.ch >> >> >> >> _______________________________________________ >> >> Pharo-project mailing list >> >> Pharo-project(a)lists.gforge.inria.fr >> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Every successful trip needs a suitable vehicle." > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 15, 2010

Re: [Pharo-project] What is the situation regarding iPhone

by John M McIntosh

Morning Hilaire. I had discussions with middle level Apple management on Aug 5th. I am told decisions should be forthcoming: "the next few weeks" On 2010-08-15, at 3:33 AM, Hilaire Fernandes wrote: > 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Aug. 15, 2010

[Pharo-project] [update 1.2] #12093

by Marcus Denker

12093 ----- Issue 2807: Small cleanup for Inspector Issue 2806: small code-critique cleanup of FileList Issue 2799: Class binding -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Aug. 15, 2010