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

Re: [Pharo-project] Weird result with OSProcess and Applescript

by Igor Stasenko

you're probably one of the few who using OSProcess plugin and in such fashion.. i'd willing to help, but i don't know much about OP implementation. Maybe you will have some response if you post on vm-dev list? On 24 February 2012 21:47, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > So weird! Even compiling the script into a file and running it that way has > the same result: > > PipeableOSProcess waitForCommand: '/usr/bin/osascript -ss > "/path/to/get_source_of_current_safari_tab.scpt"' > > For now, I made a Ruby one-liner, using rb-appscript, that doesn't hang > waitForCommand:, but I'm still curious... > > -- > View this message in context: http://forum.world.st/Weird-result-with-OSProcess-and-Applescript-tp4415603… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Best regards, Igor Stasenko.

Feb. 24, 2012

[Pharo-project] change pharo image title

by Usman Bhatti

Is there a way to programmatically set the title of a pharo image on startup? I grabbed the first level pasteup morph and tried to play with it but I didn't find the intended method. thanx usman

Feb. 24, 2012

Re: [Pharo-project] Weird result with OSProcess and Applescript

by Sean P. DeNigris

So weird! Even compiling the script into a file and running it that way has the same result: PipeableOSProcess waitForCommand: '/usr/bin/osascript -ss "/path/to/get_source_of_current_safari_tab.scpt"' For now, I made a Ruby one-liner, using rb-appscript, that doesn't hang waitForCommand:, but I'm still curious... -- View this message in context: http://forum.world.st/Weird-result-with-OSProcess-and-Applescript-tp4415603… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 24, 2012

Re: [Pharo-project] Spoon presentation 2012-02-24

by Craig Latta

Hi Chris-- > You showed us this earlier in the week -- and the feedback then was, > "voice-over, please." When the music started I hoped perhaps you were > going to sing it to us. :) Heh. Yeah, all this version adds is the ability to watch it passively on YouTube. I'm editing a voice-over now for a future version. > It's nice demo, but so far I've only seen the components that are IN > Spoon -- I am interested in seeing an OUTPUT of Spoon. Anything to > take me to the next-level of understanding and confidence about it.. Sure; the next movie I'm making is basically the real presentation, with lots of departures from the slides into the live system. I expect there will be versions of different lengths for various attention spans, and the full version will be about an hour. thanks again, -C -- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 415 287 3547

Feb. 24, 2012

Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3

by Igor Stasenko

