August 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Pharo-users] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release

by Dale Henrichs

There were some Metacello performance issues that popped up when using the MetacelloBrowser, so I was reluctant to publicize the MetacelloBrowser until the issues were resolved. While working on tODE, I isolated and fixed the performance issues, so the next release of Metacello (soonish) will have fixes for the performance issues and then the MetacelloBrowser will be ready to be used ... it does need some GUI polish ... Dale ----- Original Message ----- | From: "Alexandre Bergel" <alexandre.bergel(a)me.com> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Wednesday, August 31, 2011 2:02:55 PM | Subject: Re: [Pharo-project] [Pharo-users] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release | | Dale and I worked on the MetacelloBrowser. I believe the UI needs to | be polished. Probably having something based on Glamour would cool | to have. | I worked on Versionner because I just need a commit button. | | Cheers, | Alexandre | | | On 31 Aug 2011, at 17:57, Igor Stasenko wrote: | | > is it just me, or there are more people who know nothing about it? | > | > i know how to do a parallel programs, | > but i have no means to know what happens in parallel to my little | > universe unless i can read it from some well known source :) | > | > On 31 August 2011 23:46, Alexandre Bergel <alexandre.bergel(a)me.com> | > wrote: | > :-) | > I use Versionner for simple case and the MetacelloBrowser for more | > complicated stuff. | > Check at the screenshot. You see, there is a commit button :-) It | > saves all the dependent packages, create a new version, ask you | > for the comment, and save the config. I rarely use the Monticello | > browser actually. | > | > <Screen Shot 2011-08-31 at 17.24.53.png> | > | > Cheers, | > Alexandre | > | > | > On 31 Aug 2011, at 17:23, Igor Stasenko wrote: | > | >> On 31 August 2011 23:19, Alexandre Bergel | >> <alexandre.bergel(a)me.com> wrote: | >>>> For development configuration is useless and just time sink. | >>> | >>> I strongly disagree. Metacello was sold to please users. | >>> Actually, I use it for me, the developper. I create a new | >>> version at each commit. It works wonderfully. | >>> | >> | >> sorry, but if during development you need to do 2 commits of 20 | >> packages , calculate how much time it would take for you to | >> manuallly update a configuration for each update. | >> it is time sink. | >> | >> if you do that once per day, its okay.. but for every commit . no. | >> its | >> is absurd. | >> | >>> Alexandre | >>> | >>> | >>>> But for release it has completely different purpose: it helps us | >>>> to | >>>> identify what exactly and what version of it will be put in | >>>> final | >>>> version. And gives a simple and concrete answer how to reproduce | >>>> it, | >>>> in case of need. | >>>> Since we're are talking about release, i don't see how we could | >>>> do | >>>> that without configurations. | >>>> | >>>> Yes, sure it could be done manually to manifest all packages and | >>>> their | >>>> version(s) included into release, but it still means that | >>>> someone has to do it one way or another. | >>>> | >>>> | >>>> On 31 August 2011 23:03, StÃ©phane Ducasse | >>>> <stephane.ducasse(a)inria.fr> wrote: | >>>>> Marcus | >>>>> | >>>>> We only do what is possible :) | >>>>> | >>>>> - for the configurations of let us take what exist. We | >>>>> cannot control everything. I do not have the time and | >>>>> knowledge for that. | >>>>> Lukas decided that configurations are evil. Ok perfect | >>>>> now we fix them when we know what should be loaded. | >>>>> | >>>>> - Then for example to integrate the broken highlight I | >>>>> need the code first. I still do not know which slice to | >>>>> load in 1.3. | >>>>> Two days ago I spent time on it loading the wrong slice. | >>>>> So I decided that I will not stress. | >>>>> | >>>>> So we will fix that either in 1.3 or in 1.4 as time allows it. | >>>>> And more more important: no stress we are payed enough to | >>>>> stress and do stuff that hurts us. | >>>>> | >>>>> Stef | >>>>> | >>>>>> On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote: | >>>>>> | >>>>>>> The image contains outdated versions of RB and OB that miss | >>>>>>> some | >>>>>>> critical fixes. | >>>>>> | >>>>>> How can I know? | >>>>>> | >>>>>> It is is build using the latest MetaCello config... if the | >>>>>> config needs to be updated, | >>>>>> it needs to be updated. It does not happen by itself. | >>>>>> | >>>>>>> Also there some proposed fixes don't seem to be | >>>>>>> included | >>>>>>> <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> | >>>>>>> yet? | >>>>>>> | >>>>>> No... I have not yet found the energy to do that. | >>>>>> | >>>>>> Marcus | >>>>>> | >>>>>> -- | >>>>>> Marcus Denker -- http://marcusdenker.de | >>>>>> | >>>>>> | >>>>> | >>>>> | >>>>> | >>>> | >>>> | >>>> | >>>> -- | >>>> Best regards, | >>>> Igor Stasenko AKA sig. | >>>> | >>> | >>> -- | >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | >>> Alexandre Bergel http://www.bergel.eu | >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | >>> | >>> | >>> | >>> | >>> | >>> | >>> | >> | >> | >> | >> -- | >> Best regards, | >> Igor Stasenko AKA sig. | >> | > | > -- | > | > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | > Alexandre Bergel http://www.bergel.eu | > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | > | > | > | > | > | > | > | > | > -- | > Best regards, | > Igor Stasenko AKA sig. | | -- | _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | Alexandre Bergel http://www.bergel.eu | ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | | | | | | |

