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

Re: [Pharo-project] [ANN] Metacello configurations for Pharo.

by Michael Roberts

Hi, if you can give me a script to load the stable (blessed?) version of ConfigurationOfPharo I will try and add it to the interim build server. Also it would be ideal to have conditional logic such that the image knows if such an 'update' is present or not. That way the server goes to sleep otherwise. we would then have an update stream of sorts for Pharo. cheers, Mike

Jan. 7, 2010

Re: [Pharo-project] Pharo testers.... WE NEED YOU!!!

by Alexandre Bergel

Maybe just a keyword such as [BetaTesting] is enough. Alexandre On 7 Jan 2010, at 18:02, Mariano Martinez Peck wrote: > Do you think we need a mailing list ? Or just copying each person is > enough ? > > I am active in mailing list, but maybe some of you don't. Please let > me know what do you prefer as I -almost- have done my first dev > image based in 10505 and metacello configurations :) > > Cheers > > > On Sat, Jan 2, 2010 at 2:39 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > > wrote: > Cool....we are already 13 beta testers :) More than enought :) > > I updated http://code.google.com/p/pharo/w/list > > And we almost cover all the conbinations of OS, Browser and type of > image :) > > Cheers > > Mariano > > > On Sat, Jan 2, 2010 at 2:30 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > > wrote: > > > On Sat, Jan 2, 2010 at 1:50 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com > > wrote: > Hi Mariano, > I don't use dev or web images. I've found the PharoCore more stable, > for example now I'm fixing a dependency browser bug in the dev image > #10502 (trying a dev after a long time), and clicking with the right > button gives me : > > MessageNotUnderstood: OBTextSelection>>isMethodNode > > > Yes, this is issue: http://code.google.com/p/pharo/issues/detail?id=1182 > > but isn't just that bug, I've never worked 30 minutes with the dev/web > images without interaction bugs. I wonder what happens with Smalltalk > and Pharo newcomers when these bugs appears, but there's no survey > system for Pharo users so no one can't figure out anyway. Well, > fortunately there are no too many public word of mouth recommendation > systems yet :) > > > HernÃ¡n: I agreee 100%. All of what you describe is what I said in > the email with subject "We need to do something, seriously, ..." > > And that's exactly what I proposed to do this stuff about the beta > testers. > > Cheers > > Mariano > > Cheers, > > HernÃ¡n > > 2010/1/1 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > Sorry, I realize something. Maybe it would be cool also if you > tell us if > > you use web or dev. I happens also several times that the seaside > > installation, or pier or whatever are not working very well. > So...it would > > be cool to have both testers :) > > > > If you have access to the wiki, just add your self on it. If you > don't have > > access ask to Adrian and he will give you. Finally you can put it > here and > > then I put it in the wiki. > > > > Cheers! > > > > Mariano > > > > On Fri, Jan 1, 2010 at 10:56 PM, Mariano Martinez Peck > > <marianopeck(a)gmail.com> wrote: > >> > >> Ok.....I collect all the information here: > >> > >> http://code.google.com/p/pharo/wiki/ListOfBetaTesters > >> > >> Feel free to add something else. > >> > >> The only thing we need now is Damien's answer...maybe he is in > holidays, I > >> don't know. > >> > >> The last thing I would like to propose is that when we have a new > image to > >> test, not only we send the email to the mailing list but also cc > to each of > >> us. There is a lot of traffic (fortunately!!) in Pharo mailing > list and not > >> all the people here keeps truck for it every day. So, I think > having them in > >> cc is a good idea. > >> > >> Cheers, > >> > >> M > >> > >> On Fri, Jan 1, 2010 at 12:41 AM, Miguel CobÃ¡ > <miguel.coba(a)gmail.com> > >> wrote: > >>> > >>> > So...here is the list, if you offer yourself, it would be cool > to know: > >>> > OS, > >>> > VM version, Dev or Web, browser you usually work, 32 o 64 bits, > >>> > I will then collect this and I will put it in the wiki. > >>> > > >>> > - Mariano Martinez Peck. Mac OS, Squeak 4.2.2beta1U.app, > Dev, OB, 32 > >>> > bits > >>> > - Stan Shepherd > >>> > > >>> > > >>> > WHO ELSE IS IN THE LIST ?? > >>> > >>> Me too. > >>> > >>> - Miguel CobÃ¡, Debian GNU/Linux Squeeze (testing), Pharo0.1 of > 16 May > >>> 2008 [latest update: #10074], Web, OB, 32 bits > >>> > >>> > >>> > > >>> > cheers and happy new year!! > >>> > > >>> > >>> Feliz aÃ±o tambiÃ©n Mariano. > >>> > >>> 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 > > > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 7, 2010

