October 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 2.0] #20348

by Esteban Lorenzano

20348 ----- Issue 6761: Class side Trait methods don't work in Nautilus http://code.google.com/p/pharo/issues/detail?id=6761 Issue 6831: unload monticello package breaks RPackage http://code.google.com/p/pharo/issues/detail?id=6831 Issue 6539: Integrate Metacello http://code.google.com/p/pharo/issues/detail?id=6539 Diff information: http://ss3.gemstone.com/ss/Pharo20/Ring-Core-Kernel-EstebanLorenzano.80.diff http://ss3.gemstone.com/ss/Pharo20/NautilusCommon-EstebanLorenzano.95.diff http://ss3.gemstone.com/ss/Pharo20/Nautilus-EstebanLorenzano.368.diff http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.724.diff

Oct. 17, 2012

Re: [Pharo-project] what is your pharo story?

by sebastian＠flowingconcept.com

hahaha XD great stuff dynamic vs. static isn't an issue anymore dynamic won hands down already and years ago the thing now is to expand people's vision of what can be done with it and these are good points (to talk to engineers) the audience has other people too so I need more stories from the trenches :) sebastian o/ ----- Original Message ----- From: "Torsten Bergmann" <astares(a)gmx.de> To: pharo-project(a)lists.gforge.inria.fr Sent: Wednesday, October 17, 2012 11:19:26 AM Subject: [Pharo-project] what is your pharo story? Pick one ... STORY 1: ======== What I like most is that I do not rely on IDE vendors or tools to do measure things like: TestCase allSubclasses size inspect things like: Account allInstances collect: [:each | each value > 10 ] or script my environment: TestCase allSubclasses do: [:each | each removeFromSystem ] Try all this in any of the other "static" environments. And yes - one can shoot itself in the foot: true become: false but I like the freedom. STORY 2: ======= In any program environment you have to use a debugger. In Smalltalk you can just save the image and continue the next work day on exactly the same point you left. In other environments you usually close the IDE in the evening and start to debug the program the next day again until you are at this point, have the stack and variables in the same state. Lots of wasted time and developer resources in static world... STORY 3: ======== "Rethinking the typing" as you can see http://astares.blogspot.de/2006/08/rethinking-typing.html STORY 4: ======== When I tell people that Smalltalk is not a language - just a dynamic object system with a language built on top of it. A method, a class ... anything is an object. So if you need additions you just implement them without waiting for the next language spec or vendors. Need traits, interfaces, namespaces, ... just add them. Embed other languages: just add them (see Helvetica) http://astares.blogspot.de/2009/11/helvetia-embedding-languages.html) New control structures? Just implement them. An example: Pascal hat a REPEAT UNTIL. C/C++/Java language family and Smalltalk does not have such a construct. The difference: in Smalltalk I can just add a new method #repeatUntil: to BlockClosure if I really need it. STORY X: ======== ...

Oct. 17, 2012

Re: [Pharo-project] Progress bar in 2.0

by Esteban Lorenzano

it is supposed to be closable... but in case the update is not modal. in case the update is modal, I also would like to have it centered (since we cannot do anything else anyway) and btw... we should think on a unique place/area of the window to show notifications... showing at any point that looks cool can quickly guide us into a messy UI (well... a "more messy" UI) Esteban On Oct 17, 2012, at 4:27 PM, "Torsten Bergmann" <astares(a)gmx.de> wrote: > Why do we need this icon on the updater > progress bar? IMHO it looks awfull and we > should remove it. > > Thx > T. >

Oct. 17, 2012

Re: [Pharo-project] Progress bar in 2.0

by Camillo Bruni

click on it and you'll know. Now you can interrupt any background process and either kill/debug it. awfull is very subjective, it might not have the right size right now, but it's highly usefull. we still need to properly run the progress in a separate ui thread to enable proper interaction. On 2012-10-17, at 16:27, "Torsten Bergmann" <astares(a)gmx.de> wrote: > Why do we need this icon on the updater > progress bar? IMHO it looks awfull and we > should remove it. > > Thx > T. >

Oct. 17, 2012

[Pharo-project] Progress bar in 2.0

by Torsten Bergmann

Why do we need this icon on the updater progress bar? IMHO it looks awfull and we should remove it. Thx T.

