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

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

by Esteban Lorenzano

ok, I'll try something like this: Loader new descriptionOf: 'Blah'. "Answers the #description metacello tag for current version" Loader new descriptionOf: 'Blah' version: '1.0'. "Answers the #description metacello tag for 1.0 version" do you think this is enough? cheers, Esteban On 2010-01-08 10:26:06 -0300, Alexandre Bergel <alexandre(a)bergel.eu> said: > A description that could be obtained from the last commit comment for > example. Or/and the squeaksource description. > > Cheers, > Alexandre > > > On 8 Jan 2010, at 10:20, Esteban Lorenzano wrote: > >> Hi, >> And what info do you think it should answer? >> >> On 2010-01-08 09:39:31 -0300, Alexandre Bergel >> <alexandre(a)bergel.eu> said: >> >>> Esteban, this is excellent!! >>> It would be cool to have >>> >>> Loader new infoAbout: >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 8, 2010

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

by Alexandre Bergel

A description that could be obtained from the last commit comment for example. Or/and the squeaksource description. Cheers, Alexandre On 8 Jan 2010, at 10:20, Esteban Lorenzano wrote: > Hi, > And what info do you think it should answer? > > On 2010-01-08 09:39:31 -0300, Alexandre Bergel > <alexandre(a)bergel.eu> said: > >> Esteban, this is excellent!! >> It would be cool to have >> >> Loader new infoAbout: > > > > > _______________________________________________ > 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. 8, 2010

Re: [Pharo-project] Interim build server update

by StÃ©phane Ducasse

Now that the log file on failure is appened to the previous log I think that we should pay attention or explicitly have the possibility to write a fresh one. Because we can have a problem: I got some 5 mb log file. Stef > a simple test report for PharoCore 1.1 is now automatically published at > > http://pharo.gforge.inria.fr/experimental/ > > what do you think? > > That's really cool!!! I cannot image what good this will be together with Hudson!!! > > I am agree with the OS. Some tests use to be ok for one platform but not in another one (I don't remember right now). Even more, I would print the VM also. Maybe you can put all that information that it is put at the beginning of the PharoDebug.log. I remember there was a way to get that information....but I don't remember how hahaha. > > EXCELLENT! > > Cheers > > Mariano > > > I would propose to remove the google wiki test entries (for 1.1) and > point them here. > > cheers, > Mike > > _______________________________________________ > 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. 8, 2010

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

by StÃ©phane Ducasse

> > Alexandre, > > How about something like the following expressions: > > Gofer loadConfiguration: 'Pharo' version: '1.0-rc2.10505'. > Gofer loadConfiguration: 'NewInspector'. > Gofer loadConfiguration: 'Magritte' load: #( 'Magritte-Model' 'Magritte-Tests' ). > Gofer loadConfiguration: 'OmniBrowser' version: '1.0' load: 'Core'. sounds good. > > I whipped together some extension methods for Gofer that adds support for the above to Gofer: > > Gofer new > gemsource: 'metacello'; > package: 'Metacello-Gofer-Extensions'; > load. > > If there is no leading ConfigurationOf in the configuration name, 'ConfigurationOf' is tacked on. If no version is specified (or is nil) the latest version of the configuration is loaded. If no explicit load list is supplied (or is nil), then the default load list is loaded. In all cases it is expected that the configuration will be found in the MetacelloRepository on SqueakSource... > > Dale > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 8, 2010

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

by Esteban Lorenzano