Re: [Pharo-project] [ANN] Metacello configurations for Pharo.

by Alexandre Bergel

Hi Mariano, There is something not clear to me. How do you envision the squeaksource project 'Metacello Repository'. For Omnibrowser, should the configuration be in the ob repository, or being kept in 'Metacello Repository'? Next week I will work on OB with David. I really like his browser, but there are many bugs still... Cheers, Alexandre On 7 Jan 2010, at 17:54, Mariano Martinez Peck wrote: > (Sorry for the long email) > > Yes, after a couple of weeks, I have written most of the needed > Metacello configurations for the Dev images 1.0. Forget 1.1 for a > while. Now we are able to: > > 1) Load stable version of packages > 2) Manage the dependencies automatically > 3) Each developer can create its custom PharoDev image > 4) Flexibility to load the packages you want > 5) Choose the browser for example: OB or O2 > 6) Choose to load the tests or not > 7) Load each package in a PharoCore image without having to install > anything else (all the dependencies should be managed automatically) > 8) You can take a PharoCore image and "transform" it to a Dev image, > or even web. > 9) Others... > > This is not completed yet. There are some things that we are > discussing with Dale, but they are ok as a first step. I rather go > step by step. > > What I did is to create all the infrastructure: > > a) The Configuration classes > b) The dependencies > c) the groups, > > In summary, most of the "structure" and static information. However, > I am not sure which version to load of each package. I will probable > take care of building the Dev images, but I won't: > > - Merge anything. It will not be my task to merge OB, or RB or > whatever. > - Check every version of each package before doing a release to see > if it is stable or not. > > So...what I REALLY (actually, WE) need is that each developer, each > maintainer of the packages that we load of a PharoDev image, help us > to create the stable versions. To create a new version for the > Metacello configuration is VERY easy, The hard part is already done. > You just have to create a method and say which versions (except you > create or eliminate packages or dependencies). If you read the code, > you will probably understand it. However, you can read the Metacello > tutorial (no more than one hour), or ask me or even more in the > Metacello mailing list. So...PLEASE, I need the help of the > maintainers to create the versions. So far, I created the first > version (1.0) with the latest version. But the idea is that then you > create 1.1.1 or 1.2 or whatever you consider. > > All the configurations can be found in http://www.squeaksource.com/MetacelloRepository > > So far, I created: ConfigurationOfNewInspector, > ConfigurationOfOCompletion, ConfigurationOfOmniBrowser, > ConfigurationOfPharoMorphicExtras, ConfigurationOfPharoSound, > ConfigurationOfRefactoringBrowser, ConfigurationOfShout , > and......ConfigurationOfPharo!!! > > To install them, just download that package and evaluate the load. > Example: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfShout'; > load. > > ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load. > > And then, you can also for exaple do: > > ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load: > 'Core' > this doesn't install the tests. > > Or for example: (ConfigurationOfOmniBrowser project version: '1.0') > load: 'Dev' > > etc... > > So, you can load any project and with the group you want. All of > that can be (or should be hahahaha) perfectly loaded in a 1.0 Core > image. > > What I would really appreciate is if each maintainer can look at the > code, load the different groups and give me feedback on the > dependencies or whatever. > > I really wait your feedback. > > Mariano > > ps: I will release soon the first dev image using this :) > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 7, 2010

Re: [Pharo-project] Pharo testers.... WE NEED YOU!!!

by Mariano Martinez Peck