Aug. 31, 2011

Re: [Pharo-project] [Pharo-users] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release

by GermÃ¡n Arduino

2011/8/31 Igor Stasenko <siguctua(a)gmail.com> > is it just me, or there are more people who know nothing about it? > > I never hear about it neither :S Look as a very useful tool ......

Aug. 31, 2011

Re: [Pharo-project] Scriptable CompileMethod interface

by Nicolas Cellier

2011/9/1 Camillo Bruni <camillo.bruni(a)inria.fr>: > > On 2011-09-01, at 00:54, Nicolas Cellier wrote: >> 2011/9/1 Camillo Bruni <camillo.bruni(a)inria.fr>: >>> Today on the train I was a bit bored on what I can do with CompiledMethodsâ¦ >>> >>> It seems like there are no inspection methods on CompiledMethods. Now I lets say I use Pharo from the command line (we're almost thereâ¦) then I would like to have a small interface to browse and navigate through methodsâ¦ >>> >>> (Object >> #at:) overrides Â Â Â "return all direct overrides of this method" >>> (Bag >> #at:) super Â Â Â Â Â Â "return the method I override" >>> (Bag >> #at:) superChain Â Â Â Â "return all implementations in superclasses" >>> (Object >> #name) senders >>> (Object >> #name) implementors >>> >>> instead of doing something like >>> >>> SystemNavigation default allCallsOn: #name Â "(BTW I would prefer allSendersOf: #name)" >>> >>> What do you think? Does this make sense or not? >>> >>> cami >>> >> >> I'm not convinced. >> (Object >> #name) senders >> 1) works only if you know a class that implements #name >> 2) technically it won't return the senders of (Object >> #name) but >> the senders of (AnyOtherClass >> #name) > > Yes this is absolutely correct. But I think might have not been clear about my intentions. I do not want to replace SystemNavigation default * calls. But make sure that once you actually have a CompiledMethod you can browse from there on. > Thats what the (Object >> #name) actually should mean, I should have chosen some better example like (String >> #printOn:) or so. > > >> (Object >> #name) implementors >> 1) same as above, you must first know an implementorâ¦ > > Again, you start from an existing implementation (Object >> #name) just happens to be a random example.. > >> (Bag >> #at:) super /superChain >> is a bit better, but there is again no garanty that Bag implements >> at:, still I might want to see all implementors in superclasses. > > Nope, (Bag >> #at:) will fail if the method doesn't exist. > >> Nicolas > > > I guess what you want meant is the same navigation interface on Symbol: > > #name implementors > #foo:bar: senders > #at: superChain: Bag Â Â Â Â Â "definitely needs another name :)" > #at: implementorsAbove: Bag Â "might be betterâ¦" > > cami > Yes, but this will reopen the Symbol/Selector thread ;) Nicolas

Aug. 31, 2011

Re: [Pharo-project] Scriptable CompileMethod interface

by Camillo Bruni

On 2011-09-01, at 00:54, Nicolas Cellier wrote: > 2011/9/1 Camillo Bruni <camillo.bruni(a)inria.fr>: >> Today on the train I was a bit bored on what I can do with CompiledMethodsâ¦ >> >> It seems like there are no inspection methods on CompiledMethods. Now I lets say I use Pharo from the command line (we're almost thereâ¦) then I would like to have a small interface to browse and navigate through methodsâ¦ >> >> (Object >> #at:) overrides "return all direct overrides of this method" >> (Bag >> #at:) super "return the method I override" >> (Bag >> #at:) superChain "return all implementations in superclasses" >> (Object >> #name) senders >> (Object >> #name) implementors >> >> instead of doing something like >> >> SystemNavigation default allCallsOn: #name "(BTW I would prefer allSendersOf: #name)" >> >> What do you think? Does this make sense or not? >> >> cami >> > > I'm not convinced. > (Object >> #name) senders > 1) works only if you know a class that implements #name > 2) technically it won't return the senders of (Object >> #name) but > the senders of (AnyOtherClass >> #name) Yes this is absolutely correct. But I think might have not been clear about my intentions. I do not want to replace SystemNavigation default * calls. But make sure that once you actually have a CompiledMethod you can browse from there on. Thats what the (Object >> #name) actually should mean, I should have chosen some better example like (String >> #printOn:) or so. > (Object >> #name) implementors > 1) same as above, you must first know an implementorâ¦ Again, you start from an existing implementation (Object >> #name) just happens to be a random example.. > (Bag >> #at:) super /superChain > is a bit better, but there is again no garanty that Bag implements > at:, still I might want to see all implementors in superclasses. Nope, (Bag >> #at:) will fail if the method doesn't exist. > Nicolas I guess what you want meant is the same navigation interface on Symbol: #name implementors #foo:bar: senders #at: superChain: Bag "definitely needs another name :)" #at: implementorsAbove: Bag "might be betterâ¦" cami

Aug. 31, 2011

Re: [Pharo-project] Scriptable CompileMethod interface

by Nicolas Cellier

2011/9/1 Camillo Bruni <camillo.bruni(a)inria.fr>: > Today on the train I was a bit bored on what I can do with CompiledMethodsâ¦ > > It seems like there are no inspection methods on CompiledMethods. Now I lets say I use Pharo from the command line (we're almost thereâ¦) then I would like to have a small interface to browse and navigate through methodsâ¦ > > (Object >> #at:) overrides Â Â Â "return all direct overrides of this method" > (Bag >> #at:) super Â Â Â Â Â Â "return the method I override" > (Bag >> #at:) superChain Â Â Â Â "return all implementations in superclasses" > (Object >> #name) senders > (Object >> #name) implementors > > instead of doing something like > > SystemNavigation default allCallsOn: #name Â "(BTW I would prefer allSendersOf: #name)" > > What do you think? Does this make sense or not? > > cami > I'm not convinced. (Object >> #name) senders 1) works only if you know a class that implements #name 2) technically it won't return the senders of (Object >> #name) but the senders of (AnyOtherClass >> #name) (Object >> #name) implementors 1) same as above, you must first know an implementor... (Bag >> #at:) super /superChain is a bit better, but there is again no garanty that Bag implements at:, still I might want to see all implementors in superclasses. Nicolas

Aug. 31, 2011

Re: [Pharo-project] Scriptable CompileMethod interface

by Benjamin

On Sep 1, 2011, at 12:35 AM, Camillo Bruni wrote: > Today on the train I was a bit bored on what I can do with CompiledMethodsâ¦ > > It seems like there are no inspection methods on CompiledMethods. Now I lets say I use Pharo from the command line (we're almost thereâ¦) then I would like to have a small interface to browse and navigate through methodsâ¦ > > (Object >> #at:) overrides "return all direct overrides of this method" Look in Nautilus, I have wrote an extension for that > (Bag >> #at:) super "return the method I override" Bag super lookupSelector: #at: ? > (Bag >> #at:) superChain "return all implementations in superclasses" +1 > (Object >> #name) senders +1 > (Object >> #name) implementors +1 > instead of doing something like > > SystemNavigation default allCallsOn: #name "(BTW I would prefer allSendersOf: #name)" > > What do you think? Does this make sense or not? > > cami Ben ;)

Aug. 31, 2011

[Pharo-project] Scriptable CompileMethod interface

by Camillo Bruni

Today on the train I was a bit bored on what I can do with CompiledMethodsâ¦ It seems like there are no inspection methods on CompiledMethods. Now I lets say I use Pharo from the command line (we're almost thereâ¦) then I would like to have a small interface to browse and navigate through methodsâ¦ (Object >> #at:) overrides "return all direct overrides of this method" (Bag >> #at:) super "return the method I override" (Bag >> #at:) superChain "return all implementations in superclasses" (Object >> #name) senders (Object >> #name) implementors instead of doing something like SystemNavigation default allCallsOn: #name "(BTW I would prefer allSendersOf: #name)" What do you think? Does this make sense or not? cami

Aug. 31, 2011

[Pharo-project] editing methods without header

by Tudor Girba

Hi, Currently, when we edit a method, we use one text morph that includes both the header and the body of the method. I am searching for an easy way to edit only the body of the methods, but still have completion and syntax highlighting. Any ideas of how to approach this? Cheers, Doru -- www.tudorgirba.com "Be rather willing to give than demanding to get."

Aug. 31, 2011

Re: [Pharo-project] [Pharo-users] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release

by Tudor Girba

Hi, For development involving multiple people in the same time, you cannot rely on hardcoded package versions in configurations, because there is no merge support, so you will never know when you are missing a version. The only model that works reliably now is to depend on a baseline for development. That means that when you develop, you integrate relentlessly the latest package versions. When you release you can use the same baseline and hardcode the package versions. Cheers, Doru On 31 Aug 2011, at 23:02, Alexandre Bergel wrote: > Dale and I worked on the MetacelloBrowser. I believe the UI needs to be polished. Probably having something based on Glamour would cool to have. > I worked on Versionner because I just need a commit button. > > Cheers, > Alexandre > > > On 31 Aug 2011, at 17:57, Igor Stasenko wrote: > >> is it just me, or there are more people who know nothing about it? >> >> i know how to do a parallel programs, >> but i have no means to know what happens in parallel to my little universe unless i can read it from some well known source :) >> >> On 31 August 2011 23:46, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> :-) >> I use Versionner for simple case and the MetacelloBrowser for more complicated stuff. >> Check at the screenshot. You see, there is a commit button :-) It saves all the dependent packages, create a new version, ask you for the comment, and save the config. I rarely use the Monticello browser actually. >> >> <Screen Shot 2011-08-31 at 17.24.53.png> >> >> Cheers, >> Alexandre >> >> >> On 31 Aug 2011, at 17:23, Igor Stasenko wrote: >> >>> On 31 August 2011 23:19, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>>> For development configuration is useless and just time sink. >>>> >>>> I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully. >>>> >>> >>> sorry, but if during development you need to do 2 commits of 20 >>> packages , calculate how much time it would take for you to >>> manuallly update a configuration for each update. >>> it is time sink. >>> >>> if you do that once per day, its okay.. but for every commit . no. its >>> is absurd. >>> >>>> Alexandre >>>> >>>> >>>>> But for release it has completely different purpose: it helps us to >>>>> identify what exactly and what version of it will be put in final >>>>> version. And gives a simple and concrete answer how to reproduce it, >>>>> in case of need. >>>>> Since we're are talking about release, i don't see how we could do >>>>> that without configurations. >>>>> >>>>> Yes, sure it could be done manually to manifest all packages and their >>>>> version(s) included into release, but it still means that >>>>> someone has to do it one way or another. >>>>> >>>>> >>>>> On 31 August 2011 23:03, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>>>> Marcus >>>>>> >>>>>> We only do what is possible :) >>>>>> >>>>>> - for the configurations of let us take what exist. We cannot control everything. I do not have the time and knowledge for that. >>>>>> Lukas decided that configurations are evil. Ok perfect now we fix them when we know what should be loaded. >>>>>> >>>>>> - Then for example to integrate the broken highlight I need the code first. I still do not know which slice to load in 1.3. >>>>>> Two days ago I spent time on it loading the wrong slice. So I decided that I will not stress. >>>>>> >>>>>> So we will fix that either in 1.3 or in 1.4 as time allows it. >>>>>> And more more important: no stress we are payed enough to stress and do stuff that hurts us. >>>>>> >>>>>> Stef >>>>>> >>>>>>> On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote: >>>>>>> >>>>>>>> The image contains outdated versions of RB and OB that miss some >>>>>>>> critical fixes. >>>>>>> >>>>>>> How can I know? >>>>>>> >>>>>>> It is is build using the latest MetaCello config... if the config needs to be updated, >>>>>>> it needs to be updated. It does not happen by itself. >>>>>>> >>>>>>>> Also there some proposed fixes don't seem to be >>>>>>>> included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> >>>>>>>> yet? >>>>>>>> >>>>>>> No... I have not yet found the energy to do that. >>>>>>> >>>>>>> Marcus >>>>>>> >>>>>>> -- >>>>>>> Marcus Denker -- http://marcusdenker.de >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Best regards, >>>>> Igor Stasenko AKA sig. >>>>> >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> -- >> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > -- www.tudorgirba.com "Value is always contextual."

Aug. 31, 2011

Re: [Pharo-project] opening a text in a window

by Jimmie Houchin

I am working in a Pharo 1.3 image and this works well for me. ws := Workspace openLabel: 'my new workspace'. ws toggleStylingActive. ws contents: 'my new content'. I like opening with a descriptive label rather than just adding another "Workspace" window on my screen or on my tabs at the bottom. It helps to identify and find. I can refresh the contents with them remaining unstyled. From my experiments I have discovered that toggling from a styled state to an unstyled state is only successful if the contents are empty, ''. Toggling from an unstyled state to a styled state is always successful. I can do the below, executing each line at a time in sequence in a Workspace and it behaves like the comments on each line. r := Random new. ws := Workspace openLabel: 'my new workspace'. ws toggleStylingActive. " de-activates styling". ws contents: '"', r next asString, '"'. " no styling as expected". ws toggleStylingActive. " activates styling". ws contents: '"', r next asString, '"'. " styling changes as expected". ws toggleStylingActive. " de-activates styling". ws contents: '"', r next asString, '"'. " styling did not change, WHY??? ". ws contents: ''. ws contents: '"', r next asString, '"'. " styling changes" ws toggleStylingActive. " activates styling". ws contents: '"', r next asString, '"'. " styling changes". Strange behavior. Thanks for the information. Jimmie On 8/31/2011 3:45 PM, StÃ©phane Ducasse wrote: > In latest 1.4 > > wk := Workspace new. > wk contents: 'lkhkhkjhkjh'. > wk toggleStylingActive. > wk open > > so I imagine easily that we can define a better creation method but this one is working well. > > Stef > > > On Aug 31, 2011, at 6:04 PM, Alexandre Bergel wrote: > >> hi! >> >> Is there a way to open a text in a window in Pharo? >> Doing: Workspace openContents: 'hello world' >> shows >> <Screen Shot 2011-08-31 at 13.03.06.png> >> >> Is there a way to remove the syntax highlighting? >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >

Aug. 31, 2011