September 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] how to improve the menus

by Lukas Renggli

> So who is responsible for the menus in OB? The menus in the columns come from OB. The menu in the edit pane comes from Squeak though and certain commands are intercepted by OB. I think it would make sense if OB changed that and provided the whole menu by itself. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Sept. 12, 2008

Re: [Pharo-project] Re: how to load sophie

by Michael Rueger

Andrew Tween wrote: > If you don't want to install it all from scratch then... which takes a patched 3.8/Tweak image and about 90 minutes... > If you download Sophie from www.sophieproject.org > (http://www.sophieproject.org/download) > and run it, then the File>>Exit menu item will close the Sophie > application but leave the Squeak image running so you can open browsers You beat me to it :-) Michael

Sept. 12, 2008

[Pharo-project] Re: how to load sophie

by Andrew Tween

"StÃ©phane Ducasse" <Stephane.Ducasse(a)inria.fr> wrote in message news:7916FF5C-0CA0-4562-A69F-65B4B54C8067@inria.fr... > Hi mike > > I would like to browse the code but not only from MC but in a real image. > How do I get sophie loaded (even in 3.8 or others). > In particular I would like to see how URI are used in the code. If you don't want to install it all from scratch then... If you download Sophie from www.sophieproject.org (http://www.sophieproject.org/download) and run it, then the File>>Exit menu item will close the Sophie application but leave the Squeak image running so you can open browsers etc. Cheers, Andy > > Setf

Sept. 12, 2008

[Pharo-project] how to load sophie

by StÃ©phane Ducasse

Hi mike I would like to browse the code but not only from MC but in a real image. How do I get sophie loaded (even in 3.8 or others). In particular I would like to see how URI are used in the code. Setf

Sept. 12, 2008

[Pharo-project] show bytecode menu -> DNU

by StÃ©phane Ducasse

Hi if one of you could have a look at the menu item show bytecode. Stef

Sept. 12, 2008

Re: [Pharo-project] About fixes for noury and other

by StÃ©phane Ducasse

Noury I harvested your classBuilder fixes. For the MC related ones, could you package them separately and in a way that merge is working well Then post them in the bugtracking and that we can ask lukas or adrian to have a look? Tx > StÃ©f, > > On 11 sept. 08, at 21:32, Noury Bouraqadi wrote: > >> On 11 sept. 08, at 09:44, StÃ©phane Ducasse wrote: >> >>> Hi noury >>> >>> I started to harvest your fixes and I learned something :) >>> when most of your fixes are about extending or changing a package >>> just publish a new version of that package. This way I can use the >>> merge tool >>> and be much more efficient, do not create a specific package with >>> specific class extension >>> for it else I have to modify everything by hand. >>> >> This sounds like a cleaner way indeed. >> If you didn't finish harvesting it, I can split different changes >> as you suggest. >> > Did you harvested my previous fixes ? > Cause I added an extra bug fix (attached) to the class builder to > avoid the creation of "zombie" classes (classes not in the > SystemDictionary => Memory leak) when class variable names are > lowercase. The test > > BTW, where one can check to see if a package has been harvested? > > Noury > ------------------------------------------------------------------ > Dr. Noury Bouraqadi - Enseignant/Chercheur > Responsable de l'enseignement de l'informatique > ARMINES - Ecole des Mines de Douai - Dept. I.A. > http://vst.ensm-douai.fr/noury > > European Smalltalk Users Group Board > http://www.esug.org > ------------------------------------------------------------------ > > <fixClassVarsVarlidation-Noury12sept2008.cs> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 12, 2008

Re: [Pharo-project] About fixes for noury and other

by Noury Bouraqadi