Ahhhh... ok :) On 2010-01-08 09:48:17 -0300, Mariano Martinez Peck <marianopeck(a)gmail.com> said: > > > On Fri, Jan 8, 2010 at 1:12 PM, Esteban Lorenzano > <estebanlm(a)gmail.com>wrote: > >> btw, ConfigurationOfPharo shouldn't be ConfigurationOfPharoDev? >> >> > No. For that we have the groups. The same ConfigurationOfPharo will be used > for differents stuff: > > ConfigurationOfPharo project version: 'xxx' load: 'StandardPharoDev' > > or > > ConfigurationOfPharo project version: 'xxx' load: 'StandardPharoWeb ' (if > they came back) > > or > > ConfigurationOfPharo project version: 'xxx' load: 'SOMETHING' (if they came > back) > > Cheers > > Mariano > > > >> On 2010-01-07 17:54:27 -0300, Mariano Martinez Peck >> <marianopeck(a)gmail.com> said: >> >>> >>> >>> (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 :) >>> >>> >>> (Sorry for the long email) Yes, after a couple of weeks, I have >> writ= >>> ten most of the needed Metacello configurations for the Dev images 1.0. >> For= >>> get 1.1 for a while. Now we are able to: 1) Load stable version of >> p= >>> ackages >>> 2) Manage the dependencies automatically 3) Each developer can create >> it= >>> s custom PharoDev image >>> 4) Flexibility to load the packages you want 5) Choose the browser for >> e= >>> xample: OB or O2 6) Choose to load the tests or not 7) Load each >> pack= >>> age in a PharoCore image without having to install anything else (all the >> d= >>> ependencies should be managed automatically) >>> >>> 8) You can take a PharoCore image and "transform" it to a Dev >> ima= >>> ge, or even web. 9) Others... This is not completed yet. There >> a= >>> re 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 >> Configura= >>> tion classes b) The dependencies >>> c)=A0 the groups, In summary, most of the "structure" >> and = >>> static information. However, I am not sure which version to load of each >> pa= >>> ckage. 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. >> Yo= >>> u 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 >> probab= >>> ly understand it. However, you can read the Metacello tutorial (no more >> tha= >>> n one hour), or ask me or even more in the Metacello mailing list. >> So...PLE= >>> ASE, I need the help of the maintainers to create the versions. So far, I >> c= >>> reated the first version (1.0) with the latest version. But the idea is >> tha= >>> t then you create 1.1.1 or 1.2 or whatever you consider. >>> All the configurations can be found in <a href=3D" >> http://www.squeaksour= >>> ce.com/MetacelloRepository"> >> http://www.squeaksource.com/MetacelloRepository= >>> </a> So far, I created:=A0 ConfigurationOfNewInspector, >> Configuratio= >>> nOfOCompletion, ConfigurationOfOmniBrowser, >> ConfigurationOfPharoMorphicExtr= >>> as, ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, >> Configura= >>> tionOfShout , and......ConfigurationOfPharo!!! >>> To install them, just download that package and evaluate the load. >> Exam= >>> ple: Gofer new =A0=A0=A0 squeaksource: >> 'MetacelloRepository&#= >>> 39;; =A0=A0=A0 package: 'ConfigurationOfShout'; =A0=A0=A0 >> loa= >>> d. ((Smalltalk at: #ConfigurationOfShout) project version: >> '1.0&= >>> #39;) load. >>> And then, you can also for exaple do:=A0 >>> ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') >> load= >>> : 'Core'=A0 this doesn't install the tests. Or >> for = >>> example:=A0 (ConfigurationOfOmniBrowser project version: '1.0') >> loa= >>> d: '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 >> depende= >>> ncies or whatever. >>> I really wait your feedback. Mariano ps:=A0 I will >> relea= >>> se 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 >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > <div class=3D"gmail_quote">On Fri, Jan 8, 2010 at 1:12 PM, Esteban = > Lorenzano <<a > href=3D"mailto:estebanlm@gmail.com">este= > banlm(a)gmail.com</a>> > wrote: <blockquote class=3D"gmail_quote" = > style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8= > ex; padding-left: 1ex;"> > btw, ConfigurationOfPharo shouldn't be ConfigurationOfPharoDev? > </blockquote><div> No. For that we have the groups. The same Configu= > rationOfPharo will be used for differents stuff: ConfigurationOfPhar= > o project version: 'xxx' load: 'StandardPharoDev' > or ConfigurationOfPharo project version: 'xxx' load: 'St= > andardPharoWeb '=A0=A0 (if they came back) or Configurat= > ionOfPharo project version: 'xxx' load: 'SOMETHING'=A0 (if = > they came back) > > Cheers Mariano > =A0</div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px so= > lid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> > On 2010-01-07 17:54:27 -0300, Mariano Martinez Peck > <div><div></div><div class=3D"h5"><<a href=3D"mailto:marianopeck@gmail.c= > om">marianopeck(a)gmail.com</a>> said: > > > > > > > (Sorry for the long email) > > > > Yes, after a couple of weeks, I have written most of the needed Metace= > llo > > 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 an= > ything > > else (all the dependencies should be managed automatically) > > 8) You can take a PharoCore image and "transform" it to a De= > v image, or even > > web. > > 9) Others... > > > > This is not completed yet. There are some things that we are discussin= > g 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) =A0the 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 c= > are of > > building the Dev images, but I won't: > > > > - Merge anything. It will not be my task to merge OB, or RB or whateve= > r. > > - 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<br= >> > > maintainer of the packages that we load of a PharoDev image, help us t= > o > > create the stable versions. To create a new version for the Metacello<= > br> > > configuration is VERY easy, The hard part is already done. You just ha= > ve 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 t= > han > > 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 th= > e idea > > is that then you create 1.1.1 or 1.2 or whatever you consider. > > > > All the configurations can be found in > > <a href=3D"http://www.squeaksource.com/MetacelloRepository" target=3D"= > _blank">http://www.squeaksource.com/MetacelloRepository</a> > > > > So far, I created: =A0ConfigurationOfNewInspector, ConfigurationOfOCom= > pletion, > > ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphicExtras, > > ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, > > ConfigurationOfShout , and......ConfigurationOfPharo!!! > > > > To install them, just download that package and evaluate the load. Exa= > mple: > > > > Gofer new > > =A0 =A0 squeaksource: 'MetacelloRepository'; > > =A0 =A0 package: 'ConfigurationOfShout'; > > =A0 =A0 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: =A0(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 c= > ode, > > load the different groups and give me feedback on the dependencies or<= > br> > > whatever. > > > > I really wait your feedback. > > > > Mariano > > > > ps: =A0I will release soon the first dev image using this :) > > > > > </div></div>> (Sorry for the long email) Yes, after a= > couple of weeks, I have writ=3D > > ten most of the needed Metacello configurations for the Dev images 1.0= > . For=3D > > get 1.1 for a while. Now we are able to: 1) Load st= > able version of p=3D > > ackages > > 2) Manage the dependencies automatically 3) Each developer ca= > n create it=3D > > s custom PharoDev image > > 4) Flexibility to load the packages you want 5) Choose the br= > owser for e=3D > > xample: OB or O2 6) Choose to load the tests or not = > 7) Load each pack=3D > > age in a PharoCore image without having to install anything else (all = > the d=3D > > ependencies should be managed automatically) > > > > 8) You can take a PharoCore image and &quot;transform&quot; it= > to a Dev ima=3D > > ge, or even web. 9) Others... This is not= > completed yet. There a=3D > <div class=3D"im">> re some things that we are discussing with Dale, but= > they are ok as a first=3D > </div>> =A0step. I rather go step by step. > > What I did is to create all the infrastructure: &lt= > ;br>a) The Configura=3D > > tion classes b) The dependencies > > c)=3DA0 the groups, In summary, most of the &qu= > ot;structure&quot; and =3D > > static information. However, I am not sure which version to load of ea= > ch pa=3D > > ckage. I will probable take care of building the Dev images, but I won= > &#39;=3D > > t: > > > > - Merge anything. It will not be my task to merge OB, or RB = > or whatever=3D > > . - Check every version of each package before doing a releas= > e to see if=3D > > =A0it is stable or not. So...what I REALLY (actuall= > y, WE) need is that=3D > <div class=3D"im">> =A0each developer, each maintainer of the packages t= > hat we load of a PharoDev=3D > > =A0image, help us to create the stable versions. To create a new versi= > on for =3D > </div>> the Metacello configuration is VERY easy, The hard part is alrea= > dy done. Yo=3D > <div class=3D"im">> u just have to create a method and say which version= > s (except you create or=3D > </div>> =A0eliminate packages or dependencies). If you read the code, yo= > u will probab=3D > > ly understand it. However, you can read the Metacello tutorial (no mor= > e tha=3D > > n one hour), or ask me or even more in the Metacello mailing list. So.= > ..PLE=3D > > ASE, I need the help of the maintainers to create the versions. So far= > , I c=3D > > reated the first version (1.0) with the latest version. But the idea i= > s tha=3D > > t then you create 1.1.1 or 1.2 or whatever you consider. > > All the configurations can be found in <a href=3D3D"= > <a href=3D"http://www.squeaksour" target=3D"_blank">http://www.squeaksour</= > a>=3D > > <a href=3D"http://ce.com/MetacelloRepository" target=3D"_blank">ce.com= > /MetacelloRepository</a>"><a href=3D"http://www.squeaksource.com/Me= > tacelloRepository=3D" target=3D"_blank">http://www.squeaksource.com/Metacel= > loRepository=3D</a> > > > </a> So far, I created:=3DA0 ConfigurationOfN= > ewInspector, Configuratio=3D > > nOfOCompletion, ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphi= > cExtr=3D > > as, ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, Conf= > igura=3D > > tionOfShout , and......ConfigurationOfPharo!!! > > To install them, just download that package and evaluate the= > load. Exam=3D > > ple: Gofer new =3DA0=3DA0=3DA0 squeaksourc= > e: &#39;MetacelloRepository&#=3D > > 39;; =3DA0=3DA0=3DA0 package: &#39;ConfigurationOfShout&a= > mp;#39;; =3DA0=3DA0=3DA0 loa=3D > > d. ((Smalltalk at: #ConfigurationOfShout) project v= > ersion: &#39;1.0&=3D > > #39;) load. > > And then, you can also for exaple do:=3DA0 <br&= > gt; > > ((Smalltalk at: #ConfigurationOfShout) project version: &#39;1.0&a= > mp;#39;) load=3D > > : &#39;Core&#39;=3DA0 this doesn&#39;t install t= > he tests. Or for =3D > > example:=3DA0 (ConfigurationOfOmniBrowser project version: &#39;1.= > 0&#39;) loa=3D > > d: &#39;Dev&#39; > > etc... So, you can load any project and w= > ith the group you want.=3D > <div class=3D"im">> =A0All of that can be (or should be hahahaha) perfec= > tly loaded in a 1.0 Core =3D > </div>> image. What I would really appreciate is if e= > ach maintainer can look=3D > > =A0at the code, load the different groups and give me feedback on the = > depende=3D > > ncies or whatever. > > I really wait your feedback. Mariano<= > br> ps:=3DA0 I will relea=3D > > se soon the first dev image using this :) > > > <div><div></div><div class=3D"h5">> > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > <a > href=3D"mailto:Pharo-project@lists.gforge.inria.fr">Pharo-project@l= ists.gforge.inria.fr</a> > > > <a href=3D"http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo= > -project" target=3D"_blank">http://lists.gforge.inria.fr/cgi-bin/mailman/li= > stinfo/pharo-project</a> > > > > > _______________________________________________ > Pharo-project mailing list > <a > href=3D"mailto:Pharo-project@lists.gforge.inria.fr">Pharo-project(a)lists.= gforge.inria.fr</a> <a > > href=3D"http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-proj= > ect" target=3D"_blank">http://lists.gforge.inria.fr/cgi-bin/mailman/listinf= > o/pharo-project</a> > </div></div></blockquote></div> > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 8, 2010

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

