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

Re: [Pharo-project] [update 2.0] #20162

by Marcus Denker

On Jun 26, 2012, at 9:25 PM, StÃ©phane Ducasse wrote: > strnage I did not find it on jenkins. Jenks stopped to build automatically after we do an update. (we need a jenkis bug tracker...) > When I updated from 57 i got problems (may be my image was shaky). > > On Jun 26, 2012, at 8:40 PM, Marcus Denker wrote: > >> 20162 >> ----- >> >> Issue 6157: remove dead lmmplugin code >> http://code.google.com/p/pharo/issues/detail?id=6157 >> >> Issue 6161: Finder: Change Pattern back to Examples >> http://code.google.com/p/pharo/issues/detail?id=6161 >> >> Issue 6168: Changeset>>#superclassOrder: should be only used by ChangeSet related objects >> http://code.google.com/p/pharo/issues/detail?id=6168 >> >> >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> > > -- Marcus Denker -- http://marcusdenker.de

June 26, 2012

Re: [Pharo-project] Pharo and Namespaces

by James Foster

On Jun 26, 2012, at 11:19 AM, StÃ©phane Ducasse wrote: >>>> What happened to the project from GermÃ¡n Leiva >>>> http://www.youtube.com/watch?v=n4I7fSVNX2A >>> >>> we do not want class level namespace because this is the mess >> >> As the sponsor for GermÃ¡n's project, I have some interest in this topic. StÃ©phane has said a couple times that it is wrong but has never taken time to explain his objections. > > We do not want to have class name resolution at the granularity of a class. And are you saying this because you think GermÃ¡n's implementation does this? > Why because it means that in the same package reading the code containing a class Foo could be a different one. I don't understand your example. I don't know what you mean by "package reading the code." Are you describing a package that defines classes Foo and Bar, and a method in a class Bar that references the Foo in the same package? Are you providing this example because you think GermÃ¡n's implementation does not support this use case? > I'm saying that since years. I agree you have been saying that GermÃ¡n's implementation isn't what you want. I just don't understand what you don't like about it. Name resolution of all variables (including Globals, of which Classes are a subset) should be part of a method compile. At the time a method is compiled, an 'environment' should be provided to the compiler that indicates how global name resolution should occur. This is a tools issue and it should be possible to specify the default namespace environment for the method, for a method category, for a class, for a class category, for a package, and for the system as a whole. In addition, within a particular method it should be possible to explicitly reference a particular namespace environment, whether through syntax (dot or double colons) or through message sends (e.g., a Dictionary's #'at:' method). I prefer not to add new syntax and favor GemStone's implementation over that of VisualWorks. If you don't have time to discuss this in depth I would be less frustrated if you would wait to say it is wrong until you have time to explain why. James Foster

June 26, 2012

Re: [Pharo-project] [update 2.0] #20162

by StÃ©phane Ducasse

strnage I did not find it on jenkins. When I updated from 57 i got problems (may be my image was shaky). On Jun 26, 2012, at 8:40 PM, Marcus Denker wrote: > 20162 > ----- > > Issue 6157: remove dead lmmplugin code > http://code.google.com/p/pharo/issues/detail?id=6157 > > Issue 6161: Finder: Change Pattern back to Examples > http://code.google.com/p/pharo/issues/detail?id=6161 > > Issue 6168: Changeset>>#superclassOrder: should be only used by ChangeSet related objects > http://code.google.com/p/pharo/issues/detail?id=6168 > > > > -- > Marcus Denker -- http://marcusdenker.de > >

June 26, 2012

Re: [Pharo-project] MCSqueaksourceRepository

by StÃ©phane Ducasse

On Jun 26, 2012, at 8:51 PM, Sven Van Caekenberghe wrote: > In your case I would diagnose that as a 'Ruby Fat Finger' ;-) :) We should learn and take what is good there. - good nice support for file - string manipulation - ` with the new small kernel it will be interesting to see coral

June 26, 2012

[Pharo-project] Nautilus - Can't Rename Temporary

by Sean P. DeNigris

Issue 6174: [Bug]: Nautilus - Can't Rename Temporary http://code.google.com/p/pharo/issues/detail?id=6174 1. In a Nautilus code pane, select a temporary 2. Click to bring up the menu with "Source code refactoring" 3. Choose Rename Temporary 4. Fill in a new name You will see and invalid variable name error. This is because NautilusRefactoring>>renameTemporaryNamed: oldname Between: anInterval from: aMethod is receiving an empty Text for oldName Any ideas? -- View this message in context: http://forum.world.st/Nautilus-Can-t-Rename-Temporary-tp4636773.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 26, 2012

Re: [Pharo-project] Integrating OSProcess?

by David T. Lewis

Yes :) On Tue, Jun 26, 2012 at 09:00:02PM +0200, St?phane Ducasse wrote: > thanks dave :) > I just wanted to say that sometimes forking and pushing is the best way to make progress and it does not imply that > people are stealing, just wanted to go faster? whatever. > Stef > > On Jun 26, 2012, at 8:27 PM, David T. Lewis wrote: > > > On Tue, Jun 26, 2012 at 08:09:42PM +0200, St?phane Ducasse wrote: > >> > >> On Jun 26, 2012, at 5:33 PM, Sean P. DeNigris wrote: > >> > >>> Issue 5796: Integrate OSProcess > >>> http://code.google.com/p/pharo/issues/detail?id=5796 > >>> > >>> Are we doing this? If so, are we forking it (I hope not), or just > >>> integrating updated package versions as Dave releases them? > >> > >> This is an interesting question. I know that Camillo and Damien or somebody else made pipeable working. > >> I suggested that the code is sent to dave for integration in his package. (I do not know if this was done). Now if we really want to have a > >> strong interoperation with the rest of the world either OSProcess has a pharo branch and a nice packaging > >> or may be this is time to fork. I could understand that dave does not have cycles to handle that. > >> > >> Forking in itself is not a bad process when it serves a clear purpose. Look at Pharo. We did it not just for fun (and it was never an easy solution > >> after all the effort we did since years to promote Squeak - books, videos, lectures?.) but to accomplish a vision. > >> > >> So if we get a really hyper cool system to execute commands like ` in ruby then I want it immediately at the price of forking :) > >> > >> Stef > >> > > > > PipeableOSProcess should be working in Pharo now. > > > > A Metacello configuration to load OSProcess plus part of CommandShell > > (PipeableOSProcess and related classes) might be helpful for Pharo. I'm > > not working on that, so that might be a good thing for someone to do. > > > > Dave > > > > >

