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

[Pharo-project] for 1.0 did we put the welcome message

by StÃ©phane Ducasse

with the summary of all the actions? Stef

March 19, 2010

Re: [Pharo-project] CleanUp unused packages

by Laval Jannik

Hi Mariano, I am not sure, but I think FixUnderscores should be useful for old packages loaded in pharo. For example, some projects still use _, so we need FixUnderscore to fix them automatically. Personally, I use it on the whole Pharo 3 months ago. Cheers, Jannik On Mar 18, 2010, at 23:37 , Mariano Martinez Peck wrote: > http://code.google.com/p/pharo/issues/detail?id=2165 > > There are some packages that has to be removed. For example: > - PinesoftEnhancementsForFreeType: This package is empty > - FixUnderscores: This package is old, is not needed any more and has no references > > The fix is to evaluate: > > (MCPackage named: 'PinesoftEnhancementsForFreeType') unload. > (MCPackage named: 'FixUnderscores') unload. > > Cheers > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 19, 2010

Re: [Pharo-project] recategorizing all the categories...

by HernÃ¡n Morales Durand

I understand, but what if people do want classify papers labelled "as yet unclassified"? HernÃ¡n 2010/3/18 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > because there is a difference between my desk and the desk of marcus. > My desk is full of paper and I'm the only one that can find sometimes on it > (which is ok this is my desk) > but now if marcus needs to use my desk it will take him more time to find > something. > While with a nicely labelled desk then this is easier to find something. > > Stef > > On Mar 18, 2010, at 5:22 AM, HernÃ¡n Morales Durand wrote: > > > Hi Stef, > > I don't see why unclassified should correlate to dirt. > > Cheers, > > > > HernÃ¡n > > > > 2010/3/17 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > hi guys > > > > I wanted to know if one you try tried to automatically recategorized all > the methods of the system. > > Because I'm tired to get this as yet unclassified in my face. I looks to > my like dirt in the street. > > Wanna get clean... > > > > Stef > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 19, 2010

Re: [Pharo-project] A challenge for us

by Miguel Enrique CobÃ¡ Martinez

El jue, 18-03-2010 a las 11:14 -0300, GermÃ¡n Arduino escribiÃ³: > 2010/3/18 Henrik Johansen <henrik.s.johansen(a)veloxit.no>: > > > > I guess the correct incantation was (ConfigurationOfPharo project version: > > '1.0-rc3.10515') load. :) > > We really should set up a backup repository with all the packages included > > in specs though. > > Older versions have already stopped working twice now due to package > > deletions, first FFI, and then RB. > > F.ex, doing (ConfigurationOfPharo project version: '1.0-rc2.10508') load in > > a 10508rc2 Core image will now fail. > > Cheers, > > Henry > > I tried (ConfigurationOfPharo project version: '1.0-rc3.10515') load > on 1.1UNSTABLE #11277 and > fail with "TheWorldMenu class DNU #registerOpenCommand: " Isn't this because of the new Menu code with registration capabilities instead of the old menu code? I think that as soon as Pharo 1.0 is released, Mariano will work on making the corresponding 1.1 ConfigurationOfPharo and we all test it. BTW, you could copy the current 10515 version and change it and adapt it to Pharo 1.1 and that way we all can start try it. Cheers > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

March 19, 2010

Re: [Pharo-project] [Esug-list] ESUG selected as GSoC 2010 mentoring organization!!!!

by Serge Stinckwich

Thank you Mariano and Janko for the great effort ! On Fri, Mar 19, 2010 at 5:33 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > We are incredibly proud to announce that ESUG was selected for the GSoC > 2010. We have a long list of wonderful projects, mentors and a cool website. > > We want to thank you to all the people who help us publishing project ideas, > giving feedback on the submit text or the English, etc. > > For the moment, we don't know the slots (amount of projects) that we will > receive. > > Don't worry. We will contact you again very soon to let you know the > following steps. > > Now, prepare yourself. We have to show the rest of the world why we love > Smalltalk so much :) > > Thank you very much. > > The very happy GSoC admin team > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/listinfo/esug-list > > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

March 19, 2010

Re: [Pharo-project] [GS/SS Beta] ESUG selected as GSoC 2010 mentoring organization!!!!