Do you think we need a mailing list ? Or just copying each person is enough ? I am active in mailing list, but maybe some of you don't. Please let me know what do you prefer as I -almost- have done my first dev image based in 10505 and metacello configurations :) Cheers On Sat, Jan 2, 2010 at 2:39 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > Cool....we are already 13 beta testers :) More than enought :) > > I updated http://code.google.com/p/pharo/w/list > > And we almost cover all the conbinations of OS, Browser and type of image > :) > > Cheers > > Mariano > > > On Sat, Jan 2, 2010 at 2:30 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> >> >> On Sat, Jan 2, 2010 at 1:50 AM, HernÃ¡n Morales Durand < >> hernan.morales(a)gmail.com> wrote: >> >>> Hi Mariano, >>> I don't use dev or web images. I've found the PharoCore more stable, >>> for example now I'm fixing a dependency browser bug in the dev image >>> #10502 (trying a dev after a long time), and clicking with the right >>> button gives me : >>> >>> MessageNotUnderstood: OBTextSelection>>isMethodNode >>> >>> >> Yes, this is issue: http://code.google.com/p/pharo/issues/detail?id=1182 >> >> >>> but isn't just that bug, I've never worked 30 minutes with the dev/web >>> images without interaction bugs. I wonder what happens with Smalltalk >>> and Pharo newcomers when these bugs appears, but there's no survey >>> system for Pharo users so no one can't figure out anyway. Well, >>> fortunately there are no too many public word of mouth recommendation >>> systems yet :) >>> >> >> >> HernÃ¡n: I agreee 100%. All of what you describe is what I said in the >> email with subject "We need to do something, seriously, ..." >> >> And that's exactly what I proposed to do this stuff about the beta >> testers. >> >> Cheers >> >> Mariano >> >> >>> Cheers, >>> >>> HernÃ¡n >>> >>> 2010/1/1 Mariano Martinez Peck <marianopeck(a)gmail.com>: >>> > Sorry, I realize something. Maybe it would be cool also if you tell us >>> if >>> > you use web or dev. I happens also several times that the seaside >>> > installation, or pier or whatever are not working very well. So...it >>> would >>> > be cool to have both testers :) >>> > >>> > If you have access to the wiki, just add your self on it. If you don't >>> have >>> > access ask to Adrian and he will give you. Finally you can put it here >>> and >>> > then I put it in the wiki. >>> > >>> > Cheers! >>> > >>> > Mariano >>> > >>> > On Fri, Jan 1, 2010 at 10:56 PM, Mariano Martinez Peck >>> > <marianopeck(a)gmail.com> wrote: >>> >> >>> >> Ok.....I collect all the information here: >>> >> >>> >> http://code.google.com/p/pharo/wiki/ListOfBetaTesters >>> >> >>> >> Feel free to add something else. >>> >> >>> >> The only thing we need now is Damien's answer...maybe he is in >>> holidays, I >>> >> don't know. >>> >> >>> >> The last thing I would like to propose is that when we have a new >>> image to >>> >> test, not only we send the email to the mailing list but also cc to >>> each of >>> >> us. There is a lot of traffic (fortunately!!) in Pharo mailing list >>> and not >>> >> all the people here keeps truck for it every day. So, I think having >>> them in >>> >> cc is a good idea. >>> >> >>> >> Cheers, >>> >> >>> >> M >>> >> >>> >> On Fri, Jan 1, 2010 at 12:41 AM, Miguel CobÃ¡ <miguel.coba(a)gmail.com> >>> >> wrote: >>> >>> >>> >>> > So...here is the list, if you offer yourself, it would be cool to >>> know: >>> >>> > OS, >>> >>> > VM version, Dev or Web, browser you usually work, 32 o 64 bits, >>> >>> > I will then collect this and I will put it in the wiki. >>> >>> > >>> >>> > - Mariano Martinez Peck. Mac OS, Squeak 4.2.2beta1U.app, Dev, OB, >>> 32 >>> >>> > bits >>> >>> > - Stan Shepherd >>> >>> > >>> >>> > >>> >>> > WHO ELSE IS IN THE LIST ?? >>> >>> >>> >>> Me too. >>> >>> >>> >>> - Miguel CobÃ¡, Debian GNU/Linux Squeeze (testing), Pharo0.1 of 16 May >>> >>> 2008 [latest update: #10074], Web, OB, 32 bits >>> >>> >>> >>> >>> >>> > >>> >>> > cheers and happy new year!! >>> >>> > >>> >>> >>> >>> Feliz aÃ±o tambiÃ©n Mariano. >>> >>> >>> >>> 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 >>> >> >> >

Jan. 7, 2010

Re: [Pharo-project] Notifications of windows opening/closing/focus

by Alexandre Bergel

