- Pharo-dev - lists.pharo.org

[Pharo-project] Cog-Mac-Cocoa + OSProcess problem

by laurent laffont

Hi Esteban, using last built of Cog-Mac-Cocoa VM, my image crashes as soon as it opens because of OSProcess. Works with StackVM 4.0 The image is Pharo1.3 with SmallHarbour (smallharbour.org) loaded. You can download the image from http://lolgzs.free.fr/pharo/SmallHarbourCrash.zip The log: *** Warning: Warning: OSProcess not available or OSProcess plugin not functioning THERE_BE_DRAGONS_HERE MessageNotUnderstood: PipeableOSProcess class>>output 26 July 2011 9:21:12 am VM: Mac OS - intel - 1070 - Croquet Closure Cog VM [CoInterpreter VMMaker-oscog-IgorStasenko.96] 21.0 Image: Pharo1.3 [Latest update: #13287] PipeableOSProcess class(Object)>>doesNotUnderstand: #output Receiver: PipeableOSProcess Arguments and temporary variables: aMessage: output exception: MessageNotUnderstood: PipeableOSProcess class>>output resumeValue: nil Receiver's instance variables: superclass: PipeJunction methodDict: a MethodDictionary(#addToErrorPipeline:->(PipeableOSProcess>>#addTo...etc... format: 148 instanceVariables: #('pipeFromError' 'processProxy' 'keepInitialStdOutOpen' 'ke...etc... organization: ('command pipelines - private' addToErrorPipeline: prepareOutputF...etc... subclasses: nil name: #PipeableOSProcess classPool: nil sharedPools: nil environment: a SystemDictionary(lots of globals) category: #'CommandShell-Piping' traitComposition: {} localSelectors: nil UnixProcess>>waitForCommandOutput: Receiver: a UnixProcess with pid nil Arguments and temporary variables: aCommandString: 'openssl passwd -crypt -quiet -noverify "a"' Receiver's instance variables: pid: nil sessionID: nil stdIn: nil stdOut: nil stdErr: nil processAccessor: a UnixOSProcessAccessor on pid nil allMyChildren: a Dictionary() accessProtect: a Semaphore() ppid: nil pthread: nil path: nil programName: nil arguments: nil environment: nil SHSystemLayer>>waitForProcessCommandOutput: Receiver: a SHSystemLayer Arguments and temporary variables: aString: 'openssl passwd -crypt -quiet -noverify "a"' Receiver's instance variables: osProcess: a UnixProcess with pid nil Cheers, Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st

July 26, 2011

Re: [Pharo-project] pharo ide task force - morphic issues

by Tudor Girba

Hi, On 25 Jul 2011, at 23:28, laurent laffont wrote: > Hi Doru, > > === Integrate TWM windows grouping mechanism > - I know that for it to work, it requires some changesets that need to be filed in. > - It would be great if they were integrated :) > > in 1.3 ? They have been integrated in 1.4. Great, I did not know. 1.4 should be just fine. Cheers, Doru > Laurent. > > > - See thread: > http://lists.gforge.inria.fr/pipermail/pharo-project/2011-June/050116.html > > > > > > > > > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "The coherence of a trip is given by the clearness of the goal." > > > > > > -- www.tudorgirba.com "Every thing has its own flow."

July 25, 2011

Re: [Pharo-project] A request or suggestion.

by laurent laffont

On Mon, Jul 25, 2011 at 6:06 PM, Gary Chambers <gazzaguru2(a)btinternet.com>wrote: > ** > I think I know what Friedrich means, groups of items under a single taskbar > entry (with popup shortlist). > Unfortunately there is no formal mechanism for identifying individual > windows as belonging to a a group. > > Any window can have whatever title/label it wants, models are not either > present or identical for the same "type" of window etc. > > Could introduce a "taskbar type" perhaps, maybe TWm does something similar > for grouping. > Actually in TWM windows groups are defined in TilingWM, windows protocol, based on SystemWindow model class. For example: TilingWM>>browsers ^ self windowsOfModels: #(Browser OBSystemBrowser OBCodeBrowser NautilusUI NautilusUI2 MessageListBrowser FinderUI). TilingWM>>monticellos ^ self windowsOfModels: #(MCTool MCPackageManager). We can enable "custom" groups, should be quite easy (using a pragma and / or system settings), I don't know if it's useful. Laurent. > > Regards, Gary > > ----- Original Message ----- > *From:* Patrick Barroca <patrick.barroca(a)gmail.com> > *To:* Pharo-project(a)lists.gforge.inria.fr > *Sent:* Monday, July 25, 2011 4:31 PM > *Subject:* Re: [Pharo-project] A request or suggestion. > > Hello, > > TWM stands for Tiling Windows Manager, check screencasts at the author's > blog to see it in action: > http://magaloma.blogspot.com/. > > I think it could cover you needs pretty well ;) > > > On Mon, Jul 25, 2011 at 9:50 AM, Friedrich Dominicus < > frido(a)q-software-solutions.de> wrote: > >> StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> writes: >> >> > Check the settings because you can say to the window manager that it >> should stagger or position them in another way. >> > Else have a look at TWM >> > Stef >> I tried to change the window positioning but that was not what I wanted >> to have I want in the low applicaton bar a group of Workspaces a group >> of Browsers etc. >> >> So what option are you referring to? >> >> Regards >> Friedrich >> >> -- >> Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim >> Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus >> >> > > > -- > Patrick Barroca > >