by Miguel Enrique CobÃ¡ Martinez

El jue, 18-03-2010 a las 23:33 +0100, Mariano Martinez Peck escribiÃ³: > We are incredibly proud to announce that ESUG was selected for the > GSoC 2010. We have a long list of wonderful projects, mentors and a > cool website. > > We want to thank you to all the people who help us publishing project > ideas, giving feedback on the submit text or the English, etc. > > For the moment, we don't know the slots (amount of projects) that we > will receive. > > Don't worry. We will contact you again very soon to let you know the > following steps. > > Now, prepare yourself. We have to show the rest of the world why we > love Smalltalk so much :) > > Thank you very much. > > The very happy GSoC admin team Very good news. Thanks Mariano and Janko for the effort -- Miguel CobÃ¡ http://miguel.leugim.com.mx

March 19, 2010

Re: [Pharo-project] MethodProperties question

by Mariano Martinez Peck

On Wed, Mar 17, 2010 at 6:37 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > yeap > open a ticket > > Done: http://code.google.com/p/pharo/issues/detail?id=2166 > Stef > On Mar 17, 2010, at 4:46 PM, Mariano Martinez Peck wrote: > > > Hi folks (Marcus ?). > > > > I saw this class was removed, however: > > > > 1) The class MethodPropertiesTest is still alive. Shouldn't we remove it > ? > > > > 2) After evaluating "ScriptLoader new cleanUpForRelease" > > > > if I inspect > > > > SystemNavigation default obsoleteClasses > > > > I have a "AnObsoleteMethodProperties" > > > > 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 >

March 19, 2010

Re: [Pharo-project] Question about HostMenuSystem

by Michael Rueger

On 3/18/10 3:38 PM, Mariano Martinez Peck wrote: > Hi folks. I want to remove HostMenuSystem from PharoCore image. > Probably, I can put it on PharoDev image but of course, it will be > accesible also from squeaksource to download it. I don't this is a > "core" package. In order to do that, I found the following problem. > > Look to InputEventSensor >> processMenuEvent: evt You could also remove this code completely, including the call to processMenuEvent: and then the HostMenuSystem could register its own input event listener upon installation. See UserInterruptHandler for an example how to do this. Michael

March 18, 2010

Re: [Pharo-project] recategorizing all the categories...

by Mariano Martinez Peck

I am not responsible of the consequences of the following code: First: Gofer new squeaksource: 'autoMethodCat'; package: 'AutomaticMethodCategorizer'; load. After: | autoCat | autoCat := AutomaticMethodCategorizer new. Smalltalk allClassesDo: [:each | autoCat categorizeAllUncategorizedMethodsOf: each ]. Cheers Mariano On Wed, Mar 17, 2010 at 8:59 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > hi guys > > I wanted to know if one you try tried to automatically recategorized all > the methods of the system. > Because I'm tired to get this as yet unclassified in my face. I looks to my > like dirt in the street. > Wanna get clean... > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 18, 2010

[Pharo-project] Question about HostMenuSystem

by Mariano Martinez Peck

Hi folks. I want to remove HostMenuSystem from PharoCore image. Probably, I can put it on PharoDev image but of course, it will be accesible also from squeaksource to download it. I don't this is a "core" package. In order to do that, I found the following problem. Look to InputEventSensor >> processMenuEvent: evt | handler localCopyOfEvt | localCopyOfEvt := evt shallowCopy. handler := (HostSystemMenus defaultMenuBarForWindowIndex: (localCopyOfEvt at: 8)) getHandlerForMenu: (localCopyOfEvt at: 3) item: (localCopyOfEvt at: 4). handler handler value: localCopyOfEvt There is the only place where HostSystemMenus is used. Now I am trying to see the best way to remove this. The first approach that came to my mind, which may not be the best to implement this method as follows: processMenuEvent: evt "By default the menu events are not handled. In case you want to handle them you should override this method" And of course, in the package HostSystemMenus we override that method with the original code. Then I though some kind of notification or oberser pattern, where someone can register as an "observer" and then, then this menu events occurs, these guys are notified. Maybe using Announcments? My skills here are quite limited. What do you think ? Can you help me ? Cheers Mariano

March 18, 2010