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

Re: [Pharo-project] Issue 3706 in pharo: In OB: Text in comment pane of Browser uses syntax highlighting

by pharo＠googlecode.com

Comment #21 on issue 3706 by renggli: In OB: Text in comment pane of Browser uses syntax highlighting http://code.google.com/p/pharo/issues/detail?id=3706 You have to use Shout and eCompletion from that same repository. They both had to be changed to work with the next text editors too.

March 13, 2011

Re: [Pharo-project] Issue 3815 in pharo: Filing in Class comments raises an error

by pharo＠googlecode.com

Updates: Labels: Milestone-1.2 Comment #8 on issue 3815 by ryd...(a)gmail.com: Filing in Class comments raises an error http://code.google.com/p/pharo/issues/detail?id=3815 Never the less, not being able to selectively install changes from a change set is clearly a regression from 1.1.1, and should not be pushed to 1.3

March 13, 2011

Re: [Pharo-project] [Pharo-users] Last pending things for Pharo 1.2

by Guillermo Polito

Ok, I've blessed as release the version used in pharo dev from the following Configs: ConfigurationOfPharoMorphicExtras ConfigurationOfPharoNonCore ConfigurationOfPharoSound ConfigurationOfRefactoringBrowser ConfigurationOfScriptManager ConfigurationOfShout ConfigurationOfXMLSupport ConfigurationOfOCompletion ConfigurationOfNile ConfigurationOfObjectMetaTools These ones were already blessed: ConfigurationOfAutotest ConfigurationOfProfStef ConfigurationOfXMLWriter ConfigurationOfAutomaticMethodCategorizer These one left to be blessed: ConfigurationOfOmniBrowser (I'd like not to release it until we get that last issue fixed) ConfigurationOfMemoryMonitor (Alex, can the actual version be released?) ConfigurationOfPharo (I'd like not to release it until everything is ready) On Sun, Mar 13, 2011 at 7:45 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Sun, Mar 13, 2011 at 7:19 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> >> >> On Sat, Mar 12, 2011 at 4:19 PM, Mariano Martinez Peck < >> marianopeck(a)gmail.com> wrote: >> >>> So....here is the list of things I guess are pending: >>> >>> 1) "Release" all configurations included in Pharo (this is, >>> ConfigurationOfPharo and all it dependencies). I mean, we should NOT use or >>> depend on #development versions. >>> >> >> I'll take a look at this... I had two weeks without programming, and I >> can't sleep now without doing something :P >> > > please, be my guest :) > > >> >> >>> 2) Update the one click image to use latest cog images and "pharo >>> prepared vms". There are some issues regarding this... >>> 3) Write down all the things/summary done in Pharo 1.2 >>> 5) Update SystemVersion current -->> Pharo1.2rc2 of 27 January 2011 >>> update 12340 >>> 6) Condense sources? condense changes? #cleanUpForRelease >>> >>> Cheers >>> >>> Mariano >>> >> >> >

March 13, 2011

Re: [Pharo-project] Issue 3581 in pharo: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory

by pharo＠googlecode.com

Comment #7 on issue 3581 by snoob...(a)yahoo.ie: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory http://code.google.com/p/pharo/issues/detail?id=3581 This looks like an issue with the method cache. ObjectAsMethodWrapper>>install manipulates the methodDict directly. We should change the following code in that method from self wrappedClass methodDict at: self selector put: self. to rather be self wrappedClass addSelector: self selector withMethod: self. This ensures that the method cache is flushed in Behaviour>>basicAddSelector:withMethod: See CompiledMethod>>flushCache {accessing} and Symbol>>flushCache {system primitives}

March 13, 2011

Re: [Pharo-project] Issue 1836 in pharo: Adding dedicated accessors for VM parameters

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2 Comment #12 on issue 1836 by marcus.d...(a)gmail.com: Adding dedicated accessors for VM parameters http://code.google.com/p/pharo/issues/detail?id=1836 Not for 1.2

March 13, 2011

Re: [Pharo-project] Issue 2822 in pharo: possible XMl enhancement

by pharo＠googlecode.com

Updates: Status: WontFix Comment #2 on issue 2822 by marcus.d...(a)gmail.com: possible XMl enhancement http://code.google.com/p/pharo/issues/detail?id=2822 So we close this?

March 13, 2011

Re: [Pharo-project] [COTDC] 30 - StepMessage

by laurent laffont

Not sure, but try: I'm a MorphicAlarm to force the step of the receiver at a #stepTime period. See WordState>>runLocalStepMethodsIn: Laurent. On Fri, Mar 11, 2011 at 7:14 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Today: StepMessage > > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent >

March 13, 2011

Re: [Pharo-project] Issue 3169 in pharo: Not execute Script Cmd-t in OB?

by pharo＠googlecode.com

Updates: Status: Invalid Comment #2 on issue 3169 by marcus.d...(a)gmail.com: Not execute Script Cmd-t in OB? http://code.google.com/p/pharo/issues/detail?id=3169 I close this report.

March 13, 2011

Re: [Pharo-project] Issue 3706 in pharo: In OB: Text in comment pane of Browser uses syntax highlighting

by pharo＠googlecode.com

Comment #20 on issue 3706 by guillerm...(a)gmail.com: In OB: Text in comment pane of Browser uses syntax highlighting http://code.google.com/p/pharo/issues/detail?id=3706 Now I'm trying the version of OB in lukas repo, but It seems it doesn't work with shout :(

March 13, 2011

Re: [Pharo-project] Issue 3706 in pharo: In OB: Text in comment pane of Browser uses syntax highlighting

by pharo＠googlecode.com

Comment #19 on issue 3706 by laurent....(a)gmail.com: In OB: Text in comment pane of Browser uses syntax highlighting http://code.google.com/p/pharo/issues/detail?id=3706 A rule may be that PharoCore integrators should have write access to all dependents repository used in Pharo. If someone refuse write access to Pharo integrators, then the package should not be in Pharo. So the dependent repository is not public, but confidence is here community managed and may resolve the stuck problem.

March 13, 2011