July 25, 2011

Re: [Pharo-project] [update 1.4] #14057

by StÃ©phane Ducasse

We were talking about a kind of value holder which was played by MorphicModel and that was using a kind of accessor ( asymbol) and that gary extended. And we are thinking that having a good one would be better to the accessor one. But we discovered that while cleaning slider. Stef On Jul 25, 2011, at 11:18 PM, Schwab,Wilhelm K wrote: > Are we talking about events/announcements? I ask because the Dolphin way of doing things like this is that #value: triggers events, #setValue: does not - more or less. It is a very nice system. > > Caveat emptor: Dolphin also makes a lot of use of comparison policies (identity and equality being big players, of course). I have always suspected that these arose from a need to moderate/quench what might otherwise become a recursive meltdown of events in response to non-changes. > > Bill > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Gary Chambers [gazzaguru2(a)btinternet.com] > Sent: Monday, July 25, 2011 12:08 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] [update 1.4] #14057 > > I did check. Having a single accessor (with mutation) does not cover all the > cases. Some users require *no* getter, for instance, so would be erroneous > to update in response to a change. > > Regards, Gary > > ----- Original Message ----- > From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Monday, July 25, 2011 4:36 PM > Subject: Re: [Pharo-project] [update 1.4] #14057 > > > Did you check what we did? > Because it would give us some confidence :) > > Stef > > On Jul 25, 2011, at 4:21 PM, Gary Chambers wrote: > >> Some trickyness. >> >> Use of a combined accessor vs. separate get/set selectors may cause some >> problems since less flexible. >> Users exist in Slider subclasses and DiffMorph. Plus the TEasilyThemed and >> UITheme helpers. >> >> Regards, Gary >> >> ----- Original Message ----- From: "StÃ©phane Ducasse" >> <stephane.ducasse(a)inria.fr> >> To: "pharo-project open-source Smalltalk" >> <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Friday, July 22, 2011 6:31 PM >> Subject: [Pharo-project] [update 1.4] #14057 >> >> >> 14057 >> ----- >> >> - Issue 4513: ScrollBar and MorphicModel needs cleaning. Stef and Igor >> killing tha big monster - Part two. :) >> http://code.google.com/p/pharo/issues/detail?id=4513 >> >> Gary it would be good that you check because we have two ways to to a >> perform: accessor and setValueSelector while only one would be enough. >> >> Stef and Igor >> > > > >

July 25, 2011

Re: [Pharo-project] pharo ide task force - morphic issues

by laurent laffont

Hi Doru, > === Integrate TWM windows grouping mechanism > - I know that for it to work, it requires some changesets that need to be > filed in. > - It would be great if they were integrated :) > in 1.3 ? They have been integrated in 1.4. Laurent. > - See thread: > http://lists.gforge.inria.fr/pipermail/pharo-project/2011-June/050116.html > > > > > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "The coherence of a trip is given by the clearness of the goal." > > > > > >

July 25, 2011

Re: [Pharo-project] [update 1.4] #14057

by Schwab,Wilhelm K