I sent the wrong version of the changeset in my previous email. Attached the right one. Noury On 12 sept. 08, at 19:18, Noury Bouraqadi wrote: > StÃ©f, > > On 11 sept. 08, at 21:32, Noury Bouraqadi wrote: > >> On 11 sept. 08, at 09:44, StÃ©phane Ducasse wrote: >> >>> Hi noury >>> >>> I started to harvest your fixes and I learned something :) >>> when most of your fixes are about extending or changing a package >>> just publish a new version of that package. This way I can use the >>> merge tool >>> and be much more efficient, do not create a specific package with >>> specific class extension >>> for it else I have to modify everything by hand. >>> >> This sounds like a cleaner way indeed. >> If you didn't finish harvesting it, I can split different changes >> as you suggest. >> > Did you harvested my previous fixes ? > Cause I added an extra bug fix (attached) to the class builder to > avoid the creation of "zombie" classes (classes not in the > SystemDictionary => Memory leak) when class variable names are > lowercase. The test > > BTW, where one can check to see if a package has been harvested? > > Noury > ------------------------------------------------------------------ > Dr. Noury Bouraqadi - Enseignant/Chercheur > Responsable de l'enseignement de l'informatique > ARMINES - Ecole des Mines de Douai - Dept. I.A. > http://vst.ensm-douai.fr/noury > > European Smalltalk Users Group Board > http://www.esug.org > ------------------------------------------------------------------ > > <fixClassVarsVarlidation-Noury12sept2008.cs> Noury Bouraqadi ------------------------------------------------------------------ Dr. Noury Bouraqadi - Enseignant/Chercheur Responsable de l'enseignement de l'informatique ARMINES - Ecole des Mines de Douai - Dept. I.A. http://vst.ensm-douai.fr/noury European Smalltalk Users Group Board http://www.esug.org ------------------------------------------------------------------

Sept. 12, 2008

Re: [Pharo-project] About fixes for noury and other

by StÃ©phane Ducasse

Normally when you enter a bug fix in the issue I will close it when it is harvested/refused.... I will do the classbuilder related ones now. Stef On Sep 12, 2008, at 7:18 PM, Noury Bouraqadi wrote: > StÃ©f, > > On 11 sept. 08, at 21:32, Noury Bouraqadi wrote: > >> On 11 sept. 08, at 09:44, StÃ©phane Ducasse wrote: >> >>> Hi noury >>> >>> I started to harvest your fixes and I learned something :) >>> when most of your fixes are about extending or changing a package >>> just publish a new version of that package. This way I can use the >>> merge tool >>> and be much more efficient, do not create a specific package with >>> specific class extension >>> for it else I have to modify everything by hand. >>> >> This sounds like a cleaner way indeed. >> If you didn't finish harvesting it, I can split different changes >> as you suggest. >> > Did you harvested my previous fixes ? > Cause I added an extra bug fix (attached) to the class builder to > avoid the creation of "zombie" classes (classes not in the > SystemDictionary => Memory leak) when class variable names are > lowercase. The test > > BTW, where one can check to see if a package has been harvested? > > Noury > ------------------------------------------------------------------ > Dr. Noury Bouraqadi - Enseignant/Chercheur > Responsable de l'enseignement de l'informatique > ARMINES - Ecole des Mines de Douai - Dept. I.A. > http://vst.ensm-douai.fr/noury > > European Smalltalk Users Group Board > http://www.esug.org > ------------------------------------------------------------------ > > <fixClassVarsVarlidation-Noury12sept2008.cs> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 12, 2008

Re: [Pharo-project] About fixes for noury and other

by Noury Bouraqadi

StÃ©f, On 11 sept. 08, at 21:32, Noury Bouraqadi wrote: > On 11 sept. 08, at 09:44, StÃ©phane Ducasse wrote: > >> Hi noury >> >> I started to harvest your fixes and I learned something :) >> when most of your fixes are about extending or changing a package >> just publish a new version of that package. This way I can use the >> merge tool >> and be much more efficient, do not create a specific package with >> specific class extension >> for it else I have to modify everything by hand. >> > This sounds like a cleaner way indeed. > If you didn't finish harvesting it, I can split different changes as > you suggest. > Did you harvested my previous fixes ? Cause I added an extra bug fix (attached) to the class builder to avoid the creation of "zombie" classes (classes not in the SystemDictionary => Memory leak) when class variable names are lowercase. The test BTW, where one can check to see if a package has been harvested? Noury ------------------------------------------------------------------ Dr. Noury Bouraqadi - Enseignant/Chercheur Responsable de l'enseignement de l'informatique ARMINES - Ecole des Mines de Douai - Dept. I.A. http://vst.ensm-douai.fr/noury European Smalltalk Users Group Board http://www.esug.org ------------------------------------------------------------------

Sept. 12, 2008

[Pharo-project] removing the DockingBar and TheWorldMainDockingBar

by StÃ©phane Ducasse

Hi all I was ready to remove the novice mode and I think that we should remove DockingBar and TheWorldMainDockingBar Now gary it may introduce conflicts with etoy removal. What do you think? When will you send us the etoy removal? Stef

Sept. 12, 2008