by Esteban Lorenzano

Hi, And what info do you think it should answer? On 2010-01-08 09:39:31 -0300, Alexandre Bergel <alexandre(a)bergel.eu> said: > Esteban, this is excellent!! > It would be cool to have > > Loader new infoAbout:

Jan. 8, 2010

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

by Alexandre Bergel

Thanks for your comments. I renamed the announcement accordingly to your comments. I attached a screenshot of the new hierarchy Better? Alexandre On 8 Jan 2010, at 08:57, Henrik Johansen wrote: > On Jan 8, 2010, at 11:56 18AM, Gary Chambers wrote: > >> Looks ok to me. >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Thursday, January 07, 2010 8:27 PM >> Subject: Re: [Pharo-project] Notifications of windows opening/ >> closing/focus >> >> >>> >>>> 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]. > I don't particularly like the naming. > > - Why including Announcement at the end? > - Why does one contain a verb, and the other a > - When are they fired? Closing implies to me it's not been closed > yet, but fired somewhere after the closing has started, while > CreationWindow I have no idea what means. > > MorphicWindowOpen(ed/ing) > MorphicWindowClos(ed/ing) > > are both easier to read for me, shorter, and more in line with the > naming convention for Pragma announcements already in Pharo. > > Cheers, > Henry > _______________________________________________ > 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. 8, 2010