On 24 February 2012 20:48, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Sig, > > Fair enough. Â I find 1..3 to unstable, and the thrashing sounds about right. Â For now I am trying to carve a home in 1.4. > i don't think it is fair labeling 1.3 unstable. It is quite stable and worked well for me. Now there's always space for improvement, but that's doesn't nullifies the quality of previous hard work of many people (pharo 1.3, 1.2 , 1.1, 1.0 squeak etc..) > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Igor Stasenko [siguctua(a)gmail.com] > Sent: Friday, February 24, 2012 1:37 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3 > > On 24 February 2012 16:11, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: >> Guys, >> >> I'm hoping Sig will see this an immediately know what is at play. Â I don't even know if there is a fix, but there appears to be in 1.4. Â If backporting that to 1.3 is feasible, it should be done. Â I *think* I know some keywords that might pull his relevant reply (something like "you are a victim of") from the archive. Â Can't do it right now. >> > i remember it. > And no, i don't see why these changes are needed to be backported to 1.3. > It was : > http://code.google.com/p/pharo/issues/detail?id=5167&q=finalization&colspec… > > and fix which were integrated was about improving a situation with > runaway processes and interrupt handling. > > Now, that bug entry is still not closed, becaue we have to deal with > so-called "finalization trashing", whether it is real issue or not. > As to me, this is not an issue, because finalization "trashing" is a > consequence but not the cause. And since it is better to fix the cause > instead, that what i actually did. > And then during integration i made a mistake in one method (an > overlooking), causing debugger to not open, but it is already > reverted. > All this is related to 1.4 bleeding edge, not to 1.3. > And i personally don't see good reason porting it to 1.3. It is not > critical. We just improved this part a bit. So, the new pharo version > is naturally better than older one.. that's why we got versions > and development process. :) > If we would start backporting everything, then we don't need versions > anymore. We then will just have single image and fight with all > dragons at once. > >> BTW, Â I took Stef's reply and used it to good effect - might have even figured out why I couldn't build images. Â All part of testing. Â If you look, you'll find code of mine in the image. Â Have you noted some of my responses to help others - probably not. Â But I would rather not play "I haven't seen" games. >> >> Bill >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Sven Van Caekenberghe [sven(a)beta9.be] >> Sent: Friday, February 24, 2012 6:02 AM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3 >> >> On 24 Feb 2012, at 11:12, Schwab,Wilhelm K wrote: >> >>> There is a tracker entry, but please understand it's the middle of the night here and I'm in and out. Â I think Sig will know the details more off the top, otherwise I'll search later. Â Would you rather I say nothing about a known bug? >> >> I can't find anything with Schwab, Bill or Wilhelm in any issue ever in http://code.google.com/p/pharo/issues/list (there are a handful that are more than half a year old, magically you even received help). I read this mailing list all the time, I can't remember seeing a concrete, reproduceable bug report. Please, correct me if I am wrong. >> >> Some, like Stef, even took the trouble of trying to load some of the stuff that was causing you trouble, only to report that it worked for them. >> >> I and many others ask for help and report problems here all the time. It is incredible how people spring up all the time to help others with both simple and deep problems. It is often so that the one reporting a problem did something wrong himself, I am guilty here as well, but even then people took the trouble to look and give some of their valuable time. >> >> The way you ask the question makes a huge difference: provide details, make it reproduceable, don't include negative stuff. >> >> I'll make you a promise: I'll give you some of my personal time to try whatever you report next as 'BAD bug, makes 1.3 unstable, rendering the image useless', provided there is a description of how I should do it. >> >> Sven >> >> >> >> >> >> > > > > -- > Best regards, > Igor Stasenko. > > -- Best regards, Igor Stasenko.

Feb. 24, 2012

Re: [Pharo-project] receiving tcp messages

by Igor Stasenko

for telnet-kind-of communication, i think there is already base classes for doing that.. i have no image before my eyes now, but look for things related to mail client, and ftp.. the base class is called something like CommandBlahBlah, which implements a simple "readline" over socket. 2012/2/24 GÃ¶ran Krampe <goran(a)krampe.se>: > On 02/24/2012 06:38 PM, Tudor Girba wrote: >> >> Hi Sven (and Goran), >> >> Thanks a lot! This is pretty much what I was looking for. > > > As I wrote - if you are after a forking *server* - then load Blackfoot from > SS and use it as a base. I took Kom and stripped it down to its barest form > and made a base class etc, it should be obvious. It does basically what Sven > wrote. > > regards, GÃ¶ran > -- Best regards, Igor Stasenko.

Feb. 24, 2012

Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3

by Schwab,Wilhelm K