>> If everybody agrees on this, it would be cool to include it in Pharo >> soon. At each new version of Morphic, I will have to update this, and >> this is boring. > > Yes I would be happy. I did not want to push this change because I > could not assess > the impact in term of slowdown. Now if we get an ok from gary and/or > others > this is ok for me. I understand this. You're right on this. I simply did not have the time and pressure from users to push it. >> It does some overrides in: >> - SystemWindow: for deletion, resize, ... >> - ScrollPane: notification for scrolling. This part is probably not >> nicely designed, but it works > > what is the increment of notification because it can geenrate a lot > of events? there is no notification if there is no subscription. Alexandre > >> - PasteUpMorph: World can now emit event for window creation and >> deletion >> >> The method SystemWindow>>openAsIsIn: is overriden. The new version >> belongs to Morphic, before it belonged to Polymorph. Loading this >> version make Polymorph dirty therefore. >> >> 5 test methods are provided in MorphicWindowNotificationTest. All >> tests are green in a pharo1.0-10502-rc1dev09.12.2 >> -=-=-=-=-=-=-=-=-=-=-=-= >> >> Comments are welcome >> >> Cheers, >> Alexandre >> >> >> On 7 Jan 2010, at 10:58, Gary Chambers wrote: >> >>> Fair enough. Perhaps the "global" announcer could be accessed via >>> the >>> class-side of SystemWindow. >>> >>> Lots of evil ways of manipulating morphs too. Just thought about >>> hide/show >>> etc. >>> >>> Regards, Gary >>> >>> ----- Original Message ----- >>> From: "Henrik Johansen" <henrik.s.johansen(a)veloxit.no> >>> To: <Pharo-project(a)lists.gforge.inria.fr> >>> Sent: Thursday, January 07, 2010 1:28 PM >>> Subject: Re: [Pharo-project] Notifications of windows opening/ >>> closing/focus >>> >>> >>>> >>>> On Jan 7, 2010, at 2:10 04PM, Gary Chambers wrote: >>>> >>>>> That is one option, though it does seem to be burdensome on the >>>>> announcement >>>>> consumers to (depending upon requirements) possibly have to track >>>>> all >>>>> windows themselves. >>>>> >>>>> Regards, GaryI am not talking about Announcers, but where the >>>>> Announcement is created. >>>> >>>> I'm not talking about letting the window be the announcer, but >>>> where the >>>> announcement is made. >>>> >>>> So you'd do >>>> openAsIsIn: aWorld >>>> "current implementation" >>>> someAnnouncer announce: (WindowOpened for: self in: self world) >>>> >>>> someAnnouncer could be a global announcer for all window events. >>>> >>>> Cheers, >>>> Henry >>>> _______________________________________________ >>>> 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 >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 7, 2010

Re: [Pharo-project] [ANN] Metacello configurations for Pharo.

by Mariano Martinez Peck