Re: [Pharo-project] Nanosecond-level profiling in Pharo?

by Alexandre Bergel

Thanks for all your answers. cheers, Alexandre On 8 Jan 2010, at 01:22, John McIntosh wrote: > I think Eliot wanted those in my vm work I think qwaq has them > time to add them I think > > should it return a Long integer or a double > > On 1/7/10, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Some times I wanted smaller grain for running tests... but most of >> the >> time millis are good enough :) >> >> On 2010-01-07 18:52:16 -0300, Alexandre Bergel >> <alexandre(a)bergel.eu> said: >> >>> Hi! >>> >>> I am currently working on a new profiler for Pharo. The idea is to >>> graphically renders a profiling using Mondrian. I hope to release it >>> soon. >>> When discussing with an expert in the field (Walter Binder), the >>> question about time grain was raised. I am partly based on >>> MessageTally, which has a millisecond grain. Anyone is aware of a >>> finer grain? At the level of nanosecond? Does it makes sense since >>> there is no JIT (yet)? >>> >>> Cheers, >>> Alexandre >> >> >> >> >> _______________________________________________ >> 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> > Corporate Smalltalk Consulting Ltd. http:// > www.smalltalkconsulting.com > = > = > = > = > = > ====================================================================== > > _______________________________________________ > 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. 8, 2010

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