Are we talking about events/announcements? I ask because the Dolphin way of doing things like this is that #value: triggers events, #setValue: does not - more or less. It is a very nice system. Caveat emptor: Dolphin also makes a lot of use of comparison policies (identity and equality being big players, of course). I have always suspected that these arose from a need to moderate/quench what might otherwise become a recursive meltdown of events in response to non-changes. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Gary Chambers [gazzaguru2(a)btinternet.com] Sent: Monday, July 25, 2011 12:08 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [update 1.4] #14057 I did check. Having a single accessor (with mutation) does not cover all the cases. Some users require *no* getter, for instance, so would be erroneous to update in response to a change. Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Monday, July 25, 2011 4:36 PM Subject: Re: [Pharo-project] [update 1.4] #14057 Did you check what we did? Because it would give us some confidence :) Stef On Jul 25, 2011, at 4:21 PM, Gary Chambers wrote: > Some trickyness. > > Use of a combined accessor vs. separate get/set selectors may cause some > problems since less flexible. > Users exist in Slider subclasses and DiffMorph. Plus the TEasilyThemed and > UITheme helpers. > > Regards, Gary > > ----- Original Message ----- From: "StÃ©phane Ducasse" > <stephane.ducasse(a)inria.fr> > To: "pharo-project open-source Smalltalk" > <Pharo-project(a)lists.gforge.inria.fr> > Sent: Friday, July 22, 2011 6:31 PM > Subject: [Pharo-project] [update 1.4] #14057 > > > 14057 > ----- > > - Issue 4513: ScrollBar and MorphicModel needs cleaning. Stef and Igor > killing tha big monster - Part two. :) > http://code.google.com/p/pharo/issues/detail?id=4513 > > Gary it would be good that you check because we have two ways to to a > perform: accessor and setValueSelector while only one would be enough. > > Stef and Igor >

July 25, 2011

Re: [Pharo-project] List of next large actions

by StÃ©phane Ducasse

On Jul 25, 2011, at 10:02 PM, Luc Fabresse wrote: > > > > 2011/7/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On Jul 25, 2011, at 9:46 PM, Luc Fabresse wrote: > > > Hi Stef, > > > > - Add RBengine > > - step one add RBEngine packages > > > > what is RBEngine? > > the engine doing refactoring= > AST (for Opal :)) > Refactoring > RBModel = selection of the entities to be manipulated > RBCritics > RBASTPatternMatcher > > Yes ok, I mis-read. > I was thinking of something related to RPackge ;-) No I'm working on it :) Now one of these days we should sync and think about modules for pharo :)

July 25, 2011

Re: [Pharo-project] List of next large actions

by Luc Fabresse

2011/7/25 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On Jul 25, 2011, at 9:46 PM, Luc Fabresse wrote: > > > Hi Stef, > > > > - Add RBengine > > - step one add RBEngine packages > > > > what is RBEngine? > > the engine doing refactoring= > AST (for Opal :)) > Refactoring > RBModel = selection of the entities to be manipulated > RBCritics > RBASTPatternMatcher > Yes ok, I mis-read. I was thinking of something related to RPackge ;-) Luc > > > > > > #Luc > > > > - step two (check RPackage changes) > > > > - Add OCompletion > > > > - Add Ecompletion > > > > - Integrate SystemAnnouncer > > - step one load package > > - would be cool to convert SystemChangeNotifierTest into tests > usable for SystemAnnouncer (even if RPackage has a lot of tests). > > - step two replace SystemChangeNotifier emission > > > > - Integrate Ring > > - SystemNavigation should use Ring Objects > > - Replace Source* and MethodReference by Ring Object > > > > > > May be I missed some points but it would be good to have that in 1.4 > > > > Stef > > > > >

July 25, 2011

Re: [Pharo-project] List of next large actions

by StÃ©phane Ducasse

On Jul 25, 2011, at 9:46 PM, Luc Fabresse wrote: > Hi Stef, > > - Add RBengine > - step one add RBEngine packages > > what is RBEngine? the engine doing refactoring= AST (for Opal :)) Refactoring RBModel = selection of the entities to be manipulated RBCritics RBASTPatternMatcher > > #Luc > > - step two (check RPackage changes) > > - Add OCompletion > > - Add Ecompletion > > - Integrate SystemAnnouncer > - step one load package > - would be cool to convert SystemChangeNotifierTest into tests usable for SystemAnnouncer (even if RPackage has a lot of tests). > - step two replace SystemChangeNotifier emission > > - Integrate Ring > - SystemNavigation should use Ring Objects > - Replace Source* and MethodReference by Ring Object > > > May be I missed some points but it would be good to have that in 1.4 > > Stef >

July 25, 2011

Re: [Pharo-project] List of next large actions

by Luc Fabresse

Hi Stef, - Add RBengine > - step one add RBEngine packages > what is RBEngine? #Luc > - step two (check RPackage changes) > > - Add OCompletion > > - Add Ecompletion > > - Integrate SystemAnnouncer > - step one load package > - would be cool to convert SystemChangeNotifierTest into tests > usable for SystemAnnouncer (even if RPackage has a lot of tests). > - step two replace SystemChangeNotifier emission > > - Integrate Ring > - SystemNavigation should use Ring Objects > - Replace Source* and MethodReference by Ring Object > > > May be I missed some points but it would be good to have that in 1.4 > > Stef >

July 25, 2011