Oct. 17, 2012

Re: [Pharo-project] RPackage by-hand code

by Goubier Thierry

Le 17/10/2012 16:08, Esteban Lorenzano a Ã©crit : > can I have your image to explore? > (if there are some "private" code, I can sign whatever confidentiality agreement you want :P) I have two images: a brand new 20346 image with a minimum of packages loaded (the one just before RPackageOrganizer initialize), and the one where I saw the problem in the first place. There is nothing private in there; all the packages are on ss3. The simpler is probably the new one (it's also a bit smaller). Thierry > Esteban > > On Oct 17, 2012, at 3:56 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> Le 17/10/2012 14:16, Esteban Lorenzano a Ã©crit : >>> I also would like to collect how your methods were missing... it is reproducible? >> >> It's even worse than I thought. I'm now loosing the code in three packages when I do >> >> RPackageOrganize initialize >> >> They just don't appear at all in Nautilus; as if they didn't exist. >> >> Thierry >> >>> Esteban >>> >>> On Oct 17, 2012, at 1:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> is there an MCWorkingCopy of your code package? >>>> >>>> MCWorkingCopy allManagers. >>>> >>>> and a package info? >>>> >>>> PackageIngo allPackages. >>>> >>>> Esteban >>>> >>>> On Oct 17, 2012, at 1:56 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >>>> >>>>> Le 17/10/2012 13:49, Esteban Lorenzano a Ã©crit : >>>>>> Hi, >>>>>> >>>>>> RPackageOrganizer initialize. >>>>>> >>>>>> should do it. >>>>>> >>>>>> Esteban >>>>> >>>>> It doesn't. >>>>> >>>>> Trust me, I tried. Multiple times :( >>>>> >>>>> Thierry >>>>> >>>>>> On Oct 17, 2012, at 1:41 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I have a problem in Pharo 2.0, among the recent updates, RPackage lost most of the code in one of my packages. Would someone know how to write a small script to force a reload in RPackage of a Smalltalk Category ? >>>>>>> >>>>>>> The code is still there, in the right system category, but neither Nautilus nor Monticello sees it, and I'm afraid of doing anything like saving the package which would erase most of what is in it. >>>>>>> >>>>>>> My Pharo version is 20346. >>>>>>> >>>>>>> Thanks in advance, >>>>>>> >>>>>>> Thierry >>>>>>> -- >>>>>>> Thierry Goubier >>>>>>> CEA list >>>>>>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>>>>>> 91191 Gif sur Yvette Cedex >>>>>>> France >>>>>>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Thierry Goubier >>>>> CEA list >>>>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>>>> 91191 Gif sur Yvette Cedex >>>>> France >>>>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>>>> >>>> >>> >>> >>> >> >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> > > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Oct. 17, 2012

[Pharo-project] what is your pharo story?

by Torsten Bergmann

Pick one ... STORY 1: ======== What I like most is that I do not rely on IDE vendors or tools to do measure things like: TestCase allSubclasses size inspect things like: Account allInstances collect: [:each | each value > 10 ] or script my environment: TestCase allSubclasses do: [:each | each removeFromSystem ] Try all this in any of the other "static" environments. And yes - one can shoot itself in the foot: true become: false but I like the freedom. STORY 2: ======= In any program environment you have to use a debugger. In Smalltalk you can just save the image and continue the next work day on exactly the same point you left. In other environments you usually close the IDE in the evening and start to debug the program the next day again until you are at this point, have the stack and variables in the same state. Lots of wasted time and developer resources in static world... STORY 3: ======== "Rethinking the typing" as you can see http://astares.blogspot.de/2006/08/rethinking-typing.html STORY 4: ======== When I tell people that Smalltalk is not a language - just a dynamic object system with a language built on top of it. A method, a class ... anything is an object. So if you need additions you just implement them without waiting for the next language spec or vendors. Need traits, interfaces, namespaces, ... just add them. Embed other languages: just add them (see Helvetica) http://astares.blogspot.de/2009/11/helvetia-embedding-languages.html) New control structures? Just implement them. An example: Pascal hat a REPEAT UNTIL. C/C++/Java language family and Smalltalk does not have such a construct. The difference: in Smalltalk I can just add a new method #repeatUntil: to BlockClosure if I really need it. STORY X: ======== ...

Oct. 17, 2012

Re: [Pharo-project] RPackage by-hand code

by Esteban Lorenzano

can I have your image to explore? (if there are some "private" code, I can sign whatever confidentiality agreement you want :P) Esteban On Oct 17, 2012, at 3:56 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Le 17/10/2012 14:16, Esteban Lorenzano a Ã©crit : >> I also would like to collect how your methods were missing... it is reproducible? > > It's even worse than I thought. I'm now loosing the code in three packages when I do > > RPackageOrganize initialize > > They just don't appear at all in Nautilus; as if they didn't exist. > > Thierry > >> Esteban >> >> On Oct 17, 2012, at 1:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> is there an MCWorkingCopy of your code package? >>> >>> MCWorkingCopy allManagers. >>> >>> and a package info? >>> >>> PackageIngo allPackages. >>> >>> Esteban >>> >>> On Oct 17, 2012, at 1:56 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >>> >>>> Le 17/10/2012 13:49, Esteban Lorenzano a Ã©crit : >>>>> Hi, >>>>> >>>>> RPackageOrganizer initialize. >>>>> >>>>> should do it. >>>>> >>>>> Esteban >>>> >>>> It doesn't. >>>> >>>> Trust me, I tried. Multiple times :( >>>> >>>> Thierry >>>> >>>>> On Oct 17, 2012, at 1:41 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I have a problem in Pharo 2.0, among the recent updates, RPackage lost most of the code in one of my packages. Would someone know how to write a small script to force a reload in RPackage of a Smalltalk Category ? >>>>>> >>>>>> The code is still there, in the right system category, but neither Nautilus nor Monticello sees it, and I'm afraid of doing anything like saving the package which would erase most of what is in it. >>>>>> >>>>>> My Pharo version is 20346. >>>>>> >>>>>> Thanks in advance, >>>>>> >>>>>> Thierry >>>>>> -- >>>>>> Thierry Goubier >>>>>> CEA list >>>>>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>>>>> 91191 Gif sur Yvette Cedex >>>>>> France >>>>>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Thierry Goubier >>>> CEA list >>>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>>> 91191 Gif sur Yvette Cedex >>>> France >>>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>>> >>> >> >> >> > > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Oct. 17, 2012

Re: [Pharo-project] RPackage by-hand code

by Goubier Thierry

Le 17/10/2012 14:16, Esteban Lorenzano a Ã©crit : > I also would like to collect how your methods were missing... it is reproducible? It's even worse than I thought. I'm now loosing the code in three packages when I do RPackageOrganize initialize They just don't appear at all in Nautilus; as if they didn't exist. Thierry > Esteban > > On Oct 17, 2012, at 1:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> is there an MCWorkingCopy of your code package? >> >> MCWorkingCopy allManagers. >> >> and a package info? >> >> PackageIngo allPackages. >> >> Esteban >> >> On Oct 17, 2012, at 1:56 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> >>> Le 17/10/2012 13:49, Esteban Lorenzano a Ã©crit : >>>> Hi, >>>> >>>> RPackageOrganizer initialize. >>>> >>>> should do it. >>>> >>>> Esteban >>> >>> It doesn't. >>> >>> Trust me, I tried. Multiple times :( >>> >>> Thierry >>> >>>> On Oct 17, 2012, at 1:41 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >>>> >>>>> Hi, >>>>> >>>>> I have a problem in Pharo 2.0, among the recent updates, RPackage lost most of the code in one of my packages. Would someone know how to write a small script to force a reload in RPackage of a Smalltalk Category ? >>>>> >>>>> The code is still there, in the right system category, but neither Nautilus nor Monticello sees it, and I'm afraid of doing anything like saving the package which would erase most of what is in it. >>>>> >>>>> My Pharo version is 20346. >>>>> >>>>> Thanks in advance, >>>>> >>>>> Thierry >>>>> -- >>>>> Thierry Goubier >>>>> CEA list >>>>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>>>> 91191 Gif sur Yvette Cedex >>>>> France >>>>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> Thierry Goubier >>> CEA list >>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>> 91191 Gif sur Yvette Cedex >>> France >>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>> >> > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Oct. 17, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 418 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 17, 2012