Sig, Fair enough. I find 1..3 to unstable, and the thrashing sounds about right. For now I am trying to carve a home in 1.4. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Igor Stasenko [siguctua(a)gmail.com] Sent: Friday, February 24, 2012 1:37 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3 On 24 February 2012 16:11, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Guys, > > I'm hoping Sig will see this an immediately know what is at play. I don't even know if there is a fix, but there appears to be in 1.4. If backporting that to 1.3 is feasible, it should be done. I *think* I know some keywords that might pull his relevant reply (something like "you are a victim of") from the archive. Can't do it right now. > i remember it. And no, i don't see why these changes are needed to be backported to 1.3. It was : http://code.google.com/p/pharo/issues/detail?id=5167&q=finalization&colspec… and fix which were integrated was about improving a situation with runaway processes and interrupt handling. Now, that bug entry is still not closed, becaue we have to deal with so-called "finalization trashing", whether it is real issue or not. As to me, this is not an issue, because finalization "trashing" is a consequence but not the cause. And since it is better to fix the cause instead, that what i actually did. And then during integration i made a mistake in one method (an overlooking), causing debugger to not open, but it is already reverted. All this is related to 1.4 bleeding edge, not to 1.3. And i personally don't see good reason porting it to 1.3. It is not critical. We just improved this part a bit. So, the new pharo version is naturally better than older one.. that's why we got versions and development process. :) If we would start backporting everything, then we don't need versions anymore. We then will just have single image and fight with all dragons at once. > BTW, I took Stef's reply and used it to good effect - might have even figured out why I couldn't build images. All part of testing. If you look, you'll find code of mine in the image. Have you noted some of my responses to help others - probably not. But I would rather not play "I haven't seen" games. > > Bill > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Sven Van Caekenberghe [sven(a)beta9.be] > Sent: Friday, February 24, 2012 6:02 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3 > > On 24 Feb 2012, at 11:12, Schwab,Wilhelm K wrote: > >> There is a tracker entry, but please understand it's the middle of the night here and I'm in and out. I think Sig will know the details more off the top, otherwise I'll search later. Would you rather I say nothing about a known bug? > > I can't find anything with Schwab, Bill or Wilhelm in any issue ever in http://code.google.com/p/pharo/issues/list (there are a handful that are more than half a year old, magically you even received help). I read this mailing list all the time, I can't remember seeing a concrete, reproduceable bug report. Please, correct me if I am wrong. > > Some, like Stef, even took the trouble of trying to load some of the stuff that was causing you trouble, only to report that it worked for them. > > I and many others ask for help and report problems here all the time. It is incredible how people spring up all the time to help others with both simple and deep problems. It is often so that the one reporting a problem did something wrong himself, I am guilty here as well, but even then people took the trouble to look and give some of their valuable time. > > The way you ask the question makes a huge difference: provide details, make it reproduceable, don't include negative stuff. > > I'll make you a promise: I'll give you some of my personal time to try whatever you report next as 'BAD bug, makes 1.3 unstable, rendering the image useless', provided there is a description of how I should do it. > > Sven > > > > > > -- Best regards, Igor Stasenko.

Feb. 24, 2012

[Pharo-project] Emergency evaluator refresh problem

by Usman Bhatti

After exiting from emergency evaluator in pharo, pharo desktop/home is not repainted/refreshed. Is it an issue or a feature? [image: Inline image 2]

Feb. 24, 2012

Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3

by Igor Stasenko

On 24 February 2012 16:11, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Guys, > > I'm hoping Sig will see this an immediately know what is at play. Â I don't even know if there is a fix, but there appears to be in 1.4. Â If backporting that to 1.3 is feasible, it should be done. Â I *think* I know some keywords that might pull his relevant reply (something like "you are a victim of") from the archive. Â Can't do it right now. > i remember it. And no, i don't see why these changes are needed to be backported to 1.3. It was : http://code.google.com/p/pharo/issues/detail?id=5167&q=finalization&colspec… and fix which were integrated was about improving a situation with runaway processes and interrupt handling. Now, that bug entry is still not closed, becaue we have to deal with so-called "finalization trashing", whether it is real issue or not. As to me, this is not an issue, because finalization "trashing" is a consequence but not the cause. And since it is better to fix the cause instead, that what i actually did. And then during integration i made a mistake in one method (an overlooking), causing debugger to not open, but it is already reverted. All this is related to 1.4 bleeding edge, not to 1.3. And i personally don't see good reason porting it to 1.3. It is not critical. We just improved this part a bit. So, the new pharo version is naturally better than older one.. that's why we got versions and development process. :) If we would start backporting everything, then we don't need versions anymore. We then will just have single image and fight with all dragons at once. > BTW, Â I took Stef's reply and used it to good effect - might have even figured out why I couldn't build images. Â All part of testing. Â If you look, you'll find code of mine in the image. Â Have you noted some of my responses to help others - probably not. Â But I would rather not play "I haven't seen" games. > > Bill > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Sven Van Caekenberghe [sven(a)beta9.be] > Sent: Friday, February 24, 2012 6:02 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3 > > On 24 Feb 2012, at 11:12, Schwab,Wilhelm K wrote: > >> There is a tracker entry, but please understand it's the middle of the night here and I'm in and out. Â I think Sig will know the details more off the top, otherwise I'll search later. Â Would you rather I say nothing about a known bug? > > I can't find anything with Schwab, Bill or Wilhelm in any issue ever in http://code.google.com/p/pharo/issues/list (there are a handful that are more than half a year old, magically you even received help). I read this mailing list all the time, I can't remember seeing a concrete, reproduceable bug report. Please, correct me if I am wrong. > > Some, like Stef, even took the trouble of trying to load some of the stuff that was causing you trouble, only to report that it worked for them. > > I and many others ask for help and report problems here all the time. It is incredible how people spring up all the time to help others with both simple and deep problems. It is often so that the one reporting a problem did something wrong himself, I am guilty here as well, but even then people took the trouble to look and give some of their valuable time. > > The way you ask the question makes a huge difference: provide details, make it reproduceable, don't include negative stuff. > > I'll make you a promise: I'll give you some of my personal time to try whatever you report next as 'BAD bug, makes 1.3 unstable, rendering the image useless', provided there is a description of how I should do it. > > Sven > > > > > > -- Best regards, Igor Stasenko.