June 26, 2012

Re: [Pharo-project] Integrating OSProcess?

by StÃ©phane Ducasse

thanks dave :) I just wanted to say that sometimes forking and pushing is the best way to make progress and it does not imply that people are stealing, just wanted to go fasterâ¦ whatever. Stef On Jun 26, 2012, at 8:27 PM, David T. Lewis wrote: > On Tue, Jun 26, 2012 at 08:09:42PM +0200, St?phane Ducasse wrote: >> >> On Jun 26, 2012, at 5:33 PM, Sean P. DeNigris wrote: >> >>> Issue 5796: Integrate OSProcess >>> http://code.google.com/p/pharo/issues/detail?id=5796 >>> >>> Are we doing this? If so, are we forking it (I hope not), or just >>> integrating updated package versions as Dave releases them? >> >> This is an interesting question. I know that Camillo and Damien or somebody else made pipeable working. >> I suggested that the code is sent to dave for integration in his package. (I do not know if this was done). Now if we really want to have a >> strong interoperation with the rest of the world either OSProcess has a pharo branch and a nice packaging >> or may be this is time to fork. I could understand that dave does not have cycles to handle that. >> >> Forking in itself is not a bad process when it serves a clear purpose. Look at Pharo. We did it not just for fun (and it was never an easy solution >> after all the effort we did since years to promote Squeak - books, videos, lectures?.) but to accomplish a vision. >> >> So if we get a really hyper cool system to execute commands like ` in ruby then I want it immediately at the price of forking :) >> >> Stef >> > > PipeableOSProcess should be working in Pharo now. > > A Metacello configuration to load OSProcess plus part of CommandShell > (PipeableOSProcess and related classes) might be helpful for Pharo. I'm > not working on that, so that might be a good thing for someone to do. > > Dave > >

June 26, 2012

Re: [Pharo-project] MCSqueaksourceRepository

by Sven Van Caekenberghe

In your case I would diagnose that as a 'Ruby Fat Finger' ;-) On 26 Jun 2012, at 20:27, Camillo Bruni wrote: > On 2012-06-26, at 20:06, Sven Van Caekenberghe wrote: >> On 26 Jun 2012, at 20:02, Camillo Bruni wrote: >> >>> That saved me so far 39 * 'http://www.squeaksource.com/'.size characters :P >> >> Arch, is that a dot (.) between the string and size ?? >> >> My eyes hurtâ¦. > > aiaiai what a misfortunate fat finger :D

June 26, 2012

[Pharo-project] Google Code labels/templates

by Sean P. DeNigris

Someone had suggested to remove the "Pharo 1.4 Enhancement" template, since we're not accepting any. That makes sense. Also, the Nautilus template labels the issue "Nautilus", but the label in the list is "Type-Nautilus". Which brings me to my next question... The other Types are Bug, Enhancement, Cleanup, Feature [1]. Nautilus and Jenkins [2] really don't fit into this framework. Maybe because there will be many fewer issues, we don't need the level of granularity of [1] for [2]. But when we get close to a release, it'd be nice to know that there is 1 Nautilus bug and 10 Enhancements pending (i.e. probably only one critical thing) vs. 11 Type-Nautilus. So, now that I said all that, it seems the most powerful/flexible approach would be to leave the "nautilus" tag, remove the leading "Type-" from "Type-[Jenkins|Spec|Seed]", and then to make templates for Jenkins/Spec/Seed like the one for Nautilus. What do you think? Sean -- View this message in context: http://forum.world.st/Google-Code-labels-templates-tp4636767.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 26, 2012

[Pharo-project] [update 2.0] #20162

by Marcus Denker

20162 ----- Issue 6157: remove dead lmmplugin code http://code.google.com/p/pharo/issues/detail?id=6157 Issue 6161: Finder: Change Pattern back to Examples http://code.google.com/p/pharo/issues/detail?id=6161 Issue 6168: Changeset>>#superclassOrder: should be only used by ChangeSet related objects http://code.google.com/p/pharo/issues/detail?id=6168 -- Marcus Denker -- http://marcusdenker.de

June 26, 2012