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

Re: [Pharo-project] Refactor -> Rename class

by Sean Allen

I've accidentally done the non refactoring one more times than I want to recount. Hiding it from me would be something I'm completely in favor of. 2010/8/13 Carla F. Griggio <carla.griggio(a)gmail.com>: > I agree. Maybe the refactor option and non-refactor option could be swapped? > I mean, the 'rename class' option that doesn't do the refactor could be in > the list of the bottom, so we don't lose the option just in case. > > On Fri, Aug 13, 2010 at 7:25 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> yes I would love that too :) >> >> Stef >> >> On Aug 13, 2010, at 10:22 AM, Nicolas Paez wrote: >> >> > >> > 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. >> > >> > <moz-screenshot-56.png> >> > >> > Regards, >> > NicolÃ¡s >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 17, 2010

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

by John M McIntosh

On 2010-08-16, at 1:39 AM, Hilaire Fernandes wrote: > Hello John, > > Please keep up informed. > > What is the situation for the Scratch viewer, is it still in the AppleSotre? no. The process for approval is what being worked, until that happens I can't say if anything like Scratch (which downloads executable byte codes), or Smalltalk (which is an interpreter), is allowed. The fact that Scratch is both doesn't complicate matters either. -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Aug. 17, 2010

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

by Dale Henrichs

Stef, Can we arrange to have a discussion about this issue at ESUG? There are a number of closely related things that need to be considered and I think that with email it is not easy ... Dale StÃ©phane Ducasse wrote: > this was more or less what I had in mind but with a limited knowledge of metacello. > > Stef > >> >> I think that we should do is a piece of code that does the following: >> >> - Take a ConfiguraitonOfXXX and do a "publish in Pharo Repository" >> - This can propmt which Pharo version, or directly which PharoRepository >> - Then it will ask which VERSION should be loaded in the already selected Pharo version >> - It should be asked WHICH group (optional) >> >> Once this is done, the code has to do the following: >> >> - Iterates all the project and packages referenced and COPY ALL OF THEM into the same repository. Or maybe we can have another repo. >> This will copy all the .mzc of the project and its dependencies. With this you will make sure that you have EVERYTHING you need to load it. >> >> - take that ConfigurationOfXXX and automatically compile a class side #load that based in your answers, does the correct job. >> In addition, this method should do a repositoryOverride: with the selected repository. >> Example: >> >> load >> | version | >> version := self project version: selectedVersion. >> version repositoryOverrides: selectedPharoRepository. >> version load: selectedGroup. >> >> Maybe it can implement a particular load: that recieves the common parameter >> >> >> >> Then, if you are in Pharo 1.0 the only thing you have to do is to explore the repository PharoRepository10 and browse the confs....you select the one you want and load it (with Gofer or Monticello Browser). Once that is done, you just evaluate: >> >> ConfiguarationOfXXX load. >> >> and that's all. >> >> What do you think ? >> Dale? >> >> >> >> Cheers >> >> -- >> Miguel CobÃ¡ >> http://miguel.leugim.com.mx >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> 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. 16, 2010

Re: [Pharo-project] which Shout repository should we use?

by Mariano Martinez Peck

On Mon, Aug 16, 2010 at 8:32 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > But, a simple instance variable rename would solve the problem for now. Why > is that not good enough now and then remove it later? > > Yes, that's good enough. My question was more general than this particular situation. I wanted to discuss which repository Pharo official images should use. > Cheers, > Doru > > > > On 16 Aug 2010, at 18:25, Lukas Renggli wrote: > > 2010/8/16 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >>> >>> >>> On Sun, Aug 15, 2010 at 6:21 PM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>> >>>> >>>> this is a good question. >>>> for now I would just update the configuration to point for the repo of >>>> lukas :) >>>> >>> >>> But now for example, I need to remove the style instVar in >>> PluggableShoutMorph because in Pharo 1.2 it has already such instVar. >>> But I don't know if I can commit or if Lukas would integrate such change >>> in >>> his repo beacuse that will break Shout to load in Pharo 1.1 (the image he >>> uses) >>> >> >> I will fix it as soon as the PharoCore 1.2 release candidate is out >> and I am able to use the image. >> >> so... lukas what do you think we should do? >>> >> >> So either fix it in Pharo or create your own 'temporary' version of >> Shout in the repository where you keep all the versions for building >> the images. >> >> Lukas >> >> -- >> 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 >> > > -- > www.tudorgirba.com > > "We cannot reach the flow of things unless we let go." > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 16, 2010

Re: [Pharo-project] Working on Pharo 1.2

by StÃ©phane Ducasse