Feb. 24, 2012

Re: [Pharo-project] New IDE alternative (was Misc. newbie questions)

by Igor Stasenko

omg.. i like that. what i would add is that depending on workflow, sometime i would like to have standard view for usual navigation, tree view for focusing on some specific class/package and bubble view for focusing on some concrete exemplar (be it method or class or inspector).. that means that i would like to have it all, nicely put together , of course :) On 24 February 2012 20:02, S Krish <krishnamachari.sudhakar(a)gmail.com> wrote: > I love Pharo's ability to mould/ twist in spare time something that is > imminently usable.. > > Just playing around over an hour plus, I find this tree view grouping > more convinient than current browsers in giving a coherent view that > easily extends: > > All editable code text morphs, spreading over to mutliple worlds one > can traverse too if needed. or appears on tab anyways for each group. > > a) Package, Class, Category , Hierarchy levels. > > b) Senders, implementors .. > > c) Arbitrary groups of methods if one desires to.. > > Can also include some class definition info bubble/ reduce noise > through some more optimization to make it optimized > > ... we can have a little customizations too to get a good grip of the > whole as well as the part. > > But I agree, Gaucho / Code Bubbles are nice, but I am afraid fo > fragmented view it will still represented. May be each will have > little twist of his predilictions and cannot be highly generalized. > > > On 2/24/12, Igor Stasenko <siguctua(a)gmail.com> wrote: >> On 24 February 2012 00:18, Matias Garcia Isaia <mgarciaisaia(a)gmail.com> >> wrote: >>> On Thu, Feb 23, 2012 at 5:08 PM, Mariano Martinez Peck >>> <marianopeck(a)gmail.com> wrote: >>>> Nooo!!! he comes from Java!! he starts with index 0. Kill him!!! Â ;) >>> >>> Ooops... Time to get a new identity :) >>> >>> >>> On 23 February 2012 19:47, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> wrote: >>>> Sure we know. >>>> And we also know that it requires effort and lot of people are talking. >>> >>> I know there's a loooong way to see what CodeBubbles can do, and that >>> requires to do a big effort, but imagined that some kind of >>> alternative - I'm not sure that CB is **exactly** what I want (sure >>> Java-ers want to see **something more** than just a file pimped with >>> colours, but Smalltalk **allready has** much more than a text file - >>> have real code) Â - could be very less effort-consuming. Making the >>> current browser (Nautilus? - newbie here :) ) pop a new >>> Â¿window?Â¿morph? showing a method instead of updating a single pane >>> (the current one showing method's source) don't seems to be so "far" >>> away to me. >>> >>> Of course that's my point of view, based on what I imagine that could >>> be. I should spend some time to see how it is implemented, and to see >>> if it really is that simple, but anyway trust you if you say is a huge >>> effort... >>> >> >> Well, popping out a new morph every time you clicking around is easy part. >> The hard part is to make this stuff really consistent and easy to use >> for navigation and development. >> It requires far more serious work than just spending 2 hours >> implementing "bubbling" behavior. >> >>> >>> Cheers :) >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> >> -- Best regards, Igor Stasenko.

Feb. 24, 2012