On Thu, Jan 7, 2010 at 9:54 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > (Sorry for the long email) > > Yes, after a couple of weeks, I have written most of the needed Metacello > configurations for the Dev images 1.0. Forget 1.1 for a while. Now we are > able to: > > 1) Load stable version of packages > 2) Manage the dependencies automatically > 3) Each developer can create its custom PharoDev image > 4) Flexibility to load the packages you want > 5) Choose the browser for example: OB or O2 > 6) Choose to load the tests or not > 7) Load each package in a PharoCore image without having to install > anything else (all the dependencies should be managed automatically) > 8) You can take a PharoCore image and "transform" it to a Dev image, or > even web. > 9) Others... > > This is not completed yet. There are some things that we are discussing > with Dale, but they are ok as a first step. I rather go step by step. > > What I did is to create all the infrastructure: > > a) The Configuration classes > b) The dependencies > c) the groups, > > In summary, most of the "structure" and static information. However, I am > not sure which version to load of each package. I will probable take care of > building the Dev images, but I won't: > > - Merge anything. It will not be my task to merge OB, or RB or whatever. > - Check every version of each package before doing a release to see if it > is stable or not. > > So...what I REALLY (actually, WE) need is that each developer, each > maintainer of the packages that we load of a PharoDev image, help us to > create the stable versions. To create a new version for the Metacello > configuration is VERY easy, The hard part is already done. You just have to > create a method and say which versions (except you create or eliminate > packages or dependencies). If you read the code, you will probably > understand it. However, you can read the Metacello tutorial (no more than > one hour), or ask me or even more in the Metacello mailing list. > So...PLEASE, I need the help of the maintainers to create the versions. So > far, I created the first version (1.0) with the latest version. But the idea > is that then you create 1.1.1 or 1.2 or whatever you consider. > > All the configurations can be found in > http://www.squeaksource.com/MetacelloRepository > > So far, I created: ConfigurationOfNewInspector, > ConfigurationOfOCompletion, ConfigurationOfOmniBrowser, > ConfigurationOfPharoMorphicExtras, ConfigurationOfPharoSound, > ConfigurationOfRefactoringBrowser, ConfigurationOfShout , > and......ConfigurationOfPharo!!! > > To install them, just download that package and evaluate the load. Example: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfShout'; > load. > > ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load. > > And then, you can also for exaple do: > > ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load: > 'Core' > this doesn't install the tests. > > Or for example: (ConfigurationOfOmniBrowser project version: '1.0') load: > 'Dev' > > etc... > > So, you can load any project and with the group you want. All of that can > be (or should be hahahaha) perfectly loaded in a 1.0 Core image. > > What I would really appreciate is if each maintainer can look at the code, > load the different groups and give me feedback on the dependencies or > whatever. > > I really wait your feedback. > > Mariano > > ps: I will release soon the first dev image using this :) > >

Jan. 7, 2010

[Pharo-project] [ANN] Metacello configurations for Pharo.

by Mariano Martinez Peck

(Sorry for the long email) Yes, after a couple of weeks, I have written most of the needed Metacello configurations for the Dev images 1.0. Forget 1.1 for a while. Now we are able to: 1) Load stable version of packages 2) Manage the dependencies automatically 3) Each developer can create its custom PharoDev image 4) Flexibility to load the packages you want 5) Choose the browser for example: OB or O2 6) Choose to load the tests or not 7) Load each package in a PharoCore image without having to install anything else (all the dependencies should be managed automatically) 8) You can take a PharoCore image and "transform" it to a Dev image, or even web. 9) Others... This is not completed yet. There are some things that we are discussing with Dale, but they are ok as a first step. I rather go step by step. What I did is to create all the infrastructure: a) The Configuration classes b) The dependencies c) the groups, In summary, most of the "structure" and static information. However, I am not sure which version to load of each package. I will probable take care of building the Dev images, but I won't: - Merge anything. It will not be my task to merge OB, or RB or whatever. - Check every version of each package before doing a release to see if it is stable or not. So...what I REALLY (actually, WE) need is that each developer, each maintainer of the packages that we load of a PharoDev image, help us to create the stable versions. To create a new version for the Metacello configuration is VERY easy, The hard part is already done. You just have to create a method and say which versions (except you create or eliminate packages or dependencies). If you read the code, you will probably understand it. However, you can read the Metacello tutorial (no more than one hour), or ask me or even more in the Metacello mailing list. So...PLEASE, I need the help of the maintainers to create the versions. So far, I created the first version (1.0) with the latest version. But the idea is that then you create 1.1.1 or 1.2 or whatever you consider. All the configurations can be found in http://www.squeaksource.com/MetacelloRepository So far, I created: ConfigurationOfNewInspector, ConfigurationOfOCompletion, ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphicExtras, ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, ConfigurationOfShout , and......ConfigurationOfPharo!!! To install them, just download that package and evaluate the load. Example: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfShout'; load. ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load. And then, you can also for exaple do: ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load: 'Core' this doesn't install the tests. Or for example: (ConfigurationOfOmniBrowser project version: '1.0') load: 'Dev' etc... So, you can load any project and with the group you want. All of that can be (or should be hahahaha) perfectly loaded in a 1.0 Core image. What I would really appreciate is if each maintainer can look at the code, load the different groups and give me feedback on the dependencies or whatever. I really wait your feedback. Mariano ps: I will release soon the first dev image using this :)

Jan. 7, 2010

Re: [Pharo-project] Notifications of windows opening/closing/focus

by StÃ©phane Ducasse