by Mariano Martinez Peck

On Fri, Jan 8, 2010 at 1:12 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > btw, ConfigurationOfPharo shouldn't be ConfigurationOfPharoDev? > > No. For that we have the groups. The same ConfigurationOfPharo will be used for differents stuff: ConfigurationOfPharo project version: 'xxx' load: 'StandardPharoDev' or ConfigurationOfPharo project version: 'xxx' load: 'StandardPharoWeb ' (if they came back) or ConfigurationOfPharo project version: 'xxx' load: 'SOMETHING' (if they came back) Cheers Mariano > On 2010-01-07 17:54:27 -0300, Mariano Martinez Peck > <marianopeck(a)gmail.com> said: > > > > > > > (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 :) > > > > > > (Sorry for the long email) Yes, after a couple of weeks, I have > writ= > > ten most of the needed Metacello configurations for the Dev images 1.0. > For= > > get 1.1 for a while. Now we are able to: 1) Load stable version of > p= > > ackages > > 2) Manage the dependencies automatically 3) Each developer can create > it= > > s custom PharoDev image > > 4) Flexibility to load the packages you want 5) Choose the browser for > e= > > xample: OB or O2 6) Choose to load the tests or not 7) Load each > pack= > > age in a PharoCore image without having to install anything else (all the > d= > > ependencies should be managed automatically) > > > > 8) You can take a PharoCore image and "transform" it to a Dev > ima= > > ge, or even web. 9) Others... This is not completed yet. There > a= > > re 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 > Configura= > > tion classes b) The dependencies > > c)=A0 the groups, In summary, most of the "structure" > and = > > static information. However, I am not sure which version to load of each > pa= > > ckage. 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. > Yo= > > u 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 > probab= > > ly understand it. However, you can read the Metacello tutorial (no more > tha= > > n one hour), or ask me or even more in the Metacello mailing list. > So...PLE= > > ASE, I need the help of the maintainers to create the versions. So far, I > c= > > reated the first version (1.0) with the latest version. But the idea is > tha= > > t then you create 1.1.1 or 1.2 or whatever you consider. > > All the configurations can be found in <a href=3D" > http://www.squeaksour= > > ce.com/MetacelloRepository"> > http://www.squeaksource.com/MetacelloRepository= > > </a> So far, I created:=A0 ConfigurationOfNewInspector, > Configuratio= > > nOfOCompletion, ConfigurationOfOmniBrowser, > ConfigurationOfPharoMorphicExtr= > > as, ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, > Configura= > > tionOfShout , and......ConfigurationOfPharo!!! > > To install them, just download that package and evaluate the load. > Exam= > > ple: Gofer new =A0=A0=A0 squeaksource: > 'MetacelloRepository&#= > > 39;; =A0=A0=A0 package: 'ConfigurationOfShout'; =A0=A0=A0 > loa= > > d. ((Smalltalk at: #ConfigurationOfShout) project version: > '1.0&= > > #39;) load. > > And then, you can also for exaple do:=A0 > > ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') > load= > > : 'Core'=A0 this doesn't install the tests. Or > for = > > example:=A0 (ConfigurationOfOmniBrowser project version: '1.0') > loa= > > d: '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 > depende= > > ncies or whatever. > > I really wait your feedback. Mariano ps:=A0 I will > relea= > > se 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 > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 8, 2010

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

by Alexandre Bergel

> How about something like the following expressions: I feel the notion of Configuration unnecessary. > Gofer loadConfiguration: 'Pharo' version: '1.0-rc2.10505'. Gofer load: 'Pharo' version: '1.0-rc2.10505'. is shorter > Gofer loadConfiguration: 'NewInspector'. Gofer load: 'NewInspector' > Gofer loadConfiguration: 'Magritte' load: #( 'Magritte-Model' > 'Magritte-Tests' ). Gofer forProject: 'Magritte' loadClassCategories: #( 'Magritte-Model' 'Magritte-Tests' ). > Gofer loadConfiguration: 'OmniBrowser' version: '1.0' load: 'Core'. Gofer forProject: 'OmniBrowser' loadConfiguration: 'Core' version: '1.0' > In all cases it is expected that the configuration will be found in > the MetacelloRepository on SqueakSource... Shall I move ConfigurationOfMondrian from Mondrian to MetacelloRepository? I have no problem in doing so. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 8, 2010