so it worked for me :) Stef On Aug 16, 2010, at 10:14 PM, Adrian Lienhard wrote: > > On Aug 16, 2010, at 21:53 , Lukas Renggli wrote: > >> That's excellent, but is Pharo 1.2 already stable? > > No, its not stable. I just picked a random link to allow people to test this setup. Sorry for the confusion... > > Adrian > >> >> On 16 August 2010 21:51, Adrian Lienhard <adi(a)netstyle.ch> wrote: >>> Just as a test, I created the following page that redirects to a Pharo download zip. >>> >>> http://pharo-project.org/pharo-download/stable >>> >>> It redirects with a HTTP 302 response. Does that work for the scripts in use? We would like to keep the files on the existing server and serve them from there. >>> >>> Adrian >>> >>> >>> On Aug 15, 2010, at 16:35 , Adrian Lienhard wrote: >>> >>>> We are working on it... or rather, we are discussing how to do it. It's not forgotten. >>>> >>>> Adrian >>>> >>>> On Aug 15, 2010, at 14:42 , Sean P. DeNigris wrote: >>>> >>>>> >>>>> >>>>> StÃ©phane Ducasse wrote: >>>>>> >>>>>> send the code :) >>>>>> >>>>> >>>>> What is the status of the unique link to stable and trunk discussed at >>>>> http://forum.world.st/is-there-an-unique-URL-to-the-latest-pharo-core-or-de… >>>>> ? Having a static url would prevent having to constantly update the URL >>>>> referenced in the "find trunk here" message. I created an issue: >>>>> http://code.google.com/p/pharo/issues/detail?id=2805 >>>>> >>>>> Sean >>>>> -- >>>>> View this message in context: http://forum.world.st/Working-on-Pharo-1-2-tp2322972p2325897.html >>>>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> 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

Aug. 16, 2010

Re: [Pharo-project] We want your photo

by StÃ©phane Ducasse

Yes! Stef On Aug 16, 2010, at 10:12 PM, laurent laffont wrote: > for http://pharo-project.org/community/contributors > > and a little description of your Pharo usage and / or contributions. > > Thanks, > > Laurent Laffont > > http://pharocasts.blogspot.com/ > http://magaloma.blogspot.com/ > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 16, 2010

[Pharo-project] [update 1.2] #12096

by StÃ©phane Ducasse

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.

Aug. 16, 2010

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

by Mariano Martinez Peck

On Mon, Aug 16, 2010 at 9:35 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > did you check is there is a safe guard when the category start with *? > This is not up to AutomaticMethodCategorizer. I mean, by code, the only defined rules are the ones that are in #defaultCategorizationRules If you want you can add more rules. For a rule you can say something like this: add: (MethodCategorizationRule whenSelectorMatches: 'is*' categorizeIn: #testing); if you do something like this for example: add: (MethodCategorizationRule whenSelectorMatches: 'is*' categorizeIn: #*Something); There will be no error in AutomaticMethodCategorizer and Something will be recognized as it were a package. More or less could happen the same with a selector that doesn't apply to any rule. For example, suppose #aFunnySelector doesn't match any rule, but there are 10 implementors in the image and the 80% of them has category *Something. Then. it will apply *Something also to that selector. That's what I understood. However, I don't think it is a big deal and we can live with that. > ?Stef > > > > > 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 > > > > > > > > > > > One important thing I forgot to say is that the order is important here. > Notice that the pattern rules are first and then the rules for the most used > categories...this means that for example printOn: will be always in > 'printing'. However, in the system most printOn: could be in 'print' > category... > > > > So it is important what you want more...if specific patterns or maintain > consistency with what you have in the system... > > > > cheers > > > > mariano > > > > > > > > > > > > > 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 > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 16, 2010

Re: [Pharo-project] Working on Pharo 1.2

by Adrian Lienhard

On Aug 16, 2010, at 21:53 , Lukas Renggli wrote: > That's excellent, but is Pharo 1.2 already stable? No, its not stable. I just picked a random link to allow people to test this setup. Sorry for the confusion... Adrian > > On 16 August 2010 21:51, Adrian Lienhard <adi(a)netstyle.ch> wrote: >> Just as a test, I created the following page that redirects to a Pharo download zip. >> >> http://pharo-project.org/pharo-download/stable >> >> It redirects with a HTTP 302 response. Does that work for the scripts in use? We would like to keep the files on the existing server and serve them from there. >> >> Adrian >> >> >> On Aug 15, 2010, at 16:35 , Adrian Lienhard wrote: >> >>> We are working on it... or rather, we are discussing how to do it. It's not forgotten. >>> >>> Adrian >>> >>> On Aug 15, 2010, at 14:42 , Sean P. DeNigris wrote: >>> >>>> >>>> >>>> StÃ©phane Ducasse wrote: >>>>> >>>>> send the code :) >>>>> >>>> >>>> What is the status of the unique link to stable and trunk discussed at >>>> http://forum.world.st/is-there-an-unique-URL-to-the-latest-pharo-core-or-de… >>>> ? Having a static url would prevent having to constantly update the URL >>>> referenced in the "find trunk here" message. I created an issue: >>>> http://code.google.com/p/pharo/issues/detail?id=2805 >>>> >>>> Sean >>>> -- >>>> View this message in context: http://forum.world.st/Working-on-Pharo-1-2-tp2322972p2325897.html >>>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > 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

Aug. 16, 2010

[Pharo-project] We want your photo

by laurent laffont

for http://pharo-project.org/community/contributors and a little description of your Pharo usage and / or contributions. Thanks, <http://pharo-project.org/community/contributors> Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

Aug. 16, 2010