> Hi! > > In the PharoTaskForces SqueakSource repository I committed a new > version of Morphic (Morphic-Alexandre_Bergel.393). This version > includes the window announcement I have been working on for few months > already. > > Here is an example of a unit test. > -=-=-=-=-=-=-=-=-=-=-=-= > MorphicWindowNotificationTest>>testWindowCreationAndDeletion > > | t window newWindowCreated r | > t := 0. > World announcer on: MorphicCreationWindowAnnouncement do: [:ann | > t := t + 1. newWindowCreated := ann window]. > World announcer on: MorphicClosingWindowAnnouncement do: [:ann | t := > t + 10. newWindowCreated := ann window]. > window := SystemWindow labelled: 'foo'. > window openInWorld. > > self assert: (t = 1). > self assert: (window == newWindowCreated). > window delete. > > self assert: (t = 11). > self assert: (window == newWindowCreated). > -=-=-=-=-=-=-=-=-=-=-=-= > If everybody agrees on this, it would be cool to include it in Pharo > soon. At each new version of Morphic, I will have to update this, and > this is boring. Yes I would be happy. I did not want to push this change because I could not assess the impact in term of slowdown. Now if we get an ok from gary and/or others this is ok for me. > > The comment of the .mcz is > -=-=-=-=-=-=-=-=-=-=-=-= > This new version extends Morphic with a window event mechanism. > It add a variables to SystemWindow (thus implies a recompilation of > all subclasses of SystemWindow). > It does some overrides in: > - SystemWindow: for deletion, resize, ... > - ScrollPane: notification for scrolling. This part is probably not > nicely designed, but it works what is the increment of notification because it can geenrate a lot of events? > - PasteUpMorph: World can now emit event for window creation and > deletion > > The method SystemWindow>>openAsIsIn: is overriden. The new version > belongs to Morphic, before it belonged to Polymorph. Loading this > version make Polymorph dirty therefore. > > 5 test methods are provided in MorphicWindowNotificationTest. All > tests are green in a pharo1.0-10502-rc1dev09.12.2 > -=-=-=-=-=-=-=-=-=-=-=-= > > Comments are welcome > > Cheers, > Alexandre > > > On 7 Jan 2010, at 10:58, Gary Chambers wrote: > >> Fair enough. Perhaps the "global" announcer could be accessed via the >> class-side of SystemWindow. >> >> Lots of evil ways of manipulating morphs too. Just thought about >> hide/show >> etc. >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "Henrik Johansen" <henrik.s.johansen(a)veloxit.no> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Thursday, January 07, 2010 1:28 PM >> Subject: Re: [Pharo-project] Notifications of windows opening/ >> closing/focus >> >> >>> >>> On Jan 7, 2010, at 2:10 04PM, Gary Chambers wrote: >>> >>>> That is one option, though it does seem to be burdensome on the >>>> announcement >>>> consumers to (depending upon requirements) possibly have to track >>>> all >>>> windows themselves. >>>> >>>> Regards, GaryI am not talking about Announcers, but where the >>>> Announcement is created. >>> >>> I'm not talking about letting the window be the announcer, but >>> where the >>> announcement is made. >>> >>> So you'd do >>> openAsIsIn: aWorld >>> "current implementation" >>> someAnnouncer announce: (WindowOpened for: self in: self world) >>> >>> someAnnouncer could be a global announcer for all window events. >>> >>> Cheers, >>> Henry >>> _______________________________________________ >>> 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 >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 7, 2010

Re: [Pharo-project] Sceencast tutorial in Linux?

by Mariano Martinez Peck

I used recordmydesktop. Quite easy and useful. Cheers Mariano On Thu, Jan 7, 2010 at 9:19 PM, Stan Shepherd <stan.shepherd414(a)gmail.com>wrote: > > Hi, has anyone had any experience of recording/editing screencasts on a > Linux > box? > If so, which tools did you find gave good quality? > > Thanks, ...Stan > -- > View this message in context: > http://n2.nabble.com/Sceencast-tutorial-in-Linux-tp4268568p4268568.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 >

Jan. 7, 2010

[Pharo-project] Sceencast tutorial in Linux?

by Stan Shepherd

Hi, has anyone had any experience of recording/editing screencasts on a Linux box? If so, which tools did you find gave good quality? Thanks, ...Stan -- View this message in context: http://n2.nabble.com/Sceencast-tutorial-in-Linux-tp4268568p4268568.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 7, 2010